FOG::HostnameChanger Failed: Incomplete server response; got: 2; wanted: 6.

[Baite]

@Wayne-Workman - Thank you so much for helping me try to fix this out.
Just a question: what is the error “FOG::HostnameChanger Failed: Incomplete server response; got: 2; wanted: 6.”. I never saw it “gotting” 2 - so what does the 2 stand for?

[Wayne Workman]

@Baite Currently, the old client and new client can co-exist if you leave the AES encryption checkbox unchecked.

The new client is in my opinion stable enough. It has some issues with renaming a PC after joined to a Domain - so when you want to rename, you simply unjoin the domain - then manually delete the computer’s old object from AD - then have fog rename and then rejoin. this is the method I use when I don’t want to just reimage.

When I just want to reimage with a new name - I hold the power button down on the computer to turn it off - then update it’s name in FOG and delete it’s object from AD - and then tell fog to image it. But I’m compulsive like that…

[Baite]

@Wayne-Workman In my case, I always use an image WITHOUT sysprep. When the image is deployed to clients, the first thing FOG used to do is to rename the computer accordingly to the definitions and only then it was joined to the domain. Can I still use it like that?
Another thing, is the Printers Management working in the new version?

[Baite]

@Wayne-Workman
I just need a quick help (I hope). I am having trouble with Renaming computers with the legacy client since I upgraded to latestes version (git). My older version had almost a year. Now I get “FOG::HostnameChanger Failed: Incomplete server response; got: 2; wanted: 6” and “FOG::HostnameChanger Host name was not found in the database”. Now I am trying with the new client. Installed it (downloaded from Fog WebUI) but am getting error at Hostname Changer again:
--------------------------------HostnameChanger-------------------------------

02-09-2015 18:28 Client-Info Version: 0.9.4
02-09-2015 18:28 HostnameChanger Running…
02-09-2015 18:28 Middleware::Communication URL:
http://10.114.187.14/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=00:23:7D:51:86:68|0A:00:27:00:00:00||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1

02-09-2015 18:28 Middleware::Communication Response: Success
02-09-2015 18:28 Middleware::Communication URL:
http://10.114.187.14/fog/service/hostname.php?moduleid=hostnamechanger&mac=00:23:7D:51:86:68|0A:00:27:00:00:00||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1

02-09-2015 18:28 Middleware::Communication Response: Success
02-09-2015 18:28 HostnameChanger Checking Hostname
02-09-2015 18:28 HostnameChanger Renaming host to 2015-HP-nVidia
02-09-2015 18:28 HostnameChanger Unregistering computer
02-09-2015 18:28 HostnameChanger Removing host from active directory
02-09-2015 18:28 HostnameChanger ERROR: Required Domain information is missing
02-09-2015 18:28 HostnameChanger Updating registry
02-09-2015 18:28 RegistryHandler ERROR: Could not set SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerNameComputerName
02-09-2015 18:28 RegistryHandler ERROR: Impossível criar uma subchave estável sob uma chave ascendente volátil.

What might be the “Required Domain information”?

[Baite]

This post is deleted!

[Wayne Workman]

@Baite said:

@Wayne-Workman In my case, I always use an image WITHOUT sysprep. When the image is deployed to clients, the first thing FOG used to do is to rename the computer accordingly to the definitions and only then it was joined to the domain. Can I still use it like that?
Another thing, is the Printers Management working in the new version?

I’m not sure what order the client does things - but since you do not sys-prep, you should be using the early hostname changer located here:

FOG Configuration -> FOG Settings -> General Settings -> FOG_CHANGE_HOSTNAME_EARLY

That setting changes the name of the computer before it even boots up - it happens DURING imaging.

[Wayne Workman]

@Baite said:

What might be the “Required Domain information”?

get rid of the “.local” on the domain name and see what happens. Also - for troubleshooting, clear out the OU stuff too.

[Baite]

@Wayne-Workman I just removed all the values and filled them all again, and now it started working in the new client (didn’t test the legacy one).

[Wayne Workman]

@Baite Awesome. Let us know.

[Tom Elliott]

I’m going to solve this only because it seems a very particular set of information was causing the problem. While I was concerned my recent changes were the main cause, it seems they really weren’t, potentially.

I’m only solving because the problem was relatively easy to correct for.