Computer name being overwritten by image rather than fog database
-
Do I need to install the service on the hosts or just activate it on the server. Do the laptops need to be still connected to fog on first boot for this to happen?
-
the service is typically installed before you create the image, so all hosts will have it installed. on first boot, the service will attempt to check in with the fog server over http to check if the computer has the correct name on every boot.
-
This is my problem, once the device has restarted post imaging, it usually gets unplugged and sent out to site so doesn’t see the fog server until it next gets imaged.
-
Hostname changer is quick it only needs to be up for a few mins before it renames itself and restarts itself again.
-
i’m tracking down why the early hostname change isn’t working and trying to create a fix. you’ll need to update your server to get it when it’s finished.
-
Ok, thank you a million. I have just run another test, manually changed the computer name to 12345 and post imaging it has become the same as the master image computer name.
-
[quote=“Junkhacker, post: 44558, member: 21583”]i’m tracking down why the early hostname change isn’t working and trying to create a fix. you’ll need to update your server to get it when it’s finished.[/quote]
From what it sounds like (to me, anyways) is that the hostname changer (immediately after imaging completes) is looking to change the name on the C:\ partition, where Windows core files are normally located.
Chris Shanks said he changed the location to E:.
I think FOG is just trying in the wrong place…
-
Sort of, the core windows registry files where the computer name is stored are still saved on the C drive however I have made a different partition the “active” partition to allow the advanced repair options available when F8 is pressed during boot.
However the pc still boots from the C drive and I would like the computer name on the same drive to match the ID on fog rather than the master image.
-
If the image is sysprepped, this may explain the hostname not reflecting directly after imaging completes. It’s taking the information of the unattend file (if used) or generating a random one, or awaiting entry of one as the system loads up the first time.
-
I don’t use sysprep or any other file/system. Up to this point fog has just worked ( as it’s so well built
) and the computer name has been changed to reflect the host name from the server. -
i am currently testing what i suspect to not be working
