Forum Discussion
How are you managing Group Policy changes after AGPM end of support?
Hi, I’m interested in how organizations are handling Group Policy change management now that AGPM is no longer supported. In environments where GPOs are still heavily used, what are you relying on today for version history, change tracking, rollback and approvals? Are you continuing with AGPM, moving to products such as GPOADmin or Cayosoft, or mainly using native GPMC backups and PowerShell? I’m also interested in whether there is still a gap around having a clear web-based view of GPO history and changes, especially being able to understand exactly what changed and which users or computers may be affected before a change is applied. I’d be interested to hear how this is handled in real production environments and what parts of the process are still manual or difficult.
1 Reply
You need AGPM’s controlled editing, history, approval, and rollback after its support boundary. AGPM 4.0 reached end of support on April 15, 2026, so it is not a supported long-term control. Microsoft’s built-in option is GPMC: back up each GPO before approved changes, store the backup set in access-controlled storage, and document the change request, administrator, and rollback point in your ticketing system. GPMC supports backup, restore, copy, import, and reporting, but does not reproduce AGPM’s archive-and-approval workflow. For a pilot, export representative GPOs, practice restoring one in a lab, and confirm how security filtering, WMI filters, and links behave during rollback. If web-based approvals and detailed audit history are mandatory, evaluate a replacement through procurement and security; Microsoft does not designate a single successor. Keep AGPM only as a temporary, risk-accepted bridge with tested backups and a migration date.
