Active Directory Join Failing

[Wayne Workman]

@Joe-Schmitt what are your thoughts on this?

[Joe Schmitt]

@jeffscott the quickest way to see what’s going on is to do the following steps on a problematic machine:

• Open an administrative CMD, and run net stop fogservice
• Navigate to your FOG server’s web portal, select the host you are working on and perform these steps:
  • Press Reset Encryption Data if its an option
• Download our Debugger.exe and run it
• The Debugger will open a console that has a fog: prompt, please enter these commands, pressing enter after each one (replace {server-ip} with your actual FOG server IP):
  • middleware configuration server http://{server-ip}/fog
  • middleware authentication handshake
  • dump cycle save

---

The debugger should point you to a FOGCycle.txt file. This contains all the information the server tells the client, completely decrypted. Can you make sure the hostnamechanger section has the correct active directory login/OU information? You can then hopefully debug the problem better and identify what credential the client is receiving.

To clean up:

• Close the debugger
• click Reset Encryption Data again on the host in the gui
• start back up the fog service if you want

---

@Moderators feel free to copy & paste these steps for people with similair issues in the future. The steps shouldn’t change in the foreseeable future.

[jeffscott]

@joe-schmitt

OK, I performed that procedure and I can see the password that it is passing is no where near correct…

Looks like it is an encrypted version??? (I can’t even tell what one of the characters is)

[Joe Schmitt]

@Tom-Elliott it seems the server is not sending the password correct.

[Tom Elliott]

Where have you changed the Password?

[jeffscott]

@tom-elliott

2 Places:

Initially in FOG Configuration, FOG System Settings, Active Directory Defaults

&

Subsequently re-entered it in Host Management, Active Directory for the Host I’m testing with

Entering the password in the “Domain Password” Field. Leaving “Domain Password Legacy” field blank

[Tom Elliott]

@jeffscott just to clarify, you’re using the plaintext password in the non legacy password field? Maybe we can remote tomorrow so I can see what’s going on?

[jeffscott]

@tom-elliott

Hey Tom,

Sorry, I was away for a few days…

Yes, I’m using the non-legacy password field. Yes, I’d be willing to do a remote session.

Thanks,

Jeff

[jeffscott]

Hey Tom,

I’m just now coming back around to this…

Any updates on this?

Thanks,

Jeff

[Tom Elliott]

@jeffscott I’m willing whenever you’re able. Maybe this afternoon? (I’m on EDT)

[jeffscott]

@tom-elliott

Ugh…

We keep missing each other. How do you want to go about connecting?

[jeffscott]

@tom-elliott

Any chance we can revisit this?

[Sebastian Roth]

@jeffscott Hey, I hope you are still around in the forums. I just looked into an issue that sounds very similar to what you have. See here: https://forums.fogproject.org/topic/12407/active-direcory-join-fail-bad-password-1-5-4

Just found your post here by accident and thought this might be along the same lines. Can you confirm your password starts with a special character that might cause this issue?! I really hope to figure this out but I’m still unable to replicate the issue from the information I have so far.

[x23piracy]

@Sebastian-Roth FYI, i am using 1.5.4 with a ad join password starting with % (percent sign) in production.

[Sebastian Roth]

@x23piracy Thanks, that’s good to know. Although I guess it might be that $ special case causing the issue for the other users as it is used for variables in PHP, as line end in regular expressions such things.