Windows Server 2012 – Migrating FSMO Roles

I installed one AD when Microsoft Windows Server 2012 was still in Release Candidate with the Datacenter edition, of course since few days my DC was rebooting every hour, the trial licence did expire few days ago.. So I had to install a new DC and promote it the transfer all FSMO roles from my “old” server to the new one.

First thing I had to do is to add this new server to the existing forest as a new domain controller :

2013-01-20_12-56-31 2013-01-20_12-56-48

2013-01-20_12-57-08 2013-01-20_12-57-32

2013-01-20_12-57-48 2013-01-20_12-58-04


I did it using the gui but you can also use PowerShell to get the same result :

# Windows PowerShell script for AD DS Deployment
Import-Module ADDSDeployment
Install-ADDSDomainController `
-NoGlobalCatalog:$false `
-CreateDnsDelegation:$false `
-CriticalReplicationOnly:$false `
-DatabasePath "C:\Windows\NTDS" `
-DomainName "METAL.INC" `
-InstallDns:$true `
-LogPath "C:\Windows\NTDS" `
-NoRebootOnCompletion:$false `
-ReplicationSourceDC "DC02.METAL.INC" `
-SiteName "Default-First-Site-Name" `
-SysvolPath "C:\Windows\SYSVOL" `

Now the server has been added to the forest as a new domain controller, on the new server after launching PowerShell command line, i used the Move-ADDirectoryServerOperationMasterRole command to transfer all the FSMO roles. EAch role corresponding to a number :


Role Name Number
PDCEmulator 0
RIDMaster 1
InfrastructureMaster 2
SchemaMaster 3
DomainNamingMaster 4

So my command line looked like that

Move-ADDirectoryServerOperationMasterRole -Identity "DC01" -OperationMasterRole 0,1,2,3,4

This is it !

Don’t forget to demote the “old” domain controller before getting rid of it. I wanted to blog about that because I’m not manipulating Active Directory controller every day and here is my scratch notebook so, this is to keep track on what I’m doing and share information.

Post author