VMware

VMware vCenter Update Manager Release Notes


VMware vCenter Update Manager 4.0 | 21 MAY 2009 | Build 162871

Last Document Update: 25 April 2013

Check periodically for additions and updates to these release notes.

These release notes cover the following topics:

These release notes provide information about the VMware vCenter Update Manager, an optional module for VMware vCenter Server 4.0. For information about new vCenter Server features, requirements, and installation, see the VMware vSphere 4.0 Release Notes. For more information about VMware vCenter Update Manager, see the VMware vCenter Update Manager Administration Guide.


What's New

VMware vCenter Update Manager is a new release and includes the following enhancements:

  • Compliance dashboard – A new actionable policy-based compliance dashboard allows the users to view virtual datacenter wide patch compliance and take remediation actions.
  • Orchestrated datacenter upgrades – This new feature facilitates automated, two-step datacenter-wide upgrade process to ESX/ESXi 4.0 using Update Manager baselines and baseline groups. Now, the upgrades are simply staged as host upgrade, and virtual machine VMware Tools and virtual hardware upgrade. You can use a VMware vCenter Update Manager host upgrade baseline to upgrade hosts at a cluster, folder, and datacenter level. You can also use a virtual machine upgrade baseline group to upgrade the virtual hardware of the virtual machines and VMware Tools at the same time.
  • VMware Tools and virtual hardware upgrades – VMware vCenter Update Manager provides new default baselines to scan virtual machines for the latest VMware Tools and virtual hardware versions. You can view the compliance status of the virtual machines against the default VMware Tools Upgrade to Match Host and VM Hardware Upgrade to Match Host baselines. You can perform VMware Tools and virtual hardware upgrades of individual virtual machines or virtual machine upgrades at a folder, cluster, or datacenter level.
  • Virtual appliance upgrades – Update Manager 4.0 provides new virtual appliance upgrade default baselines to scan and upgrade a virtual appliance to the latest released or latest critical version. Update Manager also provides you the ability to create virtual appliance upgrade baselines. For more information about virtual appliances, see VMware Studio Documentation.
  • Third-party patching – Update Manager 4.0 provides the capability to install updates for third-party ISV/IHV components on ESX/ESXi hosts by using VMware vSphere Installation Bundle (VIB) packages. Update Manager enables adding third-party URL addresses from which you can download third-party patch metadata and content for ESX/ESXi 4.x hosts.
  • Baseline groups – Update Manager 4.0 provides the feature to aggregate individual patch and upgrade baselines into baseline groups. The baseline group functionality allows you to specify non-conflicting upgrade baselines, and a set of patch baselines in one group to scan and remediate an inventory object against it. Update Manager provides a resolution in case you try to remediate against conflicting baselines.
  • Staging patches – Update Manager allows you to download patches for hosts from the Update Manager server to an ESX/ESXi host for later remediation. Staging patches in this way speeds up remediation; when you are ready to apply the patches, they are available locally on the host.
  • Shared patch repository – vCenter Update Manager Download Service is enhanced. With this release the vCenter Update Manager Download Service (UMDS) can be set up to download third-party ESX/ESXi 4.x patches. The patch metadata and patch binaries that UMDS downloads can be exported to a server, a portable storage device, or the machine on which Update Manager is installed. The export of the updates serves for setting up a shared repository. After you export the updates, you can set up Update Manager to use the shared repository as a patch download source.
  • There are changes in the way Update Manager handles host patches:
    • Update Manager automatically resolves and installs dependencies during remediation
      If a patch in a baseline requires the installation of another patch, Update Manager detects the pre-requisite in the depot and installs it along with the selected patch.
    • Obsoleted patches are not staged
      Patches are not staged if they are obsoleted by patches in the baselines or baseline groups for the same stage operation. Update Manager stages only patches that it can install in a subsequent remediation process, based on the present scan results of the host. If a patch is obsoleted by patches in the same selected patch set, the obsoleted patch is not staged.
    • Update Manager might not install or stage conflicting patches
      If a patch is in conflict with some other patches that are installed on the host, the conflicting patch might not be installed or staged. However, if there is another patch in the baseline that resolves the conflicts, the conflicting patch is installed. For example, if a baseline contains patch A and patch C, and patch A conflicts with patch B, which is already installed in the host, but patch C obsoletes patch B and patch C is not in conflict with patch A, the remediation process against the baseline installs patches A and C.
    • Update Manager installs the newer version of a patch
      When multiple versions of the same patches are selected, Update Manager installs the newest version in the selected patch set and skips the old versions.
This release contains known issues described in Known Issues.

Top of Page

Hardware Requirements and Sizing Estimator

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

Sizing Estimator

Disk storage requirements vary depending on your deployment. For more information, see the VMware vCenter Update Manager Sizing Estimator. The Sizing Estimator calculates the size of the VMware vCenter Update Manager 4.0 database and patch store. The estimate it makes is calculated from the information that you enter about your deployment, such as the number of the hosts and virtual machines. The sizing estimator also provides recommendations for the Update Manager database and server deployment models.

For information about the VMware vCenter Update Manager performance, best practices and recommendations, see the VMware vCenter Update Manager Performance and Best Practices white paper.

Top of Page

Installation Notes

Installation of VMware vCenter Update Manager requires network connectivity with an existing vCenter Server 4.0 system. Each installation of vCenter Update Manager must be associated with a single vCenter Server instance.

The Update Manager module consists of a client component that is a plug-in interface to a VMware vSphere Client 4.0 instance, and a server component that can be installed on the same system as vCenter Server or on a different system.

Before you install Update Manager, you must install vCenter Server.

Future releases of VMware vCenter Update Manager might not support installation on 32-bit Windows operating systems. VMware recommends installing vCenter Update Manager on a 64-bit operating system.

The VMware vCenter Update Manager - PowerShell Library is not available for this release.

Top of Page

Upgrade Notes

Upgrades from the vSphere 4.0 Beta and the vSphere 4.0 Release Candidate releases to vSphere 4.0 are not supported. Uninstall vCenter Server 4.0 Beta 2 (build 115113) or Release Candidate (build 140822), and perform a fresh installation of vCenter Server 4.0.

Upgrades from the vCenter Update Manager 4.0 Beta 2 (build 114000) and the vCenter Update Manager 4.0 Release Candidate (build 140797) releases to vCenter Update Manager 4.0 are not supported. Uninstall vCenter Update Manager 4.0 Beta 2 or Release Candidate and vCenter Update Manager Download Service 4.0 Release Candidate and delete the patch repository. All patches released for the Beta 2 and Release Candidate releases must be removed from both the vCenter Update Manager and vCenter Update Manager Download Service repositories. Perform fresh installations of vCenter Update Manager 4.0 and vCenter Update Manager Download Service 4.0.

This release allows upgrades from previous Update Manager 1.x versions.

Before you upgrade Update Manager from a previous version, you must upgrade vCenter Server and the vSphere Client to a compatible version.

The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of vSphere Update Manager with other VMware vSphere components, including ESX/ESXi, VMware vCenter Server, and the vSphere Client. In addition, this site also provides information about supported management and backup agents before installing ESXi or vCenter Server.

Top of Page

Interoperability and Supported Operating Systems

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

ESX Hosts Scanning and Remediation

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

Virtual Machine Scanning and Remediation
  • Windows XP Professional, 32 bit, SP2 Required
  • 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 Server 2008
  • 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

Top of Page

Known Issues

The known issues in this VMware vCenter Update Manager release are grouped as follows:

Installing and Upgrading

  • A Minimum of 600MB of Free Space for Update Manager on the Boot Drive Is Required to Install Update Manager
    Although Update Manager does not need to be installed on the boot drive, some required components must be installed on the boot drive. 600MB of space for Update Manager is required at installation time to accommodate these required components, as well as temporary files used during the installation.
    Workaround: Ensure at least 600MB of free space on the boot drive before installing Update Manager.
  • You Cannot Install Update Manager to a Directory Containing an Exclamation Mark
    In the installation wizard of Update Manager, you can change the installation path of Update Manager. Changing the installation directory to a folder that contains an exclamation mark results in an error and the installation does not complete. Installation paths that have an exclamation mark are not supported.
  • During Update Manager Installation a Wrong Warning Message Might Appear
    During the Update Manager installation, you might be incorrectly warned that the patch download location you specify has insufficient free space. This issue occurs when you select a path to a drive with free space more than 20GB and create a new folder on that drive. The minimum recommended amount of patch store location free space is 20GB. More space might be necessary, depending on your deployment system.
    Workaround: Ignore the message and proceed.
  • When You Upgrade Update Manager an Error Message During the Database Upgrade Might Appear
    When you upgrade Update Manager, you have to upgrade the database. If you use an Oracle database and grant the user only the connect privilege, an error message for insufficient privileges is displayed. Even if you provide the user the execute on dbms_lock, create procedure, create sequence, create table, create any sequence, and the create any table privileges, the database upgrade fails.
    Workaround: Grant the following set of privileges to the Update Manager database user:
    • connect
    • execute on dbms_lock
    • create view
    • create procedure
    • create table
    • create sequence
    • create any sequence
    • create any table
    • create type
    • unlimited tablespace
  • After Installing Update Manager 4.0 Client Plug-In You Cannot Enable Update Manager Client 1.0 or Update Manager Client 1.0 Update 1 on the Same Computer
    Update Manager Client 1.0 (or Update Manager Client 1.0 Update 1) might be represented as installed on the VI Client Plug-in Manager although you have not installed it when:
    1. You install VirtualCenter 2.5 (or VirtualCenter 2.5 Update 1), Update Manager server 1.0 (or Update Manager server 1.0 Update 1) and VI Client 2.5 (or VI Client 2.5 Update 1), but do not install Update Manager Client 1.0 (or Update Manager Client 1.0 Update 1).
    2. You upgrade the VI Client to vSphere Client (formerly VI Client) 4.0.
    3. You connect the vSphere Client to a vCenter Server system with which Update Manager 4.0 is registered.
    4. You download and install the VMware vCenter Update Manager Client 4.0 plug-in.
    5. You connect the vSphere Client 4.0 to VirtualCenter Server 2.5 (or VirtualCenter 2.5 Update 1).
    The vSphere Client Plug-in Manager shows the Update Manager Client 1.0 (or Update Manager Client 1.0 Update 1) as installed although you have not installed it. You cannot enable the plug-in either.
    Workaround: Uninstall vCenter Update Manager Client 4.0 plug-in. Connect the VI Client 2.5 (or VI Client 2.5 Update 1) to VirtualCenter 2.5 (or VirtualCenter 2.5 Update 1) and install Update Manager Client 1.0 (or Update Manager Client 1.0 Update 1). After this, install VMware vCenter Update Manager Client 4.0 plug-in again. Both versions of the client plug-ins can co-exist on one computer. This issue has been fixed in VI Client 2.5 Update 2 and later releases.

Top of Page

Scanning and Remediation

  • After Host Patch Scan the Patch Details Window Might Display Misleading Information
    When you scan a host in a clean state against a patch baseline that contains conflicting dependencies, the Patch Details window might display misleading information. For example, suppose the patch baseline contains patches A, B, and C. Patch A depends on patch B, and patch B is in conflict with patch C. When you select patch A in the Patch Details window, the conflict-related information is displayed at the bottom of the window: Following update dependencies conflict with host: B. However, patch C, which is in conflict with patch B is not displayed in the Patch Details window. If patch C is not installed on the host, the patch dependency from patch B does not conflict with the host as reported in the Patch Details window.
  • Remediation Tasks Fail for Some Microsoft Products
    Update Manager does not remediate some Microsoft products. Details of these failures are logged in an event, and can be viewed using the vSphere Client.
    • Application of SP2 for Microsoft Content Management Server 2002 and SP2 for Internet Explorer 6 fail. You can scan for them only.
    • Applications of some service packs to Exchange require user intervention, so they cannot be completed automatically.
  • Host Remediation Might Fail if the /etc/vmware/esx.conf File Is Locked
    ESX 3.5 host remediation run on the hour might fail. Update Manager reports the failure of the remediation as Platform Configuration Error, while the Update Manager log files report the error as: Could not lock/etc/vmware/esx.conf. The remediation failure is caused because both the remediation process and another process in the host try to acquire the lock for the /etc/vmware/esx.conf file. For ESX 3.5 hosts the refreshrd process runs every hour exactly by the /etc/cron.hourly/refreshrd script. If the remediation process starts at the same time, it might fail if it cannot acquire the lock.
    Workaround: Repeat the remediation.
  • Host Patch and Upgrade Remediation Might Fail
    Host patch and upgrade remediation might fail with the message There are errors during the remediation operation if an inaccessible virtual machine exists on the host. The reason for this failure might be that the virtual machine files reside on a disconnected network storage.
    Workaround: Connect the disconnected network storage or remove the inaccessible virtual machine from the vSphere inventory.
  • Host Patch Remediation Might Fail
    Host patch remediation against the default host Update Manager baselines or user-defined host patch baselines might fail if the baseline contains one or more conflicting patches.
  • Host Upgrade Scan and Remediation Might Fail
    Host upgrade scan and remediation might fail with the AgentInstallFailed error message. This error might result from insufficient free space on the ESX/ESXi host.
    Workaround: To upgrade ESX/ESXi hosts, ensure you have at least 10MB free space in the /tmp directory of the host.
  • New: Update Manager Remediation Process Might Fail When Installing Windows Vista or Windows Server 2008 Guest Patches
    The Update Manager remediation process might fail when installing some Windows Vista or Windows Server 2008 guest patches and report the Windows Vista and Windows Server 2008 virtual machines as not compliant.
    Workaround: Reboot the virtual machine and perform a scan. The scan will show the virtual machine as compliant.
  • Host Remediation Might Fail or Remain in Progress in a High Latency Network
    Due to extensive distance between the vCenter Server system, Update Manager server, and the managed hosts, host remediation might fail or remain in progress for a long time. The host fails to exit maintenance mode if one of the patch installations times out. Update Manager reports both the task for the host to exit maintenance mode and the installation task as Operation times out. on the Tasks and Events tab.
  • VMware Tools Upgrade Fails for Virtual Machines Created on Hosts of Versions 2.5.x
    When you scan a virtual machine with the VMware Tools version corresponding to ESX 2.5.x against a VMware Tools Upgrade to Match Host baseline, the VMware Tools Upgrade to Match Host baseline state is Non-Compliant. Although the state is noncompliant, the VMware Tools upgrade fails with a VM Tools installed in the VM doesn't support automatic upgrade error message. Automatic upgrade for VMware Tools is supported only for virtual machines created on hosts running versions ESX 3.0.x, ESX 3.5 or higher, and ESX 3i version 3.5 or higher.
    Workaround: Upgrade VMware Tools manually by right-clicking the virtual machine in the inventory and selecting Guest > Install/Upgrade VMware Tools.
  • Patch Remediation Might Fail When You Upgrade the Virtual Hardware and Apply Patches at the Same Time
    When you remediate a Windows 2000 Professional SP4 virtual machine with virtual hardware version 3 against a baseline group containing the VM Hardware Upgrade to Match Host baseline and patch baselines, the patch remediation might fail. After the upgrade of the virtual hardware, Update Manager powers the virtual machine on and displays a System Settings Change dialog box asking you to restart the system. If you do not click Yes, the machine does not restart and the remediation process stops. Patch remediation fails, because the process times out. The error message you receive is: VMware vCenter Update Manager Guest Agent failed to respond in time on <virtual_machine_name>. Please check if the VM is powered on and Guest Agent is running.
    Workaround: Click Yes in the System Settings Change dialog box to restart the virtual machine.
  • vCenter Update Manager 4.0 Does Not Allow Fresh Install of New Third-Party Modules on Hosts
    vCenter Update Manager 4.0 does not allow fresh install of new third-party software modules on ESX/ESXi hosts. Update Manager enables applying updates to third-party modules that are already installed on the host.
  • VMware Tools Upgrade Might Fail With a Generic Error Message
    VMware Tools upgrade on a virtual machine in which the VMware Tools service is not running might fail with the VMware Tools upgrade failed for <virtual_machine_name> generic error message.
    Workaround: Start the VMware Tools service in the guest operating system and perform the upgrade again.
  • Host Remediation Might Fail for Some Patches
    Patch remediation of a host might fail when a patch (for example, patch A) in a baseline input conflicts with the host and the conflict cannot be resolved by the other patches in the baseline input.
    Workaround: The Patch Details window for patch A displays a recommendation to use the resolving patch B. As this is the solution, include the required patch B into the baseline to apply it along with patch A. More information can be found in a KB article associated with the patch A.
  • You Must Not Use a Shared Datastore For ESX Host Upgrade Remediation
    When you remediate a cluster or folder of ESX hosts against an upgrade baseline, in the Remediation wizard you can specify the VMDK location to which to migrate the COS of the ESX host. VMware recommends that you use a local datastore, not a specific datastore, which is shared by the hosts.
    Workaround: If the ESX hosts you want to upgrade have local storage, you can successfully upgrade them individually by selecting to use a local datastore.
  • ESX Host Upgrade Remediation Fails for Diskless Hosts
    When you remediate ESX hosts against an upgrade baseline, in the Remediation wizard you can specify the VMDK location to which to migrate the COS of the ESX host. If you want to perform the remediation at a cluster or folder level, VMware recommends that you use a local datastore. It is not recommended to use a datastore shared within many hosts, because the upgrade fails for the diskless hosts in the container object.
    Workaround: Upgrade the diskless ESX hosts individually. In such a case you can select a specific network datastore as long as it is not shared with other hosts.
  • Distributed Power Management Might Cause Update Manager Operations on Hosts to Fail
    Distributed Power Management (DPM) might cause scan, stage and remediation operations on hosts with no running virtual machines to fail. If DPM is enabled on a cluster, it might put the hosts with no running virtual machines in standby mode, regardless of any running operations (such as the Update Manager operations) and the scan, stage and remediation might not complete.
    Workaround: Disable DPM on the cluster, perform the Update Manager operations, and re-enable DPM.
  • Timezone Patches 931836 and 933360 Are Displayed as Missing, Although They Are Not Applicable
    Timezone patches 931836 and 933360 are obsolete patches, which were pulled shortly after the Update Manager 1.0 Update 2 release and are no longer available for downloading. Shavlik provides the functionality to check if you have these patches installed on your virtual machines. If they are installed on a virtual machine, Update Manager reports the patches as Installed. Otherwise, the patches are reported as Missing, although they should be marked as Not Applicable. Patch 931836 is superseded by patch 933360, which is superseded by patch 942763, and patch 942763 is superseded by 951072. If patch 951072 is installed, then the other patches are not needed.
    Workaround: To obtain the correct compliance state for a virtual machine, you must remove the above mentioned patches from the patch baseline defined in your environment and perform the scan again.

Top of Page

Internationalization Issues

  • You Cannot Install Update Manager and Download Patches to Directories with Non-ASCII Characters in Their Names
    In the installation wizard of Update Manager, you can change the installation and patch download locations of the Update Manager. Changing the installation and patch download locations to folders containing non-ASCII characters in their names might result in errors. Only ASCII characters are supported in installation paths and user names. However, non-ASCII characters are supported in passwords.
  • You Cannot Install Update Manager in Simplified Chinese Language on Japanese Operating Systems
    If you select Simplified Chinese as an installation language on a Japanese operating system, an error 1158 appears and the installation fails. You can select Japanese, German, or English as the installation language on a Japanese operation system.
  • Virtual Machine Patch Remediation Might Fail if a Localized Version of the Patch Is Not Available
    When you apply patches to a localized guest operating system, the remediation process might fail if a patch for the specific locale has not been released by the vendor. Update Manager reports an error: Failed to install patch <patch_name>.
    Workaround: Contact the patch vendor for localization-specific information.
  • Remediation Might Fail for Some Localized Patches for Windows
    Due to patch installer issues, Update Manager might fail to install some localized patches for Windows with error code 1618 - another installation is already in progress.
    Workaround: Retry the remediation operation.
  • New: VMware vCenter Update Manager Online Help Might Fail to Open on Some Localized Windows Systems
    If you install Update Manager on a Windows operating system different from English, Deutsch, Japanese, and Simplified Chinese, you cannot open the Update Manager Online Help from the Help menu. In addition, if you click other links or buttons for Help within the Update Manager Client, the following error message appears: Missing help file.
    Workaround: Navigate to the Update Manager help directory (the default folder is C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\Update Manager 4.0\Help\en\) and double-click index.html, or copy the Update Manager online help files from
    C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\Update Manager 4.0\Help\en\
    to
    C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\Update Manager 4.0\Help\.
    Have in mind that copying the files up one level is not always recommended.

Top of Page

Using Update Manager

  • New: Security vulnerabilities in the Jetty Web server version embedded in Update Manager
    The following Update Manager versions embed Jetty Web server version 6.1.6:
    • Update Manager 1.0 Update 2 and later
    • Update Manager 4.0
    • Update Manager 4.0 Update 1
    • Update Manager 4.0 Update 1 Patch 1
    • Update Manager 4.0 Update 1 Patch 2
    • Update Manager 4.0 Update 2
    • Update Manager 4.1
    Two security vulnerabilities are reported for the Jetty Web server version 6.1.6:
    • CVE-2009-1523 (http://jira.codehaus.org/browse/JETTY-1004) identifies a directory traversal vulnerability. It allows for obtaining files from the system where Update Manager is installed by a remote, unauthenticated attacker. For an attack to be successful, the attacker would need to be on the same network as the system where Update Manager is installed.
    • CVE-2009-1524 (http://jira.codehaus.org/browse/JETTY-980) identifies is a cross-site scripting vulnerability. It allows for running JavaScript in the browser of the user who clicks a URL containing a malicious request to Update Manager. For an attack to be successful the attacker would need to lure the user into clicking the malicious URL.
    The vulnerabilities are classified as Important, according to the VMware Security Response Policy.
    Workaround: Upgrade Jetty to version 6.1.22. For more information, see Upgrade the Jetty Web server embedded in VMware vCenter Update Manager by using a security fix (KB 1023962).
  • You Might Not Be Able to See Patch Type, Impact, or Vendor Information After Initial Download of Patches
    After the initial download of patches, you see a list of patches in the Patch Repository tab or when you create a fixed patch baseline. In such a case, you might not see information like type of the patch, its impact, or the vendor publishing the patch. In addition, when you create a dynamic patch baseline, you might see the list of vendors empty.
    Workaround: Restart the Update Manager Client plug-in.
  • You Cannot Stage Patches to ESX/ESXi 3.x Hosts
    Staging patches to individual ESX/ESXi 3.x hosts or container objects containing ESX/ESXi 3.x and ESX/ESXi 4.0 hosts fails. The Recent Tasks pane displays the error message: There are errors during staging operation. VMware vCenter Update Manager 4.0 supports staging patches only for ESX/ESXi 4.0 hosts.
  • During VMware Tools Upgrade You Might See a Misleading Error Message in Recent Tasks Pane
    When you perform a VMware Tools upgrade of a virtual machine, you might see a misleading error message Cannot complete operation because VMware Tools is not running in this VM even though the remediation is successful.
  • VMware Tools Upgrade for a Virtual Machine on a Host in Maintenance Mode Might Fail with a Misleading Error Message
    When you upgrade a virtual machine on a host that is in maintenance mode, the remediation might fail with a misleading error message The VMware Tools installed in the VM does not support automatic upgrade. Please upgrade VMware Tools manually in the Tasks and Events tab. Remediation of a virtual machine on a host in maintenance mode is not possible the right error message is: There are errors during the remediation operation.
  • During VMware Tools Upgrade Remediation a Wrong Event Error Message Might Appear
    When you remediate a Linux virtual machine against the VMware Tools Upgrade to Match Host baseline, a wrong error message Cannot remediate <virtual_machine_name> for patches: Remediation of Linux VMs is not supported is displayed on the Events tab. This event is not related with the upgrade of VMware Tools.
  • VMware Tools Upgrade Remediation Might Fail with a Misleading Event Error Message
    When you try to upgrade VMware Tools on a virtual machine with no installed VMware Tools, the remediation fails with a misleading error message: VMware vCenter Update Manager had an unknown failure. Check Tasks and Events tab and logs for more details. Update Manager does not support VMware Tools upgrade for virtual machines on which VMware Tools is not installed.
  • Scheduling a Remediation Task Generates a Set of Tasks and One of Them Is Misleading
    When you schedule a remediation task, several active tasks appear in the Recent Tasks pane. One of these tasks is Remediate Entity. This task appears when you create a new remediation task and is not an actual remediation task in which the objects are remediated. The Remediate Entity task creates sub-tasks for the scheduled remediation based on your input in the Remediate wizard.
  • Admin View and Compliance View Quick-Switch Links Might Not Work Properly if Your Environment Is in Linked Mode
    If your vCenter Server system is a part of a Connected Group in vCenter Linked Mode and you have an Update Manager instance registered with each vCenter Server system, the Admin view and Compliance view navigation links might not work properly. For example, Update Manager instance 1 is registered with vCenter Server 1 and Update Manager instance 2 is registered with vCenter Server system 2. When you select an object managed by vCenter Server 1, click the Update Manager tab, and then click Admin view in the upper-right corner, you see the Administrator's view of Update Manager instance 1. When you click Compliance view, select an object from the inventory managed by vCenter Server 2, and click Admin view in the upper-right corner, you see the Administrator's view of Update Manager instance 1 again.
    Workaround: Click Compliance view and then click Admin view again to see the Administrator's view of the second Update Manager instance.
  • When You Perform a VMware Tools Upgrade You Might See a Misleading Error Message
    When you perform a VMware Tools upgrade of a virtual machine with insufficient free space, the remediation fails due to the lack of space with a wrong error message The VMware Tools operation was canceled.
  • Conflicting Patches Are Counted in the Remediation Wizard
    After you scan a selected object against a patch baseline, you might see a number of conflicting patches in the Patch Baselines window. When you try to remediate the selected object, the conflicting patches are counted in the Remediation wizard as patches that are going to be installed on the object, but only some or none of the conflicting patches are installed during the remediation process.
  • Updated: Update Manager Does Not Support a Re-Import of a Host Upgrade File
    Update Manager does not support the re-import of host upgrade files (ISO for ESX hosts and ZIP for ESXi hosts) if an already imported file gets corrupt or manually deleted from the Update Manager patchstore. Importing upgrade files for a particular release is a one-time activity. Once you upload the upgrade files, you must use the existing release upgrades available in Update Manager to create a new host upgrade baseline. In addition, if you create an upgrade baseline with the new ESX 4.0 Evaluation copy (build 171294), you cannot create a new upgrade baseline for the ESX 4.0 Licensed version (build 164009).
  • Update Manager Service Might Fill the \Temp Directory With Many System Temporary Files
    You might see many files with names like ufa{*}.tmp and ufa{*}.tmp.LOG{*} in the Windows \Temp directory (the default location is C:\WINDOWS\Temp).
    • ufa{*}.tmp files – These files are created when the Update Manager service becomes unavailable in the middle of an offline virtual machine scan. To delete the ufa{*}.tmp files, for example to delete a ufa729F.tmp file:
      1. Select Start > Run.
      2. In the Run window enter regedit.
      3. In the Registry Editor navigate to the My Computer\HKEY_LOCAL_MACHINE folder and select the ufa729F.tmp file.
      4. Select File > Unload Hive.
      5. Open a Command Prompt window.
      6. Navigate to C:\ and enter the following command:
        del C:\Windows\Temp\ufa729F.tmp
    • ufa{*}.tmp.LOG{*} files – These files are Windows transaction log files for registry operations. They can be generated as a result of Windows logging registry transactions and the Windows OS does not remove them after use. ufa{*}.tmp.LOG{*} files are like any other Windows temporary files and can be deleted as a part of a Windows Disk Cleanup task.
      To delete the ufa{*}.tmp.LOG{*} files, for example to delete a ufaFF50.tmp.LOG2 file:
      1. Open a Command Prompt window.
      2. Navigate to C:\ and enter the following command:
        del C:\Windows\Temp\ufaFF50.tmp.LOG2

Top of Page