VMware

VMware Update Manager 1.0 Update 1 Release Notes


VMware Update Manager 1.0 Update 1| 04/10/2008 | Build 63965

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 VMware Infrastructure 3 version 3.5 Release Notes for your product.

Installation Notes

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

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

Upgrade Notes

You have to upgrade both the Update Manager client and Update Manager server to Update Manager 1.0 Update 1 client and Update Manager 1.0 Update 1 server, along with the upgrade of VirtualCenter Server 2.5 to VirtualCenter Server 2.5 Update 1 and VirtualCenter client 2.5 to VirtualCenter client 2.5 Update 1. Otherwise, you might encounter one of the issues listed in the Installing and Upgrading topic of the Known Issues.

Update Manager 1.0 Update 1 is not compatible with VirtualCenter 2.5 and Update Manager 1.0 is not compatible with VirtualCenter 2.5 Update 1:

Compatibility Matrix
  Update Manager 1.0 Update Manager 1.0 Update 1
VirtualCenter 2.5 Yes No
VirtualCenter 2.5 Update 1 No Yes

When you upgrade Update Manager 1.0 to Update Manager 1.0 Update 1, the configuration file, vci-integrity.xml (C:\Program Files\VMware\Infrastructure\Update Manager) is overwritten by the installer. No configuration settings that you have edited manually in this file are preserved after the upgrade, but all settings written to that file from the UI are preserved. To save your changes to the configuration settings, create a backup of this file before you perform the upgrade.

Minimum Hardware Requirements

Update Manager minimum hardware requirements 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 2 or more logical cores, each with a speed of 2GHz
  • Network:
      10/100 Mbps
  • Memory:
    • 2 GB RAM if Update Manager and VirtualCenter Server are on different machines
    • 4 GB RAM if Update Manager and 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.

For best performance, use a Gigabit connection between Update Manager and ESX Server hosts. 10/100 Mbps connections are also acceptable.

Network Port Requirements

For information about the VMware Update Manager network port requirements, see VMware Update Manager Network Port Requirements (KB 1004543).

Interoperability and Supported Operating Systems

Update Manager 1.0 Update 1 is compatible with VirtualCenter Server 2.5 Update 1 and later. For information about VirtualCenter Server 2.5 Update 1, see the VMware Infrastructure 3 version 3.5 Update 1 Release Notes for your product:

  • ESX Server 3.5 Update 1 and Virtual Center 2.5 Update 1 (HTML)
  • ESX Server version 3.5 Update 1 Embedded and Virtual Center 2.5 Update 1 (HTML)
  • ESX Server version 3.5 Update 1 Installable and Virtual Center 2.5 Update 1 (HTML)

Update Manager can scan and remediate a variety of ESX Hosts, virtual machines, and applications including the following:

ESX Server Scanning and Remediation

  • ESX Server 3.5 and later
  • ESX Server 3i and later

Virtual Machine Scanning and Remediation
  • Windows XP Professional, SP2 Required, 32 bit
  • Windows XP Professional 64 bit
  • 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 and later
  • Microsoft SQL Server versions 7.0/2000/2005
  • Microsoft SQL Server Desktop Edition (MSDE) version 1.0 and later
  • Exchange 2000 Server and Exchange Server 5.0
  • Internet Explorer version 4.0 and later
  • Outlook Express version 4.01 and later
  • Microsoft Site Server 3.0
  • ISA Server 2000
  • Microsoft .NET Framework, version 1.0 and later
  • Microsoft Data Access Components (MDAC) 2.5 and later
  • BizTalk Server 2000 and later
  • SNA Server 4.0
  • Host Integration Server 2000
  • WinZip 8.1 and later
  • Apache 1.3 and 2.0
  • Firefox 1.0 and later
  • RealPlayer 10 and later
  • Adobe Acrobat Reader

Resolved Issues

The following known issues in Update Manager 1.0 have been resolved in Update Manager 1.0 Update 1:

  • Update Manager might fail when it scans or remediates a large collection of objects.
  • Recursive operations on a host could fail after the host is removed from a cluster.
  • Baselines might become noncompliant after remediation, and need to be remediated multiple times to become compliant.
  • Shutting down a Linux virtual machine during Update Manager Agent installation causes problems.
  • Download tasks might fail due to network connectivity problems.
  • Database case-sensitivity affects search results.

Known Issues

Installing and Upgrading

VMware Update Manager Plug-In Fails to Install
Update Manager plug-in might fail to install with one of the following messages:

  • Error 25089 - incorrect username/password for VirtualCenter Server
  • Error 25085 - Setup failed to register VMware Update Manager extension to VMware VirtualCenter Server

For more information, see VMware Update Manager Plug-In fails to install (KB 1003468).

Update Manager Plug-In Might Fail to Launch
Update Manager plug-in might fail to launch, although it is installed successfully. For more information, see Unable to enable Update Manager Plugin (KB 1004680).

Update Manager Plug-In Might Not Be Available After You Upgrade to VirtualCenter Server 2.5 Update 1
After you upgrade to VirtualCenter 2.5 Update 1, if you choose to install a fresh database for VirtualCenter Server, the Update Manager plug-in will not be available in the VI Client. For more information, see Update Manager and Converter Enterprise Plug-Ins are not Available in the VI Client (KB 1004292).

After You Upgrade VirtualCenter and Update Manager, the Update Manager Plug-In Might Fail to Launch
If the VirtualCenter upgrade installation completes and the Update Manager upgrade also completes, the Update Manager plug-in might fail to launch. Update Manager starts and attempts to connect using the new port, but VirtualCenter continues to use the port configuration from the previous installation. For more information, see VirtualCenter does not use the custom port specified during installation (KB 1004412).

Update Manager Plug-In Download Button Is Not Available After You Upgrade Update Manager Server

Workaround: Run the Update Manager client installer manually from the installation directory: \docroot\vci\downloads\VMware-UMClient.exe. The default installation directory is C:\Program Files\VMware\Infrastructure\Update Manager\.

After You Upgrade Update Manager, the Update Manager Plug-In Cannot Be Enabled
If Update Manager and VirtualCenter Server are running on different hosts, after you upgrade Update Manager the proxy information gets lost in the configuration file of Update Manager. VI Client does not connect to Update Manager Web server.

Workaround: Repair the Update Manager 1.0 Update 1 installation.

Having Different Versions of VI Client and Update Manager Plug-In Produces an Error
If you have installed one version of VI Client and another of Update Manager plug-in, or if you have upgraded VI Client, but not Update Manager plug-in or the reverse, you receive an error message.

Workaround: Upgrade both VI Client and Update Manager plug-in.

Upgrading Update Manager Might Fail When Update Manager and VirtualCenter Are Installed on Different Machines
If Update Manager and VirtualCenter Server are installed on separate machines, when you upgrade Update Manager using the unified installer, you might receive an error message, such as Insuffiecient Privileges.

Workaround: Cancel the installation by clicking the Cancel button. Restart your system and upgrade Update Manager with the unified installer.

Upgrading Update Manager with Unified Installer Might Fail When Update Manager and VirtualCenter Are Installed on Different Machines
If Update Manager and VirtualCenter Server are installed on separate machines, when you upgrade Update Manager using the unified installer, you might receive an error message, such as Invalid HTTP port number or TCP/IP port is already in use. It must be in the 1-65535 range.

Workaround: Stop Converter Enterprise (if installed) and Update Manager services before you upgrade Update Manager.

Scanning and Remediation

Update Manager Reports an Error Message When Scanning and Remediating an ESX Host
Update Manager fails to scan and remediate an ESX host if the machine on which it is installed has multiple NICs. For more information, see VMware Update Manager host scan fails with "Metadata for patch missing" when the Update Manager host has multiple NICs (KB 1004330).

Update Manager Might Fail to Scan an ESX Server
Update Manager might fail to scan an ESX Server with the error message: Patch Metadata Not Found. For more information, see Update Manager fails to scan an ESX Server for updates when using non-default Web Services HTTP port (KB 1003943).

Update Manager 1.0 Might Fail When It Scans a Virtual Machine
You might not be able to scan a virtual machine with Update Manager 1.0 if Update Manager 1.0 Update 1 Guest Agent is installed on the same virtual machine.

Workaround: Uninstall the Update Manager 1.0 Update 1 Guest Agent from the virtual machine and perform the scan again.

A Scheduled Remediation Task Might Fail
If you have too many patches in the Exclusions list, a scheduled remediation task might fail with the error message: A specified parameter was not correct. Value.

Workaround: To reduce the patches in the Exclusions list, create a baseline with the patches you need and then schedule a remediation task.

Using Update Manager

A Blank Error Message Appears When Update Manager Server Becomes Unavailable
If the Update Manager client plug-in is enabled, and the Update Manager server becomes unavailable, an additional blank pop-up message displays along with the regular service down message.

Workaround: Click OK. Restart the Update Manager server and re-enable the plug-in.

VCI_UNDO_ORACLE.sql Script Completes Successfully, Despite Errors
If you run the VCI_UNDO_ORACLE.sql script, you see many errors. However the script completes successfully.

Online Help

Errors and Omissions
There are some minor errors and omissions in the Working with Baselines section of the Update Manager online help. For complete information, see these topics in the updated VMware Update Manager Administration Guide.

Internationalization Issues

You Cannot Install Update Manager Server on a Computer with Non-ASCII Characters in Its Name
If you try to install Update Manager server on a computer with non-ASCII characters in its name, the installation will fail.

You Cannot Install Update Manager in a Directory with Non-ASCII Characters in Its Name
In the installation wizard of Update Manager, you can select a different installation directory for the product than the default one (C:\Program Files\VMware\Infrastructure\Update Manager). If you select a folder containing non-ASCII characters as an installation directory, the installation fails.

You Cannot Download Patches to a Directory with Non-ASCII Characters in Its Name
In the installation wizard of Update Manager, you can select a different directory for downloading patches than the default one (C:\Documents and Settings\All Users\Application Data\VMware\VMware Update Manager\Data\). If you select a folder containing non-ASCII characters, you can proceed to the next step and no warning message appears. However, when the installation starts, you receive an error message and the installation fails.

Full-Width Numbers Are Invalid in the Schedule a Scan Wizard
In the Schedule a Scan wizard, if you enter a full-width number in any of the time fields and go to the next page, the value becomes 0. Only half-width numbers are treated as numeric values. No warning message notifies you that full-width numbers are invalid.

You Cannot Enter the Maximum Number of Non-ASCII Characters as a Task Name in the Schedule a Scan Wizard
In the Schedule a Scan wizard, if a task name contains the maximum number of 80 non-ASCII characters, you are able to finish the wizard. However, you receive an error message in the Recent Tasks panel. You receive no other warning messages. A task containing the maximum number of non-ASCII characters in its name does not appear in the Scheduled Tasks panel.

Workaround: Shorten the task name.

The Schedule Updates Download Wizard Might Contain Corrupted and Truncated Text if You Use Non-ASCII Characters

Workaround: Use only ASCII characters for the Task Name and Task Description fields in the Schedule Task Page of the Schedule Updates Download wizard.

Localization Issues

When You Upgrade Update Manager, You Have To Re-Register the Installer with VirtualCenter Server
There are many localization files, that have to be upgraded.

Workaround: For the standalone Update Manager Installer the re-registration happens only when you run VMware-UpdateManager.exe from the commandline. The command is: > VMware-UpdateManager.exe /S /V"VC_SERVER_ADMIN_PASSWORD=\"<PASSWORD> \" VUM_FORCE_REGISTER_EXTENSION=1", where PASSWORD is the placeholder for the VirtualCenter Server administrator's password.

When You Upgrade Update Manager, the Default Scheduled Download Updates Task Is Not Localized

The Schedule Updates Download Wizard Contains Non-Localized Fields
In the Schedule Updates Download wizard the default Task Name and Task Description are not localized in Chinese.

The Ready to Complete Page of the Remediate Wizard Contains a Non-Localized Word
In the Remediate wizard, you can schedule the remediation. If you configure the remediation to start immediately, in the Ready to Complete page of the wizard, the word "Immediate" is not localized.

There Is a Truncation of the Text in the Assign Permissions Window
When you assign permissions for a host in the Inventory, and select the View Compliance Status privilege for VMware Update Manager, the description of the privilege is truncated.

There Is a Truncation of Text in the Add a Baseline Wizard
In the Ready to Complete page of the Add a Baseline wizard, the text might be truncated.

There Is a Truncation of Text in the Installation Wizard of Update Manager Download Service
If you cancel the Update Manager Download Service installation, the InstallShield Wizard Completed page of the installation wizard might contain truncated text.