Hybrid Configuration Wizard being Stupid

[Jonah]

Hi all,

 

Desperately hoping someone can help as I'm tearing my hear out with this! We have a seemingly very odd issue when trying to run the Office 365 Hybrid Configuration Wizard...

 

It fires up fine, finds the appropriate Exchange server and then gets to the credential page for the Exchange box and Office 365, and this is where the fun starts.

 

Office 365 credentials work and connect fine, no problem.

 

But regardless of what we put in for the "on-premises Exchange administrator" account, it throws an "Invalid Username or Password" error. This is regardless of using the current Windows identity checkbox, or typing the credentials in manually.

 

What's interesting, is that no errors are logged in the log file, and check of the security log on the Exchange box shows a successful logon from the .exe:

 

An account was successfully logged on.

 

Subject:

Security ID:

Account Name:

Account Domain:

Logon ID: 0x4C41A02

 

Logon Information:

Logon Type: 2

Restricted Admin Mode: -

Virtual Account: No

Elevated Token: Yes

Impersonation Level: Impersonation

 

New Logon:

Security ID:

Account Name:

Account Domain:

Logon ID: 0x4E548FB

Linked Logon ID: 0x4E549B7

Network Account Name: -

Network Account Domain: -

 

Process Information:

Process ID: 0x3190

Process Name: C:\Users\\AppData\Local\Apps\2.0\P740GNBT.DPA\JK4MHM40.9KB\micr..tion_5329ec537c0b4b5c_0011.0000_72ec5a2eed6c5911\Microsoft.Online.CSE.Hybrid.App.exe

 

If I then *purposefully* put a wrong username/password combo in then I get the expected audit failure in the security log AND also an expected entry in the HCW log file:

 

10393 [Client=UX, Page=Credentials, Thread=1] Windows Auth Failure: [ErrorCode=0x80004005] [NativeErrorCode=0x52E]

 

I've also ran TCPView to see what the HCW is doing when I hit OK at the credential prompt, and it's (unsurprisingly) opening an LDAP connection to one of our DCs. So I checked the security log on said DC, and it's showing a successful logon - so what the hell is the HCW complaining about?!

 

So this indicates it's not a credential error, but I have absolutely no idea what it could be!!!

 

The account we're using is a member of Domain Admins, Enterprise Admins and Exchange Organization Management.

 

We're running Exchange 2016 Standard, CU 15 on Server 2016 LTSC.

 

Any assistance would be unimaginably appreciated as this is now driving me mad!

 

Cheers