VMware

VMware Update Manager 1.0 Update 3 Release Notes


VMware Update Manager 1.0 Update 3 | 10/16/2008 | Build 63985

What's in the Release Notes

The release notes cover the following topics:

These release notes provide information on VMware Update Manager, an optional module for VMware VirtualCenter. For information on new VirtualCenter features, requirements, and installation, see the release notes for your product.

Note: In many public documents, VMware ESX Server 3.5 is now known as VMware ESX 3.5, and VMware ESX Server 3i as VMware ESXi 3.5. These release notes use the earlier convention to match the product interfaces and documentation. The name of the Virtual Appliances Development Kit (VADK) has changed to VMware Studio, but the Update Manager documentation uses the earlier name of this product. A future release will update the product names.

Installation Notes

This section includes information about the installation of Update Manager and its optional modules.

Update Manager

Update Manager installation requires network connectivity with an existing VirtualCenter Server 2.5 or higher. Each installation of Update Manager must be associated with a single VirtualCenter Server instance. The Update Manager module consists of a plug-in that runs on the VMware Infrastructure Client, and a server component that can be installed on the same system as the VirtualCenter Server or on a different system.

The following matrix lists the compatibility of Update Manager versions against VirtualCenter Server and VI Client:

Compatibility Matrix
 
VirtualCenter Server
VI Client
 
2.5
2.5
Update 1
2.5
Update 2
2.5
Update 3
2.5
2.5
Update 1
2.5
Update 2
2.5
Update 3
Update Manager 1.0
Yes
No
No
No
Yes
No
No
No
Update Manager 1.0 Update 1
No
Yes
No
No
No
Yes
No
No
Update Manager 1.0 Update 2
No
No
Yes
No
No
No
Yes
No
Update Manager 1.0 Update 3
No
No
No
Yes
No
No
No
Yes

Update Manager Download Service

The optional Update Manager Download Service (UMDS) installer requires a database. The installation program includes an option to create a SQL Server 2005 Express database, or use an existing Microsoft SQL Server or Oracle database.

VMware Infrastructure Update Manager – PowerShell Library

The VMware Update Manager – PowerShell Library is a set of commandlets for scanning and remediating virtual machines or hosts, downloading software updates, and creating baselines. It can be installed and used on any machine that has VMware Infrastructure Toolkit (for Windows) installed and access to a VirtualCenter Server.

VMware Infrastructure Update Manager – PowerShell Library is an experimental feature and is supported only in English.

During the installation of the Update Manager, you can select to install the optional VMware Infrastructure Update Manager – PowerShell Library.

Upgrade Notes

This release allows upgrades from all previous Update Manager versions.

Upgrading Update Manager

To upgrade Update Manager to Update Manager 1.0 Update 3, you must first upgrade VirtualCenter to VirtualCenter 2.5 Update 3.

Note: Before you start the upgrade, you must stop the Update Manager service.

When a VI Client 2.5 Update 3 instance connects to the VirtualCenter Server 2.5 Update 3 instance (and Update Manager 1.0 Update 3), the VI Client detects the correct Update Manager plug-in version and tries to load it. If the necessary Update Manager 1.0 Update 3 plug-in version is not available, the VI Client prompts you to install it and provides a way to download it.

Use the unified installer for the Update Manager upgrade or installation.

On the VirtualCenter Server Information page of the upgrade wizard, enter the VirtualCenter Server IP and credentials from the original installation to keep the Update Manager's registration with the VirtualCenter Server valid.

Upgrading Update Manager Download Service

Update Manager Download Service (UMDS) and Update Manager must be of the same version. To upgrade the UMDS:

  1. Upgrade Update Manager.

    During the Update Manager upgrade, the database schema will be upgraded, but the data in the database is retained.
  2. Upgrade Update Manager Download Service.

    The binaries for UMDS are located in the umds folder on the installation CD, or a extracted zip binary. The Installation wizard upgrades the UMDS from the older to the newer version.

To obtain the new update metadata and to update the already existing information in the database, download the ESX Server patches and import them to the machine on which Update Manager server is installed.

To confirm that the upgrade of UMDS was successful, ensure it can download and import patches to Update Manager 1.0 Update 3. For example, to download the ESX Server host patches and to import them to Update Manager 1.0 Update 3 server:

  1. Log in to the machine on which Update Manager Download Service is installed.
  2. Select Start > Run, type cmd, and press Enter.
  3. Change to the directory where UMDS is installed.

    The default folder is C:\Program Files\VMware\Infrastructure\Update Manager.
  4. Set up a download of all ESX Server host updates by running the following command:

    vmware-umds -S -h true -w false -l false
  5. Run the program to download updates:

    vmware-umds -D
  6. Export the patches to a portable storage device or a shared folder by running the following command:

    vmware-umds -E --dest <repository_path>

    Here, <repository_path> is the full path to your export directory.

    To include only the updates downloaded in step 4, use the download start time option (-s). For example, to export only the updates downloaded after October 03, 2008, run the following command:

    vmware-umds -E --dest <repository_path> -s 2008-10-03T00:00:00
  7. Import the patches to the machine on which Update Manager server is installed.

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. The minimum requirements to ensure acceptable performance are as follows:

  • 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 ESX Server hosts.
  • Memory:
    • 2GB RAM if Update Manager and the VirtualCenter Server are on different machines
    • 4GB RAM if Update Manager and the VirtualCenter Server are on the same machine

Disk storage requirements vary depending on your deployment. For more information, see the VMware Update Manager Sizing Estimator.

Interoperability and Supported Operating Systems

Update Manager can scan and remediate a variety of ESX Server hosts, virtual machines, virtual appliances, and applications.

ESX Server Scanning and Remediation

  • ESX Server 3.5 or higher
  • ESX Server 3i or higher
  • ESX Server 3.0.3

Virtual Machine Scanning and Remediation
  • Windows XP Professional, SP2 Required, 32 bit
  • Windows XP Professional 64 bit
  • Windows 2003 Datacenter
  • Windows 2000 Server, SP4 with Update Rollup 1
  • Windows 2000 Professional, SP4 Required
  • Windows Server 2003, SP1 Required
  • Windows Server 2003 R2
  • Windows Server 2003 x64
  • Windows Server 2003 Standard/Web, 32-bit and 64-bit
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Business (x64)
  • Windows Vista Enterprise (x64)

Virtual Machine Scanning
  • Red Hat Enterprise Linux AS 3.0 (Update 5 Required)
  • Red Hat Enterprise Linux ES 3.0 (Update 5 Required)
  • Red Hat Enterprise Linux AS 4.0 (Update 2 Required)
  • Red Hat Enterprise Linux ES 4.0 (Update 2 Required)

Application Scanning and Remediation:
  • Internet Information Server (IIS)
  • Windows Media Player, version 7.0 or higher
  • Microsoft SQL Server versions 7.0/2000/2005
  • Microsoft SQL Server Desktop Edition (MSDE) version 1.0 or higher
  • Exchange 2000 Server and Exchange Server 5.0
  • Internet Explorer version 4.0 or higher
  • Outlook Express version 4.01 or higher
  • Microsoft Site Server 3.0
  • ISA Server 2000
  • Microsoft .NET Framework, version 1.0 or higher
  • Microsoft Data Access Components (MDAC) 2.5 or higher
  • BizTalk Server 2000 or higher
  • SNA Server 4.0
  • Host Integration Server 2000
  • WinZip 8.1 or higher
  • Apache 1.3 and 2.0
  • Firefox 1.0 or higher
  • RealPlayer 10 or higher
  • Adobe Acrobat Reader

Resolved Issues

The following known issues in Update Manager 1.0, Update Manager 1.0 Update 1, and Update Manager 1.0 Update 2 have been resolved in Update Manager 1.0 Update 3:

  • VMware Update Manager Installation Wizard Is No Longer Interrupted When Upgrading Update Manager
    When Update Manager is updated to Update Manager 1.0 Update 2, the VMware Update Manager Installation Wizard might be interrupted due to the absence of the msvcr71.dll file in C:\WINDOWS\System32, displaying an error message similar to the following:
    The wizard was interrupted, please run the installation again.
    This release fixes the issue.
  • Update Manager Can Be Upgraded with an ISO Image File
    When VirtualCenter is updated to VirtualCenter 2.5 Update 2 by using an ISO image file, Update Manager might fail to update to Update Manager 1.0 Update 2 with a message similar to the following:
    Please insert the Disk: 1
    This release fixes the issue.
  • A Blank Pop-Up Window Appears When Update Manager Server Becomes Unavailable
    This release fixes an issue where an additional blank pop-up window is displayed along with the regular service down message, when the Update Manager client plug-in is enabled and the Update Manager server becomes unavailable.
  • Update Manager Schedules Download of Update Without Failure
    This release fixes an issue where Update Manager might fail to schedule download of updates using the Schedule Update Download Wizard, with an error message similar to the following:
    object reference not set to an instance of an object
  • Update Manager Supports Subsequent Downloads of ESX Server Host Patches
    This release fixes an issue where if ESX Server host patches are removed from the patch repository on the disk, Update Manager fails to download the patches again.

Known Issues

Please refer the known issues associated with the previous releases. Except for the issues listed in this section and in the Resolved Issues section of these release notes, all known issues are the same as with previous releases. For more information, refer Update Manager 1.0 Release Notes, Update Manager 1.0 Update 1 Release Notes, and Update Manager 1.0 Update 2 Release Notes.

The Known Issues are grouped as follows:

Installing and Upgrading

  • Baseline Updates Might Not Be Available Even If Update Manager Has Downloaded Information of the Updates
    When Update Manager is installed without being connected to the Internet, or with disabled Internet proxy settings, Update Manager will not be able to download metadata of available updates, and no baseline updates will be available. After Update Manager installation, if the Update Manager configuration is modified to work with an Internet proxy server, and the metadata of updates is downloaded or imported using the Update Manager command-line interface, the Update Repository tab displays information of the updates, but the Baseline tab might not display any information. A message similar to the following might be displayed in the Baseline tab:
    Baseline can not be created as there is not updates on update manager server........
    Workaround: To enable the Baseline tab to display baseline updates, restart the VI Client or re-enable Update Manager on a VI Client.
  • VirtualCenter Server Might Fail to Display the Upgraded Version of Update Manager
    When Update Manager is upgraded, the Available tab in the Plugin Manager window might fail to update the version of the installed Update Manager. However, the Installed tab in the Plugin Manager window displays the correct Update Manager version.
    Workaround: To enable the Available tab to display the correct version of the installed Update Manager, restart the VirtualCenter Server.

Scanning and Remediation

  • An Operation to Scan Powered Off Linux Virtual Machines for Updates Might Fail When ESX Server Host Is Added Back to the VirtualCenter Inventory
    When an ESX Server host with Linux virtual machines is removed from the VirtualCenter Server and added back to the VirtualCenter inventory with the Linux virtual machines in the powered off state, an operation to scan the powered off Linux virtual machines for updates might fail with a message similar to the following:
    The server database does not support the Software Inventory for the target.
    Workaround:When an ESX Server host with Linux virtual machines is added back to the VirtualCenter inventory, power on the Linux virtual machines and scan them for updates at least once, before scanning the virtual machines when they are powered off.
  • Update Manager Might Fail to Scan Supported Versions of Linux Virtual Machines for Updates
    During the creation of a Linux virtual machine, when a Linux operating system that is not supported by Update Manager is defined as the operating system of the Linux virtual machine, but the virtual machine is installed with a Linux operating system that is supported by Update Manager, an operation to scan the supported Linux virtual machine might fail, with an error message similar to the following:
    The attempted operation cannot be performed on the object.
    Workaround: Change the defined Linux operating system version of the virtual machine to match the version that is actually installed, and scan the virtual machine for updates.
    To change the Linux operating system defined for the virtual machine:
    1. Right-click the Linux virtual machine that you are unable to scan for updates, and select Edit Settings
    2. In the Options tab, edit the General Options setting and change the guest operating system version to match the Linux operating system that is installed on the virtual machine.
  • Scanning or Remediating Virtual Machine Might Fail During VMotion Migration
    Update Manager might fail to scan or remediate virtual machines, if they are migrated while they are being scanned or remediated. Error messages similar to the following might be displayed:
    There are errors during the scan operation.
    There are errors during the remediate operation.
    Workaround: Ensure that virtual machines remain on the same ESX Server Host, while the virtual machines are being scanned or remediated by Update Manager.
  • Remediate Operation Might Fail on DPM Enabled DRS Cluster
    When VMware Distributed Power Management (DPM) is enabled on a VMware DRS enabled cluster, an operation to remediate the cluster using Update Manager might fail with a message similar to the following:
    There are errors during remediation process
    Workaround: When remediating DRS enabled clusters, disable DPM:
    1. Right-click the DRS enabled cluster, and select Edit Settings.
    2. In the <Cluster_Name> Settings window, select Power Management.
    3. Click the Off radio button, to disable DPM on the cluster.
  • Remediate Operation Might Fail on Clusters That Have VMware HA Strict Admission Control and VMware DRS with DPM Enabled
    On a cluster, when VMware HA is enabled with the option Prevent VMs from being powered on if they violate availability constraints, and VMware DRS is enabled with Automatic as the power management DPM option, an operation to remediate the cluster using Update Manager might fail with a message similar to the following:
    There are errors during remediation process
    Workaround: When remediating VMware HA and VMware DRS with DPM enabled clusters, disable VMware HA strict admission control, and VMware DPM:
    1. Right-click the VMware HA and VMware DRS enabled cluster, and select Edit Settings.
    2. In the <Cluster_Name> Settings window, select VMware HA.
    3. Click the Allow VMs to be powered on even if they violate availability constraints radio button, to disable VMware HA strict admission control.
    4. In the <Cluster_Name> Settings window, select Power Management.
    5. Click the Off radio button, to disable DPM on the cluster.
    For more information on implications of enabling or disabling VMware HA strict admission control when using DRS and VMware DPM, refer KB 1007006.

Using Update Manager

  • Update Manager Client Plug-In Disconnects from VI Client Intermittently
    The Update Manager Client plug-in might unload from the VI Client when the Update Manager Client is momentarily disconnected from the Update Manager server.
    Workaround: Re-enable the Update Manager plug-in in the VI Client.