This article provides instructions on how to incorporate a new version of a component baseline currently in the vCenter Lifecycle Manager Depot.
A Component Baseline cannot be updated to a newer version. Each version of a component requires creation of its own baseline. If you want to use a newer version of a component, and a baseline for that newer version is not already in the vCenter Lifecycle Manager Depot, it will have to be created.
For detailed instructions on creating a ZeroLock Agent Component Baseline, please refer to the article How to Create a ZeroLock® Agent Component Baseline in vCenter.
For this exercise, we are upgrading from ZeroLock Agent Component Version 3.1.16 to 3.1.17.
In the image below, you can see that we have two (2) ZeroLock Agent Component baselines, zerolock 3.1.16 and 3.1.17.
Navigate to Inventory | Updates | Baselines. Attach the ZeroLock Agent Component baseline for the new version. We selected zerolock 3.1.17, which shows the status of the Baseline as Missing.
Select zerolock-3.1.17 baseline by checking the box next to it, then click CHECK COMPLIANCE followed by REMEDIATE. Wait for the remediation task to complete before proceeding.
NOTE: The ESXi host will be rebooted as part of the remediation process.
After the host reboots, you will see that the status of the zerolock-3.1.17 baseline has changed to Installed, and the status of zerolock-3.1.16 baseline has changed to Obsoleted By Host.
The ZeroLock Management Console should now display the new version.
As a best practice, baselines that are Obsoleted By Host should be detached. To detach the ZeroLock Agent Component Version 3.1.16 baseline, select DETACH under the ATTACHED BASELINES section then, in the dialog box that appears, select the baseline then the DETACH button.
You have successfully upgraded the ZeroLock Agent Component baseline.