With
it being over 10 years
since the Windows Server 2003 unleash, there is presently however 5 months left as of the time of this post was written for official Microsoft
support.
This guide
was actually created as additional resource
of addressing the necessity to
transfer the DC FSMO roles from windows server 2003 to windows server 2012 R2.
In Windows DC surroundings, the FSMO roles hold all the required data regarding the DC. It is a necessity to have all this 5 roles operational properly to require care of correct DC
surroundings. The roles in question unit as follows:
• Schema
master
• Domain
naming master
• RID
master
• PDC aper
•
Infrastructure master
The
following setup is utilized for
this demonstration:
| Server Name | Operating System | Server Roles |
| canitpro-dc2k3.canitpro.local | Windows server is 2003 SP2 x86 | Active Directory FSMO roles, DNS |
| CANITPRO-DC2K12.canitpro.local | Windows server is 2012 R2 x64 | Additional Domain Controller, DNS |
In this example, the windows 2012 r2 server is already supplementary to the domain and promoted to an additional domain controller.
Note: Before adding Windows Server 2008 to a Windows Server 2003 surroundings, preparation of the forest and domain schema is necessary by running ad prep forest prep and ad prep domain prep from windows 2008 provide files support ad prep is required. In Windows Server 2012 R2 you’re doing not have to be compelled to be compelled to fret concerning it once adding said server as additional domain controller. Once you run the DC promo it’s going to automatically update it in Windows Server 2003 machine remotely.
Step 1: Transferring the free master, PDC individual and Infrastructure Master Roles
As the initiative let’s look but we have a tendency to ar ready to transfer these 3 roles over to new server.
1. Log in to the windows 2012 R2 server as domain administrator.
2. Click on Server Manager then Tools then Active Directory Users and Computers.
3. In MMC, right click on the name then click on Operation Masters
4. In next window it’s going to show the 3 FSMO roles. The default is PDC. In their it shows the current PDC holder. Then it’s asking if to be have compelled to modification it to new windows 2012 r2 server click on modification.
5. Click affirmative to continue
6. Once its guarantee as operation completed we have a tendency to ar ready to see the window shows the current PDC role holder as new windows 2012 r2 server.
7. Please repeat constant steps to transfer the free master and Infrastructure master Roles
Step 2: Transfer domain naming master role
1. Log in to the windows 2012 R2 server as domain administrator.
2. Click on Server Manager then Tools then Active Directory Domains and Trusts
3. In the MMC, right click on Active Directory Domains and Trusts > Operations Master…
4. In here it shows the current domain naming master role holder (canitpro-dc2k3.canitpro.local) and its asking if we’d prefer to maneuver it to windows server 2012 R2 (CANITPRO-DC2K12.canitpro.local). Click on modification to maneuver the role over.
5. Click affirmative to continue
6. Once it is checked that concerning task completion we have a tendency to ready to see current domain naming master is windows server 2012 R2 (CANITPRO-DC2K12.canitpro.local).
Step 3: Transfer schema master role
1. Log in to the windows 2012 R2 server as domain administrator
2. Open the Run window in server (Windows key + R) and then type regsvr32 schmmgmt.dll and press the key enter.
3. Click alright to continue
4. Open the Run window once more, sort mmc and click on OK
5. Then in mmc window click on File > Add-Remove Snap-in…
6. Then from snap in choose Active Directory Schema and click on on the Add button
7. Click the Ok button to continue
8. Then right click Active Directory Schema and clickChange Active Directory Domain Controller.
9. In the Next window select the windows server 2012 R2 DC (CANITPRO-DC2K12.canitpro.local) and click on the OK button.
10. Associate data message is provided. Click alright to continue
11. Right click Active Directory Schema > Operation Master
12. In here it shows this schema master role holder (canitpro-dc2k3.canitpro.local) and it’s asking if we’d prefer to maneuver it to windows server 2012 R2 (CANITPRO-DC2K12.canitpro.local). Click change to maneuver the role over.
13. Click affirmative to continue
14. Once it’s confirmed, the current schema master will presently show windows server 2012 R2 (CANITPRO-DC2K12.canitpro.local).
Now we’ve a bent to successfully move all. To verify all 5 FSMO roles ar stirred over to the new windows server 2012 R2, open transmission in said server and type command NetCom question fame and press enter.
It
will take it slow to
maneuver all the information over.
At that point it’s
safe to relegate the
DC role from the windows 2003 server.
Once
demoted, make sure the forest sensible level and domain sensible level is raised to
Windows Server 2012 R2 to experience new
changes.
