Exchange 2013 CU6 and later uses out-of-site domain controllers and global catalog servers
In pre-CU6 installations, when the Exchange process requests domain controllers, as long as there is a single suitable domain controller in the In-Site list, the topology service returns it and does not search the Out-of-Site list any further. This behavior occurs regardless of how many domain controllers are requested by the client. This may cause an unbalanced load issue, especially during site failover. Domain controllers that remain in the failed-out site bear a greater load than domain controllers from outside the site.
To fix this issue, the MinSuitableServer configurable setting has been introduced. The topology service first checks whether there's a sufficient number of suitable servers in the In-Site list. If not, it adds servers from the Out-of-Site list. A similar change has also been made in topology discovery.
For example, if the number of in-site domain controllers is fewer than what's specified by the MinSuitableServer value (which is 3, by default), out-of-site domain controllers will be used. As soon as the number of in-site domain controllers is greater than the MinSuitableServer value, out-of-site domain controllers will not be used any longer.
This default value can be changed in the Microsoft.Exchange.Directory.TopologyService.exe.config file. You can do this by adding the MinSuitableServer value in the Topology MinimumPrefixMatch = "2" section.
- Open the Microsoft.Exchange.Directory.TopologyService.exe.config file.
- Locate the following text in the "Topology" section:EnableWholeForestDiscovery = "true"
- Add the following line after the line in step 2:MinSuitableServer = "1"
The section should now look like this:EnableWholeForestDiscovery = "true"
MinSuitableServer = "1"
ForestWideAffinityRequested = "true"/>
- Save the changes.
- Restart the Microsoft Exchange Active Directory Topology service.
ИД на статията: 3088777 – Последен преглед: 08/24/2015 16:22:00 – Редакция: 1.0