How to migrate objects from one domain to another in the same forest

In some occasions, due to political and/or management decisions there may be a need to create a new domain in your existing forest.
Although the migration process is already well documented, it might be worth noting some specific details in the process.

1. Configure and verify correct DNS connections between one domain to another:
�
��� Deploying DNS
�
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dnsbd_dns_overview.asp
�
2. Migrate users and�computers objects to the target domain by using ADMT 2.0:�
�
��� Preparing to Restructure Active Directory Domains Within a Forest
�
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dssbh_rera_lrei.asp
�
3. Optional Stage - If the target domain needs to include objects with Exchange attributes, you'll need to:
�
���� a. Run "setup /domainprep" from the Exchange installation disk, on the domain controller
�������������� that currently holds the "infrastructure" FSMO.
�
������� The following link describes the process of�implementing "domainprep":
�������
���� Chapter 2: Installing New Exchange 2003 Servers
�
http://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/fa02f087-7fe7-4eb7-b859-12632d762f9e.mspx
�
�
���� b. Install New Exchange server in the new domain, and connect it to the exiting Exchange organization.
�
���� c. Configure new Exchange Recipient Update Service (RUS):
�
����� Multiple recipient update services in a single domain
�
����� http://support.microsoft.com/?kbid=294792
�
����� LDAP Error Message Is Logged After You Install Exchange in Multiple Domains
�
�� �� http://support.microsoft.com/?scid=kb;en-us;313167
�
���� d. Move user's mailboxes that were migrated in step 2 to the new Exchange server.
�
���� e. Configure Public folder replication between the Exchange servers:
�
�� Chapter 3: Controlling Public Folder Replication
�
http://www.microsoft.com/technet/prodtechnol/exchange/guides/WorkingE2k3Store/cbdaaffd-750c-4a3d-8bb6-4d0474ef6eea.mspx
�
Note: It is recommended to configure at least one domain controller to function as global catalog:
�
� Planning Global Catalog Server Placement
�
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dssbd_topo_dljo.asp
�
4. Migrate objects that can't be migrate by using ADMT 2.0 by using "movetree" utility:
�
��� How to Use the "movetree" utility to Move Objects Between Domains in a Single Forest
�
��� http://support.microsoft.com/default.aspx?scid=kb;en-us;238394
�

Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain
�
http://support.microsoft.com/default.aspx?scid=kb;en-us;555040
�
Exchange Server 2003 Administration Guide
�
http://www.microsoft.com/downloads/details.aspx?FamilyID=98E45481-1458-4809-97D6-50D8AEEBD8A1&displaylang=en

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.