This Post is for an Active Directory services Migration from Windows Server 2003 to Windows Server 2012R2, these all the Steps are used by myself for live Migration without any Downtime.

1. Active Directory Domain Live Migration
from 2003 to 2012 R2...
This Post is for an Active Directory services Migration from
Windows Server 2003 to Windows Server 2012R2, these all
the Steps are used by myself for live Migration without any
Downtime.
My Present Server Form:-
Determine your Present scenario, as we have two AD Server working on Windows server
2003.
1. NS1.domain.com (Server 2003) - Domain Controller with all the FSMO Roles.
2. NS2.domain.com (Server 2003) - Another Domain Controller in the same domain.
Bullet Points for Migrations:-
1. First we will demote the server (NS2) to a member server.
2. Disjoin the member server from the domain.
3. Remove the server from the network.
4. Install and configure the ADDS and DNS Roles on NS2
5. Add this new server NS2 to Domain as an additional Domain Controller
6. Transfer the FSMO roles to new server (i.e. on NS2)
7. Now Demote the NS1.
8. Format and install Windows Server 2012R2 on NS1
9. add NS1 to Domain
10. Install and configure the ADDS and DNS Roles on NS1
11. Add this new server NS1 to Domain as an additional Domain Controller
12. Transfer FSMO Roles to NS1 server to make it Primary ADDS Server.
13. Test the Functionality/Errors via repadmin or dcdiag command.
Need to Consider:-
However, before performing such tasks, there is a little data gathering that needs to be done. we
need to note the following:
1. Is the serverthe last Domain Controller in the domain? – This means once removed,
the domain will no longer exists and any objects associated with the domain will be
deleted. (will not do this)

2. 2. Is the serveracting as the only Global Catalog Server? – It is crucial that each domain
have at least on Global Catalog Server. So before you remove this Domain Controller,
you need to make sure that the domain contains another Global Catalog server.
3. Does the server hosts Operation Master(FSMO) roles? – It is important to note down
any FSMO roles assigned to the Domain Controller before removing it from the network.
When the server is being demoted, any FSMO roles are transferred to another Domain
Controller in the domain. Thus we need to verify if this was done correctly.
4. Does the server hosts any other Server Roles? – If the server hosts any other roles,
removing the server from the network may cause certain services to stop working. It is
important to migrate these roles any other Server Roles from the Domain Controller
before demoting the server.
Prerequisite for Migration :-
1. Take the Backup of System State via ntbackup to all the server you have as a AD
services installed.
2. Check the FSMO role, Which Server hold that roles via command line - "netdom
query fsmo" result would be like that :-
C:>netdom query fsmo
Schema owner NS1.domain.com
Domain role owner NS1.domain.com
PDC role NS1.domain.com
RID pool manager NS1.domain.com
Infrastructure owner NS1.domain.com
The command completed successfully.
So here "NS1.domain.com" having all the FSMO Roles.
for more details about FSMO Roles please refer the URL :- "https://support.microsoft.com/en-
us/kb/324801"
Plan for Migration:-
As we found the in FSMO query result, all the FSMO roles is having NS1 server so that we can
Start with NS2 Server.
Demote the Server from AD "NS2.domain.com" from the
active Directory
1. Start with DCPROMO command.
2. Do not select "this server is the last domain controller in the domain".
3. Set the new Password for the Administrator, "after remove from AD this server will act
as a member server" in existing Domain Controller.
4. Complete the Process.

3. 5. Remove the server from Domain, as after removed the AD, the server now a member
server of Active Directory Domain Controllers.
6. Format and Install Windows Server 2012 R2.
7. Configure IP Address, Host name and add this Server to AD Domain.
8. Add Roles, Active Directory Domain Services and DNS Server.
9. Completes the Process ADDS.
10. Now this Server is a Additional Domain Controller into your Existing Forest.
FSMO Roles Transfer to this New Server (NS2)
Transfer the Schema Master Role
Use the Active Directory Schema Master snap-in to transfer the schema master role. Before you
can use this snap-in, you must register the Schmmgmt.dll file.
Register Schmmgmt.dll
1. Click Start, and then click Run.
2. Type regsvr32 schmmgmt.dll in the Open box, and then click OK.
3. Click OK when you receive the message that the operation succeeded.
Transfer the Schema Master Role
1. Click Start, click Run, type mmc in the Open box, and then click OK.
2. On the File, menu click Add/Remove Snap-in.
3. Click Add.
4. Click Active Directory Schema, click Add, click Close, and then click OK.
5. In the console tree, right-click Active Directory Schema, and then click Change Domain
Controller.
6. Click Specify Name, type the name of the domain controller that will be the new role
holder, and then click OK.
7. In the console tree, right-click Active Directory Schema, and then click Operations
Master.
8. Click Change.
9. Click OK to confirm that you want to transfer the role, and then click Close.
Transfer the Domain Naming Master Role
1. Click Start, point to Administrative Tools, and then click Active Directory Domains and
Trusts.
2. Right-click Active Directory Domains and Trusts, and then click Connect to Domain
Controller.
NOTE: You must perform this step if you are not on the domain controller to which you
want to transfer the role. You do not have to perform this step if you are already
connected to the domain controller whose role you want to transfer.

4. 3. Do one of the following:
o In the Enter the name of another domain controller box, type the name of the
domain controller that will be the new role holder, and then click OK.
-or-
o In the Or, select an available domain controller list, click the domain controller
that will be the new role holder, and then click OK.
4. In the console tree, right-click Active Directory Domains and Trusts, and then click
Operations Master.
5. Click Change.
6. Click OK to confirm that you want to transfer the role, and then click Close.
Transfer the RID Master, PDC Emulator, and
Infrastructure Master Roles
1. Click Start, point to Administrative Tools, and then click Active Directory Users and
Computers.
2. Right-click Active Directory Users and Computers, and then click Connect to Domain
Controller.
NOTE: You must perform this step if you are not on the domain controller to which you
want to transfer the role. You do not have to perform this step if you are already
connected to the domain controller whose role you want to transfer.
3. Do one of the following:
o In the Enter the name of another domain controller box, type the name of the
domain controller that will be the new role holder, and then click OK.
-or-
o In the Or, select an available domain controller list, click the domain controller
that will be the new role holder, and then click OK.
4. In the console tree, right-click Active Directory Users and Computers, point to All
Tasks, and then click Operations Master.
5. Click the appropriate tab for the role that you want to transfer (RID, PDC, or
Infrastructure), and then click Change.
6. Click OK to confirm that you want to transfer the role, and then click Close.
Check the FSMO roles on New server (NS2) with command
if all have been Transferred successfully.
C:>netdom query fsmo
Schema owner NS2.domain.com
Domain role owner NS2.domain.com
PDC role NS2.domain.com
RID pool manager NS2.domain.com
Infrastructure owner NS2.domain.com
The command completed successfully.
So here "NS2.domain.com" having all the FSMO Roles.

5. So Now we are good to go to do the Same Steps with NS1 to Demote it and Promote after a
Fresh installation of Windows Server 2012 R2.
After a Fresh Installation of NS1 we can transfer all the FSMO roles with the help of the same
steps as we did for NS2 to this NS1 Server to keep this server as a Primary Domain or ADDS
server.
Check the FSMO roles on New server (NS1) with command if all have been
Transferred successfully.
C:>netdom query fsmo
Schema owner NS1.domain.com
Domain role owner NS1.domain.com
PDC role NS1.domain.com
RID pool manager NS1.domain.com
Infrastructure owner NS1.domain.com
The command completed successfully.
So here "NS1.domain.com" having all the FSMO Roles.
After ADDS Migration Server Form :-
After Successfully Migration our Server Farm would be...
1. NS1.domain.com ( Windows Server 2012R2 ) - Domain Controller with all the FSMO
Roles.
2. NS2.domain.com (Windows Server 2012R2 ) - Another Domain Controller in the same
domain.
All the steps are done by me, and listed all the major Points here in this post, although if found
inexactitudes, please do let me know.
your valuable suggestions are always welcomed !!!
Thanks !!!
Manish Sharma
Skype - ctrlasol
Mob - +91.95840.91000
Manish.sharma3@yahoo.com