Skip to content
Tutorials Center
My learning

Topics

Lesson 19 of 38 ยท Active Directory Structure

Global Catalog and FSMO Roles

Understand the Global Catalog and the five FSMO operations master roles in Active Directory: what each does, where it lives, how to find, transfer and seize them.

Multi-master replication means most changes can be made on any domain controller. A few jobs, however, cannot be shared safely, and one service has to know about the whole forest. These two special cases are the Global Catalog and the FSMO roles (Flexible Single Master Operations). Understanding them explains many logon problems, replication puzzles and disaster recovery decisions.

In this lesson you will learn what the Global Catalog stores and who needs it, what each of the five FSMO roles does, how to find the role holders, and how a transfer differs from a seizure. A Python stand-in checks which operations would fail when a role holder is unavailable.

The Global Catalog

A Global Catalog (GC) server is a domain controller that holds:

  • a full, writable copy of its own domain's objects (as every DC does), and
  • a partial, read-only copy of every object in every other domain of the forest, with only the attributes marked as partial attribute set (PAS) members (names, logon names, email, group membership and the like).

Together this gives one place where a forest-wide search can be answered. The GC listens on its own ports: 3268 (LDAP) and 3269 (LDAPS). The first DC in a forest is a GC automatically; you can enable the role on any DC with the NTDS Settings property in Sites and Services.

What uses the Global Catalog?

Need Why the GC
Logon Retrieves the user's universal group memberships so the access token is complete. Without a reachable GC, logon fails in multi-domain forests (unless universal group caching is on)
UPN logon Looks up the account holding [email protected]
Forest-wide search Address book lookups in Exchange and Outlook, "Find" in ADUC across domains
Application lookups Applications that need to find any user in the forest with one query

Query the GC on port 3268 with the forest root as base to search all domains at once:

Terminal
ldapsearch -LLL -H ldap://dc1.corp.example.test:3268 -D "[email protected]" -W \
  -b "DC=example,DC=test" "(sAMAccountName=asmith)" distinguishedName

The GC returns only partial-set attributes. To add more attributes to the set, you change the isMemberOfPartialAttributeSet flag in the schema, which triggers a full GC re-replication across the forest, so do it carefully.

In single-domain forests every DC can simply be a GC, and Microsoft recommends this, because every DC already has all objects.

Global Catalog

Forest-wide search Ports 3268 and 3269.
Partial copies Selected attributes only.
Logon Universal group membership.

Make most DCs Global Catalogs in small forests

1 / 2

FSMO roles

Five operations are performed by exactly one DC at a time. Two roles exist once per forest, three once per domain.

Role Scope Purpose
Schema Master Forest Only DC that accepts schema changes
Domain Naming Master Forest Adds or removes domains and application partitions
PDC Emulator Domain Time source for the domain, password changes and lockout, Group Policy edits default, legacy NT compatibility
RID Master Domain Hands out blocks of relative identifiers to DCs so they can create SIDs that are unique
Infrastructure Master Domain Updates cross-domain references (names and SIDs of group members from other domains)

Why single masters?

  • Schema: concurrent changes to the schema in different places could break the forest.
  • Domain naming: two admins adding "sales.example.com" at once would conflict.
  • RID: each new object needs a unique SID. The RID Master gives each DC a pool of 500 RIDs; the DC uses them and asks for more as needed. Giving out the same range twice would create duplicate SIDs.
  • PDC Emulator: the most visible role. It is the authoritative time source (all DCs sync from it, and clients from their DC), it receives urgent password changes so a recently changed password works instantly everywhere, and it gets lockout information.
  • Infrastructure: keeps references to objects in other domains current. It should not sit on a Global Catalog server unless all DCs are GCs (or, in a single domain, it does not matter).

What happens when a role holder is down?

Role Effect if offline
PDC Emulator Time drift, slow password change propagation, lockout oddities; very visible quickly
RID Master No immediate effect until DCs run out of their RID pool; new objects cannot be created after that
Infrastructure Stale display names for cross-domain group members; rarely noticed
Schema Only schema changes fail
Domain Naming Only domain additions and removals fail

Finding role holders

POWERSHELL
Get-ADForest | Select-Object SchemaMaster, DomainNamingMaster
Get-ADDomain | Select-Object PDCEmulator, RIDMaster, InfrastructureMaster
netdom query fsmo

Transfer versus seize

  • A transfer is a graceful handover between two healthy DCs, with up-to-date replication. It is the normal way:

    POWERSHELL
    Move-ADDirectoryServerOperationMasterRole -Identity "DC2" -OperationMasterRole PDCEmulator, RIDMaster
    
  • A seizure forces the role onto another DC when the old holder is permanently gone. Add -Force. After a seizure, the old DC must never return to the network with its previous state, because it would believe it still holds the role. Rebuild it from scratch.

Before you demote or decommission a DC, check whether it holds any roles and move them. Placing all roles on one well-managed DC is common in small environments; larger ones spread them across DCs.

Never seize a role if the old holder can be fixed or brought back to a healthy state. Prefer a transfer, and only seize in true disasters. After a seizure of the RID Master, make sure replication has converged.

Checking role availability (Python stand-in)

This stand-in models a small forest with five roles and two domain controllers, then reports which operations would fail if a given DC went down. It teaches the dependencies, not real behavior.

Python What breaks if this DC is down?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Which DC for logon? (Python stand-in)

To see how the GC matters for logon, this model checks whether a user's universal group membership can be fetched, with and without a reachable GC.

Python Logon needs universal groups

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which ports does the Global Catalog use for LDAP and LDAP over TLS?

    GC LDAP is 3268 and GC LDAPS is 3269; 389 and 636 are the regular LDAP ports.
  2. 2. How many FSMO roles exist per forest and per domain?

    Schema Master and Domain Naming Master are per forest; PDC Emulator, RID Master and Infrastructure Master are per domain.
  3. 3. The role holder is permanently destroyed. Which action moves the role?

    A seizure forces the role onto another DC. The old DC must not return in its previous state.
  4. 4. Which role is the authoritative time source for the domain?

    The PDC Emulator of the forest root domain is the top of the time hierarchy.

Summary

  • The Global Catalog holds a full copy of its domain and a partial copy of all others, served on ports 3268 and 3269.
  • The GC supplies universal group membership at logon and answers forest-wide searches.
  • FSMO roles: Schema Master and Domain Naming Master per forest; PDC Emulator, RID Master and Infrastructure Master per domain.
  • Find holders with Get-ADForest, Get-ADDomain or netdom query fsmo.
  • Transfer roles gracefully; seize only when the holder is gone for good, and never reconnect the old DC as it was.

Next: Group Policy Objects and Processing Order