Home > Articles > Microsoft > MCTS

  • Print
  • + Share This
This chapter is from the book

Seizing an Operations Master Role

If a DC hosting a critical operations master role (previously called flexible single master operations role, [FSMO]) fails, you might need to have another DC take over the role. The best choice is to transfer the role while both servers are operational. However, if the role holder fails, you can seize the role using a DC that is operational.

The following steps show how to seize a role.




Start a command prompt with administrative permissions on a domain controller.


Type ntdsutil and press Enter.


Type roles and press Enter. This accesses the fsmo maintenance prompt.


Type connection and press Enter. This accesses the server connections prompt.


Identify the fully qualified domain name (FQDN) of the operational DC. Substitute your DC's name in the following command:

  • connect to server dc1.pearson.pub


Type quit and press Enter. This brings you back to the fsmo maintenance prompt.


Identify the role you want to seize. These are identified in ntdsutil as Infrastructure Master, Naming Master, PDC, RID Master, and Schema Master. Use one of the following commands to seize the role:

  • seize infrastructure master
  • seize naming master
  • seize pdc
  • seize rid master
  • seize schema master


A confirmation dialog box appears similar to Figure 12-4. Review it and click Yes if you want to seize the role.


Type quit and press Enter twice to exit ntdsutil.

Figure 12-4

Figure 12-4 Seizing an operations role

  • + Share This
  • 🔖 Save To Your Account