New to Fog.... A little help with hostname changer and Join AD

[SlimJim]

Hello all,

So, I’m new to fog and I’m using Ubuntu 12.04LS, fog rv3480, and the newest fog client service 0.7.4 which is set to Automatically start up. I’m having some trouble getting the hostname changer and Join AD to work and I don’t really know where to start troubleshoot as I’m not sure if I have set this all up correctly. The only logs I’m aware of are on the client located in C:\ and C:\Users*user*\ , oh and obviously the log in fog settings. I’ve dug through the event viewer on the client and haven’t really found anything to suggest it’s even trying to change the name, the only thing that sticks out is “CommunicationHandler Response: Invalid host certificate” in the fog log. I apologize if this has been answered a million different times, but I have looked through the forums, just haven’t found anything relevant to this error.

I’m guessing I haven’t set something up correctly and I could really use some assistance.

Thanks in Advance,

James

[SlimJim]

Also, the machine I captured the image from was sysprepped and fogprepped and answer file has * for computer name, not sure if that makes a difference, but a post I read suggested it may.

[Tom Elliott]

Problem with the hostname changer is that 3480 does not generate the srvpublic.key file 0.7.4 is looking for. This is somewhat intentional as it, too, was extremely insecure. We’re now generating our own certificate authority and signing a certificate based on the CA.

[SlimJim]

@Tom-Elliott

Tom,

Thanks for the quick reply. What would you suggest to get this working, should I downgrade to a working svn or use the legacy client or generate my own keys?

Thanks,

James

[Wayne Workman]

@Tom-Elliott said:

Please try these commands:

sudo rm -rf /opt/fog/snapins/CA /opt/fog/snapins/SSL /var/www/fog/management/other/ssl

Edit the installer updater piece in /opt/fog/.fogsettings and delete the last two lines of the file:

They should look like:

caCreated="yes" and maybe vhostCreated="yes"

if you don’t have those lines then don’t worry about it.

Then try re-running the installer.

[Tom Elliott]

I think you should uninstall the fog client, and re-install from the client loactions. Basically you have to re-download the new client and install it.

[SlimJim]

This post is deleted!

[SlimJim]

This post is deleted!

[SlimJim]

@Wayne-Workman

I’ve tried completely removing the fog service and reinstalling and I keep getting the same errors in fog.log:

Invalid host certificate
URL: http://myfogserver/fog/management/other/ssl/srvpublic.crt
ERROR: Could not download file
ERROR: The remote server returned an error: 404 not found
ERROR: Could not get security token
ERROR: Could not find file C:\Windows\system32\token.dat
ERROR: Could not authenticate
ERROR: The system cannot find the file specified

Was the CA and ssl supposed to be recreated? Any further suggestions before I go digging?

Thanks so much for all your help!!

[Tom Elliott]

Can you rerun the fog installer with:

sudo ./installfog.sh --recreate-CA --recreate-keys

[Joe Schmitt]

Just a heads up, you installed the beta client.And the specific version you install won’t work with hostname changer. I’d either switch to the legacy client OR wait until I fix v0.8.0 of the beta.

[SlimJim]

@Jbob

Ah… Yes, I realized it was a new version 0.8.0, but didn’t realize it was beta. Thanks for the heads up.

[SlimJim]

@Tom-Elliott

Logs after rerun:

5/27/2015 12:15 PM CommunicationHandler Response: Invalid host certificate
5/27/2015 12:15 PM CommunicationHandler URL: http://myfogserver/fog/management/other/ssl/srvpublic.crt
5/27/2015 12:15 PM CommunicationHandler ERROR: Could not get security token
5/27/2015 12:15 PM CommunicationHandler ERROR: Could not find file ‘C:\Windows\system32\token.dat’.
5/27/2015 12:15 PM EncryptionHandler CA cert found
5/27/2015 12:15 PM EncryptionHandler ERROR: Certificate validation failed
5/27/2015 12:15 PM EncryptionHandler ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)
5/27/2015 12:15 PM CommunicationHandler ERROR: Could not authenticate
5/27/2015 12:15 PM CommunicationHandler ERROR: Certificate is not from FOG CA
5/27/2015 12:15 PM CommunicationHandler URL: http://myfogserver/fog/management/other/ssl/srvpublic/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=00:21:70:0A:9A:A2||00:00:00:00:00:00:00:E0&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&new

[Joe Schmitt]

I’ll re-iterate my message. I’d wait until we fix v0.8.0

[SlimJim]

@Jbob

Lol, I know, I just figured Tom wanted the logs and I was already in the middle of rerunning the installer when you commented. Just finished the legacy client installer.

Thanks,

James

[SlimJim]

@Tom-Elliott

With the legacy client, I’m not getting:

HostnameChanger Failed: Incomplete server response; got 7; wanted: 6
HostnameChanger: Host name was not found in the database

Thanks,

James

[Tom Elliott]

Did you set the “product-key” field on the host?

[SlimJim]

@Tom-Elliott

Yes, that was it!!! Again, thank you guys so much for all your help and hard work!!!

James

[SlimJim]

@Jbob

Sorry to bother, just a quick question for ya, is the domain join working in 0.8.1?

[Wayne Workman]

@James-Harting said:

@Jbob

Sorry to bother, just a quick question for ya, is the domain join working in 0.8.1?

Yes and No.

I am still having issues with it… but that doesn’t mean you’ll have issues.