Domain controller XXXXXXX.PROD.OUTLOOK.COM is overloaded. Please try again later.

asked 2021-04-26T19:23:38.943+00:00
Ziv Rivkis 1 Reputation point

While performing basic migration progress lookup tasks such as getting last sync date, data consistency scores, completion time stamp, etc we receive the following error:

Domain controller DB6PR11A900DC03.NAMPR11A900.PROD.OUTLOOK.COM is overloaded. Please try again 
    + CategoryInfo          : NotSpecified: (:) [Get-MoveRequestStatistics], DCOverloadedException
    + FullyQualifiedErrorId : [Server=LNXP265MB0460,RequestId=d54c23cf-df52-43ae-b5f7-20d13f972e56 
   ,TimeStamp=26/04/2021 19:01:36] [FailureCategory=Cmdlet-DCOverloadedException] 1373CB42,Micros  
    + PSComputerName        :

The domain controller is not always the same, and we don't perform the same queries. Most of the queries are very basic PS scripts to retrieve data about the migration batches and their status. This occurs at least once a day and different domain controllers are specified.

What is the best way to avoid this (missing parameter in the script?)?



Azure Active Directory
Azure Active Directory
An Azure enterprise identity service that provides single sign-on and multi-factor authentication.
12,588 questions
No comments
{count} votes

2 answers

Sort by: Most helpful
  1. answered 2021-05-12T13:58:22.743+00:00
    VipulSparsh-MSFT 15,956 Reputation points

    @Ziv Rivkis Thanks for reaching out and sincere apologies for time taken to respond to this. We are working towards improving our response time significantly.

    This is a generic issue which occurs mostly because multiple Exchange servers send many large LDAP queries at the same time, triggering a complete topology discovery for each query.

    You need to follow certain steps in order to fix it :

    Install this 2961522 Update Rollup 7 for Exchange Server 2010 Service Pack 3
    Note :This update can randomize the deferral time for Exchange to send out the LDAP queries of complete topology discovery.

    There are few workaround as well, which can be found at :


    If the suggested response helped you resolve your issue, please do not forget to accept the response as Answer and "Up-Vote" for the answer that helped you for benefit of the community.

    No comments

  2. answered 2021-05-12T15:08:17.887+00:00
    Ziv Rivkis 1 Reputation point

    Hi @VipulSparsh-MSFT , thank you commenting. Any idea how I can install the patch on a M365 Exchange server? I also tried running the commands provided in your link on our M365 tenant but I am getting these errors:

    Set-ExchangeServer -identity LNXP265MB0460 -StaticExcludedDomainControllers DB6PR11A900DC03.NAMPR11A900.PROD.OUTLOOK.COM  
    Set-ExchangeServer : The term 'Set-ExchangeServer' is not recognized as the name of a cmdlet, function, script file,  
    or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and  
    try again.  
    At line:1 char:1  
    + Set-ExchangeServer -identity LNXP265MB0460 -StaticExcludedDomainContr ...  
    + ~~~~~~~~~~~~~~~~~~  
        + CategoryInfo          : ObjectNotFound: (Set-ExchangeServer:String) [], CommandNotFoundException  
        + FullyQualifiedErrorId : CommandNotFoundException  

    Any further advice would be greatly appreciated.