VMware

VMware Update Manager 1.0 Update 4 Release Notes

VMware Update Manager 1.0 Update 4 | 02/23/2009 | Build 63995

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
Update 4
2.5
2.5
Update 1
2.5
Update 2
2.5
Update 3
2.5
Update 4
Update Manager 1.0
Yes
No
No
No
No
Yes
No
No
No
No
Update Manager 1.0 Update 1
No
Yes
No
No
No
No
Yes
No
No
Yes*
Update Manager 1.0 Update 2
No
No
Yes
No
No
No
No
Yes
No
Yes*
Update Manager 1.0 Update 3
No
No
No
Yes
No
No
No
No
Yes
Yes*
Update Manager 1.0 Update 4
No
No
No
No
Yes
No
No
No
No
Yes

* Passed preliminary tests for compatibility. This compatibility is experimental and not fully supported.

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.
For more information, refer Update Manager - PowerShell Library Documentation.

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 4, you must first upgrade VirtualCenter to VirtualCenter 2.5 Update 4.

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

When a VI Client 2.5 Update 4 instance connects to the VirtualCenter Server 2.5 Update 4 instance (and Update Manager 1.0 Update 4), the VI Client detects the correct Update Manager plug-in version and tries to load it. If the necessary Update Manager 1.0 Update 4 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.

During the Update Manager upgrade, you cannot edit parameters such as installation path and patch download location. The system keeps the data for these parameters from the original installation. You can edit the installation and patch download location paths only when you perform a fresh Update Manager 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.

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 4. For example, to download the ESX Server host patches and to import them to Update Manager 1.0 Update 4 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:

  • Update Manager Client Plug-In Disconnects from VI Client Intermittently
    The release resolves an issue where 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.
  • vci-integrity.xml Need Not be Edited to Scan or Remediate ESX Server 3.0.3 Hosts
    In previous VMware Update Manager releases, to scan or remediate ESX Server 3.0.3 hosts users had to change the value for SupportedBaseHostVersion tag in the vci-integrity.xml file to 3.0.3 from 3.1.0.
    Starting with Update Manager 1.0 Update 4, no manual intervention is required to scan or remediate ESX Server 3.0.3 hosts.
  • Updates Are Scheduled to Download Daily
    In previous VMware Update Manager releases, the VMware Update Manager Update Download task is scheduled to run weekly by default. This setting does not provide the latest updates that might be required on a daily basis. 
    Starting with Update Manager 1.0 Update 4 release, the VMware Update Manager Update Download task is scheduled to run daily by default.
  • Issues with Scanning and Remediation of ESX Server Host with Express Patches Is Resolved
    If update repository contains patches for ESX Server Update 2 and the express patches that were released for ESX Server Update 2, Update Manager 1.0 Update 3 might fail to scan or remediate ESX Server hosts and displays a message similar to the following:
    Update Manager had a failure.
    This issue is resolved.

  • Update Manager and UMDS Downloads Updates After Proxy Authentication Information Is Entered in the vum-proxyAuthCfg.exe File
    This release resolves an issue where if Update Manager or UMDS is configured for use with an Internet proxy that requires authentication and proxy authentication information is correctly provided in the vum-proxyAuthCfg.exe file in the Update Manager or UMDS installation directory, Update Manager or UMDS might fail to download updates with a message similar to the following:
    Error: proxy authentication is required, but no auth info is provided
  • Updates to the JRE Package
    The JRE package distributed with VMware Update Manager 1.0 Update 4 is updated from 1.5.0_12 to 1.5.0_16, to address multiple security issues that exist in the earlier releases of JRE.
    For more information about security issues fixed in JRE package versions 1.5.0_16 and earlier, refer http://java.sun.com/j2se/1.5.0/ReleaseNotes.html.
    The following advisories by Secunia list the CVE identifiers related to the fixed security issues in JRE 1.5.0_13, JRE 1.5.0_14, JRE 1.5.0_15, and JRE 1.5.0_16:

    In order for attackers to attempt exploiting these vulnerabilities, they would need to have access to the service console network. According to security best practices provided by VMware, the service console must be isolated from the virtual machine network. For more information on VMware security best practices, refer http://www.vmware.com/resources/techresources/726.

Known Issues

The Known Issues are grouped as follows:

Installing and Upgrading

  • Update Manager Configuration with an Internet Proxy Might Fail if Proxy Port Has 5 Digits (KB 1008546)
  • VirtualCenter Server Might Fail to Display the Upgraded Version of Update Manager Client
    The Available tab in the Plugin Manager window might fail to display the updated version of the installed Update Manager if:
    • Update Manager is upgraded to Update Manager 1.0 Update 4
    • Update Manager 1.0 Update 3 is uninstalled, and Update Manager 1.0 Update 4 is installed.
    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 Manger, restart the VMware VirtualCenter Server service.
  • 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.
  • Irrelevant Warning Message When Installing Update Manager on a System on Which Oracle 10g R2 version 10.2.0.3 Is Installed
    When you install Update Manager with the unified installer on a system on which Oracle 10g R2 v10.2.0.3 is installed, the installer displays an irrelevant warning message: Please make sure to upgrade your Oracle Server and Client to version 10.2.0.3. See release notes for more information. However, you can ignore this message and successfully complete the installation of Update Manager.
  • Update Manager Upgrade Might Fail
    Update Manager upgrade fails if the connection to the VirtualCenter Server is lost during the upgrade process.
    Workaround: Run the upgrade again, after the connection between Update Manager and VirtualCenter Server is re-established.
  • Update Manager Upgrade Might Result in Error Messages
    When you upgrade Update Manager, even if you stop the Update Manager service before the upgrade, additional error messages might appear. If the Update Manager service is performing tasks such as scanning, remediation, or update signature, the service needs time for stopping.
    Workaround: Accept the messages and wait for Update Manager service to shut down to run the upgrade.
  • Repairing the Update Manager Installation Might Require User Input
    When you repair the Update Manager installation by using the Repair option from the Add or Remove Programs functionality, the installer requires you to input some values (for example, VirtualCenter Server IP) that you entered during the installation. Enter the correct values to repair the installation.
  • 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 installation.
  • 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 Insufficient Privileges. Workaround: Cancel the installation by clicking the Cancel button. Restart your system and upgrade Update Manager with the unified installer.
  • Reinstalling Update Manager Might Produce Errors
    Uninstalling Update Manager might fail to stop all Update Manager services. If you reinstall Update Manager, an error might appear at the end of the process. The installation is successful despite this error.
  • Reinstalling Update Manager Might Fail
    Update Manager installer might fail with the message warning 25015, unable to install Update Manager. This error occurs when you attempt to install Update Manager on a machine that previously had Update Manager installed and then removed. To resolve this issue, reboot the machine.
  • Remediation of KB896423 on Windows 2000 Servers SP4 Might Fail
    Update Manager installs Updates on Virtual Machines in silent mode, so interactive users receive no information about updates or service pack installations. Installation of KB896423 on Windows 2000 SP4 might, on occasion, result in an error which displays a dialog box to users. The dialog box includes the message spoolsv.exe - Entry point not found. This problem is believed to result from a specific combination of patches being installed on the Virtual Machine. /
    Such an error might result in the particular remediation task making no progress. To enable remediation progress, close the dialog box from the virtual machine console.
  • Installing Update Manager with Unified Installer Might Fail if Disparate Databases Are Used (KB 1003277)
  • VMware Update Manager Plug-In fails to install (KB 1003468)
  • Unable to enable Update Manager plug-in (KB 1004680)
  • Update Manager and Converter Enterprise Plug-Ins Are Not Available in the VI Client (1004292)
  • VirtualCenter fails to connect to Update Manager if a new HTTP or HTTPS Web Services port is specified during VirtualCenter installation (1004412)

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 that is being updated using the Update Manager, the remediate operation to update the cluster might fail with a message similar to the following:
    There are errors during remediation process
    Workaround: When remediating DRS enabled clusters, disable DPM and power on any hosts that are in standby mode to allow their remediation.
    To disable DPM:
    1. Right-click the DRS enabled cluster, and select Edit Settings.
    2. In the <Cluster_Name> Settings window, select Power Management.
    3. Select Off as the default power management option for the cluster.
  • Offline Scanning Might Be Slowed Down by Antivirus Software
    When antivirus software, such as McAfee, is running on the machine on which Update Manager server is installed, the offline scanning of the virtual machines in your deployment system might be significantly slowed down.
    Workaround: Disable the antivirus on-access scanning or exclude vmware-updatemgr.exe from the blocking functionality of the antivirus software.

  • Installation of Windows XP x64 SP2 During Remediation Might Fail
    Windows XP x64 SP2 requires interactive desktop and the remediation process might fail.
    Workaround: Manually install Windows XP x64 SP2 on the virtual machine.
  • Remediation Task Might Fail for Remote ESX Server Hosts
    Remediating remote ESX Server hosts with large patch files might fail due to networking issues. The file transfer from the local depository to the remediated ESX Server hosts might take longer than expected, and might produce timeouts.
  • Datacenter Remediation Might Not Affect the Right ESX Server Hosts
    When you schedule a remediation task for a datacenter, the remediation operation is performed on the ESX Server hosts that are in the datacenter when the task is scheduled. If you change the datacenter's configuration before the start of the remediation, and for example, move ESX Server hosts in or out of the datacenter, remediation is performed only on the hosts that were in the datacenter before the configuration change.
  • Remediation Process Might Fail to Install Patches on a Virtual Machine
    The remediation process might fail to install all patches on a virtual machine in which the applications' locales differ from the operating system's locale. When you remediate virtual machines with mixed locales, patches of only one locale are applied at a time. This produces installation error for the rest of the patches that are of a different locale.
    Workaround: Repeat the remediation until the baseline becomes compliant with the virtual machine.
  • Remediation Might Fail with File Is Not Signed Message in the Windows Event Viewer Log of the Virtual Machine
    When a Windows patch file is downloaded incorrectly (for example, due to network problems, the incomplete file is downloaded), the signature verification of the patch file during the remediation fails along with the remediation. An application event is logged and shown in the Windows Event Viewer as File is not signed, followed by the file path.
    Workaround: To re-download the missing patch file, delete the file by following the path shown in the Event Viewer log, and start another remediation process.
  • During ESX Server Host Remediation the Host Might Not Enter Maintenance Mode
    During the remediation process of an ESX Server host, the host might not enter maintenance mode, and the remediation task is not completed. The Enter Maintenance Mode task shown in the Recent Tasks pane might stay at 2% for more than four hours.
    Workaround: Check whether the virtual machines on the non-responsive ESX Server host are powered off. If necessary, manually power off the virtual machines to complete the Enter Maintenance Mode task. After you power off all machines, if the Enter Maintenance Mode task in not progressing, and if the ESX Server host cannot enter maintenance mode within 30 minutes, reboot the host service manually.
  • Remediation of ESX Server 3.5 and ESX Server 3.5 Update 1 Hosts Might Install an Equivalent Newer Version of the Patch
    When you remediate an ESX Server host against a baseline containing a patch that has an obsolete prerequisite, the Events tab displays an event message that the patch and the obsolete prerequisite are installed. However, when on the ESX Server host, the patch and the current version of the prerequisite are installed. For example, if patch A depends on patch B, and patch B is made obsolete by patch C, during the remediation against a baseline containing only patch A, Update Manager shows in the Events tab that patches A and B are installed. However, on the ESX Server machine, patches A and C are installed.
  • After Remediation of ESX Server 3.5 with ESX350-Update02 Bundle, ESX350-Update01 Bundle Might Be Displayed as Not Compliant (KB 1006383)
    After you remediate an ESX Server 3.5 host against a baseline containing the ESX350-Update02 bundle, the baseline containing the previous update (that is ESX350-Update01 bundle), might be displayed as not compliant. The ESX Server update releases are cumulative and new update releases contain all fixes in the previous update release. It is unnecessary to install ESX350-Update01 on a host that is already compliant with ESX350-Update02.
    Workaround: To make the host compliant with the attached baseline, containing the ESX350-Update01 bundle, do one of the following:

    1. Detach the baseline containing the ESX350-Update01 bundle from all hosts compliant with the baseline, containing the ESX350-Update02 bundle.
    2. Remediate the ESX host against a baseline containing the ESX350-Update01 bundle.
  • Scheduled Virtual Machine Remediation Might Fail
    Scheduled virtual machine remediation might fail at the scheduled time with a Login failed due to a bad username or password. error message. This happens when Update Manager server and VirtualCenter Server are installed on different machines whose time settings are not synchronized.
    Workaround: Ensure that the system time settings of the VirtualCenter Server and Update Manager server machines are synchronized within one minute. For example, synchronize the machines automatically with a NTP Server.
  • Remediation of ESX Server 3.5 and ESX 3.5 Update 1 Installs the Newer Version of a Patch
    When you remediate ESX Server 3.5 and ESX 3.5 Update 1 against a fixed baseline, containing a patch that has an obsolete prerequisite, the patch and the newer version of the prerequisite are installed on the host. This behavior has changed from ESX Server 3.5 Update 2 onwards and only the required bundles in a fixed baseline are installed on the host during the remediation. For example, if patch A depends on patch B, and patch B is made obsolete by patch C, during the remediation of ESX Server 3.5 Update 2, patches A and B are installed on the host.
    When you remediate an ESX Server host against a dynamic baseline, the behavior has not changed, and the patch and the newer version of the prerequisite are installed on the host.
  • 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.
  • Editing a Virtual Machine That Update Manager is Scanning or Remediating Causes Problems
    When Update Manager is scanning or remediating a virtual machine, you can modify settings for that virtual machine. Doing so might cause the scan or remediation to fail and the changes to the virtual machine might be lost. To avoid this issue, do not edit virtual machine settings while scanning or remediating that same virtual machine.
  • Remediating a Virtual Machine or Template Might Fail if VMware Tools are Unavailable
    The remediation process may employ VMware Tools. In cases where this is a requirement, remediation might fail. To resolve this issue, install or restart VMware Tools, and then retry the remediation.
  • Remediation Tasks Fail for Some Microsoft Products
    Update Manager does not remediate some Microsoft products. Details of these failures are logged in an event which can be viewed using the VI Client.
    • Application of SP2 for Microsoft Content Management Server 2002 and SP2 for Internet Explorer 6 fail. They are for scanning only.
    • Applications of some SPs to Exchange require user-intervention, so they cannot be completed automatically.
  • The Remediation Wizard does not Retain Information about Selected Updates
    In the baselines page of the Remediation wizard, if you select a specific number of updates from a baseline and then switch back to the baseline list view, the previous update selection is not remembered and all updates are selected again.
  • Update Manager Does Not Apply Windows Small Business Sever 2003 Service Packs
    Update Manager can not download or install service pack 2 (SP2) for Windows Small Business Server 2003. Update Manager accurately scans and reports if the service pack is applied, but no remediation is possible.
  • Update Manager Might Incorrectly Report Windows Vista Guest Patches As Not Being Installed
    Update Manager might report some Windows Vista virtual machines as not compliant, even after patches have been successfully installed. To resolve this condition, reboot the virtual machine. Subsequent scans will show the machine as compliant.
  • Remediating Suspended Windows 2003 Enterprise (x64) Virtual Machines Might Fail
    Remediating Windows 2003 Enterprise x64 SP2 with patches MS06-061, MS06-071, and MS07-042 might fail under certain circumstances. If such virtual machines have 256 MB of RAM, the task stops making progress at 62% and eventually fails. Changing the RAM size to 512 MB results in success for subsequent remediations.
  • Update Manager fails to scan an ESX Server for updates when using non-default Web Services HTTP port (KB 1003943)

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.
  • 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.

Using Update Manager

  • Extraneous Error Message Might Be Displayed When the Update Manager Plug-In Is Re-Enabled
    When the VMware Update Manager Server service is restarted and the Update Manager Plug-In is re-enabled, an error message similar to the following might be displayed:
    object reference not set to an instance of an object
    Workaround: Ignore the error message, and re-enable the plug-in by selecting the Enabled checkbox.
  • Update Manager Plug-In Might Get Disabled
    If antivirus software such as McAfee or other antivirus software is running on your deployment system, the Update Manager plug-in might get disabled in the VI Client.
    Workaround: Exclude the vmware-updatemgr.exe process and its ports from the scanning and blocking functionality of the antivirus software. For McAfee VirusScan Enterprise 8.5i, do the following:
    1. Select Start > Programs > McAfee > VirusScan Console.
    2. Double-click Access Protection.
    3. In the Access Protection Properties window, select the User-defined Rules category. Make sure that the Update Manager SOAP port (8084 by default), is not included in the blocking rules (double-click each rule to see its details). If you must have a rule blocking this port, add vmware-updatemgr.exe to the Processes to exclude list.
  • Update Downloads Task Might Be Set Incorrectly
    When you edit the Update Downloads task from the Configuration tab of Update Manager and in the Schedule Task page of the Schedule Update Download wizard, set the Frequency to After Startup, the frequency is not set after startup.
  • Canceled Tasks Are Always Shown in the Recent Tasks Pane
    Canceled tasks stay in the Recent Tasks pane of the VI Client until the VirtualCenter Server is shut down, unlike failed or completed tasks, which disappear from the VI Client after some time.
  • A Wrong Target Type Might Appear in the Attach Baselines Window
    After you install Update Manager and try to attach a baseline to a host by right-clicking in the Update Manager tab and selecting the Attach Baseline option, the Target Type might not be displayed as host, but as virtual machine.
    Workaround: Click the Attach Baseline link in the upper-right corner of the Update Manager tab.
  • Some Messages In the Update Manager Plug-In May Overlap Other Messages and Buttons
    When you filter the updates in the New Baseline wizard, the message showing the number of filtered updates may overlap the Filter button.
    Workaround: Enlarge the wizard window.
  • Special Characters Are Not Allowed in the Text Contains Field of the Updates Filter Page
    When you create a dynamic baseline, you must not enter special characters (symbols) in the Text contains field. You should use only valid text strings as search criteria. If you enter special characters, the baseline is invalid, it is not displayed in the Update Manager tab, and you may not be able to attach, edit, detach or delete the other baselines.
    Workaround: Delete the invalid baseline from the VCI_BASELINES table in the database.
  • 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.