Topic Last Modified: 2006-02-08
The Microsoft® Exchange Server Analyzer Tool reads the following registry entries to determine whether the Active Directory® directory service domain controller acting as the primary domain controller (PDC) emulator has been manually excluded from the list of domain controllers available for use by Exchange:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeDSAccess\Profiles\Default
If the Exchange Server Analyzer finds MinUserDC to be present and configured, a non-default configuration message is displayed.
A PDC emulator is an Active Directory operations master role computer that processes replication requests from Microsoft Windows NT® Server 4.0 backup domain controllers and processes all password updates for clients that are not running Active Directory–enabled client software. PDC emulators are also domain controllers, and are therefore available for use by applications such as Exchange.
Directory Service Access (DSAccess) is an internal component in Exchange 2000 Server and Exchange Server 2003 that controls how all Exchange components access Active Directory. The primary function of DSAccess is to maintain information about various directory-related events and operations. For example, DSAccess discovers the Active Directory topology and detects if domain controllers and global catalog servers are available and responding to queries.
By default, DSAccess includes the PDC emulator computer in its list of available and usable domain controllers. If non-Exchange programs are making heavy use of the PDC emulator, using the PDC emulator by DSAccess could cause performance problems on the PDC emulator computer, as well as on the Exchange server and the non-Exchange program computer.
To prevent such performance issues, the MinUserDC registry value can be added to the registry on an Exchange server to force DSAccess to query all other available domain controllers before querying the domain controller that holds the PDC emulator operations master role.
 Note: |
|---|
| An Exchange server configured with the MiniUserDC registry value will try to use other servers in the same domain first so it is recommended that this configuration only be set if the site contains at least two domain controllers for the domain containing the Exchange servers. |
| Important: |
|---|
| This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore the registry if a problem occurs. For information about how to restore the registry, view the "Restore the Registry" Help topic in Regedit.exe or Regedt32.exe. |
To examine and
edit the MinUserDC registry value
-
Open a registry editor, such as Regedit.exe or Regedt32.exe.
-
Navigate to: HKLM\System\CurrentControlSet\Services\MSExchangeDSAccess\Profiles\Default
-
Locate the MinUserDC value and make any required changes. If this DWORD value does not exist, you can manually create it.
-
The value data that is configured for the MinUserDC registry entry is the maximum number of domain controllers to contact before contacting the PDC emulator. For example, setting MinUserDC to 4 configures DSAccess to exclude the PDC emulator only when a total of 4 domain controllers are available. When this condition is met, the PDC emulator is excluded from use and DSAccess communicates only with the remaining 3 domain controllers.
Before you edit the registry, and for information about how to edit the registry, see the Microsoft Knowledge Base article 256986, "Description of the Microsoft Windows Registry" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).
For more information about using the MinUserDC registry entry, see the Knowledge Base article 298879, "XADM: Exchange 2000 May Experience Performance Problems When PDC Emulator Is Used for DSAccess" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=298879).