I had a clients that still running Windows Server 2003 Active Directory in their infrastructure, recently they wanted to know how actually they can migrate their AD from their legacy Server 2003 to Server 2012 R2.
So i take this opportunity to write a simple blog for those who might have a same ideas, or maybe just wanted to know how the process go through, or perhaps you also still running legacy Server 2003 AD and have budget to migrate your AD to Windows Server 2012 R2…
This is very straight forward process, but make sure you test it 1st in your Test Environment.
For this demo, i will use my OSI-Svr2003-DC01 (which is my legacy Server 2003 R2) and my OSI-Svr2012R2-MS01 (my new Windows Server 2012 R2)…
1 – On the Server 2003 R2, which is my OSI-Svr2003-DC01, open Active Directory Users and Computers, then right click domain name (osi.local), then click Raise Domain Functional Level…
2 – On the Raise Domain Functional Level interface, make sure you click Windows Server 2003 and then click Raise…
** Domain Functional Level must be setup to at least Windows 2003 mode. This is the lowest required Domain Functional Level that allow a Windows Server 2012 R2 Domain Controller installation.
3 – On the Raise Domain Functional Level box, click OK…
4 – Verify that your Current domain functional level now is Windows Server 2003…
5 – Next, open Active Directory Domain and Trusts console, right click Active Directory Domain and Trusts and then click Raise Forest Functional Level…
6 – On the Raise Forest Functional Level box, make sure taht you click Windows Server 2003 and then click Raise…
7 – On the Raise Forest Functional Level box, click OK…
8 – click OK again (it will stated that The functional level was raised successfully)…
9 – On the Raise Forest Functional Level box, verify that Current Forest functional level now is Windows Server 2003…
10 – Now lets switch to our Windows Server 2012 R2, on the Deployment Configuration interface, click Add a domain controller to an existing domain, then click select button and browse to osi.local, verify that credentials is Administrator, and then click Next…
11 – On the Domain Controller Options interface, verify that Domain Name System (DNS) server and Global Catalog (GC) is selected and fill up the Password for DSRM, and then click Next…
12 – On the DNS Options interface, click Next…
13 – on the Additional Options interface, beside the Replicate from : click dc01.osi.local (this is our Server 2003 R2 AD), and then click Next…
14 – On the Paths interface, click Next to proceed…
15 – On the Preparation Options interface, click Next…
16 – On the Reviews Options interface, verify all the information and then click Next…
17 – On the Prerequisites Check interface, verify that All prerequisites checks passed successfully, and then click Install…
18 – Please wait for few minutes for the process to complete…
19 – Once your Server 2012 R2 restart, log in as domain Administrator…
20 – on the OSI-Svr2012R2-MS01 server, open Active Directory Users and Computers console, right click domain and then click Operations Masters…
21 – On the Operations Masters interface, on the RID tab, click Change button and then click Yes…
***notice that Operation master is still dc01.osi.local***
22 – On the Active Directory Domain Services, click Ok…
*** Verify that the operations master role was successfully transferred ***
23 – Verify that Operation master now transferred to our new Server which is OSI-Svr2012R2-MS01.osi.local…
24 – Repeat the previous step no 21 – 23 for PDC and Infrastructure…
25 – Still on our OSI-Svr2012R2-MS01 server, open Active Directory Domain and Trusts console, right click Active Directory Domain and Trusts and then click Change Active Directory Domain Controller…
26 – On the Change Directory Server interface, click This Domain Controller or AD LDS instance and then choose your new 2012 R2 Windows Server which is OSI-Svr2012R2-MS01, and then click OK…
27 – On the Active Directory Domains and Trusts interface, hover over the Active Directory Domains and Trusts and verify that the server now reflects your new 2012 R2 Windows server which is OSI-Svr2012R2-MS01…
28 – On the Active Directory Domains and Trusts interface, right click Active Directory Domains and Trusts found in the folder tree and select Operations Manager…
29 – In the Operations Master interface, click Change to transfer the domain naming master role to the 2012 R2 Windows Server…
30 – Click Yes when the wizard asked if you are sure you wish to transfer the operations master role to a different computer…
31 – Once the Operations Master is successfully transferred, click OK…
32 – On the Operation Master interface, verify that Domain naming operations master is now transferred to OSI-Svr2012R2-MS01.osi.local server…
33 – On the OSI-Svr2012R2-MS01 server, open Command Prompt and then type regsvr32 schmmgmt.dll to change the Schema Master…
34 – Next we need to change Schema Master, on the OSI-Svr2012R2-MS01.osi.local server, open MMC, click File and then click Add/Remove Snap-in…
35 – On the Add or Remove Snap-ins interface, click Active Directory Schema, click Add and then click OK…
36 – On the Console1, right click Active Directory Schema and then click Change Active Directory Domain Controller…
37 – On the Change Directory Server interface, click This Domain Controller or AD LDS instance, click OSI-Svr2012R2-MS01.osi.local server and then click OK…
38 – On the Active Directory Schema box just click OK to proceed…
39 – Hover over the Active Directory Schema tree to verify the new Windows Server 2012 R2 computer is shown…
40 – on the Console1, right click Active Directory Schema and select Operations Master…
41 – On the Change Schema Master interface, click Change to transfer the schema master role to the 2012 R2 Windows Server (OSI-Svr2012R2-MS01.osi.local)…
42 – When asked if you are sure you wish to transfer the schema master role to a different computer, just click Yes…
43 – Once the schema master is successfully transferred, click OK to proceed…
44 – Verify the current schema master (online) is now OSI-Svr2012R2-MS01.osi.local, and then click Close…
45 – now our next process is to remove the legacy 2003 Windows Server from the Global Catalog Server…
Now switch back to legacy Server 2003 R2, open Active Directory Sites and Services console, browse to Sites, Default-First-Site, Servers, DC01, and then click NTDS Settings and click Properties…
46 – On the NTDS Settings Properties interface, un-tick Global Catalog and then click OK…
47 – Switch back to Server 2012 R2 (OSI-Svr2012R2-MS01.osi.local), open Command Prompt and then type Netdom query fsmo to verify that out new OSI-Svr2012R2-MS01.osi.local Server is running the FSMO role…
48 – Next, open IPv4 IP and make sure you point the DNS IP to your new OSI-Svr2012R2-MS01.osi.local IP…
49 – Our last step is to demote our legacy 2003 R2 ADDS, on the Server 2003 R2 open run and type dcpromo…
50 – on the Active Directory Installation Wizard, click Next…
51 – In the Remove Active Directory interface, proceed with next…
52 – On the Application Directory Partitions interface, click Next…
53 – on the Confirm Deletion interface, click Delete all application directory partition on this domain controller, then click Next…
54 – On the Administrator Password interface, fill up the password and then click Next…
55 – On the Summary interface, click Next…
56 – wait for the demote process to complete…
57 – Once the process completed, verify that Active Directory was removed from this computer, and click Finish…
No comments:
Post a Comment