Home | Windows | Network | Interview Questions | Database | Virtualization | Knowledge Base | Contact Us

Related Topics

Transfering FSMO

Seizing FSMO

Understanding FSMO

Quick Links

Windows 2003 KB

Windows 2008 KB

Windows 2012 KB

Exchange Q&A



Network Interview Questions

SQL Interview Questions

Windows Admin Interview Q&A

Windows Forum

Other Links



Active Directory FAQ's

AD History


Configuring New Domain

Deleted Object Recovery in AD

Global Catalog Server

NetDom Command

Replmon Command

NTDS Utility Guide


FSMO Guide

FSMO Failure

Network KB

Knowledge Base Home

Active Directory Trust

Group Policy Guide

IIS 6.0

RAID Levels


RPC Guide

Domain & Forest Functional Levels

SQL Failover Cluster


Print Server



Considerations for the FSMO placement in Active Directory

Windows 2000/2003 Active Directory domains utilize a Single Operation Master method called FSMO (Flexible Single Master Operation), as described in Understanding FSMO Roles in Active Directory.

In most cases an administrator can keep the FSMO role holders (all 5 of them) in the same spot (or actually, on the same DC) as has been configured by the Active Directory installation process. However, there are scenarios where an administrator would want to move one or more of the FSMO roles from the default holder DC to a different DC.

Windows Server 2003 Active Directory is a bit different than the Windows 2000 version when dealing with FSMO placement. In this article I will only deal with Windows Server 2003 Active Directory, but you should bear in mind that most considerations are also true when planning Windows 2000 AD FSMO roles.

Single Domain Forest

In a single domain forest, leave all of the FSMO roles on the first domain controller in the forest. You should also configure all the domain controller as a Global Catalog servers. This will NOT place additional stress on the DCs, while allowing GC-related applications (such as Exchange Server) to easily perform GC queries.

Multiple Domain Forest

In a multiple domain forest, use the following guidelines:

# In the forest root domain:

If all domain controllers are also global catalog servers, leave all of the FSMO roles on the first DC in the forest.

If all domain controllers are not also global catalog servers, move all of the FSMO roles to a DC that is not a global catalog server.

In each child domain, leave the PDC emulator, RID master, and Infrastructure master roles on the first DC in the domain, and ensure that this DC is never designated as a global catalog server (unless the child domain only contains one DC, then you have no choice but to leave it in place).

Configure a standby operations master

For each server that holds one or more operations master roles, make another DC in the same domain available as a standby operations master. Making a DC as a standby operation master involves the following actions:

The standby operations master should not be a global catalog server except in a single domain environment, where all domain controllers are also global catalog servers.

The standby operations master should have a manually created replication connection to the domain controller that it is the standby operations master for, and it should be in the same site.

Configure the RID master as a direct replication partner with the standby or backup RID master. This configuration reduces the risk of losing data when you seize the role because it minimizes replication latency.

To create a connection object on the current operations master:

1. In Active Directory Sites and Services snap-in, in the console tree in the left pane, expand the Sites folder to see the list of available sites.

2. Expand the site name in which the current role holder is located to display the Servers folder.

3. Expand the Servers folder to see a list of the servers in that site.

4. Expand the name of the server that is currently hosting the operations master role to display NTDS Settings.

5. Right-click NTDS Settings, click New, and then click Connection.

6. In the Find Domain Controllers dialog box, select the name of the standby operations master then click OK.

7. In the New Object-Connection dialog box, enter an appropriate name for the connection object or accept the default name and click OK.

To create a connection object on the standby operations master perform the same procedure as above, and point the connection to the current FSMO role holder.

Note regarding Windows 2000 Active Directory domains: If the forest is set to a functional level of Windows 2000 native, you must locate the domain naming master on a server that hosts the global catalog. If the forest is set to a functional level of Windows Server 2003, it is not necessary for the domain naming master to be on a global catalog server.

Transfering FSMO

Seizing FSMO

Understanding FSMO

HTML Comment Box is loading comments...

Designed by TechieBird