Hostnamechanger problem on new installation

[TomBagley]

Server

• FOG Version: 1.3.0 RC-8 SVN 5949
• OS: CentOS

Client

• Service Version:
• OS: 10

Description

Hi,
I recently rebuilt my Fog Server from scratch as I had an issue with quick registration and the disk space was rapidly running out.
Rebuilding has cleared up my quick reg problem however I am now having trouble with the hostname changer.

I am unsure whether it’s the same issue as described here: https://forums.fogproject.org/topic/5088/could-not-get-security-token-token-dat/9

The symptom seems similar however I am running a newer version.

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 11/10/2016 17:26 Client-Info Version: 0.9.12
 11/10/2016 17:26 Middleware::Communication URL: http://192.168.150.10/fog/management/other/ssl/srvpublic.crt
 11/10/2016 17:26 Middleware::Authentication ERROR: Could not get security token
 11/10/2016 17:26 Middleware::Authentication ERROR: Could not find file 'C:\Windows\system32\token.dat'.
 11/10/2016 17:26 Data::RSA FOG Server CA cert found
 11/10/2016 17:26 Data::RSA ERROR: Certificate validation failed
 11/10/2016 17:26 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)
 11/10/2016 17:26 Middleware::Authentication ERROR: Could not authenticate
 11/10/2016 17:26 Middleware::Authentication ERROR: Certificate is not from FOG CA
 11/10/2016 17:26 Service Sleeping for 120 seconds

This is the first machine I have tried to image. I have removed the auto-join to active directory setting in case that was affecting it but to no avail.

Let me know if you need anything else,
Tom

[Tom Elliott]

11/10/2016 17:26 Data::RSA FOG Server CA cert found
11/10/2016 17:26 Data::RSA ERROR: Certificate validation failed
11/10/2016 17:26 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)

Based on that it seems your fog server changed CA’s in between installs? Did you perform a fresh install?

[Wayne Workman]

@Tom-Elliott, yes he did:

@TomBagley said in Hostnamechanger problem on new installation:

I recently rebuilt my Fog Server from scratch

@TomBagley FYI, in the future when you do something like this, you need to follow these instructions:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server

Because you didn’t, you have to un-install and then re-install all the FOG Clients in your environment. If they are joined to the domain, you can script this. Installation arguments for the FOG Client MSI are here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options

You can uninstall via a .bat script with msiexec /x FOGService.msi or you can use the product code guid if that suites you.

All of your images that have the FOG Client installed will also need to be updated the same way, uninstall the fog client and re-install it, reboot, ensure it’s communicating properly by looking at the log, and then re-capture.

If you have a backup of your old FOG Server, we can help you restore the old certificates to the new server so you don’t have do do all of the above.

[TomBagley]

@Wayne-Workman Wow crikey thanks Wayne that makes sense I have saved those pages for future reference. My old FOG Server is just turned off I still have it in situ so any assistance restoring the certificates would be hugely helpful.

[Wayne Workman]

@TomBagley Since you have your old fog server on hand, you have saved yourself a huge amount of work. Follow the link about maintaining control of hosts when building a new server. Basically you need to get the ssl directory off of the old fog server, put it onto the new server, and re-run the installer. Then you should be good to go.

[TomBagley]

@Wayne-Workman Thanks again, will have attempt tonight / tomorrow morning and report back hopefully with good news.

[TomBagley]

@Wayne-Workman Hi Wayne,

That did the job! Thank you very much for this you may mark resolved!!

Tom