Ok, it’s time to demote existing Windows server 2003 and migrate all Windows server roles to new Windows server 2012 R2, there are no down time for Part1 steps and Part2 steps, but we need to schedule down time for Part3 steps to cut over all services.

IP Address SWAP

  1. Logon windows 2003 domain server.
  2. Demote the old Windows 2003 Domain Controller using DCPromo.exe.
  3. Rename the old Windows 2003 Server (which is now a member server) to <ServerName>-Old.
  4. Note the IP Address of <ServerName>-Old and change the IP Address.
  5. DNS Create a CName Record in DNS that points the old Windows 2003 Server to the name of the new Windows 2012 R2 Server.
  6. Logon to the new Windows 2012 R2 Server.
  7. Change the IP Address to the IP Address of the old Windows 2003 Domain Controller.

This is a very important step because if clients or servers are configured to use the old windows 2003 Server for DNS this will allow for a seamless transition.
Also DHCP Migration requires us to use the IP Address of the old server because the existing client leases are tied to that IP Address.

Server Roles Migration

Promote windows 2012 R2 server as Replica Domain Controller

  1. Logon to the new Windows 2012 R2 Server.
  2. On the Server Manager, notification is made available on the dashboard highlighted by an exclamation mark. Select it and amidst the drop down menu select Promote this server to a domain controller.
  3. Select add a Domain Controller into existing domain.
  4. Ensure the target domain is specified.  If it is not, please either Select the proper domain or enter the proper domain in the field provided.
  5. Click Change, provide the required Enterprise Administrator credentials and click the Next button.
  6. Define if server should be a Domain Name System DNS server and Global Catalog (GC). Select the Site to which this DC belongs to and define Directory Services Restoration Mode (DSRM) password for this DC.
  7. Click the Next button on the DNS options screen.
  8. In the Additional Options screen you are provided with the option to install the Domain Controller from Install From Media (IFM). Additionally you are provided the option to select the point from which DC replication should be completed. The server will choose the best location for AD database replication if not specified. Click the Next button once completed.
  9. Specify location for AD database and SYSVOL and Click the Next button.
  10. Next up is the Schema and Domain preparation.  Alternately, one could run Adprep
    prior to commencing these steps, regardless, if Adprep is not detected, it will automatically be completed on your behalf.
  11. Finally, the Review Options screen provides a summary of all of the selected options for server promotion. As an added bonus, when clicking View Script button you are provided with the PowerShell script to automate future installations. To click the Next button to continue.
  12. Should all the prerequisites pass, click the Install button to start the installation.
  13. Validate Active Directory DNS Zones are created.
  14. Validate AD Replication is working via the KCC (Knowledge Consistency Checker).
  15. Ensure there are not any errors in the event logs.

Migrate DHCP Server Role

  1. Logon to the new Windows 2012 R2 Server.
  2. Delete all of the existing database files including logfiles from %windir%\system32\dhcp.
  3. Copy the old DHCP Database from c:\export\dhcp\dhcp.mdb to %windir%\system32\dhcp.
  4. Start the DHCP Server and Authorize the DHCP Server.
  5. You should have all of the scopes from the old server including their leases now.

Migrate DNS Server Role

  1. Logon to the new Windows 2012 R2 Server.
  2. Import the Registry key from c:\export\dns\zones.reg.
  3. Copy all of the *.dns files from c:\export\dns (from the old windows 2003 domain controller) to %windir%\system32\dns.
  4. Restart the DNS Service.
  5. Validate that all of the Standard Primary and Secondary (Forward and Reverse) lookup zones are there.

Migrate Printer Server Role

  1. Logon to the old windows 2003 printer server.
  2. Download and install x64 driver for each printer on the windows 2003 server.

If the 64 bit driver is missing the Printer Migration Wizard will fail. Please keep in mind the printer divers need to be validated and test before cut over.

3. Logon to the new Windows 2012 R2 Server.

4. Open Server Manager and click All Servers in the navigation pane.

5. Click Manage in the Menu Bar and then click Add Roles and Features.

6. Click Next, select Role or feature-based Installation, and then click Next.

7. On the Select destination server page, select the server to install the Print and Document Services on. The default server is the local server. Then click Next.

8. Click Next on the Select features page.

9. On the Print and Document Services page, review the notes for the administrator and then click Next.

10. On the Select role services page, choose the role services that you wish to install. By default, Print Server is selected automatically.

11. Click Next until the Confirm installation selections page is displayed. Click Install to install the required role services.

12. Open Print Management.

13. In left pane, click Print Servers, right-click the print server that contains the printer queues that you want to export, and then click Export printers to a file. This starts the Printer Migration Wizard.

14. On the Select the file location page, specify the location to save the printer settings, and then click Next to save the printers.

15. Right-click the destination computer on which you want to import the printers, and then click Import printers from a file. This launches the Printer Migration Wizard.

16. On the Select the file location page, specify the location of the printer settings file, and then click Next.

17. Click Next to import the printers.

Hope you enjoy this post.

Cary Sun @sifusun

About Post Author

Leave a Reply