VMware vSphere Update Manager - 6.7 Installation Manual
vSphere Update Manager
Installation and
Administration Guide
17 APR 2018
VMware vSphere 6.7
vSphere Update Manager 6.7
vSphere Update Manager Installation and Administration Guide
You can find the most up-to-date technical documentation on the VMware website at:
https://docs.vmware.com/
If you have comments about this documentation, submit your feedback to
docfeedback@vmware.com
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
Copyright © 2009–2018 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc. 2
Contents
About Installing and Administering VMware vSphere Update Manager 9
Understanding Update Manager 10
1
Overview of the Update Manager Client Interfaces 11
Update Manager Client Interface in the vSphere Client 12
Update Manager Client Interface in the vSphere Web Client 12
About the Update Manager Process 13
Configuring the Update Manager Download Source 15
Downloading Updates and Related Metadata 15
Importing ESXi Images 17
Creating Baselines and Baseline Groups 17
Attaching Baselines and Baseline Groups to vSphere Objects 19
Scanning Selected vSphere Objects 20
Reviewing Scan Results 21
Staging Patches and Extensions to Hosts 21
Remediating Selected vSphere Objects 21
Installing, Upgrading, and Uninstalling Update Manager on a Windows
2
Operating System 24
System Requirements 24
Update Manager Hardware Requirements 25
Supported Windows Operating Systems and Database Formats 25
Update Manager Compatibility with vCenter Server , vCenter Server Appliance ,
vSphere Web Client , and vSphere Client 26
Required Database Privileges 26
Preparing the Update Manager Database 27
Create a 64-Bit DSN 28
About the Bundled Microsoft SQL Server 2012 Express Database Package 28
Maintaining Your Update Manager Database 28
Configure a Microsoft SQL Server Database Connection 29
Configure an Oracle Database 31
Installing Update Manager on Windows 33
Prerequisites for Installing the Update Manager Server on Windows 34
Obtain the Update Manager Installer 36
Install the Update Manager Server 36
Using the Update Manager Client Interface with Update Manager Server that Runs on
Windows 40
VMware, Inc.
3
vSphere Update Manager Installation and Administration Guide
Upgrading Update Manager that Runs on Windows 40
Upgrade the Update Manager Server 41
Upgrade the Update Manager Java Components 43
Uninstalling Update Manager that Runs on Windows 44
Uninstall the Update Manager Server that Runs on Windows 44
Best Practices and Recommendations for Update Manager Environment 44
Update Manager Deployment Models and Their Usage 45
Update Manager in the vCenter Server Appliance 46
3
Using the Update Manager Client Interfaces with Update Manager Service that Runs in the
vCenter Server Appliance 47
Start, Stop, or Restart Update Manager Service in the vCenter Server Appliance 47
Migrating Update Manager from Windows to the vCenter Server Appliance 48
4
Download and Run VMware Migration Assistant on the Source Update Manager Machine 49
Roll Back a Migration of vCenter Server Appliance with Update Manager 50
Configuring Update Manager 51
5
Update Manager Network Connectivity Settings 52
Change the Update Manager Network Settings 53
Configuring the Update Manager Download Sources 54
Configure Update Manager to Use the Internet as a Download Source 56
Add a New Download Source 57
Use a Shared Repository as a Download Source 58
Import Patches Manually 60
Configure the Update Manager Proxy Settings 60
Configure Checking for Updates 61
Configuring and Viewing Notifications 62
Configure Notifications Checks 63
View Notifications and Run the Notification Checks Task Manually 64
Types of Update Manager Notifications 65
Configuring Host and Cluster Settings 65
System Requirements for Using Quick Boot During Remediation 67
Configure Using Quick Boot During Host Remediation 67
Configure Host Maintenance Mode Settings 68
Configure Cluster Settings 69
Enable Remediation of PXE Booted ESXi Hosts 71
Take Snapshots Before Remediation 71
Configure Smart Rebooting 72
Configure the Update Manager Patch Repository Location 73
Run the VMware vSphere Update Manager Update Download Task 74
Update Manager Privileges 74
VMware, Inc. 4
vSphere Update Manager Installation and Administration Guide
Installing, Setting Up, and Using Update Manager Download Service 76
6
Compatibility Between UMDS and the Update Manager Server 77
Installing UMDS on a Windows Operating System 77
Install UMDS on a Windows Operating System 78
Installing and Upgrading UMDS on a Linux-Based Operating System 80
Supported Linux-Based Operating Systems and Databases for Installing UMDS 81
Configure PostgreSQL Database for UMDS on Linux 81
Install UMDS on a Linux OS 83
Uninstall UMDS from a Linux OS 84
Setting Up and Using UMDS 84
Set Up the Data to Download with UMDS 85
Change the UMDS Patch Repository Location 85
Configure URL Addresses for Hosts 86
Download the Specified Data Using UMDS 87
Export the Downloaded Data 88
Working with Baselines and Baseline Groups 90
7
Creating and Managing Baselines 92
Create and Edit Patch or Extension Baselines 92
Create and Edit Host Upgrade Baselines 102
Delete Baselines 109
Delete Baselines in the vSphere Web Client 110
Creating and Managing Baseline Groups 110
Create a Host Baseline Group 111
Create a Host Baseline Group in the vSphere Web Client 112
Create a Virtual Machine Baseline Group 113
Edit a Baseline Group 113
Edit a Baseline Group in the vSphere Web Client 114
Add Baselines to a Baseline Group 115
Remove Baselines from a Baseline Group 115
Delete Baseline Groups 116
Delete Baseline Groups in the vSphere Web Client 116
Attach Baselines and Baseline Groups to Objects 117
Attach Baselines and Baseline Groups to Objects in the vSphere Web Client 118
Detach Baselines and Baseline Groups from Objects 118
Detach Baselines and Baseline Groups from Objects in the vSphere Web Client 119
Scanning vSphere Objects and Viewing Scan Results 121
8
Manually Initiate a Scan of ESXi Hosts 121
Manually Initiate a Scan of Virtual Machines 122
Manually Initiate a Scan of a Container Object 122
VMware, Inc. 5
vSphere Update Manager Installation and Administration Guide
Schedule a Scan 123
Viewing Scan Results and Compliance States for vSphere Objects 124
Check Compliance of a vSphere Inventory Object 125
View Compliance Information for vSphere Objects in the vSphere Web Client 126
Review Compliance with Individual vSphere Objects 126
Compliance View 127
Compliance States for Updates 129
Baseline and Baseline Group Compliance States 130
Viewing Patch Details 132
Viewing Extension Details 132
Viewing Upgrade Details 133
Host Upgrade Scan Messages in Update Manager 134
Host Upgrade Scan Messages When Cisco Nexus 1000V Is Present 136
VMware Tools Status 137
Remediating vSphere Objects 139
9
Orchestrated Upgrades of Hosts and Virtual Machines 139
Remediating Hosts 140
Staging Patches and Extensions to ESXi Hosts 143
Stage Patches and Extensions to ESXi Hosts 143
Stage Patches and Extensions to ESXi Hosts in the vSphere Web Client 144
Remediation Specifics of ESXi Hosts 145
Remediating Hosts That Contain Third-Party Software 146
Remediating ESXi 6.0 or ESXi 6.5 Hosts Against ESXi 6.7 Image 147
Remediation Specifics of Hosts That Are Part of a vSAN Cluster 148
Remediating vSAN Clusters Against System Managed Baselines 149
Remediate Hosts Against Patch or Extension Baselines 150
Remediate Hosts Against Patch or Extension Baselines in the vSphere Web Client 151
Remediate Hosts Against an Upgrade Baseline 154
Remediate Hosts Against an Upgrade Baseline in the vSphere Web Client 155
Remediate Hosts Against Baseline Groups 158
Remediate Hosts Against Baseline Groups in the vSphere Web Client 159
Pre-Check Remediation Report 163
Remediating Virtual Machines 164
Rolling Back to a Previous Version 165
Remediate Virtual Machines 165
Upgrade VMware Tools on Power Cycle 166
Scheduling Remediation for Hosts and Virtual Machines 167
View Update Manager Events 168
10
Update Manager Events 168
VMware, Inc. 6
vSphere Update Manager Installation and Administration Guide
The Update Manager Patch Repository 179
11
Add or Remove Patches From a Baseline 179
Troubleshooting 181
12
Update Manager Client Interface Remains Visible in the vSphere Web Client After Uninstalling
Update Manager Server 181
Connection Loss with Update Manager Server or vCenter Server in a Single vCenter Server
System 182
Gather Update Manager Log Bundles 183
Gather Update Manager and vCenter Server Log Bundles 183
Log Bundle Is Not Generated 184
Host Extension Remediation or Staging Fails Due to Missing Prerequisites 184
No Baseline Updates Available 185
All Updates in Compliance Reports Are Displayed as Not Applicable 185
All Updates in Compliance Reports Are Unknown 186
VMware Tools Upgrade Fails if VMware Tools Is Not Installed 186
ESXi Host Scanning Fails 186
ESXi Host Upgrade Fails 187
The Update Manager Repository Cannot Be Deleted 187
Incompatible Compliance State 188
Updates Are in Conflict or Conflicting New Module State 189
Updates Are in Missing Package State 190
Updates Are in Not Installable State 190
Updates Are in Unsupported Upgrade State 191
Database Views 192
13
VUMV_VERSION 192
VUMV_UPDATES 193
VUMV_HOST_UPGRADES 193
VUMV_PATCHES 194
VUMV_BASELINES 194
VUMV_BASELINE_GROUPS 194
VUMV_BASELINE_GROUP_MEMBERS 195
VUMV_PRODUCTS 195
VUMV_BASELINE_ENTITY 195
VUMV_UPDATE_PATCHES 196
VUMV_UPDATE_PRODUCT 196
VUMV_ENTITY_SCAN_HISTORY 196
VUMV_ENTITY_REMEDIATION_HIST 196
VUMV_UPDATE_PRODUCT_DETAILS 197
VUMV_BASELINE_UPDATE_DETAILS 197
VUMV_ENTITY_SCAN_RESULTS 198
VMware, Inc. 7
vSphere Update Manager Installation and Administration Guide
VUMV_VMTOOLS_SCAN_RESULTS 198
VUMV_VMHW_SCAN_RESULTS 198
VMware, Inc. 8
About Installing and Administering VMware vSphere Update Manager
Installing and Administering VMware vSphere Update Manager provides information about installing,
configuring, and using VMware® vSphere Update Manager to scan and remediate the objects in your
vSphere environment. It also describes the tasks that you can perform to update your vSphere inventory
objects and make them compliant against attached baselines and baseline groups.
For scanning and remediation, Update Manager works with the following ESXi versions:
n
For VMware Tools and virtual machine hardware upgrade operations, Update Manager works with
6.0, ESXi 6.5, and ESXi 6.7.
n
For ESXi host patching operations, Update Manager works with ESXi 6.0, ESXi 6.5, and ESXi 6.7.
n
For ESXi host upgrade operations, Update Manager works withESXi 6.0, ESXi 6.5, and their
respective Update releases.
Intended Audience
This information is intended for anyone who wants to install, upgrade, migrate, or use Update Manager.
The information is written for experienced Windows or Linux system administrators who are familiar with
virtual machine technology and data center operations.
vSphere Client and vSphere Web Client
Instructions in this guide reflect the vSphere Client (an HTML5-based GUI). You can also use the
instructions to perform most of the tasks by using the vSphere Web Client (a Flex-based GUI).
Tasks for which the workflow differs significantly between the vSphere Client and the vSphere Web Client
have duplicate procedures that provide steps according to the respective client interface. The procedures
that relate to the vSphere Web Client, contain vSphere Web Client in the title.
VMware Glossary
VMware provides a glossary of terms that might be unfamiliar to you. For definitions of terms as they are
used in VMware technical documentation, go to http://www.vmware.com/support/pubs.
VMware, Inc.
9
Understanding Update Manager 1
Update Manager enables centralized, automated patch and version management for VMware vSphere
and offers support for VMware ESXi hosts, and virtual machines.
With Update Manager, you can perform the following tasks:
n
Upgrade and patch ESXi hosts.
n
Install and update third-party software on hosts.
n
Upgrade virtual machine hardware and VMware Tools.
Update Manager requires network connectivity with VMware vCenter Server. Each installation of
Update Manager must be associated (registered) with a single vCenter Server instance.
The Update Manager module consists of a server component and of a client component.
You can use Update Manager with either vCenter Server that runs on Windows or with the
vCenter Server Appliance.
If you want to use Update Manager with vCenter Server, you have to perform Update Manager
installation on a Windows machine. You can install the Update Manager server component either on the
same Windows server where the vCenter Server is installed or on a separate machine. To install
Update Manager, you must have Windows administrator credentials for the computer on which you install
Update Manager.
If your vCenter Server system is connected to other vCenter Server systems by a common vCenter
Single Sign-On domain, and you want to use Update Manager for each vCenter Server system, you must
install and register Update Manager instances with each vCenter Server system. You can use an
Update Manager instance only with the vCenter Server system with which it is registered.
From vSphere 6.5 and later, it is no longer supported to register Update Manager to a
vCenter Server Appliance during the installation of the Update Manager server on a Windows machine.
The vCenter Server Appliance delivers Update Manager as a service. Update Manager is bundled in the
vCenter Server Appliance.
The Update Manager client component is a plug-in that runs on the vSphere Web Client (Flex) and the
vSphere Client (HTML5). The Update Manager client component is automatically enabled after
installation of the Update Manager server component on Windows, and after deployment of the
vCenter Server Appliance.
VMware, Inc.
10
vSphere Update Manager Installation and Administration Guide
However, if you are using Update Manager server that runs on Windows, you can see the
Update Manager client component only in the vSphere Web Client. If you are using Update Manager with
the vCenter Server Appliance, the Update Manager client component is available in both the
vSphere Web Client and the vSphere Client.
You can deploy Update Manager in a secured network without Internet access. In such a case, you can
use the VMware vSphere Update Manager Download Service (UMDS) to download update metadata and
update binaries.
This chapter includes the following topics:
n
Overview of the Update Manager Client Interfaces
n
About the Update Manager Process
Overview of the Update Manager Client Interfaces
The Update Manager server has a client interface for the vSphere Web Client and the vSphere Client.
The Update Manager client interfaces do not require any installation, and are automatically enabled in the
vSphere Web Client and the vSphere Client after you install the Update Manager server component on
Windows, or deploy the vCenter Server Appliance.
When you use an Update Manager server instance that runs on Windows, you can use Update Manager
only with the vSphere Web Client. The vSphere Client does not support using Update Manager server
that runs on Windows and is connected to a vCenter Server instance that also runs on Windows. To use
Update Manager capabilities with the vSphere Client, use a vCenter Server Appliance where
Update Manager runs as a service.
If your vCenter Server system is connected to other vCenter Server systems by a common vCenter
Single Sign-On domain, and you have installed and registered more than one Update Manager instance,
you can configure the settings for each Update Manager instance. Configuration properties that you
modify are applied only to the Update Manager instance that you specify and are not propagated to the
other instances in the group. You can specify an Update Manager instance by selecting the name of the
vCenter Server system with which the Update Manager instance is registered from the navigation bar. In
vSphere 6.7, you can make configuration changes only by using the Update Manager client interface in
the vSphere Web Client.
For a vCenter Server system that is connected to other vCenter Server systems by a common vCenter
Single Sign-On domain, you can also manage baselines and baseline groups as well as scan and
remediate only the inventory objects managed by the vCenter Server system with which Update Manager
is registered.
The Update Manager client interface have two main views, administration view and compliance view.
n
Update Manager Client Interface in the vSphere Client
In the vSphere Client, the Update Manager client interface appears as tab Updates. The Updates
tab is a first-level tab and is last in the row of first-level tabs, following the Summary, the Monitor,
the Configure, the Permissions, and so on, tabs.
VMware, Inc. 11
vSphere Update Manager Installation and Administration Guide
n
Update Manager Client Interface in the vSphere Web Client
In the vSphere Web Client, the Update Manager client interface appears as tab Update Manager.
The Update Manager tab is a first-level tab and is last in the row of first-level tabs, following the
Summary, the Monitor, the Configure, the Permissions, and so on, tabs.
Update Manager Client Interface in the vSphere Client
In the vSphere Client, the Update Manager client interface appears as tab Updates. The Updates tab is
a first-level tab and is last in the row of first-level tabs, following the Summary, the Monitor, the
Configure, the Permissions, and so on, tabs.
In the Update Manager administration view in the vSphere Client, you have the following top-level tabs:
Home, Baselines, Updates, and ESXi Images.
Under each respective tab, you can perform the following tasks:
n
See statistics about non-compliant host and clusters in your vSphere environment.
n
Create and manage baselines and baseline groups.
n
Review the patch repository.
n
Import ESXi images.
To access the Update Manager compliance view in the vSphere Client, selected an inventory object such
as a data center, a cluster, or a host and click the Updates tab.
In the Update Manager compliance view, you can do the following tasks:
n
Check compliance and scan results for hosts and clusters.
n
Attach and detach baselines and baseline groups to hosts and clusters.
n
Generate a pre-check remediation report that lists recommended actions to ensure successful
remediation.
n
Stage patches or extensions to hosts.
n
Remediate hosts against patch, extension, and upgrade baselines. (Changing the default host and
cluster settings during remediation is not supported in vSphere 6.7).
n
Remediate hosts that are part of a vSAN cluster against system-managed baselines.
Remediation operations of virtual machines are not supported with the vSphere Client 6.7. Use the
vSphere Web Client to upgrade VMware Tools and the hardware version of the virtual machines in your
vSphere environment.
Update Manager Client Interface in the vSphere Web Client
In the vSphere Web Client, the Update Manager client interface appears as tab Update Manager. The
Update Manager tab is a first-level tab and is last in the row of first-level tabs, following the Summary,
the Monitor, the Configure, the Permissions, and so on, tabs.
VMware, Inc. 12
vSphere Update Manager Installation and Administration Guide
To see the Update Manager client interface in the vSphere Web Client, you must have the View
Compliance Status privilege.
To access the Update Manager administration view in the vSphere Web Client, click the
vSphere Web Client Home menu, and click Update Manager. From the Objects tab, click the IP Address
of the Update Manager instance you want to administer. Another way to navigate to the Update Manager
administration view is to click Go to Admin View while you are in the Update Manager compliance view.
In the Update Manager administration view in the vSphere Web Client, you have the following top-level
tabs: Getting Started, Monitor, and Manage.
Under the Monitor tab, you can perform the following tasks:
n
View Update Manager events
n
Review and check notifications
Under the Manage tab, you can perform the following tasks:
n
Configure the Update Manager settings.
n
Create and manage baselines and baseline groups.
n
Review the patch repository.
n
Import ESXi images.
To access the Update Manager compliance view in the vSphere Web Client, selected an inventory object
such as a data center, a cluster, a host, a VM, a vApp, and click the Update Manager tab.
In the Update Manager compliance view, you can do the following tasks:
n
View compliance and scan results for each selected inventory object
n
Attach and detach baselines and baseline groups from a selected inventory object.
n
Scan a selected inventory object.
n
Stage patches or extensions to hosts
n
Remediate hosts against patch, extension, and upgrade baselines
n
Remediate hosts that are part of a vSAN cluster against system-managed baselines
About the Update Manager Process
Upgrading vSphere objects and applying patches or extensions with Update Manager is a multistage
process in which procedures must be performed in a particular order. Following the suggested process
helps ensure a smooth update with a minimum of system downtime.
The Update Manager process begins by downloading information (metadata) about a set of patches and
extensions. One or more of these patches or extensions are aggregated to form a baseline. You can add
multiple baselines to a baseline group. A baseline group is a composite object that consists of a set of
nonconflicting baselines. You can use baseline groups to combine different types of baselines, and scan
and remediate an inventory object against all of them as a whole. If a baseline group contains both
upgrade and patch or extension baselines, the upgrade runs first.
VMware, Inc. 13
vSphere Update Manager Installation and Administration Guide
A collection of virtual machines and ESXi hosts or individual inventory objects can be scanned for
compliance with a baseline or a baseline group and later remediated. You can initiate these processes
manually or through scheduled tasks.
n
Configuring the Update Manager Download Source
You can configure the Update Manager server to download patches and extensions either from the
Internet or from a shared repository. You can also import patches and extensions manually from a
ZIP file.
n
Downloading Updates and Related Metadata
Downloading host patches, extensions, and related metadata is a predefined automatic process that
you can modify. By default, at regular configurable intervals, Update Manager contacts VMware or
third-party sources to gather the latest information (metadata) about available upgrades, patches, or
extensions.
n
Importing ESXi Images
You can upgrade the hosts in your environment to ESXi 6.7 by using host upgrade baselines. To
create a host upgrade baseline, you must first upload at least one ESXi 6.7 .iso image to the
Update Manager repository.
n
Creating Baselines and Baseline Groups
Baselines contain a collection of one or more patches, extensions, service packs, bug fixes, or
upgrades, and can be classified as patch, extension, or upgrade baselines. Baseline groups are
assembled from existing baselines.
n
Attaching Baselines and Baseline Groups to vSphere Objects
To use baselines and baseline groups, you must attach them to selected inventory objects such as
container objects, virtual machines, or hosts.
n
Scanning Selected vSphere Objects
Scanning is the process in which attributes of a set of hosts or virtual machines are evaluated
against all patches, extensions, and upgrades from an attached baseline or baseline group,
depending on the type of scan you select.
n
Reviewing Scan Results
Update Manager scans vSphere objects to determine how they comply with baselines and baseline
groups that you attach. You can filter scan results by text search, group selection, baseline selection,
and compliance status selection.
n
Staging Patches and Extensions to Hosts
You can stage patches and extensions before remediation to ensure that the patches and
extensions are downloaded to the host. Staging patches and extensions is an optional step that can
reduce the time during which hosts are in maintenance mode.
n
Remediating Selected vSphere Objects
Remediation is the process in which Update Manager applies patches, extensions, and upgrades to
ESXi hosts and virtual machines after a scan is complete.
VMware, Inc. 14
vSphere Update Manager Installation and Administration Guide
Configuring the Update Manager Download Source
You can configure the Update Manager server to download patches and extensions either from the
Internet or from a shared repository. You can also import patches and extensions manually from a ZIP file.
Configuring the Update Manager download source is an optional step.
If your deployment system is connected to the Internet, you can use the default settings and links for
downloading upgrades, patches, and extensions to the Update Manager repository. You can also add
URL addresses to download third-party patches and extensions. Third-party patches and extensions are
applicable only to hosts that are running ESXi 6.0 and later.
If your deployment system is not connected to the Internet, you can use a shared repository after
downloading the upgrades, patches, and extensions by using Update Manager Download Service
(UMDS).
For more information about UMDS, see Chapter 6 Installing, Setting Up, and Using Update Manager
Download Service.
With Update Manager, you can import both VMware and third-party patches or extensions manually from
a ZIP file, also called an offline bundle. Import of offline bundles is supported only for hosts that are
running ESXi 6.0 and later. You download the offline bundle ZIP files from the Internet or copy them from
a media drive, and save them on a local or a shared network drive. You can import the patches or
extensions to the Update Manager patch repository later. You can download offline bundles from the
VMware Web site or from the Web sites of third-party vendors.
Note You can use offline bundles for host patching operations only. You cannot use third-party offline
bundles or offline bundles that you generated from custom VIB sets for host upgrade from ESXi 6.0 and
ESXi 6.5 to ESXi 6.7.
For detailed descriptions of the procedures, see Configuring the Update Manager Download Sources.
Downloading Updates and Related Metadata
Downloading host patches, extensions, and related metadata is a predefined automatic process that you
can modify. By default, at regular configurable intervals, Update Manager contacts VMware or third-party
sources to gather the latest information (metadata) about available upgrades, patches, or extensions.
VMware provides information about patches for ESXi hosts.
Update Manager downloads the following types of information:
n
Metadata about all ESXi 6.x patches regardless of whether you have hosts of such versions in your
environment.
n
Metadata about ESXi 6.x patches as well as about extensions from third-party vendor URL
addresses.
n
Notifications, alerts, and patch recalls for ESXi 6.x hosts.
VMware, Inc. 15
vSphere Update Manager Installation and Administration Guide
Downloading information about all updates is a relatively low-cost operation in terms of disk space and
network bandwidth. The availability of regularly updated metadata lets you add scanning tasks on the
hosts at any time.
Update Manager supports the recall of patches for hosts that are running ESXi 6.0 or later. A patch is
recalled if the released patch has problems or potential issues. After you scan the hosts in your
environment, Update Manager alerts you if the recalled patch has been installed on a certain host.
Recalled patches cannot be installed on hosts with Update Manager. Update Manager also deletes all the
recalled patches from the Update Manager patch repository. After a patch fixing the problem is released,
Update Manager downloads the new patch to its patch repository. If you have already installed the
problematic patch, Update Manager notifies you that a fix was released and prompts you to apply the new
patch.
If Update Manager cannot download upgrades, patches, or extensions—for example, if it is deployed on
an internal network segment that does not have Internet access—you must use UMDS to download and
store the data on the machine on which UMDS is installed. The Update Manager server can use the
upgrades, patches, and extensions that UMDS downloaded after you export them.
For more information about UMDS, see Chapter 6 Installing, Setting Up, and Using Update Manager
Download Service.
You can configure Update Manager to use an Internet proxy to download upgrades, patches, extensions,
and related metadata.
You can change the time intervals at which Update Manager downloads updates or checks for
notifications. For detailed descriptions of the procedures, see Configure Checking for Updates and
Configure Notifications Checks.
Types of Software Updates and Related Terms
Update Manager downloads software updates and metadata from Internet depots or UMDS-created
shared repositories. You can import offline bundles and host upgrade images from a local storage device
into the local Update Manager repository.
Bulletin A grouping of one or more VIBs. Bulletins are defined within metadata.
Depot A logical grouping of VIBs and associated metadata that is published
online.
Host upgrade image An ESXi image that you can import in the Update Manager repository and
use for upgrading ESXi 6.0 or ESXi 6.5 hosts to ESXi 6.7.
Extension A bulletin that defines a group of VIBs for adding an optional component to
an ESXi host. An extension is usually provided by a third party that is also
responsible for patches or updates to the extension.
Metadata Extra data that defines dependency information, textual descriptions,
system requirements, and bulletins.
VMware, Inc. 16
vSphere Update Manager Installation and Administration Guide
Offline bundle ZIP An archive that encapsulates VIBs and corresponding metadata in a self-
contained package that is useful for offline patching. You cannot use third-
party offline bundles or offline bundles that you generated from custom VIB
sets for host upgrade from ESXi 6.0 or ESXi 6.5 to ESXi 6.7.
Patch A bulletin that groups one or more VIBs together to address a particular
issue or enhancement.
Roll-up A collection of patches that is grouped for ease of download and
deployment.
VIB A VIB is a single software package.
Importing ESXi Images
You can upgrade the hosts in your environment to ESXi 6.7 by using host upgrade baselines. To create a
host upgrade baseline, you must first upload at least one ESXi 6.7 .iso image to the Update Manager
repository.
With Update Manager 6.7 you can upgrade hosts that are running ESXi 6.0 or ESXi 6.5 to ESXi 6.7. Host
upgrades to ESXi 5.x, ESXi 6.0 or ESXi 6.5 are not supported.
Before uploading ESXi images, obtain the image files from the VMware Web site or another source. You
can create custom ESXi images that contain third-party VIBs by using vSphere ESXi Image Builder. For
more information, see Customizing Installations with vSphere ESXi Image Builder.
You can upload and manage ESXi images from the ESXi Images tab of the Update Manager
Administration view.
ESXi images that you import are kept in the Update Manager repository. You can include ESXi images in
host upgrade baselines. To delete an ESXi image from the Update Manager repository, first you must
delete the upgrade baseline that contains it. After you delete the baseline, you can delete the image from
the ESXi Images tab.
For more information about importing ESXi images and creating host upgrade baselines, see Create a
Host Upgrade Baseline in the vSphere Web Client.
Creating Baselines and Baseline Groups
Baselines contain a collection of one or more patches, extensions, service packs, bug fixes, or upgrades,
and can be classified as patch, extension, or upgrade baselines. Baseline groups are assembled from
existing baselines.
Host baseline groups can contain a single upgrade baseline, and various patch and extension baselines.
Virtual machine baseline groups can contain up to two upgrade baselines: one VMware Tools upgrade
baseline, and one virtual machine hardware upgrade baseline.
When you scan hosts and virtual machines, you evaluate them against baselines and baseline groups to
determine their level of compliance.
VMware, Inc. 17
vSphere Update Manager Installation and Administration Guide
Update Manager includes two predefined patch baselines and two predefined upgrade baselines. You
cannot edit or delete the predefined virtual machine baselines. You can use the predefined baselines, or
create patch, extension, and upgrade baselines that meet your criteria. Baselines you create, and
predefined baselines, can be combined in baseline groups. For more information about creating and
managing baselines and baseline groups, see Chapter 7 Working with Baselines and Baseline Groups.
Baseline Types
Update Manager supports different types of baselines that you can use when scanning and remediating
objects in your inventory.
Update Manager provides upgrade, patch, and extension baselines.
Upgrade Baselines
Baseline Description
Host Upgrade
Baseline
Virtual Machine
Upgrade Baseline
Defines to which version to upgrade the hosts in your environment. With Update Manager 6.7, you can
upgrade ESXi hosts from version 6.0 and 6.5 to ESXi 6.7.
Defines to which version to upgrade virtual hardware or VMware Tools. With Update Manager 6.7 you can
upgrade to hardware version vmx-14 and to the latest VMware Tools version on hosts that are running ESXi
6.7.
Patch Baselines
Patch baselines define a number of patches that must be applied to a given host. Patch baselines can be
either dynamic or fixed.
Baseline Description
Dynamic Patch
Baseline
Fixed Patch Baseline You manually specify which patches to include in the fixed patch baseline from the total set of patches
The contents of a dynamic baseline are based on available patches that meet the specified criteria. As the
set of available patches changes, dynamic baselines are updated as well. You can explicitly include or
exclude any patches.
available in the Update Manager repository.
Extension Baselines
Baseline Description
Extension
Baseline
Contains extensions (additional software such as third-party device drivers) that must be applied to a given host.
Extensions are installed on hosts that do not have such software installed on them, and patched on hosts that
already have the software installed. All third-party software for ESXi hosts is classified as a host extension,
although host extensions are not restricted to just third-party software.
VMware, Inc. 18
vSphere Update Manager Installation and Administration Guide
Update Manager Default Baselines
Update Manager includes default baselines that you can use to scan any virtual machine or host to
determine whether the hosts in your environment are updated with the latest patches, or whether the
virtual machines are upgraded to the latest version.
Critical Host Patches
Checks ESXi hosts for compliance with all critical patches.
(Predefined)
Non-Critical Host
Checks ESXi hosts for compliance with all optional patches.
Patches (Predefined)
VMware Tools Upgrade
to Match Host
(Predefined)
VM Hardware Upgrade
to Match Host
(Predefined)
Checks virtual machines for compliance with the latest VMware Tools
version on the host. Update Manager supports upgrading of VMware Tools
for virtual machines on hosts that are running ESXi 6.0.x and later.
Checks the virtual hardware of a virtual machine for compliance with the
latest version supported by the host. Update Manager supports upgrading
to virtual hardware version vmx-14 on hosts that are running ESXi 6.7.
Baseline Groups
Baseline groups can contain patch, extension, and upgrade baselines. The baselines that you add to a
baseline group must be non-conflicting.
A baseline group is limited to a combination of patches, extensions, and upgrades. The following are valid
combinations of baselines that can make up a baseline group:
n
Multiple host patch and extension baselines.
n
One upgrade baseline, multiple patch and extension baselines.
For example, one ESXi upgrade baseline and multiple ESXi patch or extension baselines.
n
Multiple upgrade baselines, but only one upgrade baseline per upgrade type (like VMware Tools,
virtual machine hardware, or host).
For example, VMware Tools Upgrade to Match Host baseline and VM Hardware Upgrade to Match
Host baseline.
Attaching Baselines and Baseline Groups to vSphere Objects
To use baselines and baseline groups, you must attach them to selected inventory objects such as
container objects, virtual machines, or hosts.
Although you can attach baselines and baseline groups to individual objects, a more efficient method is to
attach them to container objects, such as folders, vApps, clusters, and data centers. Individual vSphere
objects inherit baselines attached to the parent container object. Removing an object from a container
removes the inherited baselines from the object.
VMware, Inc. 19
vSphere Update Manager Installation and Administration Guide
For a detailed description of the procedure, see Attach Baselines and Baseline Groups to Objects in the
vSphere Web Client.
Scanning Selected vSphere Objects
Scanning is the process in which attributes of a set of hosts or virtual machines are evaluated against all
patches, extensions, and upgrades from an attached baseline or baseline group, depending on the type
of scan you select.
You can scan a host installation to determine whether the latest patches or extensions are applied, or you
can scan a virtual machine to determine whether it is up to date with the latest virtual hardware or
VMware Tools version.
Update Manager supports the following types of scan:
Host patch scan You can perform patch scans on ESXi 6.0 and later.
Host extensions scan You can scan ESXi 6.0 and later for extensions (additional software
modules).
Host upgrade scan You can scan ESXi 6.0 and ESXi 6.5 for upgrading to ESXi 6.5.
VMware Tools scan You can scan virtual machines running Windows or Linux for the latest
VMware Tools version. You can perform VMware Tools scans on online or
offline virtual machines and templates. You must power on the virtual
machine at least once before performing a VMware Tools scan.
Virtual machine
hardware upgrade scan
You can scan virtual machines running Windows or Linux for the latest
virtual hardware supported on the host. You can perform hardware-upgrade
scans on online or offline virtual machines and templates.
You can use VMware Studio 2.0 and later to automate the creation of ready-to-deploy vApps with pre-
populated application software and operating systems. VMware Studio adds a network agent to the guest
so that vApps bootstrap with minimal effort. Configuration parameters specified for vApps appear as OVF
properties in the vCenter Server deployment wizard. For more information about VMware Studio, see the
VMware SDK and API documentation for VMware Studio. For more information about vApp, you can also
check the VMware blog site. You can download VMware Studio from the VMware website.
You can initiate scans on container objects, such as data centers, clusters, or folders, to scan all the ESXi
hosts or virtual machines in that container object.
You can configure Update Manager to scan virtual machines and ESXi hosts against baselines and
baseline groups by manually initiating or scheduling scans to generate compliance information. Schedule
scan tasks at a data center or vCenter Server system level to make sure that scans are up to date.
For manual and scheduled scanning procedures, see Chapter 8 Scanning vSphere Objects and Viewing
Scan Results.
VMware, Inc. 20
vSphere Update Manager Installation and Administration Guide
Reviewing Scan Results
Update Manager scans vSphere objects to determine how they comply with baselines and baseline
groups that you attach. You can filter scan results by text search, group selection, baseline selection, and
compliance status selection.
When you select a container object, you view the overall compliance status of the container against the
attached baselines as a group. You also see the individual compliance statuses of the objects in the
selected container against all baselines. If you select an individual baseline attached to the container
object, you see the compliance status of the container against the selected baseline.
If you select an individual virtual machine, appliance, or host, you see the overall compliance status of the
selected object against all attached baselines and the number of updates. If you select an individual
baseline attached to this object, you see the number of updates grouped by the compliance status for that
baseline.
The compliance information is displayed on the Update Manager tab. For more information about viewing
compliance information, see Viewing Scan Results and Compliance States for vSphere Objects.
Staging Patches and Extensions to Hosts
You can stage patches and extensions before remediation to ensure that the patches and extensions are
downloaded to the host. Staging patches and extensions is an optional step that can reduce the time
during which hosts are in maintenance mode.
Staging patches and extensions to hosts that are running ESXi 5.0 or later lets you download the patches
and extensions from the Update Manager server to the ESXi hosts without applying the patches or
extensions immediately. Staging patches and extensions speeds up the remediation process because the
patches and extensions are already available locally on the hosts.
Important Update Manager can stage patches to PXE booted ESXi hosts.
For more information about staging patches, see Stage Patches and Extensions to ESXi Hosts in the
vSphere Web Client.
Remediating Selected vSphere Objects
Remediation is the process in which Update Manager applies patches, extensions, and upgrades to ESXi
hosts and virtual machines after a scan is complete.
Remediation makes the selected vSphere objects compliant with patch, extension, and upgrade
baselines.
As with scanning, you can remediate single hosts or virtual machines. You can also initiate remediation
on a folder, a cluster, or a data center level.
Update Manager supports remediation for the following inventory objects:
n
Powered on, suspended, or powered off virtual machines and templates for VMware Tools and virtual
machine hardware upgrade.
VMware, Inc. 21
vSphere Update Manager Installation and Administration Guide
n
ESXi hosts for patch, extension, and upgrade remediation.
You can remediate the objects in your vSphere inventory by using either manual remediation or
scheduled remediation. For more information about manual and scheduled remediation, see Chapter 9
Remediating vSphere Objects.
Remediating Hosts
Update Manager 6.7 supports upgrade from ESXi 6.0.x and ESXi 6.5.x to ESXi 6.7.
Important If you enable the setting from the ESX Host/Cluster Settings page of the Configuration tab,
or from the Remediate wizard, you can patch PXE booted ESXi hosts.
After you upload ESXi images, upgrades for ESXi hosts are managed through baselines and baseline
groups.
Typically, if the update requires it, hosts are put into maintenance mode before remediation. Virtual
machines cannot run when a host is in maintenance mode. To ensure a consistent user experience,
vCenter Server migrates the virtual machines to other hosts within a cluster before the host is put in
maintenance mode. vCenter Server can migrate the virtual machines if the cluster is configured for
vMotion and if VMware Distributed Resource Scheduler (DRS) and VMware Enhanced vMotion
Compatibility (EVC) are enabled. EVC is not a prerequisite for vMotion. EVC guarantees that the CPUs of
the hosts are compatible. For other containers or individual hosts that are not in a cluster, migration with
vMotion cannot be performed.
Important After you have upgraded your host to ESXi 6.7, you cannot roll back to your version ESXi
6.0.x or ESXi 6.5.x software. Back up your host configuration before performing an upgrade. If the
upgrade fails, you can reinstall the ESXi 6.0.x or ESXi 6.5.x software that you upgraded from, and restore
your host configuration. For more information about backing up and restoring your ESXi configuration,
see vSphere Upgrade.
Remediation of ESXi 6.0 and 6.5 hosts to their respective ESXi update releases is a patching process,
while the remediation of ESXi hosts from version 6.0 or 6.5 to 6.7 is an upgrade process.
Remediating Virtual Machines
You can upgrade VMware Tools, and the virtual hardware of virtual machines to a later version. Upgrades
for virtual machines are managed through the Update Manager default virtual machine upgrade
baselines.
Orchestrated Upgrades
With Update Manager, you can perform orchestrated upgrades of hosts and virtual machines. With
orchestrated upgrades, you can upgrade hosts and virtual machines in your vSphere inventory by using
baseline groups.
You can perform an orchestrated upgrade of hosts by using a baseline group that contains a single host
upgrade baseline and multiple patch or extension baselines. Update Manager first upgrades the hosts
and then applies the patch or extension baselines.
VMware, Inc. 22
vSphere Update Manager Installation and Administration Guide
You can perform an orchestrated upgrade of virtual machines by using a virtual machine baseline group
that contains the following baselines:
n
VM Hardware Upgrade to Match Host
n
VMware Tools Upgrade to Match Host
You can use orchestrated upgrades to upgrade the virtual hardware and VMware Tools of virtual
machines in the inventory at the same time. The VMware Tools upgrade baseline runs first, followed by
the virtual machine hardware upgrade baseline.
Orchestrated upgrades can be performed at a cluster, folder, or a data center level.
VMware, Inc. 23
Installing, Upgrading, and
Uninstalling Update Manager on
a Windows Operating System 2
You can install Update Manager server on a Windows virtual or physical machine and connect it to a
vCenter Server instance that also runs on Windows. You can later uninstall the Update Manager server. If
you are running Update Manager server of an earlier version, you can upgrade it to version 6.7.
n
System Requirements
To run and use the Update Manager server, you must ensure that your environment satisfies certain
conditions. You also must ensure that the vCenter Server and Update Manager are of compatible
versions.
n
Preparing the Update Manager Database
The Update Manager server and Update Manager Download Service (UMDS) that you install on
Windows require a database to store and organize server data. Update Manager supports Oracle,
Microsoft SQL Server databases.
n
Installing Update Manager on Windows
The Update Manager server is a 64-bit application. You can install the Update Manager server for
Windows only on 64-bit Windows machines.
n
Upgrading Update Manager that Runs on Windows
You can upgrade to Update Manager 6.7 only from Update Manager versions 6.0 or 6.5 that are
installed on a 64-bit Windows operating system.
n
Uninstalling Update Manager that Runs on Windows
Update Manager has a relatively small impact on computing resources such as disk space. Unless
you are certain that you want to remove Update Manager, leave an existing installation in place.
n
Best Practices and Recommendations for Update Manager Environment
You can install Update Manager on the server on which vCenter Server runs or on a different server.
System Requirements
To run and use the Update Manager server, you must ensure that your environment satisfies certain
conditions. You also must ensure that the vCenter Server and Update Manager are of compatible
versions.
VMware, Inc.
24
vSphere Update Manager Installation and Administration Guide
Before you install Update Manager on Windows, you must set up an Oracle or Microsoft SQL Server
database. If your deployment is relatively small and contains up to 5 hosts and 50 virtual machines, you
can use the bundled Microsoft SQL Server 2012 Express database, which you can select to install from
the Update Manager installation wizard.
You can install Update Manager on a physical server or on a virtual machine. You can install the
Update Manager server component on the same Windows machine as vCenter Server or on a different
machine. After you install the Update Manager server component, to use Update Manager, the
Update Manager client is automatically enabled on the vSphere Web Client.
If your vCenter Server system is connected to other vCenter Server systems by a common vCenter
Single Sign-On domain, you can install and register Update Manager instances with each vCenter Server
system.
Update Manager Hardware Requirements
You can run Update Manager on any system that meets the minimum hardware requirements.
Minimum hardware requirements for Update Manager vary depending on how Update Manager is
deployed. If the database is installed on the same machine as Update Manager, requirements for
memory size and processor speed are higher. To ensure acceptable performance, verify that your system
meets the minimum hardware requirements.
Table 2‑1. Minimum Hardware Requirements
Hardware Requirements
Processor Intel or AMD x86 processor with two or more logical cores, each with a speed of 2GHz
Network 10/100 Mbps
For best performance, use a Gigabit connection between Update Manager and the ESXi hosts
Memory 2GB RAM if Update Manager and vCenter Server are on different machines
8GB RAM if Update Manager and vCenter Server are on the same machine
Update Manager uses a SQL Server or Oracle database. You should use a dedicated database for
Update Manager, not a database shared with vCenter Server, and should back up the database
periodically. Best practice is to have the database on the same computer as Update Manager or on a
computer in the local network.
Depending on the size of your deployment, Update Manager requires a minimum amount of free space
per month for database usage. For more information about space requirements, see the VMware
vSphere Update Manager Sizing Estimator.
Supported Windows Operating Systems and Database Formats
Update Manager works with specific databases and operating systems.
The Update Manager server requires a 64-bit Windows system.
VMware, Inc. 25
vSphere Update Manager Installation and Administration Guide
To see a list of the supported Windows operating systems on which you can install the Update Manager
server and the UMDS, see Supported host operating systems for VMware vCenter Server installation.
The supported Windows operating systems for vCenter Server installation listed in the article also apply
for installation of the respective versions of the Update Manager server and the UMDS.
Note Make sure the Windows system on which you are installing the Update Manager server is not an
Active Directory domain controller.
The Update Manager server that you install on Windows requires a SQL Server or an Oracle database.
Update Manager can handle small-scale environments using the bundled in the installer SQL Server
2012 Express database. For environments with more than 5 hosts and 50 virtual machines, create either
an Oracle or a SQL Server database for Update Manager. For large-scale environments, set up the
Update Manager database on a different computer than the Update Manager server and the
vCenter Server database.
To see a list of database formats that are compatible with the Update Manager server and the UMDS,
select the Solution/Database Interoperability option from the VMware Product Interoperability Matrixes
at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
Update Manager Compatibility with vCenter Server , vCenter Server Appliance , vSphere Web Client , and vSphere Client
Update Manager 6.7 is compatible only with vCenter Server 6.7 and its components.
An Update Manager server that runs on Windows is only compatible with the vCenter Server that runs on
Windows and the vSphere Web Client.
The vCenter Server Appliance is packed with the Update Manager server, and after deployment runs
Update Manager as a service. The vCenter Server Appliance supports Update Manager client interfaces
in both the vSphere Client and the vSphere Web Client.
There are differences in the Update Manager user interface between the vSphere Client and the
vSphere Web Client. For example, in the vSphere Client you are unable to change Update Manager
configuration settings, or change default remediation options in the remediation wizard, or remediate
VMs. For such operations, use the vSphere Web Client.
Required Database Privileges
The set of database privileges needed for the Update Manager installation and upgrade differs from the
set of privileges needed for the Update Manager administration.
Before installing or upgrading Update Manager, you must grant adequate privileges to the database user.
VMware, Inc. 26
vSphere Update Manager Installation and Administration Guide
Table 2‑2. Database Privileges Needed for Installation or Upgrade of Update Manager
Database Privileges
Oracle Either assign the DBA role, or grant the following set of privileges to the Update Manager Oracle database
user.
n
connect
n
execute on dbms_lock
n
create view
n
create procedure
n
create table
n
create sequence
n
create any sequence
n
create any table
n
create type
n
unlimited tablespace
Microsoft SQL
Server
Make sure that the database user has either a sysadmin server role or the db_owner fixed database role on
the Update Manager database and the MSDB database. Although the db_owner role is required for the
upgrade, SQL jobs are not created as part of the Update Manager installation or upgrade.
To run Update Manager, you must grant a set of minimum privileges to the database user.
Table 2‑3. Database Privileges Needed for Using Update Manager
Database Privileges
Oracle The minimum required privileges of the Oracle database user are the following:
n
create session
n
create any table
n
drop any table
Microsoft SQL
Server
The database user must have either a sysadmin server role or the db_owner fixed database role on the
Update Manager database and the MSDB database.
Preparing the Update Manager Database
The Update Manager server and Update Manager Download Service (UMDS) that you install on
Windows require a database to store and organize server data. Update Manager supports Oracle,
Microsoft SQL Server databases.
Before installing the Update Manager server on a Windows machine, you must create a database
instance and configure it to ensure that all Update Manager database tables can be created in it. You can
install and configure the Microsoft SQL Server 2012 Express database that is embedded with
Update Manager. Microsoft SQL Server 2012 Express is recommended for small deployments of up to
5 hosts and 50 virtual machines.
Update Manager 6.7 server is a 64-bit application, and you can install it only on 64-bit machines.
Update Manager requires a 64-bit DSN.
To use Microsoft SQL Server and Oracle databases, you must configure a 64-bit system DSN and test it
with ODBC.
VMware, Inc. 27
vSphere Update Manager Installation and Administration Guide
The Update Manager database you use can be the same as the vCenter Server database. You can also
use a separate type of database, or you can use existing database clusters. For optimal results in a large-
scale environment, use a dedicated Update Manager database that runs on a different machine than the
vCenter Server system database.
The Update Manager server requires administrative credentials to connect to the database. If the
database user name and password change after you install the Update Manager server or UMDS on
Windows, you can reconfigure Update Manager and UMDS without the need to reinstall them. See the
Reconfiguring VMware vSphere Update Manager documentation.
Before you begin the database setup, review the supported databases. If you create an ODBC
connection to a database server that is not supported, a DSN for the unsupported database might be
displayed in the drop-down menu of the Update Manager installation wizard. For more information about
the supported database patches, see the Solution/Database Interoperability option from the VMware
Product Interoperability Matrixes at
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php. If you do not prepare your
database correctly, the Update Manager installer might display error or warning messages.
Create a 64-Bit DSN
The Update Manager 6.7 system must have a 64-bit DSN. This requirement applies to all supported
databases.
Procedure
1 From the Windows Start menu, select Control Panel > Administrative Tools > Data Sources
(ODBC).
2 Create a system DSN.
If you have a Microsoft SQL database, create the system DSN by using SQL Native Client version 10
or 11.
3 Test the connectivity.
The system now has a DSN that is compatible with Update Manager. When the Update Manager installer
prompts you for a DSN, select the 64-bit DSN.
About the Bundled Microsoft SQL Server 2012 Express Database Package
The Microsoft SQL Server 2012 Express database package is installed and configured when you select
Microsoft SQL Server 2012 Express as your database during the Update Manager installation or upgrade.
No additional configuration is required.
Maintaining Your Update Manager Database
After your Update Manager database instance and Update Manager server are installed and operational,
perform standard database maintenance processes.
VMware, Inc. 28
vSphere Update Manager Installation and Administration Guide
Maintaining your Update Manager database involves several tasks:
n
Monitoring the growth of the log file and compacting the database log file, as needed. See the
documentation for the database type that you are using.
n
Scheduling regular backups of the database.
n
Backing up the database before any Update Manager upgrade.
See your database documentation for information about backing up your database.
Configure a Microsoft SQL Server Database Connection
When you install Update Manager, you can establish an ODBC connection with a SQL Server database.
If you use SQL Server for Update Manager, do not use the master database.
See your Microsoft SQL ODBC documentation for specific instructions on configuring the SQL Server
ODBC connection.
Procedure
1 Create a SQL Server database by using SQL Server Management Studio on SQL Server.
The Update Manager installer creates all tables, procedures, and user-defined functions (UDF) within
the default schema of the database user that you use for Update Manager. This default schema does
not necessarily have to be dbo schema.
2 Create a SQL Server database user with database operator (DBO) rights.
Make sure that the database user has either a sysadmin server role or the db_owner fixed database
role on the Update Manager database and the MSDB database.
The db_owner role on the MSDB database is required for installation and upgrade only.
Create a New Data Source (ODBC)
To prepare a Microsoft SQL Server database to work with Update Manager, you have to create a data
source (ODBC).
Procedure
1 On your Update Manager server system, select Control Panel > Administrative Tools > Data
Sources (ODBC).
2 Click the System DSN tab.
VMware, Inc. 29
vSphere Update Manager Installation and Administration Guide
3 Create or modify an ODBC system data source.
Option Action
Create an ODBC system data source a Click Add.
b For Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2 Express,
Microsoft SQL Server 2012, or Microsoft SQL Server 2014 select SQL Native
Client, and click Finish.
Modify an existing ODBC system data
source
Double-click the ODBC system data source that you want to modify.
To see a detailed list of all Microsoft SQL Server database versions that are compatible with the
Update Manager server and the UMDS, select the Solution/Database Interoperability option from
the VMware Product Interoperability Matrixes at
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
4 In the Microsoft SQL Server DSN Configuration window, enter the necessary information and click
Next.
a Type an ODBC DSN in the Name text field.
For example, type VUM.
b (Optional) Type an ODBC DSN description in the Description text field.
c Select the SQL Server name from the Server drop-down menu.
Type the SQL Server machine name in the text field if you cannot find it in the drop-down menu.
5 Configure the SQL Server authentication, and click Next.
n
If you are using a local SQL Server, you can select Integrated Windows NT authentication.
n
If you are using a remote SQL Server, you must use the SQL Server authentication method.
If you use the SQL Server authentication method, in the Update Manager installation wizard supply
the same user name, password, and ODBC DSN that you used to configure the ODBC.
Important Update Manager does not support Windows authentication of the database when the
database is located on a different machine because of local system account issues. Make sure that if
the Update Manager database is on a remote machine, the database, and the system DSN use SQL
Server authentication.
6 Select a database from the Change the default database to drop-down menu, specify the ANSI
settings, and click Next.
7 Specify the language and translation settings, where to save the log files, and click Finish.
What to do next
To test the data source, in the ODBC Microsoft SQL Server Setup window, click Test Data Source, and
click OK. Ensure that SQL Agent is running on your database server by double-clicking the SQL Server
icon in the system tray.
VMware, Inc. 30
Loading...