Before you update or upgrade an ESXi host or a container object with vSphere Lifecycle Manager baselines, you must first check its compliance status.

You use vSphere Lifecycle Manager to check the compliance status of ESXi hosts against the baselines and baseline groups that you attach to the hosts or to a parent container object. You do a compliance check on hosts to determine whether they have the latest patches or extensions. During the compliance check, attributes of the host are evaluated against all patches, extensions, and upgrades from an attached baseline or baseline group.

You can check the compliance status of a single ESXi host or a valid container object. Supported groups of ESXi hosts include virtual infrastructure container objects such as folders, clusters, and data centers. When you initiate a compliance check for a container object, vSphere Lifecycle Manager scans all the ESXi hosts in that container object.

Note: If you initiate a compliance check for an inventory object, for example data center, that contains clusters that use vSphere Lifecycle Manager images, the compliance check is not performed for those clusters. Operations

To generate compliance information, you can initiate compliance checks manually or you can schedule the compliance checks to run at regular periods. Schedule compliance checks at a data center or vCenter Server system level to make sure that the objects in your inventory are up-to-date.

You check the compliance status of vSphere objects from the vSphere Lifecycle Manager compliance view.

To initiate or schedule compliance checks, you must have the Scan for Applicable Patches, Extensions, and Upgrades privilege.

For more information about managing users, groups, roles, and permissions, see the vSphere Security documentation.

For a list of all vSphere Lifecycle Manager privileges and their descriptions, see vSphere Lifecycle Manager Privileges For Using Baslines.