Migrate Domain Controller from 2012 to 2012 R2

These are my notes from adding a new Windows 2012 R2 server to a network currently controlled by a Windows 2012 Server. The new server will be promoted to a domain controller, roles migrated, DHCP scope moved and then finally the original 2012 server decommissioned.

These notes are fairly generalized based on already knowing how to install the server operating system and navigating the Server Manager utility and using Powershell

Very first steps

• Install Server 2012 R2
• Install all available updates
• Rename the server
• Set a static IP address
• Join the existing domain

Making it an active Domain Controller

• Install the Active Directory Services role
• Promote it to a Domain Controller

Migrate FSMO roles

View the current roles in Powershell (run as administrator)

• netdom Query fsmo
• Get-Adforest | FL GlobalCatalogs

Opening the Schema Tool, first run the following command in Powershell

• regsvr32 schmmgmt.dll

Now open MMC and add the following snapins

• Active Directory Domains and Trusts
• Active Directory Schema
• Active Directory Sites and Services
• Active Directory Users and Computers

Changing the Schema Master

• Right click on Active Directory Schema and choose 'Change Active Directory Domain Controller'
• Choose the new domain controller - You will get a warning and that'll be addressed in the next step
• Right click on Active Directory Schema again and choose 'Operation Manager'
• Click the 'Change' button and continue

Changing the PDC, RID pool manager, and Infrastructure master roles

• Right click on Active Directory Users and Computer and choose 'Change Domain Controller', select the new DC and press Ok
• Expand Active Directory Users and Computers
• Right click on the domain name and choose Operations Master
• The top line should list the current DC and the second line should display the new DC, if so, press 'Change'
• Make sure to do this for all 3 tabs (RID, PDC, Infrastructure)

Changing the Domain Naming Master

• Right click on Active Directory Domains and Trusts and choose 'Change Active Directory Domain Controller', select the new DC and press Ok
• Right click it once again and choose Operations Master
• The top line should list the current DC and the second line should display the new DC, if so, press 'Change'

Verify the FSMO roles are all with the new server

• Open Powershell (run as administrator)
• netdom Query fsmo
• They should all be listed as the domain controller. If not, go back through the steps and address what needs to be done

Removing the Global Catalog Server

If you are decommissioning the old server, this step needs to be performed.

• Expand Active Directory Sites and Services until you see the server names. Expand the server being decommissioned.
• Right click NTDS Settings and choose Properties
• Uncheck Global Catalog and click Ok

Verify Global Catalog servers

• Open Powershell (run as administrator)
• Get-Adforest | FL GlobalCatalogs
• The old server should no longer be listed

Move the DHCP Scope to the new server

• Add the DHCP Server role on the new server
• From the Server Manager alerts section, choose 'Complete DHCP configuration'
• Open DHCP Manager

Backing up the current scope - DO THIS STEP FROM THE OLD SERVER

• Open DHCP Manager
• Right click on the server name and choose Backup
• Choose a save location and click Ok
• Now stop the DHCP Server on the old server
• Right click server name > All Tasks > Stop
• Now copy the directory with the back to the new server

Restoring the DHCP scope

• Back in DHCP Manager on the new server, right click on the server name and choose Restore
• Choose the directory with the backup
• Click Yes on the warning screen about permissions
• If it succeeds without error, you should now be able to expand the server name and see the existing scope(s)

Disable the DHCP Server service on the old server

• On the old server, go to Services, right click DHCP Server and choose Properties
• Change the Startup Type to: Disabled