OU list is empty when adding new user or group

Evgeniy Goldshtein 76 Reputation points
2022-05-25T10:05:27.793+00:00

We have Exchange 2016 CU22
When trying to choose OU while creating anew user or group, I'm getting the blank screen with "There are more results..." and "there are no items...".
The issue itself is familiar. We have more then 500 OUs, so <add key="GetListDefaultResultSize" value="5000" /> was added a few years ago.

After May updates, as usual, this line disappeared from the C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp\web.config
It happens after every Exchange update, so as usually I added it again on all servers. But his time it did not help!
I tried removing it, re-adding it, changing the number, restarting ECP pool and IIS - nothing.

I also saw a solution for Exchange 2013 to add the same line to C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ecp\web.config, but in my case I gott 502 error and ECP didn't work at all until I removed it.

Any Ideas, guys?

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,345 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. KyleXu-MSFT 26,206 Reputation points
    2022-05-26T02:03:17.39+00:00

    @Evgeniy Goldshtein

    It happens after every Exchange update, so as usually I added it again on all servers. But his time it did not help!

    From this article, we can know that this is expected behavior you need to add this value every time that you install a cumulative update.

    I suggest you use the command below to check the number of OU in your organization. Then use a use a close value in the configure file. Such as using 510, if there exist 500 OU in your AD. 

    (Get-OrganizationalUnit -ResultSize unlimited).count

    If it doesn't work for your Exchange server, I would suggest you update it to the latest version Exchange Server 2016 CU23 + May22SU: This value could work in this CU (I set this value to 1)

    205587-qa-kyle-09-50-13.png

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Evgeniy Goldshtein 76 Reputation points
    2022-05-26T08:06:27.34+00:00

    @KyleXu-MSFT As I said, we do have more then 500 OUs and used this web.config trick for years, it just stopped working.

    Anyway, I found the problem: After the last update when I copy/pasted the line into web.config on all servers, I didn't copy it right on 1 of them (out of 10). I'm not sure why all the servers were affected, but after correcting it it started to work!

    Thanks everyone!

    0 comments
  3. KyleXu-MSFT 26,206 Reputation points
    2022-05-26T08:25:48.623+00:00

    @Evgeniy Goldshtein

    Yes, you need to change it for all Exchange servers. I noticed you said "I added it again on all servers", so I didn't mention this one in the first step of troubleshooting.

    When you login EAC from Exchange server A, this request may be redirected to another Exchange server (as far as I know, it effected by the DNS record and where your admin account hosted) , so you need to change this one on all Exchange servers.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments