Sie sind auf Seite 1von 6

Using Update


Reviewing Update Manager

Update Manager is the tool that helps to patch

vSphere hosts and update VMware Tools
No longer does guest patching

Installs some 3rd party software on hosts

Cisco Nexus 1000v

Installed as a separate component and has its own

Accessed via plug-in in the VI Client

Baselines and Baseline Groups

Often there are many patches and upgrades

Too many to deal with individually

Baselines are groups of patches or other 3rd party


Baselines and Baseline Groups

Baseline Group is a selection of baselines

Makes management and application easier

Then attach those to a host or cluster

Can check compliance
Remediate if needed

Update Manager Firewall Ports

Update Manager may be on a different server

and network than vCenter
Need to be aware of network connectivity requirements

Ports between Update Manager and other objects

Talks to vCenter
Server on port 80

vSphere hosts connect

to the Update
Manager Web Server
on port 9084

Update Manager
connects to vSphere
hosts on port 902

Update Manager PlugIn connects to Update

Manager server on
port 8084

Update Manager Web

Server listens on port
9087 (SSL) for
uploading host
upgrade files

Connects to for
metadata information
on port 443 (SSL)

If any ports are already in use when Update Manager

is installed it will choose and open new ones
In the range of 9000 9100
Automatically opens these ports

Update Manager Download Service

Update Manager Download Service (UMDS) is

used if the Update Manager server cannot talk to
the Internet

Some pre-requirements
Installed on a 64-bit Windows OS
MS SQL database using a 32-bit ODBC connection
Dont install on same server as Update Manager (Why would you?)

Configured via CLI

Will show you in the lab

Configure a Shared Repository

Update Manager can use a shared

repository for downloading updates,
patches, etc
Something that you would manage
Example, approved updates stored there

Shared Repository created using UMDS

and can be
Local directory
Web server

vSphere Host Upgrades

Update Manager can be used to upgrade hosts to

vSphere 5.x
Upgrade from ESXi 4.x to ESXi 5.x
Migration from ESX 4.x to ESXi 5.x
Does NOT migrate hosts if they were upgraded from ESX 3.x to ESX 4.x

Done as an orchestrated rolling upgrade

DRS migrates VMs and puts hosts in maintenance mode
After hosts upgraded you can upgrade VMs and VMware Tools

vSphere Host Upgrade Steps

Configure Update Manager host and

cluster settings

Import an ESXi image in ISO format

Create a Host Upgrade baseline


Attach the newly created baseline to a

container (cluster, datacenter, or folder)

Scan the container

Review the scan results

Remediate the container

Troubleshooting Update Manager

Lots of things to cover

But use common sense

database connectivity
Internet connectivity from Update Manager or UMDS
free space on vSphere hosts when upgrading or patching
for conflicting updates in baselines

Highly suggest you read the Troubleshooting

section (Section 17) in the Update Manager Guide

Exporting Baselines

You can export and import patch baselines

between Update Manager installations using
Script is available in the Update Manager
Administration Guide (Section 16)

Generating Reports

Update Manager provides no reporting mechanism

Can generate reports yourself using Excel and MS
SQL Server Query
Not user friendly
Really wish theyd streamline this

Similar to the PowerCLI script there is a provided

SQL Query
Section 16 of the VMware Update Manager Administration Guide

Lab Update Manager

In this lab we will
Review the installation of Update Manager
Configure Update Manager
Discuss the different options
Create baselines and a baseline group
Attach the baseline group to objects
Scan the attached objects
Remediate objects as needed