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

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:

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.

SlimJim

@Wayne-Workman

Thanks for the reply, I will test it out.

SlimJim

@Wayne-Workman

Were you receiving any errors when it fails or was it just failing? Wondering because I’m trying to figure out if I’m missing something in my configuration? Any input would be greatly appreciated.

5/27/2015 4:25 PM Client-Info Version: 0.8.1
5/27/2015 4:25 PM HostnameChanger Running…
5/27/2015 4:25 PM CommunicationHandler URL: http://myfogserver/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=00:21:70:0A:9A:A2||00:00:00:00:00:00:00:E0&newService=1
5/27/2015 4:25 PM CommunicationHandler Response: Success
5/27/2015 4:25 PM CommunicationHandler URL: http://myfogserver/fog/service/hostname.php?moduleid=hostnamechanger&mac=00:21:70:0A:9A:A2||00:00:00:00:00:00:00:E0&newService=1
5/27/2015 4:25 PM EncryptionHandler ed2873a80337d19b5e9f9abb590a2c1b|b6a75e03e6ca4d22ce9f0c73338cc30845c800d3384a6fd1a6fdb1e8a6b8673a6c86a6e02eb8a495616a0ba02393749769b381010dfffc83b807bbdafe1d6d40b851a33a2b1a44fc55ae4d4ac6e11ff2d92c7eaa0bb797ce3947bfa870aad3fe244a17144fd1ec39894e94ce5fdc2ce40919b32e833f42a9ebace41cef494da5d424ddae4afa1f3dbd2165bb120be805d3c93a6aeb51a6cc8079b881e43f886a
5/27/2015 4:25 PM CommunicationHandler Response: Success
5/27/2015 4:25 PM HostnameChanger Checking Hostname
5/27/2015 4:25 PM HostnameChanger Hostname is correct
5/27/2015 4:25 PM HostnameChanger Registering host with active directory
5/27/2015 4:25 PM HostnameChanger ERROR: Required Domain Joining information is missing
5/27/2015 4:25 PM HostnameChanger Activing host with product key
5/27/2015 4:25 PM HostnameChanger ERROR: Windows activation disabled

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

184

12.1k

17.3k

155.4k