Thanks for your prompt reply Tom and Wayne. I am by no means aggrivatged by the feature and certainly don’t consider it a bad thing.

I was simply curious as to where this setting was set within the FOG config and how it is performing the change.

I will definitely keep it enabled as it takes one step out of the deployment process for us, nice work!

Are you able to share how FOG performs this rename injection into Windows after the image has been deployed?

For those that may come across this post the setting is under FOG Configruation - FOG Settings - General Settings, then FOG_CHANGE_HOSTNAME_EARLY.

Thanks again

We recently upgraded from .32 to 1.2.0 and have noticed since then it seems FOG is somehow renaming the Windows hostname to whatever the machine has been registered as in fog.

We do not use the FOG service, it is not installed to any machines.

We have a Windows 10 image captured in “audit mode”, we deploy it to a host registered as PC-123. Upon booting the deployed PC, its Windows hostname is PC-123. If I rename the same host within FOG to PC-456, then deploy the same image, Windows has a hostname of PC-456.

How/why is this happening!?