Cool Solutions

Mandatory baselines being removed in ZENworks 2017 Patch Management

Darrin VandenBos


August 10, 2016 10:35 am





Patch policies were introduced in the ZENworks 11 SP3 release with the intent to eventually replace the Mandatory Baseline functionality. Mandatory baselines can be used to deploy a base set of specific patches to a group of devices. Patch policies provide the same capability (deploying specific patches), but add the flexibility to deploy patches via rules as well, ensuring that devices continually receive any new patches that meet the rule criteria.

The transition period has come to an end, and we are removing mandatory baselines from the ZENworks 2017 release. If you are still using mandatory baselines, ZENworks 2017 will convert your baselines into Patch policies. One of our Patch Management engineers, Navdeep Grover, put together the following video to show you the conversion process:

Conversion of Mandatory Baselines to Patch Policies Video

To prepare to use Patch policies, you can review the following resources:

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Tags: , , , ,
Categories: Unified Endpoint Management, ZENworks, ZENworks Configuration Management, ZENworks Patch Management, ZENworks Suite


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.