FOG + Sysprep + Windows 10 1803
-
@florent said in FOG + Sysprep + Windows 10 1803:
/mnt/win/Windows/Panther/unattend.xml
well of course you know the lower case unattend.xml is wrong, correct?
Can you post what your post install scripts look like? I’m mainly interested in the script that renames the computer.
HINT: Your english is better than mine
-
@florent said in FOG + Sysprep + Windows 10 1803:
Reboot => computer join domain correctly in the correct OU but always named is WIN-XXXXX
Just a minute. I remember reading something about this. I seem to remember it was a windows 10 feature not a bug.
-
@george1421
Sorry i don’t understand, what do you mean by :
well of course you know the lower case unattend.xml is wrong, correct?For this test, i took this post install script, just putting commands in debug mode (shell) :
#!/bin/sh # . /usr/share/fog/lib/funcs.sh hd="" getHardDisk sysproduct="" doInventory modele=$(echo $sysproduct|tr 'A-Z' 'a-z') modele=$(echo $modele|sed -e 's/ //g') # Récupération des infos du host a partir de FOG wget -q -U '' -O /tmp/hinfo.txt "${web}service/hostinfo.php?mac=$mac" chmod +x /tmp/hinfo.txt . /tmp/hinfo.txt if [ "$mode_r2" = "debug" ] ; then bash fi if [ -n "$hd" ]; then partsys=$hd'1' partdata=$hd'2' echo "* Using disk device : $hd" echo "* Partition système : $partsys" echo "* Partition de données : $partdata" if [ "$mode_r2" = "debug" ] ; then # Here i put my command for sysprep bash fi echo "=> Copy Drivers" cd /mnt/win/ if [ -e "/mnt/win/drivers" ] ; then rm -r /mnt/win/drivers fi cp -a /mnt/clonages/pilotes/${modele}/${osid}/drivers /mnt/win cd umount /mnt/win rm -f /tmp/hinfo.txt fi
-
@florent If you want FOG to do this automatically these command should be in a script that is called every time the system is imaged.
I would think YOUR post install script would look similar to my scripts here:
https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection/6I would guess that you don’t need the fog.drivers and the fog.log scripts only fog.postdownload and fog.ad scripts. Then you would update the fog.postdownload script to only call the fog.ad script.
echo "Done" debugPause # . ${postdownpath}fog.log # . ${postdownpath}fog.drivers . ${postdownpath}fog.ad umount /ntfs ;;
-
I’m currently deploying a Win10 1803 image to a computer in my office. I want to make sure I don’t speak wrong about it working like I say. I don’t deploy every day so I would to check to be sure.
-
@george1421 Yes the scripts are still working with 1803 to rename the host.
-
@george1421
Yes i added what i have in my postinstall script (remember finally not empty)
You see bad things in this ? -
@florent Not if it works you can do what ever you want. My plan was to provide people with scripts they can copy and paste into their FOG server so its easy.
-
@george1421
Ok i hope problem comes from my postinstall scripts.
I will try this likes yoursThanks for runway
-
@george1421
Hi George,
I advanced on the problem and i am very confused…
I identify problem is just after post download scripts.
I say that because in my multiple tests if i shutdown computer just after sed, cancel fog tasks and boot on Windows 10 1803 the name is correct !See screenshot of step where i ientify problem occurs :
In tests where windows computer name is correct i shutdown computer just before this screen.As i saw rubric “Changing hostname” i search in my web FOG Settings :
-FOG Client - Hostname Changer was enabled : Now DISABLED
-General Settings / Change Hostname early was enabled : Now DISABLEDAfter disable this two settings it’s ok …
2 months to identify this !
Problem solved.Very thanks for your helps and guidance to post download scripts.
I was convinced that it was coming from Windows/Sysprep.Don’t know why that did not bother Windows 10 1709.
Thanks again