Study guide

4.3 Group Policy Preferences, Item-Level Targeting & Central Store

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.3 Group Policy Preferences, Item-Level Targeting & Central Store

Key Takeaways Explain This Topic AI

Group Policy Preferences (GPP) differ fundamentally from Group Policy Settings (GPS) because GPP does not lock the user interface and writes directly to standard registry locations rather than protected policy keys.

GPP provides four distinct CRUD lifecycle actions (Create, Replace, Update, Delete) to govern resource provisioning, state modification, and item deprovisioning across the endpoint lifecycle.

Item-Level Targeting (ILT) enables hyper-granular client-side filtering at the individual preference item level without requiring separate GPOs, WMI filters, or OU restructuring.

The 'Apply once and do not reapply' option configures default user settings upon initial policy application while permitting users to customize the setting subsequently without background refresh overwriting their changes.

The Central Store hosts Administrative Templates (.admx and localized .adml files) in SYSVOL, eliminating template version drift and replication discrepancies across administrative management stations.

Last updated: August 2026

Group Policy Preferences, Item-Level Targeting & Central Store

While standard Group Policy Settings (GPS) (also known as Administrative Templates or Policies) enforce rigid, non-negotiable configuration boundaries, enterprise IT environments frequently require flexible baseline configurations, user-customizable defaults, and granular resource mapping. Group Policy Preferences (GPP) provides this flexibility by expanding Group Policy capabilities to manage network drive maps, shared printers, environment variables, local user accounts, scheduled tasks, and arbitrary registry keys.

Furthermore, by leveraging Item-Level Targeting (ILT) and establishing a centralized SYSVOL Central Store for Administrative Templates ( .admx / .adml ), administrators can eliminate GPO sprawl and ensure consistent policy authoring across global administrative teams.

1. Group Policy Preferences (GPP) vs. Group Policy Settings (GPS)

Understanding the architectural and operational differences between Preferences and Policies is critical for enterprise administration and the AZ-800 exam. +-----------------------------------------------------------------------------------+

  • | GROUP POLICY SETTINGS (GPS) VS. PREFERENCES (GPP) |
  • | |
  • | [GROUP POLICY SETTINGS / POLICIES] [GROUP POLICY PREFERENCES] |
  • | |
  • | - Target: Protected Policy Registry Keys - Target: Standard Registry Keys |
  • | HKLM\Software\Policies (Same keys used by applications) |
  • | HKCU\Software\Policies - UI State: Fully interactive |
  • | - UI State: Greyed out / Locked (User can modify the setting) |
  • | - Removal: Cleanly "un-tattoos" registry - Removal: "Tattoos" registry |
  • | when GPO is unlinked / out of scope (Value remains unless deleted) |
  • | - Enforcement: Mandatory re-enforcement - Modes: Supports "Apply once and |
  • | on every background refresh cycle do not reapply" for baselines |
  • +-----------------------------------------------------------------------------------+

The Concept of Registry Tattooing:

Policies (GPS): Write to designated policy registry branches ( HKLM\Software\Policies , HKCU\Software\Policies , HKLM\Software\Microsoft\Windows\CurrentVersion\Policies ). The operating system locks the corresponding configuration UI in Windows. If the GPO is unlinked or deleted, the Group Policy engine automatically purges these keys during the next refresh cycle, returning the OS setting to its unconfigured state.

Preferences (GPP): Write directly to the standard registry keys utilized by applications and the OS shell. The configuration UI remains fully accessible to end users. If the GPO is unlinked or deleted, the configured settings remain in place indefinitely (this behavior is termed tattooing the registry ). To remove a preference setting, administrators must explicitly configure an action of Delete or enable Remove this item when it is no longer applied .

Comprehensive Architectural Comparison: Policies vs. Preferences

  • Architectural Dimension Group Policy Settings (Policies / GPS) Group Policy Preferences (Preferences / GPP)
  • Registry Location HKLM\Software\Policies & HKCU\Software\Policies Standard application and OS registry paths
  • UI Behavior Greyed out, disabled, or locked to the user Fully unlocked; user can alter the configured setting

Tattooing Behavior Non-tattooing; settings revert when GPO unlinked Tattooing; settings persist after GPO removal (unless configured to delete)

Enforcement Model Strictly enforced on every 90-min refresh cycle Supports Apply once and do not reapply for initial user baselines

Targeting Scope Container-level (OU/Domain) + Security/WMI Filters Item-Level Targeting (ILT) down to individual preference items

Lifecycle Actions Enabled, Disabled, Not Configured CRUD: Create, Replace, Update, Delete

2. GPP Lifecycle CRUD Operations & Common Tab Settings

Every Group Policy Preference item utilizes one of four standard lifecycle operations ( CRUD ):

Create:

Creates the resource (e.g., mapped drive, shortcut, environment variable, registry key) if it does not already exist .

If the resource already exists, the Group Policy engine leaves the existing resource completely untouched.

Replace:

Completely deletes and purges the existing resource and recreates a brand-new instance with the newly specified attributes.

Example: For a Drive Map, Replace unmaps the existing drive letter and maps the new UNC path from scratch.

Update (Default Action):

Modifies existing settings of the resource in place without recreating it.

If the resource does not exist, Update automatically creates it.

Best Practice: Use Update for ongoing configuration maintenance where existing connections should not be severed.

Delete:

Removes the resource if it exists on the endpoint.

If the resource does not exist, no action is taken. +-----------------------------------------------------------------------------------+

  • | GPP COMMON TAB ADVANCED CONTROLS |
  • | |
  • | [ ] Stop processing items on this extension if an error occurs on this item |
  • | [x] Run in logged-on user's security context (user policy option) |
  • | [x] Remove this item when it is no longer applied |
  • | [x] Apply once and do not reapply |
  • | [x] Item-level targeting [ Targeting... ] |
  • +-----------------------------------------------------------------------------------+

Critical Common Tab Options:

Run in logged-on user's security context: Evaluates and executes the preference item using the logged-on user's security token and Kerberos ticket rather than the local NT AUTHORITY\SYSTEM account. Essential for User Drive Maps and user-specific network printers that require access to authenticated file shares.

Apply once and do not reapply: The preference item is evaluated and configured only on the user's initial logon or first policy processing cycle . Subsequent background refresh cycles (every 90 minutes) skip this item. This allows IT to seed default corporate settings while allowing users to customize their preferences without having them reset.

Remove this item when it is no longer applied: When the GPO falls out of scope (e.g., the user moves to another OU or group membership changes), the Group Policy engine automatically deletes the preference item, preventing registry tattooing.

3. Item-Level Targeting (ILT) Mechanics

Item-Level Targeting (ILT) allows administrators to apply individual preference items within a single GPO to specific users, computers, hardware architectures, or network locations. Rather than creating 50 separate GPOs to map 50 departmental network drives, an administrator can create a single GPO containing 50 drive map items, each protected by an ILT filter. +-----------------------------------------------------------------------------------+

  • | ITEM-LEVEL TARGETING (ILT) FILTER LOGIC |
  • | |
  • | GPO: Corporate-Drive-Mappings |
  • | | |
  • | +-- Drive S: (\\fs01\sales) --> ILT: User is a member of SG-Sales-Dept |
  • | | |
  • | +-- Drive F: (\\fs01\finance) --> ILT: User is a member of SG-Finance-Dept |
  • | | |
  • | +-- Drive E: (\\fs01\eng) --> ILT: User is a member of SG-Engineering |
  • | | AND Operating System is Windows 11 |
  • | | AND IP Address in Range 10.20.0.0/16 |
  • | | |
  • | +-- Printer (Bldg-2-Color) --> ILT: Computer IP Address in 192.168.50.0/24 |
  • | AND Battery is NOT Present (Desktop) |
  • +-----------------------------------------------------------------------------------+

Primary ILT Targeting Categories:

Security Group: Checks whether the user or computer is a member of a specified domain or local security group (supports primary group checks and SID resolution).

Operating System: Evaluates the OS version, edition, architecture (32-bit vs 64-bit), and build number.

IP Address Range: Matches the client's current IP address or subnet mask (ideal for location-aware printer and file share mapping across branch offices).

Battery Present: Detects whether the device contains a battery (distinguishing portable laptops from fixed desktops/servers).

Disk Space / RAM / Processor: Evaluates hardware resource thresholds before executing compute-intensive tasks.

LDAP Query: Executes dynamic LDAP search filters against Active Directory objects (e.g., querying whether (department=Marketing) or (title=*Director*) ).

Registry / File / Environment Variable: Evaluates the presence or value of a specific registry key, file path, or environment variable on the endpoint.

Logical Operators & Parenthetical Grouping:

ILT supports complex boolean logic including AND , OR , Is , Is Not , and parenthetical grouping collections ( (A OR B) AND C ).

  • 4. Common Enterprise GPP Implementations # Inspecting GPP XML Configuration Files Directly in SYSVOL
  • $GpoGuid = "{31B2F340-016D-11D2-945F-00C04FB984F9}"
  • $Domain = "corp.contoso.com"
  • $DriveMapXmlPath = "\\$Domain\SYSVOL\$Domain\Policies\$GpoGuid\User\Preferences\Drives\Drives.xml"
  • # Reading XML contents to review Item-Level Targeting rules
  • [xml]$DrivesXml = Get-Content -Path $DriveMapXmlPath
  • $DrivesXml.Drives.Drive.Filters.FilterGroup

Key Preference Configurations:

Drive Maps ( User Configuration -> Preferences -> Windows Settings -> Drive Maps ):

Configures network drive letters ( H: , S: , P: ), UNC paths ( \\fileserver\share ), reconnect settings, and label names.

Best Practice: Use Action = Update with ILT based on departmental security groups.

Printers ( User/Computer Configuration -> Preferences -> Control Panel Settings -> Printers ):

Deploys TCP/IP printers, shared network printers (UNC), and local printers.

Configures the Default Printer dynamically based on the client computer's IP subnet.

Environment Variables: Sets user or system-level environment variables (e.g., APP_SERVER_URL or JAVA_HOME ).

Shortcuts: Automatically distributes application shortcuts, web links, and utilities to the Desktop, Start Menu, or Quick Launch toolbar.

Registry Settings: Directly writes, updates, or deletes arbitrary registry keys and values in HKLM or HKCU without requiring custom .admx authoring.

Power Options: Standardizes power plans (Balanced, High Performance), sleep timers, and display turn-off timeouts across desktop fleets.

5. The SYSVOL Central Store for Administrative Templates (ADMX / ADML)

The Problem of Local Administrative Template Drift:

Administrative Templates define the registry-based policy settings available in the Group Policy Management Editor ( gpme.msc ). Historically, template files were stored locally on each administrator's workstation in %SystemRoot%\PolicyDefinitions .

If Administrator A edited a GPO from a Windows 10 workstation and Administrator B edited the same GPO from a Windows Server 2022 domain controller, template version discrepancies led to administrative template drift , missing policy settings, and duplicate namespace errors. +-----------------------------------------------------------------------------------+

  • | SYSVOL CENTRAL STORE ARCHITECTURE & STRUCTURE |
  • | |
  • | UNC Path: \\<Domain>\SYSVOL\<Domain>\Policies\PolicyDefinitions\ |
  • | |
  • | \PolicyDefinitions\ |
  • | |-- WindowsUpdate.admx (Language-neutral XML policy schema definitions) |
  • | |-- BitLocker.admx |
  • | |-- SecGuide.admx |
  • | | |
  • | |-- \en-US\ (Language-specific localized display strings) |
  • | | |-- WindowsUpdate.adml |
  • | | |-- BitLocker.adml |
  • | | |-- SecGuide.adml |
  • | | |
  • | |-- \de-DE\ |
  • | | |-- WindowsUpdate.adml |
  • | +-- \fr-FR\ |
  • | |-- WindowsUpdate.adml |
  • +-----------------------------------------------------------------------------------+

The Central Store Solution:

Creating the PolicyDefinitions folder in SYSVOL establishes the Central Store . When the Group Policy Management Editor launches on any domain-joined machine, it automatically detects the Central Store in SYSVOL and loads all template definitions from SYSVOL rather than the local %SystemRoot%\PolicyDefinitions folder.

File Formats:

.admx Files: Language-neutral XML files stored directly in the root of the PolicyDefinitions folder. They define the policy category, registry key paths, value types, and UI structure.

.adml Files: Language-specific XML files stored in language subfolders (e.g., \en-US\ , \de-DE\ , \fr-FR\ ). They provide the localized display text, setting titles, and explanatory help strings. # Creating and Populating the SYSVOL Central Store via PowerShell

  • $DomainFQDN = (Get-ADDomain).DNSRoot
  • $CentralStorePath = "\\$DomainFQDN\SYSVOL\$DomainFQDN\Policies\PolicyDefinitions"
  • # 1. Create the Central Store directory if it does not exist
  • if (!(Test-Path -Path $CentralStorePath)) {
  • New-Item -Path $CentralStorePath -ItemType Directory -Force
  • }
  • # 2. Copy ADMX files from local system to Central Store
  • Copy-Item -Path "$env:SystemRoot\PolicyDefinitions\*.admx" -Destination $CentralStorePath -Force
  • # 3. Copy localized ADML language directories (e.g., en-US)
  • Copy-Item -Path "$env:SystemRoot\PolicyDefinitions\en-US" -Destination $CentralStorePath -Recurse -Force

Tip

Updating the Central Store: When Microsoft releases new Windows client builds (e.g., Windows 11 23H2/24H2) or Microsoft 365 Apps administrative templates, download the administrative template package, extract the files, and overwrite the .admx files and .adml language folders in \\<Domain>\SYSVOL\<Domain>\Policies\PolicyDefinitions . DFSR will automatically replicate the updated definitions to all domain controllers.