Fog Client fails to authenticate

[Tom Elliott]

@Joseph-Hales What you did on the fogserver shouldn’t impact anything.

On the main client’s however, would you mind uninstalling and reinstalling the client to see if that helps?

[Joseph Hales]

first step I did on client was uninstalled the client then I did the mono cleanup and update then i reinstalled the client but I will try again

[Joseph Hales]

After reinstall of client I am back to the original issue of value cannot be null.

[Joseph Hales]

Also note the Reset Encryption button never appears for the host but I can add it to a group and see it there.

[Tom Elliott]

@Joseph-Hales Group’s don’t know the status, so I make that button always present.

[Joseph Hales]

Upgraded server to latest SVN today 6072 same issue as shown below.

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 12/06/2017 17:35 Client-Info Version: 0.11.12
 12/06/2017 17:35 Client-Info OS:      Windows
 12/06/2017 17:35 Middleware::Authentication Waiting for authentication timeout to pass
 12/06/2017 17:35 Middleware::Communication Download: http://10.200.10.150/fog/management/other/ssl/srvpublic.crt
 12/06/2017 17:35 Middleware::Authentication ERROR: Could not authenticate
 12/06/2017 17:35 Middleware::Authentication ERROR: Value cannot be null.
Parameter name: authority

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------

[Sebastian Roth]

@Joseph-Hales Is this still an issue? Just wondering because we seem to have other reports on this.

[JLE]

I had this exact error message - also imaging windows 10 and also first time with new client, coming from legacy. For me this worked:

Through FOG GUI:
1.) Reset encryption data
2.) Put the FQDN in WITH the .net or whatever appendage (honeygroveisd.net) <-----works but -----> (honeygroveisd) did not.
3.) Clear out the OU container fields completely and leave it blank.

I made sure these settings were mirrored both in the group settings and in the global settings. After doing all of this it no longer gave me errors.

I highly doubt all of these were necessary but I was getting desperate

[Sebastian Roth]

@JLE For this particular errors I doubt that any of your actions helped in solving this. I suspect you reinstalled and that just solved the issue. See my post here: https://forums.fogproject.org/topic/10562/active-directory-join-fails

[JLE]

@sebastian-roth Hmm. I definitely do not reinstall anything after sysprep. I run .\sysprep /generalize /oobe /unattend /shutdown and then capture. I have the fog service set to manual with recovery options set to restart it. After the images are deployed the batch file does a net start fogservice and then they join the domain.

[Joseph Hales]

@sebastian-roth I have been busy with other things and finally revisited this issue. Recreating the certificate and tokens fixed my authentication problem I may have and AD join issue but will troubleshoot further before I open a new topic on it.

[Sebastian Roth]

@Joseph-Hales Ok, thanks for reporting back on this. Will mark this solved then. Feel free to open a new post on the AD issue if you can’t figure it out yourself.