These steps list the procedure to Seize Roles from the Primary Domain controller that hosts the FSMO roles, You need to have at a minimum two Domain Controllers to make this function, in anycase it’s bad practise to only have one domain controller as it can fail and you could be in a world of pain.
A Transfer that is done by Seizing the Role is an unexpected cause forcing you to move the Roles over.
- This can be caused when the current role holder is having issues(DC not booting or corrupted) and the role is not transferred by a planned transfer.
- This can also be done by forcing the DC to be demoted via dcpromo command.
Remember that when FSMO Roles have been seized they should no longer be able to communicate with the original Role holder. You should demote this DC as it may cause conflicts with the new holder.
Two Ways to Seize the Role Below:
Seizing the FSMO Role through Powershell
Step 1:
-
Type the following:
Move-ADDirectoryServerOperationMasterRole -Identity “DC001” –OperationMasterRole DomainNamingMaster,PDCEmulator,RIDMaster,SchemaMaster,InfrastructureMaster -Force
Note - in Exclamation would be whatever your DC would be called
-
Type Yes , or Yes to All
Seizing the FSMO role through Command Prompt
Step 1:
-
Type ntdsutil and press Enter.
Type roles and press Enter.
Type connections and press Enter.
Type connect to server (Type your DC that you want to move the role to) and press Enter.
Type quit and press Enter. -
Type seize schema master, press enter you will be promted that you are about to seize the role select yes and do the same for the other roles below.
Type seize naming master press Enter.
Type seize rid master and press Enter.
Type seize pdc and press Enter.
Type seize infrastructure master and press Enter
