@tom-elliott

Any chance we can revisit this?

@tom-elliott

Ugh…

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

Hey Tom,

I’m just now coming back around to this…

Any updates on this?

Thanks,

Jeff

@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

@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

@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)

@wayne-workman

Yes, I’ve tried that several times. Even tried using the Domain Admin…

Well, I upgraded to v1.5.2 and I’m still getting the same problem. I manually joined one client using the same credentials I have configured in FOG just to confirm my sanity in that I had the correct username/password and it was successful.

Account is getting locked out on the Domain so I still know it is passing the correct username… Evidently, it is not passing the correct password…

Hello all,

Can’t seem to get my clients to join AD…

FOG Server Version: 1.5.0-RC-13
FOG Client Version: 0.11.15 (Upgraded after having same problems with 0.11.14 that came with 1.5.0-RC-13)
Host is Windows 10 1709 Education Edition

FOG Active Directory Tab for Host:

Domain Name: domain.lan
Org Unit: blank
Domain Username: SF
Domain Password: Entered and manually confirmed correct
Domain Password Legacy: Left Blank (However, I tried by using FOGCrypt on that as well, no luck)

FOG.log on host is showing:

HostnameChanger Logon failure: unknown username or bad password, code = 1326

SF account is getting locked on domain. And Security Event Log on DC is showing bad password. (So at least I know the FOG Client is passing the correct username)

Any ideas?

Thanks,

Jeff