Flexible Single Master Operations (FSMO) Roles or Operation Masters: Active Directory updates generally multi master "Changes can be made on any DC". But we still have some roles which Microsoft does not allow to multiple DC, these role call single master.
Assign automatically to the first domain controller in a domain. Used to reduce conflict and facilitate communication concerning replication between.
- First DC in a forest holds all roles
- First DC in a new domain within existing forest holds all domain roles
Forest wide roles: Only one DC contains these roles in a forest.
Schema Master: Responsible for schema update. If this operations master is unavailable, no schema changes can be made.
Domain Naming Master: Responsible for change to configuration naming context, adding and removing domain. After update it replicates to other DCs. If unavailable, cannot add or remove domain. Domain Naming Master must also be a global catalog server "May be unnecessary in single-domain forest?
Domain wide roles: One DC contains these role with in domain.
Relative Identifier (RID) Master: Every object in AD have a unique security identifier (SID). RID master allocates each DC a pool of RIDs. When a DC’s RID pool falls too low, it requests additional RIDs from RID master. With no RID master, when a DC runs out of RIDs, new security principals (Ex. users, groups etc.) cannot be created on that DC
Primary Domain Controller (PDC) Emulator: Acts as NT PDC to NT BDCs. Password changes replicated preferentially to PDC emulator. Authentication failures due to bad password at another DC forwarded to PDC emulator before failing completely. PDC emulator also performs time synchronize.
In a Windows 2000/2003 domain, the PDC emulator role holder retains the following functions:
- Password changes performed by other DCs in the domain are replicated preferentially to the PDC emulator.
- Authentication failures that occur at a given DC in a domain because of an incorrect password are forwarded to the PDC emulator before a bad password failure message is reported to the user.
- Account lockout is processed on the PDC emulator.
- Editing or creation of Group Policy Objects (GPO) is always done from the GPO copy found in the PDC Emulator’s SYSVOL share, unless configured not to do so by the administrator.
The PDC emulator performs all of the functionality that a Microsoft Windows NT 4.0 Server-based PDC or earlier PDC performs for Windows NT 4.0-based or earlier clients.
Infrastructure Master:Object in domain referencing object in another domain uses GUID, SID and DN. E.g. group in one domain referencing user or group in another domain. Infrastructure master updates SID and DN in cross-domain references- e.g. if referenced object moves. Multiple-domain, infrastructure master role must not be held by GC server. Not a problem in single-domain forests (because no external references). IM sync its data with GC. GD always gets up to date data from all domains so if IM and GC together is same DC, IM will not work. So IM and GC should be different DC so that IM can compare his data with GC. If all DCs are GC so no need of IM as will always have up to date DATA.
Comments
Post a Comment