Hostname Changer No Reboot
-
I think there is an option to change the hostname during the imaging process… look in FOG Configuration -> Fog Settings - it’s somewhere in there.
And I think you can turn off the hostname changer service that the client uses from within the Host Management menu. I think it’s under service settings.
-
That is amazing!
I will try it on Friday, then I post here the result.
Thanks! -
I believe you will need to upgrade to SVN for that feature but its pretty stable now.
-
Sorry, what is SVN?
-
@Bruno-Nogueira said:
Sorry, what is SVN?
SVN is an abbreviation for Subversion. Subversion is a utility that many fog users use to retrieve the latest developmental revision of FOG Trunk.
Read more here on getting FOG Trunk: https://wiki.fogproject.org/wiki/index.php/SVN
-
@Wayne-Workman said:
I think there is an option to change the hostname during the imaging process… look in FOG Configuration -> Fog Settings - it’s somewhere in there.
And I think you can turn off the hostname changer service that the client uses from within the Host Management menu. I think it’s under service settings.
Hi again, I found something really weird, I have 3 images on the server (img1, img2, img3) and when I deploy the image 3 the hostname change without fog client (Tried in the same computer), when I deploy the images 1 and 2 the hostname needs client to change.
How can I allow all images to change the host without fog client?
thanks -
@Bruno-Nogueira You’re using FOG Trunk? What revision number? (look at the number in the cloud, top left).
-
@Wayne-Workman
I’m using fog 1.2.0 -
I’m not entirely positive that 1.2.0 supports hostname changing during imaging…
However, in current FOG Trunk, the setting to enable that is here:
FOG Configuration -> FOG Settings -> General Settings -> FOG_CHANGE_HOSTNAME_EARLY -
@Wayne-Workman I have that option here too and it is enabled, if the hostname changes on one image it have to be something about image configuration.
-
Maybe build a new scratch image and try?
-
@Wayne-Workman I’ve created a new image today and I will deploy it next week, then I say here if it change the hostname.
Thanks -
It’s probably noteworthy to say that you should absolutely NOT take an image from computers that are bound to an Active Directory domain…
It’d probably screw up the hostname changing… and it’d definitely screw up the trust relationship between your DCs (domain controllers) and the deployed client images…
-
@Wayne-Workman We doesn’t have any image with Active Directory active, it is just normal Windows PCs
-
@Wayne-Workman Hi, I’ve done a new deploy and the hostname doesn’t change after imaging, but after it fog try to change it (* Changing hostname…Done) so it have to be something about the Windows Image that by some reason its not changing the registry.
What is the commands fog use to change it?
Can this happen because of permissions?
Thanks!! -
@Bruno-Nogueira The only thing that I can think that is not allowing the hostname to change is your image is sysprepped, but setup for OOBE mode which requires the user to create a username and hostname.
-
Maybe I found part of my solution here:
https://forums.fogproject.org/topic/3361/early-hostname-change-not-working-win7/19My image that change the hostname only have 1 partition (not counting with small windows partitions).
But the image that’s not changing the hostname have 2 partitions and maybe it is applying hostname configuration in the last partition (only data) and not on Windows partition.
I’ve tried to config my server with the steps in the link but my fog.download its a little diffrent and some commands like “xz --decompress init.xz” doesn’t work.
-
@Tom-Elliott My image is just a normal machine clone, ready to use but not OOBE (the first start is a normal windows startup with all users and everything on it).
Do you think that update to SVN fix the problem? -
I need help!
-
@Bruno-Nogueira said:
I need help!
Please look at this thread: https://forums.fogproject.org/topic/3361/early-hostname-change-not-working-win7
That person was using FOG 1.1.2 (I imagine it’s probably fairly similar to 1.2.0). They reported that the early hostname changer only tried to change the name on the last partition restored.
How many partitions does your image have?
You said you were installing “TimeFreeze” or activating it or turning it on or something. If this is “hard drive locking” software, I have some experience with this. In the case of Centurion Technologies Smart Shield and Faronics DEEP FREEZE, both of these create a “unfrozen/unlocked” partition.
If this is the case with “TimeFreeze”, then this might be why you’re experiencing these issues with the early hostname changer…
Just a guess…