Fog Clients not joining the domain.
John L Clark
6/1/2016 12:56 PM HostnameChanger Registering host with active directory 6/1/2016 12:56 PM HostnameChanger Unknown Return Code: 1364 ------------------------------------------------------------------
Have a lab of computers and they will not join the domain after imaging
All is working now, thanks Tom
@John-L-Clark if you are not familar with GPO’s i can recommend PDQ Deploy, in free Version it’s enough to deploy simple stuff around your network.
@Joe-Schmitt All fixed.
I just wanted to make sure.
@Tom-Elliott, can you fix that? The module active file is not sensitive.
6/2/2016 11:04 AM RegistryHandler ERROR: Could not retrieve Software\Wow6432Node\FOG\Version
6/2/2016 11:04 AM RegistryHandler ERROR: Null key
6/2/2016 11:04 AM Client-Info Version:
6/2/2016 11:04 AM ClientUpdater Running…
6/2/2016 11:04 AM Middleware::Communication URL: http://192.168.101.235/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=54:27:1E:46:08:FE|08:62:66:6A:D3:62||00:00:00:00:00:00:00:E0&newService=1
6/2/2016 11:04 AM Middleware::Communication Unknown Response: Not Allowed Here
Is auto updating not functioning?
@John-L-Clark I suppose you could do a GPO to uninstall and reinstall.
ok uninstall and install of latest fog client works. Can I update all the fog clients without going to each machine?
@John-L-Clark I know what the problem is, I just don’t know how best to approach it yet.
The “reset encryption data” button is not there
I uninstalled the fog client and reinstalled the new version. This is not just one host, this is all hosts
Well it’s good to know that the security implementations are working properly.
I can download the certificate manually and then i get this error
6/2/2016 10:16 AM Client-Info Version: 0.9.12
6/2/2016 10:16 AM HostnameChanger Running…
6/2/2016 10:16 AM Middleware::Communication URL: http://192.168.101.235/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=C4:D9:87:89:1E:CB|C4:D9:87:89:1E:CC|B8:6B:23:23:94:75|C4:D9:87:89:1E:CF||00:00:00:00:00:00:00:E0&newService=1
6/2/2016 10:16 AM Middleware::Communication Unknown Response: Not Allowed Here
@John-L-Clark You should try 2 things. On that host in the fog gui, click the “reset encryption data” button and see if that fixes it.
If it does it should try to do the second thing for you, which would be updating to the latest fog client. The current version in .10.6 and you seem to have .9.12 and that error is from 5/5. So you should also check to make sure the fog service is started in
i updateded last night and now i am getting this error.
5/5/2016 2:13 PM Client-Info Version: 0.9.12
5/5/2016 2:13 PM Middleware::Communication URL: http://192.168.101.235/fog/management/other/ssl/srvpublic.crt
5/5/2016 2:13 PM Middleware::Authentication ERROR: Could not get security token
5/5/2016 2:13 PM Middleware::Authentication ERROR: Could not find file ‘C:\WINDOWS\system32\token.dat’.
5/5/2016 2:13 PM Data::RSA ERROR: Could not verify certificate is from CA
5/5/2016 2:13 PM Data::RSA ERROR: Value cannot be null.
Parameter name: certificate
5/5/2016 2:13 PM Middleware::Authentication ERROR: Could not authenticate
5/5/2016 2:13 PM Middleware::Authentication ERROR: Certificate is not from FOG CA
5/5/2016 2:13 PM Service Sleeping for 120 seconds
@John-L-Clark Group settings are not persistent to the group itself, When you apply settings via groups, those are applied not to the group but to the hosts in the group. This is one-time, however many times you do it.
The article Password Central in the wiki explains it:
The cause is the active directory settings in the group are blank and you can not change them. i will update to the latest version tonight and see how that goes.
Yes i am sorry disabled. I fixed it for now, I have to go in and clear active directory on the host and then put a check in it again and to fill in the fields and it is working now.
@John-L-Clark I don’t understand what you mean by “lock”. Does the account become disabled? Disabled/Enabled is verbatim the words used in Active Directory.
I have noticed that everytime I turn on one of the machines in the lab when it tries to join the domain it locks the AD account it uses to join the domain.