Operation Master Roles of Active Directory
In Windows NT 4.0-style domains, we have only one PDC (Primary Domain Controller) which has accepted any directory object modifications and any number of BDCs (Backup Domain Controllers)that held read-only copies of the accounts database.BDCs could authenticate users, but any changes to any attributes of domain accounts had to take place in direct communication with the PDC. Since the PDC pushed out copies of the accounts database, known as SAM database, to the BDCs for a domain, this sort of replication was known as Single-master replication.
Active Directory concepts in Windows 2000 Server and Windows Server 2003, changes the above drawbacks of NT 4.0 domains. Unless, your domain is functioning at the NT interim functional level, all domain controllers for a domain can accept changes for data in their domain, and domain controllers have peers to which, they can replicate changes to those objects. This type of setup is called as Multimaster Replication as each domain controller acts as a master, passing changes to other domain controllers until those changes are replicated fully.
Since some domain controllers need to have greater control over others, Microsoft took care of this problem by implementing special roles for some domain controllers in Active Directory, called Operations Master Roles (also know as Flexible Single master of Operation (FSMO). There are five specific operation master roles. They are:
- Schema Master (one per forest)
- Domain Naming Master (one per forest)
- RID Emulator/Pool (one per domain)
- PDC Emulator (one per domain)
- Infrastructure Master (one per domain)
Note: The first domain controller in a forest assumes all five roles simultaneously. The first domain controller in the second domain of a forest assumes all three domain-specific roles simultaneously. Organizations with only one domain controller have all five roles on that one domain controller.
Schema Master:
The Schema Master in a forest ensures that changes to the schema, or to the actual structure of the Active directory database, are made in a consistent manner. The active directory and global catalog are tangelled. The global catalog contains a subset of information from all domains within a forest. If you will added new attributes to the schema and wanted to include those in the golbal catalog, all your domain controllers that act as global catalog servers will need to received the change.
For Windows 2000-based DCs, the entire global catalog must be flushed and rebuilt on each domain controller; however for Windows Server 2003-based domain controllers, only the changes needs to be propagated.
The Schema Master role is one of the forest-specific roles, that only one domain controller in the entire forest can have.
Domain Naming Master:
The Domain Naming Master role is one of the forest-specific roles, that only one domain controller in the entire forest can have. This role protects aganist the creation of identically named domains in the same forest. The Domain Naming Master role is designed to be placed on a global catalog server on Windows 2000 forest. This role uses some information contained in the GC (Global Catalog) to fulfill its responsibilities. However in the Windows Server 2003 forest functional level, this placement is unnecessary.
To change the domain-naming master role. you must be a member of the Enterprise Admins group. Use the Active Directory Domains and Trusts tool to change the domain-naming master role.
RID Master:
The RID Master role handles the assignment and distribution of the latter portion of SIDs for objects within Active Directory. Every object in Windows is assigned a unique SID. The SID comes in the form of S-1-5-21-A-B-C-RID, where the S-1-5-21 is common to all SIDs. The "A, B, and C" parts of the number randomly generated 32-bit numbers that are specific to a domain. The RID, or relative identifier, part of the SID is another 32-bit number that is the unique part of the SID and identifies a distinct object in the directory.
The domain controller with the RID master role distributes groups of 500 unique RIDs to its brother and sister domain controllers with the domain, so that they can create unique objects.No two DCs have the same groups of RIDs to assign.
PDC Emulator:
The PDC emulator performs one of the two different roles, depending on how AD is implemented:
When AD is configured to interact with Windows NT 4.0 BDCs, or to interact with computers that don't have Windows 2000 Directory Service Client software, AD is said to be operating in mixed-mode.When AD operates in mixed-mode, the PDC emulator acts as a Windows NT PDC. In this situation, the PDC emulator synchronizes with existing Windows NT BDCs. Users or administrators of computers must contact the PDC to make the desired changes, if they are not running the DS client software for Windows 2000.
When AD is configured to interact only with Windows 2000 domain controllers and computers that run Windows 2000 DS client software, AD is said to be operating in native-mode. When operating in native-mode, the PDC emulator receives password changes more quickly than other domain controllers in the domain.
There can be only one PDC emulator in each domain in a forest.
Infrastructure Master:
The infrastructure master helps to speed up propagation and replication of certain pieces of information among the domain controllers. The infrastructure master role is designed to not be on a domain controller functioning as a GC server, unless every domain controller in your domain is a GC server as well, or if you have only one domain.
There can be only one Infrastructure master in each domain in a forest.