FSMO Roles

Planted . Last tended .
  • ADDS is built upon mult-master DB model
  • Any DC can change configuration and it replicates to everyone
  • Some activities need to be controlled, so that’s where FSMO comes in
  • Flexible Single Master Operation roles
Forest levelDomain Level
Schema Master rolePDC emulator operations master role
Domain Naming Operations master roleRID operations master role
Infrastructure operations master role

Schema Master Role

  • Requires user to be member of Schema Admins group in order to make changes
  • Schema changes made on DC hosting this role are replicated to other DCs.

Domain-Naming Operations Master

  • When we add/remove DCs
  • While adding/removing RPC call to DC hosting this role, then the activity

PDC emulator operations master

  • Manages time sync
  • maintaining password change replications
  • locking down account in case of auth failures
  • Managing gpo edits

RID operations master

  • manages a pool of RIDs
  • RIDs are used in creating SIDs
    • once RID is used it will not be used again
  • will assign block of 500RIDs to DCs

Infrastructure operations master

  • replicating SID and DN as DN changes based on location in domain
  • checks DB periodically, if it finds foreign members
    • checks in global catalog, SID and DN
    • if it is different locally, updates it
    • then replicate to other DCs
  • this role should not be on the global catalog server
Updated . Thoughts? Email me.