AD Join/Rename on client .0.8.1

[Bill Rice]

It appears that with new client the AD join feature is not functioning. there is an error stating something (im no longer at work to see the log exactly) to the effect of missing AD information so its not attempting to join the Active Directory. otherwise the NEW Client works as Described! Awesome…

Old Clients V.032 and .0.7.x to .0.8.0 will need to be manually removed prior to installing .0.8.1 I’m looking in to a way to use GPO to remove the legacy version and possibly to remove the directories/fog reg entry for the newer client version so that i can push out the msi with command line aurguments for silent install in the back ground.
If anyone has figured a way to do this easily in an AD enviroment let me know just message me please

Bit of Info about the Fog as a CA…
Must install client with the IP address of the FOG Server instead of the DNS name since the cert authority ties to the ip address when it dish’s the cert out to the client.

[jamesb]

The issue that I’m getting with 0.8.1 for the AD join is “Required Domain Joining information is missing”. I also ran the debugger and is see’s the correct domain join information, but it still gives me the error. I’m currently on SVN 3384.

[SlimJim]

@Jbob

I got anxious and ran the debugger.exe and the AD settings were correct and it gave the same error Required Domain Joining information is missing.

[SlimJim]

@Jbob

Awesome, give me 5 mins n I’ll let ya know

[SlimJim]

@Jbob

Now I get Authentication > CommunicationHandler Response: Invalid Security Token after I restarted the fog service.

[Joe Schmitt]

Did you press the “Reset Encryption Data” button?

[Joe Schmitt]

Fixed and v0.8.2 released

[Wayne Workman]

I’ll try it tomorrow.