Client does not communicate with Fog server

[Lemeunier]

Fog server : 1.5 on ubuntu 16.04 X64
Client : Windows 7 Pro X64

Hi,

I’ve change a couple of day my workstation from an old intel processor to a ryzen platform.
I had to reinstall all from the begining and recreate the fog server (in a Virtual Machine).

Obviously, the client does not communicate with the new server…
Is there a way to make them communicate again without reinstalling the client on all hosts ?

Thanks

[george1421]

@lemeunier take/move the ssl certificate from the old fog server and insert it in the new fog server, then reboot the fog server. The first time a fog client reaches the fog server it is tattooed to the fog server’s certificate.

/var/www/html/fog/management/other/ssl

[Lemeunier]

@george1421 I moved the file /var/www/fog/management/other/ssl/srvpublic.crt to the new server but it seems to not respond even after a reboot. I mean, the power managment and AD join does’nt work.

There are some others files in /var/www/fog/management/other/ , Do i need to move them too ?

[Joe Schmitt]

@lemeunier see this article for how to keep control of your clients:

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server

[Lemeunier]

@joe-schmitt Thanks. I was hopefull on this but it didn’t worked. Even worse, i cannot communucate with the client that is given with the 1.5.2 version since i’ve backed up the certificats (/opt/fog/snapins/ssl).
My old server was based on a ubuntu 17.04 (netinstall, that is not supported anymore), i tried to use the version 17.10 (netinstall) but i’ve got an error with the deployment. So i tried to use a 16.10 version but there the problems start :

• can’t use the old certificats because its not communicate
• new client won’t work anyway…

Is that because i’ve downgraded the ubuntu version ? Is there a fix of fog (kernel maybe) on the way for ubuntu 17.10 (or 18.04) ?

Thanks for all you do !

[Joe Schmitt]

@Lemeunier I don’t have time for a detailed response at the moment, but I would recommend you look at: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server

Edit: I just realized I already posted this link earlier, sorry for the duplicate

[Lemeunier]

@joe-schmitt Tkx…

[Lemeunier]

@joe-schmitt I resolve my issue with a backup of my old VM disk. I upgraded the distribution to 17.10 (18.04 stuck at curl installation) without removing the old kernels. It was working fine since a couple of day since this evening, the web UI is no more accessible. When i try to ./installfog.sh again the installation stuck at :

* ensuring node username and passwords match..........

Did you ever see that ?

EDIT: proxy problem… same as here

[Lemeunier]

I’ve got a new issue just only with the AD join function… Here in the fog log :

03/05/2018 20:49 HostnameChanger Logon failure: unknown username or bad password, code =  1326

I havn’t change anything about the acount for joining the domain… Is there a new way to configure that ?

EDIT: a server update has desactivated the fog acount (for modifying the password)… Problem solved