AGPM

Limit the GPO Versions Stored

Hello All,

Hope this post finds you in good health and spirit.

Limit the GPO Versions Stored

By default, all versions of every controlled Group Policy object (GPO) are retained in the archive on the AGPM Server. However, you can limit the number of versions retained for each GPO and delete older versions when that limit is exceeded.

When GPO versions are deleted, a record of the version remains in the history of the GPO, but the GPO version itself is deleted from the archive.

A user account with the AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure.

To limit the number of GPO versions stored

  1. In the Group Policy Management Console tree, click Change Control in the forest and domain in which you want to manage GPOs.
  2. In the details pane, click the AGPM Server tab.
  3. Select the Delete old versions of each GPO from the archive check box, and type the maximum number of GPO versions to store for each GPO, not including the current version. To retain only the current version, enter 0. The maximum must be no greater than 999.

Important

Only GPO versions displayed on the Unique Versions tab of the History window count toward the limit.

4. Click the Apply button.

Additional considerations

By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have List Contents and Modify Options permissions for the domain. You can prevent a GPO version from being deleted by marking it in the history as ineligible for deletion.

To do so, right-click the version in the history of the GPO and click Do Not Delete. So, that’s all in this blog. I will meet you soon with next stuff .Have a nice day !!!

Recommended content

How to Check the Active Directory Database Integrity

Disabling and Enabling the Outbound Replication

DFS Replication Service Stopped Replication

What is Strict Replication Consistency

The replication operation failed because of a schema mismatch between the servers involved

Troubleshooting ad replication error 8418 the replication operation failed because of a schema mismatch between the servers

How to export replication information in txt file

Repadmin Replsummary

Enabling the outbound replication

Disabling and enabling replication on schema master domain controller

How to enable strict replication consistency

How to prevent lingering objects replication in active directory

AD replication process overview

How to force active directory replication

Change notification in replication process

How to check replication partner for a specific domain controller

dcdiag test replications

Guys please don’t forget to like and share the post.Also join our WindowsTechno Community and where you can post your queries/doubts and our experts will address them .

You can also share the feedback on below windows techno email id.

If you have any questions feel free to contact us on admin@windowstechno.com also follow us on facebook@windowstechno to get updates about new blog posts.

How useful was this post?

Click on a star to rate it!

As you found this post useful...

Follow us on social media!

Was this article helpful?
YesNo

Vipan Kumar

He is an Active Directory Engineer. He has been working in IT industry for more than 10 years. He is dedicated and enthusiastic information technology expert who always ready to resolve any technical problem. If you guys need any further help on subject matters, feel free to contact us on admin@windowstechno.com Please subscribe our Facebook page as well website for latest article. https://www.facebook.com/windowstechno

Leave a Reply

Check Also
Close
Back to top button