Computer Name not changing to Host Name

[michIGY]

Deploying a windows 10 1809 image, and even after multiple restarts, the name of the computer does not change to match the hostname applied in FOG

What can I do to make the computer name match the host name

[Tom Elliott]

Does the machine have the FOG Client installed on it?
What version of FOG are you using?

[michIGY]

Machines are getting FOG client as part of the image.

(installed before image is captured)

Running FOG 1.5.4

I even have snapins deploying and set a reboot after the first one in hopes it would trigger the name change

Edit: Does this have anything to do with it?

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

The machines are being sysprep’d after FOGClient is installed - but they deploy fine without the error and on the deployed machine I see FOGService running

Edit 2: Upgraded to 1.5.5

Edit 3:

Hostname Changer Enabled?
Hostname Changer Enabled as default?

Are both enabled

[Sebastian Roth]

@michIGY Please check the fog-client log file on the host machine. Hopefully this will shed a light on what’s going on.

Not sure if we have many people with win10 1809 using the fog-client yet.

[michIGY]

obstructed fog.log attached

https://pastebin.com/G8sESew1

When I checked it yesterday I was getting a lot of

Middleware::Response ERROR: Unable to get subsection
Middleware::Response ERROR: Object reference not set to an instance of an object.

Now it seems to be

Middleware::Response Success
HostnameChanger Users still logged in and enforce is disabled, delaying any further actions

My Unattend file has two autologons as part of its process - does the host name not change while the user (a local admin) is signed in?

Edit: Trying this process, hopefully it works. https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

In the process of capturing the sysprep’d image now

Edit2: Looks like this did not solve the problem

EDIT 3: Got it working! I had conflicting rules for my domain join (probably among other things), because of that it didn’t the host because of the domain enforcing rules not getting applied at all

[Sebastian Roth]

@michIGY said in Computer Name not changing to Host Name:

HostnameChanger Users still logged in and enforce is disabled, delaying any further actions

Good you got it to work but if you ever see this again you can set an option in the FOG web UI to force even if a user is logged on.

If you see “Response Invalid security token” again you might want to try “Reset Encryption Data” in the host’s settings in the web UI.

[michIGY]

@Sebastian-Roth

Where is the setting to set hostname even if a user is logged in?

I was looking for it and stumbled upon my AD settings which is what I ended up fixing instead that fixed the issue.