XADM: Downtime Occurs When You Promote a Local Domain Controller to a Global Catalog Server

This article was previously published under Q309234
This article has been archived. It is offered "as is" and will no longer be updated.
When you promote an Exchange 2000 server that is also a domain controller to a global catalog server, and then you restart the server, Exchange 2000 immediately begins to use the local global catalog as the configuration domain controller and user domain controller, even though the global catalog information has not yet fully replicated to this server. This may cause unnecessary downtime because the Exchange 2000 server relies on configuration information from the local global catalog service, which has not yet received all of the data and is out of synchronization.
This behavior can occur because the DSAccess application programming interface (API) detects the local computer advertising as a global catalog server and prioritizes the local computer as preferred to a remote global catalog server.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.

Article ID: 309234 - Last Review: 10/24/2013 07:53:39 - Revision: 1.4

  • Microsoft Exchange 2000 Server Standard Edition
  • kbnosurvey kbarchive kbbug kbexchange2000sp2fix kbfix KB309234