Module 4: Group Policy Management

🎯 AD Administration Course · Module 4 of 8

Group Policy Management & Configuration

AZ-800
AZ-800 Exam Alignment
AZ-800

Configure and manage Group Policy: Create and link GPOs, understand inheritance, enforcement, and blocking, configure security and WMI filtering, deploy ADMX templates, and troubleshoot GPO application with gpresult and RSoP.

  • Know the GPO processing order: Local → Site → Domain → OU (LSDOU), with later settings overwriting earlier ones
  • Understand the difference between Enforced (No Override) and Block Inheritance — Enforced always wins
  • Know how Security Filtering restricts which users/computers a GPO applies to
  • Understand that gpupdate /force triggers immediate policy application without waiting for the background refresh interval
Exam Tip: AZ-800 frequently tests GPO application troubleshooting. Know that gpresult /r shows which GPOs were applied to the current user/computer. Know that Security Filtering removes the Authenticated Users group and replaces it with specific targets, which also requires the target to have Read permission on the GPO (not just Apply).
Group Policy is the primary mechanism for configuring and enforcing settings across domain-joined computers and users in Active Directory. Every security setting, software deployment, drive mapping, or restriction pushed centrally by IT flows through Group Policy. Understanding GPO creation, linking, inheritance, and troubleshooting is essential for every AD administrator.

🌐 GPO Creation and Linking

A Group Policy Object (GPO) is a collection of settings stored in the domain’s SYSVOL share and applied to users and computers. GPOs must be linked to a site, domain, or OU to take effect.

GPMC › Group Policy Objects › New GPO › Link to OU
AD
Group Policy Management Console
|
techcareers.local
🏝️ Forest: techcareers.local
🌎 techcareers.local
📄 Default Domain Policy
📁 London
📄 TC-Desktop-Settings
📄 TC-Password-Policy-HR
📁 Domain Controllers
📄 Default Domain Controllers Policy

TC-Password-Policy-HR — Scope
Links: London → HR OU
Security Filtering: TC-HR-Users (replaces Authenticated Users)
Status: Enabled (Computer & User settings)
WMI Filter: None

ⓘ When Security Filtering is applied, both Read and Apply Group Policy permissions must be set on the target group. Remove Authenticated Users only after confirming this.

📅 GPO Processing Order and Inheritance

Order Level Notes
1 Local GPO Applied first. Every Windows machine has a local GPO. Lowest priority.
2 Site Applied to all machines in an AD site. Rarely used — mostly for slow-link detection or printer deployment.
3 Domain Default Domain Policy lives here. Password Policy must be set at domain level to affect domain accounts.
4 OU (parent then child) Applied top-down through OU hierarchy. Child OU GPOs process last — highest precedence at OU level.
Conflict resolution: Later-applied settings win. Child OU GPOs override parent OU GPOs override domain GPOs (unless Enforced).
Enforced (No Override): A GPO marked Enforced cannot be blocked by Block Inheritance. Enforced always wins.
Block Inheritance: Set on an OU to prevent GPOs from parent OUs from applying. Enforced GPOs still apply.

⚠️ Password Policy Exception

The domain password policy (complexity, length, age, lockout) can ONLY be configured in a GPO linked at the domain level, not at an OU level. GPOs linked to OUs that contain password settings will not affect domain account passwords — only local account passwords on member servers. To have different password policies for different groups of users, use Fine-Grained Password Policies (covered in Module 8).

🔌 Filtering GPO Application

Filtering Type How It Works Use Case
Security Filtering Remove Authenticated Users from the GPO ACL and add specific users/groups. The GPO only applies to the specified targets. Both Read and Apply Group Policy permissions must be set. Apply a GPO to a subset of users in an OU (e.g. only Managers get a specific desktop policy)
WMI Filter A WMI query that must evaluate to True for the GPO to apply. Evaluated on the client machine. Slower than security filtering. Apply a GPO only to 64-bit machines, only to laptops, only to machines with <4GB RAM
Item-Level Targeting Available in Group Policy Preferences. Each preference item can have conditions (OS version, OU membership, IP range, etc.) Map different drives based on group membership or site without needing multiple GPOs
PowerShell — GPO Management & Troubleshooting

# Create a new GPO
New-GPO -Name 'TC-Desktop-Settings' -Comment 'Enforces corporate desktop settings'

# Link the GPO to an OU
New-GPLink -Name 'TC-Desktop-Settings' -Target 'OU=London,DC=techcareers,DC=local' -LinkEnabled Yes

# Enforce a GPO (No Override) on a specific link
Set-GPLink -Name 'TC-Desktop-Settings' -Target 'OU=London,DC=techcareers,DC=local' -Enforced Yes

# Block GPO inheritance on a child OU
Set-GPInheritance -Target 'OU=IT,OU=London,DC=techcareers,DC=local' -IsBlocked Yes

# View GPO inheritance and applied GPOs for an OU
Get-GPInheritance -Target 'OU=London,DC=techcareers,DC=local'

# Force immediate policy refresh remotely
Invoke-GPUpdate -Computer 'PC01' -Force

# Troubleshoot: show applied GPOs for current user/computer
gpresult /r

# Generate full HTML RSoP report
gpresult /h C:\GPReport.html /user techcareers\jsmith /scope user

💡 Best Practices

  • Never edit the Default Domain Policy or Default Domain Controllers Policy — create new GPOs for all custom settings so you can revert changes without affecting baseline security
  • Name GPOs descriptively: TC-[Location/Department]-[Function] (e.g. TC-London-DesktopLockout) — avoid generic names like “New GPO”
  • Keep GPOs focused on a single purpose — one GPO per setting category (software, security, drive maps) makes troubleshooting and rollback easier
  • Use gpresult /r or gpresult /h as your first troubleshooting step when users report that a policy isn’t applying
  • Store ADMX templates in the Central Store (\\domain\SYSVOL\domain\Policies\PolicyDefinitions) so all admins see the same templates
  • Use Security Filtering in preference to WMI Filters — WMI filters are evaluated on the client, adding CPU overhead and making GPO application slower

🎓 Interview Q&A

Q: A GPO is linked to the London OU and another is linked to the HR child OU. Both configure the same wallpaper setting to different values. Which setting wins?
The HR child OU GPO wins because GPOs are processed in LSDOU order — Local, Site, Domain, OU — with later-processed settings overwriting earlier ones. When processing OUs, parent OUs are processed before child OUs, so the HR OU GPO (child) is processed after the London OU GPO (parent), and its wallpaper setting overrides the parent’s setting. The exception is if the London OU GPO is set to Enforced — in that case the London wallpaper setting cannot be overridden by any child OU GPO.

Q: What is the difference between Security Filtering and Block Inheritance?
Security Filtering controls who a GPO applies to within its scope — you add specific users or groups to the ACL and remove Authenticated Users so only those targets receive the policy. Block Inheritance is set on an OU and prevents GPOs from higher levels (parent OUs, domain) from flowing into that OU. They solve different problems: Security Filtering targets specific users within an OU; Block Inheritance prevents all parent-level GPOs from applying to an entire OU subtree. Importantly, Enforced GPOs still apply even when Block Inheritance is set.

Q: A user reports their drive mapping GPO is not applying. What troubleshooting steps would you take?
Step 1: Run gpresult /r on the affected machine to see which GPOs were applied (Applied GPOs) and which were denied (Denied GPOs) and the reason. Step 2: Check Security Filtering — confirm the user’s account has both Read and Apply Group Policy permissions on the GPO. Step 3: Verify the GPO is linked to the correct OU and the link is enabled. Step 4: Check if Block Inheritance is set on the user’s OU. Step 5: Run gpupdate /force and test again. Step 6: Check the GPO settings are in the User Configuration (not Computer Configuration) since drive maps must be user-side.

🎯 AZ-800 Mock Test
Module 4 — Group Policy Management
5 questions · Scenario-based · Pass mark: 70%

Question 1 of 5

A GPO at the domain level sets the desktop wallpaper to the company logo. The IT OU has Block Inheritance enabled and a local GPO sets a different wallpaper. An administrator marks the domain GPO as Enforced. What wallpaper will IT users see?

AThe IT OU wallpaper, because Block Inheritance takes priority over Enforced
BThe company logo wallpaper, because Enforced GPOs override Block Inheritance
CNo wallpaper — the conflicting policies cancel each other out
DThe local GPO wallpaper, because local GPO is always applied last

Question 2 of 5

You configure Security Filtering on a GPO to apply to the TC-Managers group. Users in TC-Managers report the policy is not applying. The GPO is linked to the correct OU. What is the most likely cause?

AThe GPO is marked as Disabled
BSecurity Filtering only works with computer objects, not user objects
CThe TC-Managers group has Apply Group Policy permission but is missing the Read permission on the GPO
Dgpupdate has not been run on the affected machines

Question 3 of 5

Where must a password policy GPO be linked to affect domain user account passwords?

AAt the domain level — password policies only affect domain accounts when linked at the domain root
BAt the OU containing the users whose passwords you want to control
CAt the Domain Controllers OU
DAt any OU in the domain — password policy GPOs apply to all accounts regardless of link location

Question 4 of 5

A new ADMX policy template has been added for a third-party application. Admins on different workstations see different policy templates in the GPMC editor. What is the correct fix?

AInstall the ADMX template on each admin’s workstation manually
BCopy the ADMX file to C:\Windows\PolicyDefinitions on the PDC Emulator
CPush the ADMX file via a GPO startup script to all domain controllers
DCopy the ADMX and ADML files to the Central Store: \\techcareers.local\SYSVOL\techcareers.local\Policies\PolicyDefinitions