6.0.2

3 Enable Remediation of PXE Booted ESXi Hosts on page 161
You can congure Update Manager to let other software initiate remediation of PXE booted ESXi
hosts. The remediation installs patches and software modules on the hosts, but typically the host
updates are lost after a reboot.
4 Import Host Upgrade Images and Create Host Upgrade Baselines on page 161
You can create upgrade baselines for ESXi hosts with ESXi 6.0 images that you import to the
Update Manager repository.
5 Create a Host Baseline Group on page 162
You can combine one host upgrade baseline with multiple patch or extension baselines, or combine
multiple patch and extension baselines in a baseline group.
6 Aach Baselines and Baseline Groups to Objects on page 163
To view compliance information and remediate objects in the inventory against specic baselines and
baseline groups, you must rst aach existing baselines and baseline groups to these objects.
7 Manually Initiate a Scan of ESXi Hosts on page 164
Before remediation, you should scan the vSphere objects against the aached 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 164
You can review compliance information for the virtual machines, virtual appliances, and hosts against
baselines and baseline groups that you aach.
9 Remediate Hosts Against an Upgrade Baseline on page 165
You can remediate ESXi hosts against a single aached upgrade baseline at a time. You can upgrade all
hosts in your vSphere inventory by using a single upgrade baseline containing an ESXi 6.0 image.
10 Remediate Hosts Against Baseline Groups on page 168
You can remediate hosts against aached 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
ESXi host updates might require that the host enters maintenance mode before they can be applied.
Update Manager puts the ESXi hosts in maintenance mode before applying these updates. You can
congure how Update Manager responds if the host fails to enter maintenance mode.
For hosts in a container dierent 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 congure how Update Manager responds.
Hosts that are part of a Virtual SAN cluster can enter maintenance mode only one at a time. This is
specicity 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 seing 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 seing the "Number of failures to tolerate=1" for the VM storage policy, which results in
creating two copies of the virtual machine les in the Virtual SAN datastore.
Prerequisites
Required privileges: VMware vSphere Update Manager.
vSphere Upgrade
158 VMware, Inc.