Study guide

4.1 Group Policy Architecture & Processing Order (LSDOU)

Administering Windows Server Hybrid Core Infrastructure AZ-800

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About Exam AZ-800: Format, Scoring & the September 2026 Retirement

2 Chapter 1: Active Directory Domain Services Architecture & Deployment

1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships

3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join

2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale

4 Chapter 3: Hybrid Identity & Microsoft Entra Integration

3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture

5 Chapter 4: Group Policy in AD DS and Hybrid Environments

4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies

6 Chapter 5: Remote Server Management in Hybrid Environments

5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion

7 Chapter 6: Hybrid Management with Azure Arc and Azure Services

6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers

8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration

7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization

9 Chapter 8: Hyper-V High Availability, Security & Containers

8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry

10 Chapter 9: Azure IaaS Virtual Machine Administration

9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity

11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution

10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC

12 Chapter 11: IP Addressing, DHCP & IPAM Management

11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments

13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access

12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections

14 Chapter 13: File Services, DFS, SMB & Azure File Sync

13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync

15 Chapter 14: Windows Server Storage Infrastructure & High Availability

14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O

4.1 Group Policy Architecture & Processing Order (LSDOU)

Key Takeaways Explain This Topic AI

Every GPO has two halves: the Group Policy Container in the AD database, which holds version and status metadata, and the Group Policy Template in SYSVOL, which holds the actual settings files.

Group Policy applies in LSDOU order (Local, Site, Domain, Organizational Unit), and later stages overwrite earlier ones, so the OU closest to the object normally wins.

Enforced beats Block Inheritance in every case, which is why enterprise security baselines are linked high in the tree and marked Enforced.

Multiple GPOs linked at the same container are applied in reverse link-order, so the GPO with link order 1 is processed last and therefore wins.

A GPO with no link, a disabled link, or a disabled configuration half never applies, which is a common cause of settings that appear correct in the console but never reach the client.

Last updated: August 2026

Group Policy Fundamentals, Architecture & Processing Order

In enterprise hybrid and on-premises environments, Group Policy remains the foundational framework for centralizing configuration management, security baselines, and operating system governance across Active Directory Domain Services (AD DS) . Group Policy allows administrators to define desired-state configurations for operating systems, application behavior, user desktop environments, and security boundaries across thousands of domain-joined endpoints.

Mastering the internal storage architecture of Group Policy Objects, the strict execution order of policy processing, inheritance override mechanisms, security filtering nuances, and diagnostic toolsets is mandatory for passing the AZ-800 exam and managing enterprise Windows Server infrastructures.

1. Group Policy Object Architecture: GPC vs. GPT

A Group Policy Object (GPO) is not a single monolithic file. Instead, every GPO is physically split into two logically linked, independently replicated components: the Group Policy Container (GPC) stored in Active Directory and the Group Policy Template (GPT) stored in the file system within the SYSVOL shared folder. +-----------------------------------------------------------------------------------+

  • | DUAL-COMPONENT GROUP POLICY ARCHITECTURE |
  • | |
  • | [ACTIVE DIRECTORY DATABASE: NTDS.DIT] [SYSVOL REPLICATED FOLDER SHARE] |
  • | |
  • | Group Policy Container (GPC) Group Policy Template (GPT) |
  • | LDAP: CN={GUID},CN=Policies,CN=System,DC=... Path: \\<Domain>\SYSVOL\<Domain>\|
  • | Policies\{GUID} |
  • | Attributes: Directory Structure: |
  • | - versionNumber (32-bit integer) - gpt.ini (Version=<Int>) |
  • | - gPCFileSysPath (UNC to SYSVOL) - \Machine\ |
  • | - gPCMachineExtensionNames (CSE GUIDs) - Registry.pol, Scripts/ |
  • | - gPCUserExtensionNames (CSE GUIDs) - \User\ |
  • | - flags (0=Enabled, 1=UserDis, 2=CompDis) - Registry.pol, Scripts/ |
  • | |
  • | Replication Engine: Replication Engine: |
  • | - AD DS Directory Replication (RPC / DRA) - DFS Replication (DFSR) |
  • +-----------------------------------------------------------------------------------+

The Group Policy Container (GPC):

Storage Location: Stored in the Active Directory domain directory partition under CN=Policies,CN=System,DC=corp,DC=contoso,DC=com .

Function: Stores GPO metadata, status flags, link information, and the list of registered Client-Side Extension (CSE) GUIDs required to interpret the policy settings.

Version Number Tracking: Maintains a 32-bit integer attribute ( versionNumber ). The high 16 bits represent the version of the User Configuration , while the low 16 bits represent the version of the Computer Configuration .

Replication: Synchronized between domain controllers via standard Active Directory Directory Replication Service (DRS) using RPC over TCP.

The Group Policy Template (GPT):

Storage Location: Stored in the file system under \\<Domain>\SYSVOL\<Domain>\Policies\{GPO-GUID}\ .

Function: Contains the actual configuration data files, scripts, Administrative Template registry settings ( Registry.pol ), folder redirection rules, and preference XML files.

Core Files and Folders:

gpt.ini : Contains a single [General] section with a Version=<Integer> key that must match the GPC versionNumber .

\Machine\ : Contains computer-specific settings, startup/shutdown scripts, and machine Registry.pol .

\User\ : Contains user-specific settings, logon/logoff scripts, and user Registry.pol .

Replication: Synchronized across domain controllers using Distributed File System Replication (DFSR) (or legacy FRS on deprecated domain functional levels).

Important

Version Mismatch & Replication Latency: When an administrator edits a GPO, both the GPC in AD DS and the GPT in SYSVOL have their version numbers incremented simultaneously. If Active Directory replication completes before DFSR synchronizes the file system changes (or vice versa), a temporary version mismatch occurs. The Group Policy client engine compares the GPC version with the GPT version; while they disagree the client can process a stale copy of the GPO until SYSVOL converges. Each GPO's version is visible in the GPO discovery events ( 5312 applied, 5313 filtered out) and in gpresult /r , so a version that lags the GPMC's is the signal to check DFSR health rather than the GPO's settings.

2. GPO Processing Order (LSDOU) & Precedence Rules

When a domain-joined computer boots or a user signs in, the Group Policy engine processes linked GPOs in a rigid, hierarchical sequence known by the acronym LSDOU :

Local (L): The local Group Policy stored on the individual client machine ( gpedit.msc ). Includes Local Group Policy, Administrator/Non-Administrator local policies, and User-Specific local policies.

Site (S): GPOs linked to the Active Directory Site object corresponding to the client's current IP subnet.

Domain (D): GPOs linked directly to the root of the Active Directory domain container (e.g., Default Domain Policy ).

Organizational Unit (OU): GPOs linked to Organizational Units, processed sequentially from the highest ancestor Parent OU down through nested Child OUs to the specific OU containing the target computer or user account. +-----------------------------------------------------------------------------------+

  • | LSDOU PROCESSING PRECEDENCE PIPELINE |
  • | |
  • | [1. LOCAL GPO] --> Evaluated 1st (Lowest Precedence) |
  • | | |
  • | v |
  • | [2. SITE GPO] --> Evaluated 2nd (Overwrites conflicting Local settings) |
  • | | |
  • | v |
  • | [3. DOMAIN GPO] --> Evaluated 3rd (Overwrites conflicting Site settings) |
  • | | |
  • | v |
  • | [4. PARENT OU GPO] --> Evaluated 4th (Overwrites conflicting Domain settings) |
  • | | |
  • | v |
  • | [5. CHILD OU GPO] --> Evaluated LAST (HIGHEST PRECEDENCE by default) |
  • | |
  • | GOLDEN RULE: The setting processed LAST in time WINS in event of conflict. |
  • +-----------------------------------------------------------------------------------+

Link Order Within the Same Container:

When multiple GPOs are linked to the same Active Directory container (e.g., three separate GPOs linked to the Finance OU), policies are processed in reverse numeric order:

Link Order N (e.g., Link 3): Processed first.

Link Order 1: Processed last . Therefore, Link Order 1 has the highest precedence among GPOs linked to that specific container and overwrites conflicting settings from Link 2 and Link 3.

Inheritance Controls: Block Inheritance vs. Enforced

Two administrative mechanisms alter the standard LSDOU processing hierarchy:

Block Inheritance ( Block Policy Inheritance ):

Configured at the OU or Domain level .

Prevents GPOs linked to higher-level ancestor containers (Parent OUs, Domain, or Sites) from being inherited by objects within that OU.

Does not block GPOs linked directly to the OU itself.

Enforced ( Enforce / Formerly "No Override"):

Configured on an individual GPO link .

Has two critical operational effects:

Bypasses Block Inheritance: An Enforced GPO linked at the Domain or Parent OU level will be processed by child OUs even if those OUs have enabled Block Inheritance .

Forces Highest Precedence: The Enforced GPO is moved to the very end of the processing pipeline, meaning its settings overwrite conflicting settings defined in lower-level Child OUs.

Multiple Enforced GPOs: If two GPOs are marked Enforced and contain conflicting settings, the Enforced GPO linked highest in the AD DS hierarchy (Site > Domain > Parent OU) takes final precedence.

Group Policy Precedence & Override Resolution Matrix

Configuration Scenario Standard LSDOU Outcome Impact of 'Block Inheritance' on Child OU Impact of 'Enforced' on Parent/Domain GPO

Domain GPO vs. Child OU GPO Child OU GPO wins (processed later). Domain GPO is blocked; Child OU GPO applies. Domain GPO wins (Enforced overrides Child OU and ignores block).

Parent OU GPO vs. Child OU GPO Child OU GPO wins. Parent OU GPO is blocked; Child OU GPO applies. Parent OU GPO wins .

Site GPO vs. Domain GPO Domain GPO wins. Site GPO is blocked; Domain GPO is blocked (unless Enforced). If Site GPO is Enforced and Domain GPO is not, Site GPO wins .

Conflicting Enforced GPOs N/A Ignored across all containers. The Enforced GPO higher in the hierarchy (Domain over OU) wins.