Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Domain controller is overloaded after you change Active Directory configurations in Exchange Server 2010

Domain controller is overloaded after you change Active Directory configurations in Exchange Server 2010

View products that this article applies to.

Symptoms

Assume that you have a large-scale deployment that contains hundreds of Microsoft Exchange servers. After you make changes in Active Directory Domain Services (AD DS), the CPU and network resources become intermittently overloaded on some domain controllers. For example, the issue may occur after you change the Active Directory site or subnet configurations. When this issue occurs, the LDAP Search Time performance counter on the affected Exchange servers has a value that is larger than expected. 

Note You can check the CPU and network usage in Performance Monitor.

Additionally, if the domain controller has the intersite topology generator (ISTG) role, ISTG updates trigger each Exchange server to perform a complete topology discovery, and that causes this issue to occur every 15 minutes.

↑ Back to the top

Cause

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

↑ Back to the top

Resolution

To resolve this issue, install the following update:
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.

↑ Back to the top

Workaround

To work around this issue, use one of the following methods.

Method 1

Exclude the domain controller that has the ISTG role. To do this, run the following command in Exchange Management Shell (EMS):
Set-ExchangeServer -identity Server -StaticExcludedDomainControllers DomainController

Note If you want to remove the change that you have made and revert to the default behavior of Exchange, run the following command in EMS:
Set-ExchangeServer -identity Server-StaticExcludedDomainControllers:$null 

Method 2

Increase the number of domain controllers in your organization. Then, each domain controller will be connected by a smaller number of Exchange servers. This results in a smaller load for each domain controller.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about the ISTG role, go to the following Microsoft website:
General information about KCC and topology generation
For more information about the Set-ExchangeServer cmdlet, go to the following Microsoft website:
General information about the Set-ExchangeServer cmdlet

↑ Back to the top

Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2966923
Revision : 1
Created on : 1/7/2017
Published on : 8/26/2014
Exists online : False
Views : 326