Forum Discussion
Hybrid Configuration Wizard
BellaBeck73 - yes, after trawling through a .dmp file with Microsoft, for us the issue was caused by we think two things:
1) Redirecting the default Computers container to a different OU for new devices
and
2) That redirected OU having a "/" in it's name (other characters could potentially also cause it).
Not sure if that helps or not - but we are able to verify by running the following from a PowerShell prompt on the machine with the HCW installed:
[System.DirectoryServices.AccountManagement.UserPrincipal]::Current
This gave an "Unknown error (0x80005000) - the same as the HCW was throwing" - but when we then defaulted the Computers container redirection to an OU with no forward slash in the name (redircmp "OU=Test OU,OU=Company,DC=ad,DC=domain,=DC=com") then rerunning the command it returned the correct user info - and in turn the HCW then worked.
- JonahIF,
Thank you so much for the information. I was able to fix my Hybrid configuration on premise login because of your good advice. My AD Computers container was also misconfigured. I brought up a new OU named NEWComputers and redirected to it using REDIRCMP – see for example https://activedirectoryfaq.com/2014/01/redirecting-the-containers-users-and-computers-in-windows-active-directory-domains/
The hybrid configuration wizard is now allowing be to login with my on premise credentials. Cheers!
