Saturday, June 7, 2014

Migrating FSMO's Using PowerShell

PowerShell continues to make Administrative tasks easier the more it is utilized. Migrating FSMO's is also part of those task. So you have to move the Active Directory Database to another server in your environment. Let's get this task underway. In our lab environment we have two servers. One is a Server 2008 R2 server and the other a Server 2012 R2 server.

The 2012 R2 Server is joined to the domain but is not a DC. Let's run the PowerShell cmdlet Install-WindowsFeature AD-Domain-Services -IncludeManagementTools to get the role going as seen below.


Next we will run the cmdlet as shown below
Install-ADDSDomainController -CreateDnsDelegation:$false -DatabasePath 'C:\Windows\NTDS' -DomainName 'FISG.LOCAL' -InstallDns:$true -LogPath 'C:\Windows\NTDS' -NoGlobalCatalog:$false -SiteName 'Default-First-Site-Name' -SysvolPath 'C:\Windows\SYSVOL' -NoRebootOnCompletion:$true -Force:$true

Enter the Safe Mode Password to continue the install


Next restart the server to complete the install.

Next we will verify that AD replicated to our new Server by checking the Active Directory Administrative Center (ADAC).

Next we will move or FSMO's to our new Server. In PowerShell on our new server we will run the netdom query fsmo command as seen below.

Next we will run the cmdlet
Move-ADDirectoryServerOperationMasterRole -identity "FISG-DC1" -OperationMasterRole 0,1,2,3,4 as seen below to transfer the roles.

Next we will run the netdom query fsmo cmdlet again to verify that all fsmo's were transferred to FISG-DC1 as seen below.


For Server Downloads visit

For a 30 day trial of Azure with a $200 credit limit visit

By: Adnan Cartwright