Exchange 2016 doesn't display OUs in EAC

%3CLINGO-SUB%20id%3D%22lingo-sub-2480106%22%20slang%3D%22en-US%22%3EExchange%202016%20doesn't%20display%20OUs%20in%20EAC%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2480106%22%20slang%3D%22en-US%22%3E%3CP%3EBefore%20jumping%20to%20the%20conclusion%20and%20sending%20me%20this%20article%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fadministration%2Fexchange-server-not-display-all-ou%23%3A~%3Atext%3Ddisplayed%2520as%2520expected.-%2CCause%2Cto%2520show%2520in%2520this%2520view).%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Server%20doesn't%20display%20all%20OUs%20-%20Exchange%20%7C%20Microsoft%20Docs%3C%2FA%3E)%2C%20yes%2C%20I%20am%20fully%20aware%20of%20it!%20Unfortunately%2C%20it%20doesn't%20work%20as%20I%20would%20like%20it%20to%20work...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%2040%20Exchange%20servers%20and%20decided%20to%20build%20one%20new%2C%20for%20management%20purposes%20only%20and%20to%20amend%20the%20web.config%20file%20with%20the%20change%20for%20EAC%20to%20display%20OUs.%20The%20idea%20was%20to%20create%20a%20new%20DNS%20record%20to%20specifically%20access%20that%20particular%20Exchange%20server%20(or%20to%20access%20it%20via%20LAN%20%3CA%20href%3D%22https%3A%2F%2Fservername%2Fecp%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fservername%2Fecp%3C%2FA%3E)%20and%20hope%20to%20work%20-%20but%20it%20doesn't.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20way%20for%20this%20to%20work%20is%20to%20login%20to%20the%20actual%20Exchange%20server%20and%20browse%20to%20%3CA%20href%3D%22https%3A%2F%2Flocalhost%2Fecp%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flocalhost%2Fecp%3C%2FA%3E%26nbsp%3B-%20only%20then%20the%20change%20works%20and%20OUs%20are%20visible%20when%20creating%20a%20new%20mailbox.%20Is%20this%20by%20design%20or%20is%20something%20wrong%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3CBR%20%2F%3EG%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2480106%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

Before jumping to the conclusion and sending me this article (Exchange Server doesn't display all OUs - Exchange | Microsoft Docs), yes, I am fully aware of it! Unfortunately, it doesn't work as I would like it to work...

 

We have 40 Exchange servers and decided to build one new, for management purposes only and to amend the web.config file with the change for EAC to display OUs. The idea was to create a new DNS record to specifically access that particular Exchange server (or to access it via LAN https://servername/ecp) and hope to work - but it doesn't.

 

The only way for this to work is to login to the actual Exchange server and browse to https://localhost/ecp - only then the change works and OUs are visible when creating a new mailbox. Is this by design or is something wrong?

 

Thanks,
G

0 Replies