Specifications

6 Attach Baselines and Baseline Groups to Objects on page 174
To view compliance information and remediate objects in the inventory against specific baselines and
baseline groups, you must first attach existing baselines and baseline groups to these objects.
7 Manually Initiate a Scan of ESX/ESXi Hosts on page 174
Before remediation, you should scan the vSphere objects against the attached baselines and baseline
groups. To run a scan of hosts in the vSphere inventory immediately, initiate a scan manually.
8 View Compliance Information for vSphere Objects on page 175
You can review compliance information for the virtual machines, virtual appliances, and hosts against
baselines and baseline groups that you attach.
9 Remediate Hosts Against an Upgrade Baseline on page 175
You can remediate ESX/ESXi hosts against a single attached upgrade baseline at a time. You can
upgrade or migrate all hosts in your vSphere inventory by using a single upgrade baseline containing
an ESXi 5.5 image.
10 Remediate Hosts Against Baseline Groups on page 178
You can remediate hosts against attached groups of upgrade, patch, and extension baselines. Baseline
groups might contain multiple patch and extension baselines, or an upgrade baseline combined with
multiple patch and extension baselines.
Configure Host Maintenance Mode Settings
ESX/ESXi host updates might require that the host enters maintenance mode before they can be applied.
Update Manager puts the ESX/ESXi hosts in maintenance mode before applying these updates. You can
configure how Update Manager responds if the host fails to enter maintenance mode.
For hosts in a container different from a cluster or for individual hosts, migration of the virtual machines
with vMotion cannot be performed. If vCenter Server cannot migrate the virtual machines to another host,
you can configure how Update Manager responds.
Hosts that are part of a Virtual SAN cluster can enter maintenance mode only one at a time. This is
specificity of the Virtual SAN clusters.
If a host is a member of a Virtual SAN cluster, and any virtual machine on the host uses a VM storage policy
with a setting for "Number of failures to tolerate=0", the host might experience unusual delays when
entering maintenance mode. The delay occurs because Virtual SAN has to migrate the virtual machine data
from one disk to another in the Virtual SAN datastore cluster. Delays might take up to hours. You can
workaround this by setting the "Number of failures to tolerate=1" for the VM storage policy, which results in
creating two copies of the virtual machine files in the Virtual SAN datastore.
Prerequisites
Connect the vSphere Client to a vCenter Server system with which Update Manager is registered, and on
the Home page, click Update Manager under Solutions and Applications. If your vCenter Server system is
part of a connected group in vCenter Linked Mode, you must specify the Update Manager instance to use,
by selecting the name of the corresponding vCenter Server system in the navigation bar.
Procedure
1 On the Configuration tab, under Settings, click ESX Host/Cluster Settings.
Chapter 7 Upgrading and Migrating Your Hosts
VMware, Inc. 169