FOG::HostnameChanger Failed: Incomplete server response; got: 2; wanted: 6.
-
@Wayne-Workman I just uninstalled the client (yes, I used one from a USB pen - but I thought the legacy client was not changed), rebooted and then instaled the one I got from Fog Server.
Rebooted three times.
Still nothing.The client IS NOT currently bound to a domain.
In the boot menu, the name appears correctly (with the message saying it is regiistered with the new name), but the computer (Windows 7 Enterprise x64) still has the old name and this message.
-
@Baite Make sure the host’s Service Settings in the web UI are all checked. When installing the client on the host - make sure during installation that all the service settings are checked.
And a copy of the c:\fog.log file would be helpful - it gets rewrote every boot so - give us a copy with some errors in it.
-
Oh and what OS is the target host running? Is it possible that antivirus might be interfering?
-
@Wayne-Workman I made what you asked for. All Service Settings were checked, either in the UI and during the installation.
Then I tried something else. Went to Web UI for that host and, in the AD Aettings, pressed the Clear Fields button and then the Update button. Then restarted the client. Still nothing happened.
Went again to the web UI for that host, checked the “Join Domain after image task” checkbox so that the domain textboxes got filled with the default settings and then unchecek the “Join Domain after image task” checkbox. Clicked the update button and restarted the client again.
Then I got some strange info in the log (need to update some client dll).
02-09-2015 17:00 FOG::ClientUpdater File: TaskReboot.dll requires an update.
02-09-2015 17:00 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\TaskReboot.dll hash doesn’t match server hash!
02-09-2015 17:00 FOG::ClientUpdater Checking Status : UserCleanup.dll
02-09-2015 17:00 FOG::ClientUpdater File: UserCleanup.dll requires an update.
02-09-2015 17:00 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\UserCleanup.dll hash doesn’t match server hash!
02-09-2015 17:00 FOG::ClientUpdater Checking Status : UserTracker.dll
02-09-2015 17:00 FOG::ClientUpdater File: UserTracker.dll requires an update.
02-09-2015 17:00 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\UserTracker.dll hash doesn’t match server hash!
02-09-2015 17:00 FOG::ClientUpdater Checking Status : config.ini
02-09-2015 17:00 FOG::ClientUpdater File: config.ini requires an update.
02-09-2015 17:00 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\config.ini hash doesn’t match server hash!
02-09-2015 17:00 FOG::ClientUpdater 1 new modules found!
02-09-2015 17:00 FOG::ClientUpdater Checking Status :
02-09-2015 17:00 FOG::ClientUpdater File: requires an update.
02-09-2015 17:00 FOG::ClientUpdater Excepção durante um pedido WebClient.
02-09-2015 17:00 FOG::ClientUpdater em System.Net.WebClient.DownloadFile(Uri address, String fileName)
em FOG.SnapinClient.downloadAndDeploy(String localFile)
02-09-2015 17:00 FOG::ClientUpdater Client update will be applied during next service startup.
02-09-2015 17:00 FOG::ClientUpdater Client update process complete, exiting…
02-09-2015 17:05 FOG::SnapinClient Attempting to connect to fog server…
02-09-2015 17:05 FOG::SnapinClient Module is active…
02-09-2015 17:05 FOG::SnapinClient No Tasks found for: 00:23:7D:51:86:68|0A:00:27:00:00:00Restarted the client again. New error in fog.log:
02-09-2015 17:17 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\config.ini hash doesn’t match server hash!Here are 4 versions of fog.ini
-
@Wayne-Workman It’s running Windows 7 Enterprise x64 with System Center Endpoint Protection.
All was working fine before upgrading to latest version.
One question: should I try to use the new client? Is it stable enough? Can I have some hosts (older) with the legacy client and all the new with the up-to-date client?
-
@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? -
@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… -
@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? -
@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=102-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=102-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”?
-
This post is deleted! -
@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.
-
@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.
-
@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).
-
@Baite Awesome. Let us know.
-
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.
