# Microsoft Exchange – OU picker is empty when creating new user

If the Exchange ECP OU picker is blank when creating a new mailbox, you may have hit the built-in result limit and need to raise the ECP web.config value.

blog

01 Nov 2016 de

![Microsoft Exchange – OU picker is empty when creating new user](/wp-content/uploads/2016/01/MicrosoftExchange.png)

[Bilder ansehen (4)](#pf-content-image-1-0)

We had a case where creating a new user from **ECP** on **Exchange 2013** worked right up until the moment the admin needed to choose the target **Organizational Unit (OU)**. The OU picker opened, but it was effectively empty, which made the mailbox creation workflow a lot less useful than it should have been.

## What the issue looks like

The **OU picker** was not displaying any OUs at all.

[!\[Exchange 2013 ECP OU picker window showing no organizational units\](/wp-content/uploads/2016/10/img_5816ea84d2581.png)](/wp-content/uploads/2016/10/img_5816ea84d2581.png)

That immediately suggested the problem was not Active Directory visibility in general, so a quick check in **Exchange Management Shell** was the next step.

[!\[Exchange Management Shell output showing organizational units returned by Get-OrganizationalUnit\](/wp-content/uploads/2016/11/img_58187abb6ec1c.png)](/wp-content/uploads/2016/11/img_58187abb6ec1c.png)

If `Get-OrganizationalUnit` returns data correctly, the problem is often the **ECP result limit**, not missing OUs in AD.

## Fix

This is a known Exchange behavior. Exchange Control Panel only handles a limited number of OUs by default, so environments with larger OU structures can end up with a blank or incomplete picker.

First, count the OUs:

```powershell
(Get-OrganizationalUnit -ResultSize Unlimited).Count
```

![Exchange Management Shell showing the organizational unit count](/wp-content/uploads/2016/11/img_58186eb851aa3.png)

Then modify each server's `web.config`:

`C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp\web.config`

Add the following just before `</appSettings>`:

```xml
<!-- allows the OU picker when placing a new mailbox in its designated organizational unit to retrieve all OUs -->
<add key="GetListDefaultResultSize" value="2000" />
```

Use a value that is **higher than your OU count**.

[!\[web.config appSettings entry added to increase the ECP OU picker result size\](/wp-content/uploads/2016/11/img_5818723c4278b.png)](/wp-content/uploads/2016/11/img_5818723c4278b.png)

After that, open **IIS**, find **MSExchangeECPAppPool**, and **recycle** it.

[!\[IIS application pools view with MSExchangeECPAppPool selected for recycle\](/wp-content/uploads/2016/11/img_58187784216f9.png)](/wp-content/uploads/2016/11/img_58187784216f9.png)

Do this on every server that hosts the **Mailbox role**.

## Important note

This change has to be added back after every **Cumulative Update**, because Exchange setup can overwrite `web.config`. If you still maintain an older on-premises Exchange environment, keep this on your upgrade checklist.

## Current note

Microsoft still documents this as an OU limit issue in ECP, and the same workaround is still described in their troubleshooting guidance. The historical part of this post is the product version: **Exchange Server 2013 support ended on April 11, 2023**, so if you are still seeing this there, it is also a reminder that the platform itself is now out of support.

## Zugehörige Projekte

Projekte, die zu Tags, Kategorien und Inhalt dieses Beitrags passen.

[Alle Projekte](/de/projekte/)

Projekte werden abgeglichen...

[Zurück zum Blog](/blog)

## Ähnliche Beiträge

- [Microsoft Exchange – Connecting to remote server failed with the following error message](/de/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message/)
- [Exchange 2013 – Exchange Management Shell (EMS) loading very slow](/de/blog/exchange-exchange-management-shell-loading-very-slow/)
- [Get-AdPermission – The operation couldn’t be performed because object couldn’t be found](/de/blog/get-adpermission-the-operation-couldnt-be-performed-because-object/)

<!-- PowerForge markdown artifact sha256:E0D720D7B9CF75EBE07457664D6B4365739B4F0A27019BC1FA97875E87E01235 -->
