Local Administrators Removed From Member Servers After a Restricted Groups GPO Applies
Overview
When a Restricted Groups GPO reaches member servers with an incomplete Members list, Windows removes every unlisted member of Administrators at the next refresh. Confirm with event 4733 and gpresult, back up the GPO, then restore the known-good version or disable the link and re-add the removed members.
Diagnose
Symptom
What responders observe.
Use it when administrators report that they have lost local admin rights on member servers shortly after a Group Policy change, and the server's Security log shows event 4733, "A member was removed from a security-enabled local group", for the Administrators group.
Windows writes a separate 4733 for every removed member, usually preceded by event 4735, and only when the Audit Security Group Management subcategory is audited.
The usual cause is a new GPO linked to a server OU, or an edit that shortened an existing Members list.
If the 4733 events name a person in the Subject field at a time that matches nobody's policy change, treat it as a possible unauthorised change and escalate to security before you touch anything.
Detection
Metrics, logs and confirmation commands.
Root cause
Why the incident occurred.
Contain and prevent
Blast radius
What else this can affect.
Prevention
Controls and guardrails that stop it recurring.
-
Restricted Groups is policy-enforced security: whatever the Members list says is what the group becomes, every time policy applies.
-
Write the full intended membership into the list, including the server admin group, and keep a dated Backup-GPO before every edit.
-
Test a new list on a pilot OU with Get-LocalGroupMember before linking it widely.
-
When the goal is only to put a group into Administrators, Microsoft's steps use the entry's "This group is a member of" section, which adds the group as a member of another group, rather than "Members of this group", which defines the whole membership.
-
For devices managed by MDM, Microsoft recommends the LocalUsersandGroups policy from Windows 10 version 20H2, and says not to apply it together with RestrictedGroups on the same device.
-
While you are there, also review unconstrained Kerberos delegation on member servers and what Protected Users does to service and computer accounts.
Fix
Pre-flight checks
Check these before you change anything.
-
An account that still has local admin rights on an affected server, or the built-in Administrator and its password.
-
The Group Policy PowerShell module on an admin workstation.
-
Edit rights on the GPO and its links, or the GPO owner on hand.
-
An existing folder or share for GPO backups.
Commands
Get-LocalGroupMember -Group "Administrators"
Get-WinEvent -FilterHashtable @{ LogName='Security'; Id=4733; StartTime=(Get-Date).AddDays(-1) }
gpresult /scope computer /z > C:\IR\rsop-computer.txt
Get-GPInheritance -Target "OU=Servers,DC=contoso,DC=com"
Get-GPO -Name "Server Hardening"
Get-GPOReport -Name "Server Hardening" -ReportType HTML -Path C:\IR\server-hardening-now.html
Get-GPPermission -Name "Server Hardening" -TargetName "CONTOSO\GPO Admins" -TargetType Group
Set-GPLink -Name "Server Hardening" -Target "OU=Servers,DC=contoso,DC=com" -LinkEnabled No -WhatIf
Backup-GPO -Name "Server Hardening" -Path C:\IR\GpoBackups -Comment "Before Restricted Groups incident fix"
Restore-GPO -BackupId <known-good-backup-id> -Path \\FS01\GpoBackups -WhatIf
Restore-GPO -BackupId <known-good-backup-id> -Path \\FS01\GpoBackups
Set-GPLink -Name "Server Hardening" -Target "OU=Servers,DC=contoso,DC=com" -LinkEnabled No
gpupdate /target:computer /force
Add-LocalGroupMember -Group "Administrators" -Member "CONTOSO\Server Admins"
Verify and recover
Verification
Evidence required before you close the incident.
-
Run Get-LocalGroupMember -Group "Administrators" on each affected server. — The current members of Administrators. — Every member recorded from the 4733 events is present.
-
Run gpresult /scope computer /z after the refresh. — Computer RSoP output. — The Restricted Groups entry is corrected or no longer comes from this GPO. Have a member of the restored admin group perform a task that needs local admin, then check the Security log after the next refresh. — Successful task; Security log. — No new 4733 events for Administrators.
Rollback
The safe way back.
-
Run Restore-GPO -BackupId <incident-backup-id> -Path C:\IR\GpoBackups to return the GPO to the state captured before the fix, then refresh policy.
-
Run Set-GPLink -Name "Server Hardening" -Target "OU=Servers,DC=contoso,DC=com" -LinkEnabled Yes to re-enable a disabled link.
-
Run Remove-LocalGroupMember -Group "Administrators" -Member <member> to undo a member added by hand.
Escalate when
Conditions that need another owner.
-
The GPO reaches domain controllers: escalate to the directory owners at once and do not refresh policy on a DC yourself.
-
No account with admin rights works on an affected server, including the built-in Administrator.
-
The 4733 Subject is a person, not a policy change, or the GPO changed without a change record.
-
After the fix and a refresh, members are still being removed.
-
GPO owner Security incident lead.
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.
Sources
Based on the vendor sources listed below. Check each step against your environment before acting.
First published 21 November 2026
Policy CSP - RestrictedGroups
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Define security templates by using the Security Templates snap-in
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
4733(S) A member was removed from a security-enabled local group
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Get-LocalGroupMember
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Add-LocalGroupMember
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Remove-LocalGroupMember
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Get-WinEvent
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
gpresult
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
gpupdate
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Get-GPInheritance
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Get-GPO
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Get-GPOReport
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Backup-GPO
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Restore-GPO
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Get-GPPermission
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Set-GPPermission
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.
Set-GPLink
Cited for: Supports the documented platform behaviour, diagnosis or recovery controls used by this Runbook.