FOG Client unable to rename or join domain on some laptops

[JYost]

Today I have been reimaging a stack of laptops (Lenovo T460, T470, and T480’s) and was successful for about 8 in a row without any problems. The current device (Lenovo T490) has been successfully imaged in the past, but today for some reason it is not being renamed or joined to the domain (4 failed attempts in a row). I am pre-configuring the device in the web interface (and ensuring that I have the AD information entered as well as the checkboxes to rename and join domain).
I am running FOG 1.5.8 on the server, the image has FOG client 0.11.15). We’ve had many issues in the past with devices periodically not renaming or joining the domain, but since I started to use the web interface to pre-configure the hosts and create the task things have been working much better (I used to use the DOS/Pxe boot setup previously to create the task).
I’ve attached the C:\Fog.log file for you to review as I’m not entirely sure what the error messages should be telling me. Any help would be greatly appreciated.
NOTE - the laptop has an Intel I219-V NIC, Windows 10 v.1909, Single drive.
Thanks,
John YostHE-L002107-FOG2.log

[Sebastian Roth]

@JYost You seem to have a PowerManagement task scheduled for this particular host. Found this in the logs:

------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 3/16/2020 10:45 AM Client-Info Client Version: 0.11.15
 3/16/2020 10:45 AM Client-Info Client OS:      Windows
 3/16/2020 10:45 AM Client-Info Server Version: 1.5.0
 3/16/2020 10:45 AM Middleware::Response Success
 3/16/2020 10:45 AM TaskReboot Restarting computer for task
 3/16/2020 10:45 AM Power Creating shutdown command in 60 seconds
 3/16/2020 10:45 AM Bus Emmiting message on channel: Power
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 3/16/2020 10:45 AM Client-Info Client Version: 0.11.15
 3/16/2020 10:45 AM Client-Info Client OS:      Windows
 3/16/2020 10:45 AM Client-Info Server Version: 1.5.0
 3/16/2020 10:45 AM Middleware::Response Success
 3/16/2020 10:45 AM HostnameChanger A power operation is pending, aborting module
------------------------------------------------------------------------------

Go to the FOG web UI -> hosts view -> edit this particular host -> Power Management tab and I am fairly sure you will find a reboot task scheduled there.

[JYost]

Good morning,
The section of the fog.log you are looking at is dated 3/16…if you scroll down you will see the section from Friday…which brings to mind another question…why are there still fog.log entries from back in March and then appended with the log entries from Friday?

Cheers,
John

[Sebastian Roth]

@JYost Oh well, I was too quick looking at this without noticing the first part of it being really old. Next try:

 6/5/2020 2:42:30 PM HostnameChanger Checking Hostname
 6/5/2020 2:42:30 PM HostnameChanger Renaming host to HE-L002107
 6/5/2020 2:42:30 PM HostnameChanger Joining domain
 6/5/2020 2:42:35 PM HostnameChanger Success, code =  0
 6/5/2020 2:42:35 PM Power Creating shutdown command in 60 seconds

Looks pretty good to me so far. And from then on the rest of the log shows:

 6/5/2020 2:46:22 PM HostnameChanger Checking Hostname
 6/5/2020 2:46:22 PM HostnameChanger Hostname is correct
 6/5/2020 2:46:22 PM HostnameChanger Attempting to join domain
 6/5/2020 2:46:22 PM HostnameChanger Host already joined to target domain

So I can only guess on what you mean by “not entirely sure what the error messages should be telling me”. Guess you mean these log entries:

 6/5/2020 2:38 PM Client-Info Version: 0.11.15
 6/5/2020 2:38 PM Client-Info OS:      Windows
 6/5/2020 2:38 PM Middleware::Authentication Waiting for authentication timeout to pass
 6/5/2020 2:40 PM Middleware::Communication Download: http://10.6.190.155/fog/management/other/ssl/srvpublic.crt
 6/5/2020 2:40 PM Data::RSA FOG Server CA cert found
 6/5/2020 2:40 PM Data::RSA ERROR: Certificate validation failed
 6/5/2020 2:40 PM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)
 6/5/2020 2:40 PM Middleware::Authentication ERROR: Could not authenticate
 6/5/2020 2:40 PM Middleware::Authentication ERROR: Certificate is not from FOG CA

The fog-client installed on this machine was pinned to a FOG server different to the one it is talking to right now. I suppose you switched your certificates or FOG server some time between installing this fog-client (0.11.15) and letting it talk to it now. Good news is that the fog-client figured there is an update (version 0.11.19 in the logs from then on), installed that and re-pinned to the current FOG server which essentially fixed the problem.

which brings to mind another question…why are there still fog.log entries from back in March and then appended with the log entries from Friday?

This means the fog-client on this machine (or your master??) has been running in March or the date/time of this machine was way off.