HostnameChanger Hostname is correct
-
@dolf If you are sysprepping is the client disabled on startup and then re-enabled in setup complete?
-
In addition to what Joe said,
You have to disable the fog service before capture, and create a setupcomplete.cmd file that re-enables it and turns it on, and then capture your image.
Early Hostname Changer must also be off for this to work right.
details:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep -
Ooh… Didn’t know that. My setupcomplete.cmd only deletes the unattend.xml file. I have nothing that touches the FOG Client in any way. Looks like I’ll have to change the image, then? I just installed the FOG Client without any further configuration, and it works for all PCs which were added to the FOG db last year.
-
@dolf if you can, after you update your image could you try deployments with early hostname changer both on and off? If I’m right the issues that early hostname changer had with sysprep should have been fixed.
-
@Joe-Schmitt Will do!
Any idea why it would work for the old PCs but not the new ones? It find it strange.
-
@dolf said in HostnameChanger Hostname is correct:
I just installed the FOG Client without any further configuration, and it works for all PCs which were added to the FOG db last year.
It’s a race condition. You were playing with fire and got lucky until now.
-
Thanks. Makes sense. Will fix my stuff.
-
v0.11.5 of the client prevents premature startups of the service. You will still need to disable the client before syprepping and restart the computer when sysprep is complete though (as described in the updated FOG Client wiki article).
-
In @Joe-Schmitt’s second last message, the plan was to require no modification to
setupcomplete.cmd
. But the wiki still says I have to modify it. Which instructions should I follow? -
@dolf The one marked as the answer. We keep the FOG Client article updated, because it’s important.