ECP cannot display more than 500 OUs


Recently a colleague of mine found an interesting issue with an Exchange Server 2013 organization setup.

When creating new mailboxes, the local service desk personnel couldn’t select a target organizational unit (OU). The ECP dialogue just showed an empty window.


By default, the ECP OU picker result set contains 500 entries only.

The OU picker does not query the Active Directory with -ResultSize Unlimited.


Microsoft Knowledge Base article 3038717 provides the solution for this issue.

When querying the local Active Directory for the overall number of organization units using the following command, it turned out that it contained more than 4.000 OUs.

(Get-OrganizationUnit -ResultSize Unlimited).Count

Use this cmdlet to determine the current number of organization units and define a reasonable number for querying Active Directory.

Add a new key node to the ECP web.config file on your Exchange 2013 servers.


The ECP web.config file is located in

  • $exinstallClientAccessecp

Saving a modified web.config usually triggers an application pool restart. Use the following one-liner to restart the ECP application pool across all Exchange 2013 servers if required.

Get-ExchangeServer | ? { $_.AdminDisplayVersion -like '*15.*'} | % { Invoke-Command -ComputerName $_.Name -ScriptBlock {Restart-WebAppPool MSExchangeECPAppPool } }


It has not yet been verified if the issue is also present with Exchange Server 2016. If so, just let us know.


Keep enjoying the oddities of Exchange Server.

%d Bloggern gefällt das: