Articles and Tutorials

In this article I will discuss how to transfer an FSMO role, after the original role holder has gone offline. This process is called seizing, and cannot be done using the method described in Transferring FSMO Roles. Instead, the NT Directory Service Utility (ntdsutil) must be used - which is a command line program.

Note: This process should only be performed if the original role holder is offline. If a role is seized, in most cases the original role holder will need to be reinstalled before it is brought back onto the network. This is especially true for the RID Master, Schema Master and Domain Naming Master FSMO roles.

 

To start the process, open up a command prompt window, by clicking Start->Run and typing cmd. From here, type ntdsutil and press enter.

C:\WINDOWS\ntdsutil ntdsutil:

Then, type roles to access the FMSO Roles menu:

C:\WINDOWS\ntdsutil ntdsutil: roles fsmo maintenance:

At the FSMO maintenance menu, type connections:

C:\WINDOWS\ntdsutil ntdsutil: roles fsmo maintenance: connections server connections:

Then type connect to server servername (where servername is the name of the server that you wish to seize the role to):

C:\WINDOWS\ntdsutil ntdsutil: roles fsmo maintenance: connections server connections: connect to server zeus Binding to zeus... Connected to zeus using credentials of locally logged on user. server connections:

Leave this menu, by typing q and pressing enter:

C:\WINDOWS\ntdsutil ntdsutil: roles fsmo maintenance: connections server connections: connect to server zeus Binding to zeus... Connected to zeus using credentials of locally logged on user. server connections: q fsmo maintenance:

Now issue the command to sieze the role. The 5 roles have these specific commands:

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

For example:

 

C:\WINDOWS\ntdsutil ntdsutil: seize pdc

You will then receive a warning like this:

If you are sure, click yes, and the role will be seized. You may notice some errors appearing in the command line, due to the tool attempting to perform a safe transfer first. Obviously this will be impossible if the original role holder is offline, hence the errors.

You will have to seize all of the roles that the original server held before going offline. In most cases, this will be all 5.

Please remember that this process should not be taken on lightly, and the original role holder should be reinstalled before reintroduction into the network. This is not essential for PDC and Infrastructure Master roles, but I recommend that you do so anyway.