IT News, Tutorials, Solutions – SYSTEM HALT

Transfer or seize FSMO roles in Windows Server 2003

Few months ago I had a situation when one of our Windows Server 2003 DC`s crashed, the big problem was that the crashed DC owned all FSMO roles.

To explain a bit, a Windows Server 2000/2003 that is promoted to DC has 5 FSMO (Flexible Single Master Operations) usualy are kept on same DC, but in some scenarious administrators can move them to a different DC.

The five FSMO roles are:

Schema Master: The schema master domain controller controls all updates and modifications to the schema. To update the schema of a forest, you must have access to the schema master. There can be only one schema master in the whole forest.
Domain naming master: The domain naming master domain controller controls the addition or removal of domains in the forest. There can be only one domain naming master in the whole forest.
Infrastructure Master: The infrastructure is responsible for updating references from objects in its domain to objects in other domains. At any one time, there can be only one domain controller acting as the infrastructure master in each domain.
Relative ID (RID) Master: The RID master is responsible for processing RID pool requests from all domain controllers in a particular domain. At any one time, there can be only one domain controller acting as the RID master in the domain.
PDC Emulator: The PDC emulator is a domain controller that advertises itself as the primary domain controller (PDC) to workstations, member servers, and domain controllers that are running earlier versions of Windows. For example, if the domain contains computers that are not running Microsoft Windows XP Professional or Microsoft Windows 2000 client software, or if it contains Microsoft Windows NT backup domain controllers, the PDC emulator master acts as a Windows NT PDC. It is also the Domain Master Browser, and it handles password discrepancies. At any one time, there can be only one domain controller acting as the PDC emulator master in each domain in the forest.

You can transfer FSMO roles by using the Ntdsutil.exe command line utility or by using MMC snap-in. Depending on the FSMO role that you want to transfer, you can use one of the following three MMC snap-in:

• Active Directory Schema snap-in
• Active Directory Domains and Trusts snap-in
• Active Directory Users and Computers snap-in

The transfer operation works only if the DC that owns the roles is functional in your domain.
You can transfer them using Ntdsutil from your command line.

1. On any domain controller press START -> RUN type CMD then type Ntdsutil then press ENTER
2. Type roles then press ENTER
3. Type connections then press ENTER
4. Type connect to server servername , where servername is the name of the server where you want to transfer the roles.
A message will appear:

Binding to servername ...
Connected to servername using credentials of locally logged on user.
server connections:

5. Type q and press ENTER
6. It should appear now:

fsmo maintenance:

6. Now we can proceed to transfer the roles, type one by one the following commands:

Transfer schema master
Transfer domain naming master
Transfer PDC
Transfer RID master
Transfer infrastructure master

A message will appear asking if you want to transfer the role.

7. After you finish, type q and press ENTER and a nother q till you exit from Ntdsutil.

In the case you have only one DC working and the DC that owned the FSMO roles crashed you will need to use the sieze command instead of transfer

Example:

Seize schema master
Seize domain naming master
Seize PDC
Seize RID master
Seize infrastructure master

If you have any questions post them as a comment, I`ll be glad to answer.