Skip to main content

Hand-Edited GPO Permissions in SYSVOL Drift From Active Directory and Never Show in GPMC Delegation

Medium severityActive Directory About 20 minutes to fix

Overview

GPMC warns that a GPO's SYSVOL permissions are inconsistent with Active Directory. The cause is a hand-edited or inheriting folder ACL, and the Delegation tab never shows it.

At a glance

Symptom
When you select the GPO in Group Policy Management, one of two messages appears.
Likely cause
Each domain GPO has a Group Policy container, a directory object under CN=Policies,CN=System in the domain partition, and a Group Policy template, a folder…
Impact
Microsoft warns that changing either store outside GPMC can make Group Policy processing on the client fail, or stop users who should have access from editing the GPO.
Verification signal
Select the GPO again in GPMC.
Safe correction
Preconditions: you are allowed to modify security on the GPO (otherwise you only get the second message and no OK button that fixes it); you know who added…
Rollback or recovery
Reapply the saved SYSVOL ACL only if the reset removed access a documented process depends on, and only as a stopgap while you grant that access properly through…

If GPMC greets you with The permissions for this GPO in the SYSVOL folder are inconsistent with those in Active Directory, someone changed the access control list on the GPO’s folder in SYSVOL by hand, or that folder has been set to inherit permissions from its parent. A GPO is stored in two places, a Group Policy container in Active Directory and a Group Policy template folder in SYSVOL, and only GPMC and the Group Policy editor keep their permissions in step. The fix is to let GPMC rewrite the SYSVOL ACL from the Active Directory one: select OK on the prompt while holding the right to modify security on the GPO. Back up first, because that reset removes every hand-added entry, and the GPMC Delegation tab never showed those entries in the first place.

Symptom

When you select the GPO in Group Policy Management, one of two messages appears. With permission to modify security on the GPO you see:

The permissions for this GPO in the SYSVOL folder are inconsistent with those in Active Directory. It is recommended that these permissions be consistent. To change the permissions in SYSVOL to those in Active Directory, click OK.

Without that permission, the last sentence reads Contact an administrator who has rights to modify security on this GPO. instead. GPMC checks this every time you navigate to a GPO, so the prompt returns until the two sides agree. Other symptoms Microsoft ties to the same mismatch are clients failing to process the GPO and administrators who should be able to edit it finding they can’t.

False Assumption

The tempting belief is that the GPO’s folder under \\contoso.com\SYSVOL\contoso.com\Policies is an ordinary file share, so tightening or widening it with Explorer or icacls is a quick, harmless way to adjust who can read or change a policy. It looks like it works: the new entry is there when you list the folder. But GPMC presents a GPO as one unit and sets its permissions on both stores at once. A change made to only one store is invisible to the tool everyone uses to review GPO access.

Root Cause

Each domain GPO has a Group Policy container, a directory object under CN=Policies,CN=System in the domain partition, and a Group Policy template, a folder named with the GPO’s GUID under \\<DNS-domain>\SYSVOL\<DNS-domain>\Policies holding gpt.ini and the Machine and User subfolders. They share the GUID but not a storage engine, replication path or transaction: Active Directory replication carries the container, DFS Replication carries the template. Microsoft documents two causes of the inconsistency message:

  • the ACL on the SYSVOL part of the GPO has been set to inherit permissions from the parent folder, so it picks up whatever is granted on Policies;
  • someone changed the SYSVOL permissions manually.

Directory and file system permissions are not the same sets of rights, so GPMC translates between them. One Active Directory right has no file system equivalent: List Object. A GPO where an account such as Authenticated Users holds List Object in Active Directory can keep raising the prompt even after GPMC has rewritten the SYSVOL side.

Impact

Microsoft warns that changing either store outside GPMC can make Group Policy processing on the client fail, or stop users who should have access from editing the GPO. That is the availability side: a removed Read entry on the folder can stop clients reading the template.

The security side follows from how GPMC displays access. The Delegation tab and the Security Filtering section are built from the Active Directory component only. An extra grant on the SYSVOL folder, such as write access for a helpdesk group, therefore never appears in any GPMC access review. Clients read the template files from SYSVOL over SMB, so an account that can write to that folder can, in our assessment, change what the GPO delivers without holding any GPO permission an auditor would see. Treat any unexplained write entry as a finding until you know who added it and why; the same class of hidden write access is behind the Authenticated Users write trap on the SYSVOL scripts folder.

Diagnosis

Run these from a domain-joined admin workstation with the GroupPolicy PowerShell module. None of them changes anything.

  1. Get the GPO’s GUID and version numbers:
    Get-GPO -Name "<GPO name>"

    The Id field is the GUID used as the folder name. UserVersion and ComputerVersion show an AD version and a SysVol version; in a healthy GPO each pair matches. A version mismatch points at replication, which is a separate problem from permissions.

  2. List the Active Directory side, which is what GPMC shows:
    Get-GPPermission -Guid <GPO-GUID> -All

    Expect entries such as Authenticated Users with GpoApply and Domain Admins with GpoEditDeleteModifySecurity. Keep this output with your change record.

  3. List the SYSVOL side:
    icacls "\\contoso.com\SYSVOL\contoso.com\Policies\{<GPO-GUID>}"

    Compare the trustees with step 2. Entries marked (I) are inherited from the parent folder, which is the first documented cause. Explicit trustees that don’t appear in step 2 are hand-made changes, the second cause.

  4. In GPMC, open the GPO’s advanced permissions and look for any account holding List object. That is the documented cause to check when the prompt keeps returning after a reset.

Correction

Preconditions: you are allowed to modify security on the GPO (otherwise you only get the second message and no OK button that fixes it); you know who added any extra SYSVOL entries and whether they still need that access; you have tested the steps on a lab GPO first.

  1. Back up the GPO and the current SYSVOL ACL. The backup directory must already exist.
    Backup-GPO -Guid <GPO-GUID> -Path C:\GpoBackups -Comment "Before SYSVOL permission reset"
    icacls "\\contoso.com\SYSVOL\contoso.com\Policies\{<GPO-GUID>}" /save C:\GpoBackups\sysvol-acl.txt /t
  2. In GPMC, select the GPO and choose OK on the prompt. GPMC rewrites the ACL on the SYSVOL folder to match the Active Directory permissions and removes the inheritance setting from the folder if it is present. Every hand-added SYSVOL entry is removed.
  3. If the prompt returns, fix the List Object entry found in diagnosis step 4. Remove the group that holds List object from the GPO’s Active Directory permissions, or replace that entry with one that grants Read and, where the GPO should apply to it, Apply Group Policy, added through the Scope tab. Keep the read and apply permissions that the June 2016 MS16-072 Group Policy update requires. Restore defaults in the GPO’s advanced permissions also clears it, but it resets every Active Directory permission on the GPO, so re-add your security filtering and delegation from the step 2 output afterwards.
  4. If a group genuinely needs to edit the GPO, grant it through GPMC’s Delegation tab or the GroupPolicy module, never on the folder:
    Set-GPPermission -Guid <GPO-GUID> -TargetName "<group>" -TargetType Group -PermissionLevel GpoEdit -WhatIf

    Remove -WhatIf once the preview is right. GPMC sets the matching permissions on both stores when you delegate there.

Stop if the prompt persists and no account holds List object: compare Get-GPO versions and check SYSVOL replication before changing anything else.

Validation

  • Select the GPO again in GPMC. No inconsistency message appears.
  • Run icacls "\\contoso.com\SYSVOL\contoso.com\Policies\{<GPO-GUID>}" again. The GPO folder shows no (I) entries, and its trustees correspond to the Get-GPPermission -All output.
  • Get-GPPermission -Guid <GPO-GUID> -All matches the output you saved, apart from any delegation you deliberately added.
  • Get-GPO still shows matching AD and SysVol version pairs.

Rollback

Reapply the saved SYSVOL ACL only if the reset removed access a documented process depends on, and only as a stopgap while you grant that access properly through delegation, because it brings the inconsistency back. /restore takes the parent directory, as in Microsoft’s icacls c:\windows\ /restore aclfile example:

icacls \\contoso.com\SYSVOL\contoso.com\Policies\ /restore C:\GpoBackups\sysvol-acl.txt

To undo a delegation added in correction step 4, set the group back with Set-GPPermission -Guid <GPO-GUID> -TargetName "<group>" -TargetType Group -PermissionLevel None -Replace, then confirm with Get-GPPermission. If the Active Directory permissions were reset with Restore defaults, re-add each entry from the saved Get-GPPermission output with Set-GPPermission.

Prevention

  • Manage GPO permissions only in GPMC or with the GroupPolicy module, and reselect the GPO in GPMC afterwards to confirm no prompt appears. Never edit the folders under Policies in Explorer or with icacls, and never set them to inherit.
  • Sweep for hand-made grants. To find every GPO folder whose ACL explicitly names a group, use its SID with a leading *:
    icacls "\\contoso.com\SYSVOL\contoso.com\Policies\*" /findsid *<SID> /t

    Any hit for a group that has no GPMC delegation on that GPO is drift.

  • Open each GPO in GPMC as part of a periodic review: the consistency check runs on navigation, so the prompt itself is your detector.
  • Review read exposure as well as write. Anything in a GPO folder is readable by whoever the GPO grants Read, which is why SYSVOL’s broad read access exposes legacy Group Policy Preferences passwords.

Keeping GPO Access Reviewable

A GPO’s real access is the union of its Active Directory and SYSVOL ACLs, but GPMC only shows you the first. Keep them identical by making every permission change through GPMC or the GroupPolicy module, and treat the inconsistency prompt as an audit finding to investigate before you select OK, not a nuisance to click away.

3

Apply the safer control

Before you change production

Confirm the affected scope, export the current configuration, and test the replacement control in a non-production environment first.

Fix commands and configuration

The permissions for this GPO in the SYSVOL folder are inconsistent with those in Active Directory. It is recommended that these permissions be consistent. To change the permissions in SYSVOL to those in Active Directory, click OK.
Contact an administrator who has rights to modify security on this GPO.
\\contoso.com\SYSVOL\contoso.com\Policies
4

When to escalate

Validation and rollback are covered in the sections above.

Escalate

Escalate when the blast radius is uncertain, the control cannot be tested safely, or remediation requires an outage or security exception.

The KBY Brief

Fixed? Get the next one before it hits you: The KBY Brief

Practical fixes for the systems you run, by email about twice a week. Unsubscribe at any time.

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

After remediation

Further reading stays below the corrective workflow and is selected by platform, category and shared technical keywords.

Discover more

Connected KBY resources

Hand-Edited GPO Permissions in SYSVOL Drift From Active Directory and Never Show in GPMC Delegation