We help IT Professionals succeed at work.

How to do the domain migation to new server

warriorsTeah asked
May i know what is the proper step to do domain migration in window 2003
Watch Question

are you migrating from Win srv 2003 to a newer version or from legacy to Win srv 2003??.Please give the appropriate OS versions and i will give u the official Microsoft guide.


I would like to know :
1.Window 2003 ->2003
2.Window 2003-->2008
Distinguished Expert 2019

Install the new OS on the new server, for :
1, join the new server into the existing domain as another DC. Once joined, and dcpromo completes replication of the data, you can transfer the roles from the old using the ADUC interface.
2) same thing install OS.  Use the windows 2008 disk on the windows 2003 to run the adprep32 /domain /forest.  Join the 2008 system into the AD as another DC, after dcpromo the replication is complete the AD master roles can be transferred from the win2k3 to the win2k8.
you got three ways:

In-place upgrading
Windows Server 2003 and Windows Server 2003 R2 can both be upgraded in-place  to Windows Server 2008, as long as you keep the following in mind:

The Windows Server 2003 patchlevel should be at least Service Pack 1
You can't upgrade across architectures (x86, x64 & Itanium)
Standard Edition can be upgraded to both Standard and Enterprise Edition
Enterprise Edition can be upgraded to Enterprise Edition only
Datacenter Edition can be upgraded to Datacenter Edition only
This might be your preferred option when:

Your Active Directory Domain Controllers can still last three to five years (economically and technically)
You worked hard to get your Active Directory in the shape it's in.
Your servers are in tip-top shape.
Migrating this way means adding Windows Server 2008 Domain Controllers to your existing Active Directory environment. After successfully moving the Flexible Single Master Operations (FSMO) roles you can simply demote the previous Domain Controllers, remove them from the domain and throw them out of the window. Transitioning is possible for Active Directory environments which domain functional level is at least Windows 2000 Native.


I feel transitioning is the middle road between the two other ways to migrate to Windows Server 2008:

Restructuring means filling a new Active Directory from scratch
In-place upgrading means you're stuck with the same hardware and limited to certain upgrade paths
Transitioning means you get to keep your current Active Directory lay-out, contents, group policies and schema. Transitioning also means moving to new machines, which can be dimensioned to last another three to five years without trouble.
Transitioning is good when:

You worked hard to get your Active Directory in the shape it's in.
Your servers are faced with aging.
In-place upgrading leaves you with an undesired outcome (for instance 32bit DC's)
You need a chance to place your Active Directory files on different partitions/volumes.
When done right your colleagues might not even suspect a thing! The downside is you need to know exactly what you're doing, because things can go wrong pretty fast. that's why I wrote this useful piece of information .

A third way to go from Windows Server 2003 Domain Controllers to Windows Server 2008 Domain Controllers is restructuring your Active Directory environment. This involves moving all your resources from one (Windows Server 2003) domain to a new and fresh (Windows Server 2008) domain. Tools like the Active Directory Migration Tool (ADMT) are priceless in these kind of migrations.


Restructuring is good when:

Your current Active Directory environment is a mess or is uncontrolable
You want to build a new Active Directory environment and import (pieces of) your existing Active Directory environment.
You need to merge (information from)(domains from) two Active Directory forests together
You need to split (information from)(domains from) two Active Directory forests

Active Directory Migration Tool version 3.1