Roles of Active Directory or AD roles is the focal archive wherein all objects in an enterprise and their individual ascribes are put away. It’s a progressive, multi-master empowered database that can store a huge number of objects. Changes to the database can be prepared at some random Domain Controller or DC in the undertaking, whether or not the Domain Controller is disconnected or connected from the network.

With the FSMO roles command netdom, it’s exceptionally simple and fast to perceive which domain controllers have FSMO roles.

Domain controller example, on the off chance that you had different DC, they would contend over consents to make changes. This implied that you could be making changes and, in some cases, they essentially wouldn’t experience.

AD or Active Directory roles and responsibilities has five FSMO roles, two of which are one per forest and three of which are one per domain.

List of FSMO Roles

A full Active Directory framework is a part of five separate Flexible Single Master Operation or FSMO roles. Those five FSMO roles are as per the following: 

  1. Schema Master
  2. Domain Naming Master
  3. Infrastructure Master
  4. PDC or Primary Domain Controller Emulator
  5. RID or Relative ID Master

Domain Naming Masters and Schema Masters are restricted to one per forest, though the rest are restricted to one per domain.

1. Schema Master

It is an enterprise-level FSMO role; there is just a single Schema Master in the AD forest. 

The Schema Master role proprietor is the solitary domain regulator in AD forest that contains a writable schema segment. Accordingly, the domain regulator that claims the Schema Master Flexible Single Master Operation role should be accessible to change its forest’s schema. This incorporates exercises like raising the practical level of the forest and redesigning the OS of a DC to a higher variant than at present exists in the forest, both of which will acquaint refreshes with AD schema.

2. Domain Naming Master

Domain naming master in FSMO roles is liable for confirming domains, so there’s just one for each forest. This implies in case you’re making a pristine domain in a current forest, this regulator guarantees that such a domain doesn’t as of now exist. If your domain naming expert is down under any circumstances, you can’t make another domain. 

Since you don’t make domain regularly, a few endeavours like to have a domain naming master and schema master inside a similar regulator.

3. Infrastructure Master

The infrastructure master role represents:

  • Distinguished Names or DNs
  • Security Identifiers or SIDs
  • Globally Unique Identifiers or GUIDs; between domain controller roles.

The infrastructure FSMO role holder is the domain controller liable for refreshing an item’s Security Identifiers and recognized name in a cross-domain object reference. 

FSMO gives you the certainty that your domain will want to play out the essential capacity of verifying clients and authorizations without interference.

If every one of the domain controllers in a domain additionally has the worldwide index, every one of the domain controllers has the current information. It isn’t significant which domain controller holds the infrastructure master role.

4. Primary Domain Controller Emulator

The PDC is a domain level role; there is one primary domain controller in every domain in an AD forest. The primary domain controller emulator role owner is liable for a few pivotal tasks:

  • Distributed File System: By default, DFS root servers will occasionally demand refreshed distributed file system namespace data from the primary domain controller emulator.
  • Gathering Policy Updates: All GPO refreshes are focused on the domain primary domain controller emulator.
  • Password Update Processing: When PC and client passwords are changed or reset by a non-primary domain controller emulator DC, the submitted update promptly retreats to the domain’s primary domain controller emulator.
  • Time Synchronization: Each primary domain controller emulator fills in as the expert time source inside its domain.
  • Backward Compatibility: The primary domain controller emulator imitates the single-master conduct of a Windows NT PDC.

5. Relative ID Master

Relative ID FSMO Role is for the single domain controller that will interact with Relative ID Pool demands from every one of the DCs in a domain. It can likewise move or remove an object from its domain. At the point when a domain controller makes a client or group, it allocates an interesting SID to the object. 

These security identifiers include domain security identifiers which are basic for all security identifiers in a domain, and a RID, which is special for each security head security identifiers present in a domain. Every DC inside a domain is given a pool of Relative ID which they can relegate to each new security chief made. If a domain controller Relative ID pool goes under a favoured cut-off, it demands extra Relative ID from the Relative ID Master of the domain.


The five FSMO roles are significant as they go inseparably with the security of your AD. On the off chance that you realize that a specific FSMO role will go through scheduled maintenance, the FSMO role transfer to a separate domain controller.
If the most exceedingly awful ought to happen and your FSMO role crashes, you can generally seize the FSMO role to another DC if all else fails.

So, have you made up your mind to make a career in Cyber Security? Visit our Master Certificate in Cyber Security (Red Team) for further help. It is the first program in offensive technologies in India and allows learners to practice in a real-time simulated ecosystem, that will give them an edge in this competitive world.



Are you ready to build your own career?