Article ID: 812453 - Last Review: October 25, 2007 - Revision: 3.5 Moving a computer that is running Exchange 2000 Server or Exchange Server 2003 to a different domain is not supportedOn This PageSUMMARYUnder certain conditions, you may have to move a computer that is running Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 Server from its current domain to a new domain. However, moving a computer that is running Exchange 2000 or Exchange 2003 from one domain to another is not supported. Additionally, running the /disasterrecovery Setup command against the Exchange computer object that was previously in a different domain is not supported. MORE INFORMATIONThere are typically two situations in which servers might have to be moved between domains. A planned server move because of reorganizationWe recommend that if you plan to move Exchange computers between domains within same forest, you install new servers into the new domain instead. The mailboxes can then be moved from the server in the old domain to the server in the new domain, and public folder content can be replicated.Performing the move in this way will not disrupt mail delivery to the mailboxes that are being moved. Performing the move in this way will also avoid the potential data loss problems that are associated with other move methods that involve deleting and recreating the following:
For more information about how to move mailboxes in Exchange 2003, click the following article number to view the article in the Microsoft Knowledge Base: 821829
(http://support.microsoft.com/kb/821829/
)
Moving mailboxes in Exchange Server 2003
An unplanned server move that is caused by a site failure, a domain failure, or a disasterYou can restore the Exchange 2000 or Exchange 2003 databases and mailboxes to a new Exchange-based computer that you installed in the new domain. To move the current Exchange information to the new Exchange-based computer, you must have a good backup of the databases that were on the failed server.Note We do not recommend that you use the following procedure in situations in which you are trying to accomplish a “controlled” move between domains. Following these steps in that situation could cause e-mail outages, non-delivery reports (NDRs), and temporary mailflow problems. The effect on your specific Exchange organization should be tested in a lab environment. However, if you are already in a failure recovery situation in which a site or a domain has failed and the server must be rebuilt in a different domain, follow these steps:
msExchHomeServerName
For more information about these attributes and the syntax of their values, click the following article number to view the article in the Microsoft Knowledge Base:
homeMDB homeMTA 296479
(http://support.microsoft.com/kb/296479/
)
Requirements for disabling the Recipient Update Service
The easiest way to modify the user accounts in bulk is by using the ADModify utility. Use the ADModify utility to set the three attributes that were previously described for each user who had a mailbox on the failed server.To obtain the ADModify utility, contact Microsoft Product Support Services (PSS). For more information about how to contact PSS, visit the following Microsoft Web site: http://support.microsoft.com
(http://support.microsoft.com/)
To use the ADModify utility to set the three attributes for users, follow these steps:
For more information about backup and restore procedures for Exchange 2000, click the following article numbers to view the articles in the Microsoft Knowledge Base: 258243
(http://support.microsoft.com/kb/258243/
)
How to back up and restore an Exchange computer by using the Windows Backup program
813337
(http://support.microsoft.com/kb/813337/
)
How to recover or restore a single mailbox in Exchange 2000 Server
271987
(http://support.microsoft.com/kb/271987/
)
Overview of Exchange Server database architecture and database engine
| Article Translations
|
Back to the top
