Chapter 2 - Active Directory & GPO Architecture
Windows Server Group Policy (GPO) Master Handbook
Chapter 2 - Active Directory & GPO Architecture
Chapter Objectives
Understand how Active Directory stores, processes, and applies Group Policy Objects (GPOs), and how Domain Controllers, SYSVOL, Organizational Units (OUs), and replication work together.
1. Active Directory Overview
Active Directory Domain Services (AD DS) is Microsoft's directory service that stores users, computers, groups, printers, and policies. GPOs rely on AD DS to determine where policies are linked and to which users or computers they apply.
2. Active Directory Components
Forest: Highest security boundary.
Tree: One or more related domains.
Domain: Administrative and authentication boundary.
Organizational Unit (OU): Logical container used to organize users and computers and link GPOs.
Domain Controller (DC): Server hosting AD DS and SYSVOL.
3. GPO Architecture
A GPO has two main parts:
• Group Policy Container (GPC): Stored in Active Directory and contains version information and metadata.
• Group Policy Template (GPT): Stored in SYSVOL and contains policy files, scripts, and Administrative Template settings.
4. Where GPOs Are Stored
Active Directory: CN=Policies,CN=System,<Domain>
SYSVOL: \\domain\SYSVOL\domain\Policies
Both GPC and GPT versions must match for healthy policy processing.
5. SYSVOL Replication
Modern domains use DFS Replication (DFSR) to synchronize SYSVOL. If replication fails, GPOs may not apply correctly. Use repadmin and dfsrdiag (where available) to verify health.
6. GPO Linking
GPOs can be linked to Sites, Domains, or OUs. Best practice is to link most administrative policies to OUs instead of the domain root.
7. Security Filtering
By default, Authenticated Users receive policies. Security Filtering allows applying a GPO only to selected users or groups.
8. WMI Filtering
WMI Filters apply policies only when a computer meets specific criteria, such as operating system version, RAM, or laptop/desktop type.
9. Inheritance, Enforced and Block Inheritance
Child OUs inherit parent GPOs. 'Enforced' forces a GPO to apply even when inheritance is blocked. 'Block Inheritance' prevents inherited GPOs except those marked Enforced.
10. PowerShell Commands
Get-GPO -All
Get-GPLink
Get-GPInheritance -Target 'OU=IT,DC=contoso,DC=com'
Backup-GPO -All -Path D:\GPOBackup
Get-ADOrganizationalUnit -Filter *
11. Troubleshooting
• Verify DNS points only to Domain Controllers.
• Run gpupdate /force.
• Check gpresult /h report.html.
• Verify GPO link status.
• Review Security Filtering and WMI Filters.
• Confirm SYSVOL replication with repadmin /replsummary.
• Check Event Viewer > Microsoft > Windows > GroupPolicy.
12. Best Practices
Create dedicated OUs for departments, avoid linking all policies at the domain root, keep GPOs focused on one purpose, document changes, and back up GPOs before editing.
13. Interview Questions
1. What is the difference between GPC and GPT?
2. Where are GPOs stored?
3. What is SYSVOL?
4. Explain Security Filtering.
5. Explain WMI Filtering.
6. What is Block Inheritance?
7. What does Enforced do?
8. How do you troubleshoot a replication issue?
9. Why should DNS point only to domain controllers?
10. What tools do you use to verify GPO processing?
14. Practical Lab
1. Create an OU named Finance.
2. Create a GPO named Finance Desktop Policy.
3. Link it to the Finance OU.
4. Add a wallpaper setting.
5. Run gpupdate /force.
6. Verify the policy using gpresult /h report.html.
Architecture Summary
Component | Purpose |
Forest | Highest AD boundary |
Domain | Authentication and administration |
OU | Logical organization and GPO linking |
Domain Controller | Hosts AD DS and SYSVOL |
GPC | Stores GPO metadata in AD |
GPT | Stores policy files in SYSVOL |
SYSVOL | Replicated policy storage |
DFSR | Replicates SYSVOL between DCs |
Comments
Post a Comment