Better Patch Policy version management in ZCC

Idea ID 2786656

Better Patch Policy version management in ZCC

Currently (ZCM 11.4) it is not easily possible to remove all older Patch Policy version. Currently you need to display a particular older Patch Patch Policy version and hit the "Delete Selected Version" button.

For easier handling there should be on option similar to what is available for bundles, to delete all old version, leaving behind only the current published and the Sandbox version.
9 Comments
Absent Member.
Absent Member.
Please note that new patch policies are created by schedule. We had an issue that ZCC interface lags on patch policy page. The first suggestion was to delete old versions. It took days due to the issue itself. Old versions also grow the database at every single customer. Automation of policy cleanup is desired.
Absent Member.
Absent Member.
We had the same issue at several customer sites; this needs to be fixed.
New Member.
Performance issue managing patch Policies, it's not workable now
Super Contributor.
Super Contributor.
We are just starting to see this issue ourselves. It's really nice that patch polices can be dynamically created/sandboxed - but there should at least be the same feature to enable automatic cleanup once a patch policy is out of sandbox and deployed/effective.
Absent Member.
Absent Member.
A zman option exist to clean up bundle version (zman bundle-delete-version (bdv)), why not implement the same for Patch Policies ?
Absent Member.
Absent Member.
The ZMAN option would do the job, but I'd still love something through the UI.
Frequent Contributor.
Frequent Contributor.
Please God do this. I just spent 4 hours doing this to fix a problem with deleting superceeded patches and I'm not even close to done. Just one button to delete all previous patches or an interface where it they can be selected would be heaven.
Absent Member.
Absent Member.
In ZENworks 2020 we have added a configuration setting that lets you configure how many old versions you want to retain for a bundle. You can retain All, None, or a specified number such as 5. Since a Patch policy is a bundle, this setting applies to Patch policies. So, if you set it to 5, the last 5 versions of a Patch policy is retained and all others are deleted. ZENworks 2020 is in beta now with an anticipated release date of September 2019. Darrin VandenBos ZENworks Product Manager
Absent Member.
Absent Member.
ZENworks 2020 has shipped. The new "Older Bundle Versions Retain Setting" lets you determine the number of bundles you want to retain. Since Patch Policies are bundles, the setting applies. The settings is under Configuration > Management Zone Settings > Bundle, Policy, and Content. At this level, it the setting applies to all bundle folders. You can override the setting at individual bundle folders. So, for example, you could retain a different number of Patch Policy versions than DAU versions than Remediation bundle versions by setting different retain values on the various Bundles\ZPM subfolders. Darrin VandenBos ZENworks Product Manager
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.