@Tom-Elliott
Hi Tom,
BR
Klaus
Hi,
I need a little help. We created a PXE Menu Entry for the Crowdstrike Fix (https://techcommunity.microsoft.com/t5/intune-customer-success/new-recovery-tool-to-help-with-crowdstrike-issue-impacting/ba-p/4196959) and set this to default. It works perfectly and we fixed many clients in a short periode, but all clients are booting to the pxe-menu until we remove the default value from the settings.
Is it possible to make a advanced task to boot to a pxe-menu entry ? I looked at the kernel files and I didn’t find a mode or option value to boot to a pxe-menu entry.
BR
Klaus
Fog 1.5.5
bzImage Version: 4.19.1
bzImage32 Version: 4.19.1
Hi,
If I perform a full host registration in the fog menu in pxe and associate a host to a group, the ad-entries of the group will overwrite if I answer the question “Join to AD” with N!
Please let me know, If there is a bugfix available.
Best regards
Klaus
@tom: Thank you for your answer. Below you find parts of my postdownload-scripts.
@George: Thank you also. I use curl request for checking the installation (for security - I have modified some values for this post).
Example:http://{$fogip}/fog/service/computerinfo.php?mac=b0:0c:d1:53:e2:7b
hostdesc="b00cd153e27b"
imageosid="9"
imagepath="IMG_NAME"
hostusead="1"
hostaddomain="DOMAIN"
hostadou="OU"
hostaduser="AUTOLOGON_USER"
hostadpass="AUTOLOGON_PASS"
hostproductkey=""
primaryuser=""
othertag=""
othertag1=""
sysman="HP"
sysproduct="HP EliteDesk 800 G4 DM 35W"
sysserial="8CC9033P2X"
mbman="HP"
mbserial="PGVXV0D8JBTTZG"
mbasset=""
mbproductname="83E2"
caseman="HP"
caseserial="8CC9033P2X"
caseasset="8CC9033P2X"
First - I need the $osid, because Driverpacks are different in Windows Builds:
As an example for HP-Driverpacks see: http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html
The Packs are different for each Windows-Build on such devices … with no declaration, I have to copy all Drivers (that costs much time! ) and have to seperate it in the FirstLogonCommand-Script.
#Get Informations from Hardware
BiosVersion=`dmidecode -s bios-version`
Manufacturer=`dmidecode -s system-manufacturer | sed 's/ /./g'`
ComputerType=`dmidecode -s system-product-name | sed 's/ /./g'`
SerialNumber=`dmidecode -s system-serial-number | sed 's/ /./g'`
BiosDate=`dmidecode -s bios-release-date`
# Copy Device-Drivers to force-install with pnputil - the image has always the newest drivers:
rsync -a --delete --exclude='@eaDir' /images/Drivers/$Manufacturer/$ComputerType/$osid/* /ntfs/Tools/Drivers > /dev/null 2>&1
#Copy newest Bios-Release:
rsync -a --delete --exclude='@eaDir' /images/BIOS/$Manufacturer/$ComputerType/* /ntfs/Tools/Bios > /dev/null 2>&1
#Copy Hotfixes for Windows Builds and install it with Powershell to have the newest hotfixes:
rsync -a --delete --exclude='@eaDir' /images/Hotfixes/$osid /ntfs/Tools/Hotfixes > /dev/null 2>&1
#Copy the SXS Folder of the Windows Build:
rsync -a --delete --exclude='@eaDir' /images/SXS/$osid/* /ntfs/Tools > /dev/null 2>&1
Also I need it for the KMS-Key in the unattend - an example for you, how I will do it:
# Update unattend
if [ $adon = 1 ]
then
unattend=/ntfs/Windows/Panther/Unattend/unattend.xml
cp /images/unattend.xml $unattend > /dev/null 2>&1
# KMS Keys: https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys
KMSKEY_LTSB:DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ
KMSKEY_LTSC:M7XTQ-FN8P6-TTKYV-9D4CC-J462D
KMSKEY_W10:NPPR9-FWDCX-D2C8J-H872K-2YT43
IF [[ $osid -eq 10 ]]; then kmskey=$KMSKEY_W10 fi
IF [[ $osid -eq 101 ]]; then kmskey=$KMSKEY_LTSB fi
IF [[ $osid -eq 102 ]]; then kmskey=$KMSKEY_LTSC fi
dots "Set KMS-KEY in unattend.xml"
sed -i \
-e "/ProductKey/s/*/$kmskey/g" $unattend >/dev/null 2>&1
if [[ ! $? -eq 0 ]]; then
echo "Failed"
handleError "Failed to update unattend file"
fi
echo "done"
fi
Without KMS-Key Defination in unattend, I have to activate Windows in the FirstLogonCommand, that costs also more time or have to define it for each $imgid (If new images will added, the script has to be update).
I know, Hotfixes and Drivers should be in the image, but we use more than 30 Images! The problem today is, that many vendors update the drivers once a quater (with microsoft updates).
@george1421 : Thank you for your fast answer. I think you didn’t understand me.
I use fog for years and read many posts and inspect the fos files on github. Postinit and postdownload scripts are not the problem. I mount the ntfs, copy drivers, software, bios, startup-scripts for Windows - all nop.
Also i generate unattend.xml with domain-join credentials and set autologon from the fog database (I use the aduser and adpass fields)- it works perfectly.
My problem:
I will not use the $imgid variable for selecting the correct settings in the script fog.createunattend.
Why:
If I work with 5 Images with Windows 10 LTSB, 2 Images with Windows 10 LTSC (new Images) and 3 Images with Windows 10 1809, with $imgid in the script, I need to definate 10 KMS-Key-Declarations in the bash-script.
With $osid it would be 3. Fog offers me only today 1$osid for Windows 10.
Bigger problem: If new Images will added, I have to change the postdownload-bash-script to place the correct settings.
So multiple Windows 10 $osid Variables would be nice in future.
Do you have an other resolution for this problem ?
@george1421 said in NEW osName for Windows 10 Builds:
What is your real goal here? I have a complex domain structure in my company so I don’t use FOG to connect the target computer to AD, but instead use the unattend.xml file with some post install scripts to calculate the target OU, then update the unattend.xml file before WinSetup runs. What are you trying to accomplish here?
Hi George, thank you for your answer.
My Situation: We use 5 Fog Server with more than 30 Images and different os (Win7, Win8.1 and Win10 different builds). The goal is to integrate all images into 1 new FOG System.
To do this, I have to seperate in unattend.xml:
Actually I use different unattend.xml files.
Also I have to split drivers and ms-hotfixes for the differnt os and builds.
I will not do this with $ImageID in FOS. $OsID would be the best way I think.
Best regards
Klaus
I use FOG 1.5.4 and generate unattend.xml for Windows Setup and Domainjoin automatically . To seperate the unattend.xml for different Windows 10 Builds I added in the Database:
±-----±----------------±----------------+
| osID | osName | osDescription |
±-----±----------------±----------------+
| 51 | Chromium OS | Chromium OS |
| 100 | W10_LTSC | Windows 10 LTSC |
| 101 | W10_LTSB | Windows 10 LTSB |
| 102 | W10_1703 | Windows 10 1703 |
At ID 102 I got the error “invalid OS_ID”. Is there a check in the System ?
I couldn’t find a database-schema or system values to resolve the error.
Best regards
Klaus