Solved FOG + Sysprep + Windows 10 1803
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.
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.
Ok i hope problem comes from my postinstall scripts.
I will try this likes yours
Thanks for runway
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 DISABLED
After disable this two settings it’s ok …
2 months to identify this !
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.