Download Esxi 5.1 Patch 3

admin

ESXi 5.5 Express Patch 8 and ESXi 6.0 Express Patch 3 are Released. Allan Kjaer October 6, 2015 March 6, 2017. ESXi 6.0 Update 1a download: https. Patch 19192712 must be applied on both the database and client to use Oracle 12c in Windows. Download ESXi 5.1 and vCenter Server 5.1 Update 3 here. Updating VMware ESXi 5.1 Update 3 with manual patching. Hypervisor ESXi 5.5 for FREE just download the. All I need to fully patch my ESXi server 5.1 U3.

Esxi 5.1 Express Patch 3 Download

Download Esxi 5.1 Patch 35.1

Update Esxi 5.1 To 6.0

VMware vSphere Update Manager 5.1 Update 3b | 1 October 2015 | Build 2925355

Last Document Update: 1 October 2015

Check frequently for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

The Update Manager 5.1 Update 3b release notes provide information about VMware vSphere Update Manager, an optional module for VMware vCenter Server. For information about new vCenter Server features, requirements, and installation, see the VMware vSphere 5.1 Update 3 Release Notes. For more information about VMware vSphere Update Manager, see the Installing and Administering VMware vSphere Update Manager documentation.


What's New

  • The Microsoft XML version is upgraded to version MSXML6.dll.
  • The OpenSSL library is updated to version openssl-0.9.8zg.
  • The Diffie Hellman suite is removed from the default SSL cipher list.

This release contains known issues described in Known Issues.

Hardware Requirements and Sizing Estimator

Minimum hardware requirements for Update Manager vary depending on how Update Manager is deployed.

Hardware Requirements

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

For more information about the disk storage requirements, see the VMware vSphere Update Manager Sizing Estimator. The sizing estimator calculates the size of the Update Manager database and patch store. The estimate 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.

Installation Notes

This section includes information about the installation of Update Manager and Update Manager Download Service, an optional module of vSphere Update Manager.

Update Manager

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

The Update Manager module consists of a server component and client component. The Update Manager server can be installed on the same system as vCenter Server or on a different system.
The Update Manager provides two client components:

  • Update Manager Client, which is a plug-in interface to a VMware vSphere Client instance.
  • Update Manager Web Client, which is a plug-in interface to a VMware vSphere Web Client instance.

Before you install Update Manager, you must install vCenter Server. For database compatibility information, see Databases that Support Installation of the Update Manager Server.

The Update Manager 5.1 Update 3 server can be installed only on 64-bit Windows operating systems.

Update Manager Web Client

Update Manager Web Client is a plug-in to the vSphere Web Client. You can use Update Manager Web Client for viewing scan results and compliance states for vSphere inventory objects.

After you install the Update Manager server component, the Update Manager Web Client plug-in is automatically enabled on vSphere Web Client. The Update Manager Web Client plug-in appears as an Update Manager tab under the Monitor tab in the vSphere Web Client.
To be able to see Update Manager Web Client in vSphere Web Client, you must have the View Compliance Status privilege.
If you are logged in to the vSphere Web Client while installing Update Manager server, after the installation is completed log out of the vSphere Web Client and log in to it again so that the Update Manager tab appears.

Update Manager Client

Update Manager Client is a plug-in interface to a VMware vSphere Client instance. Update Manager Client plug-in provides the capabilities you need for patch and version management of your vSphere inventory.

The Update Manager Client has a separate installer from the Update Manager server component.

The Update Manager 5.1 Update 3 Client can be installed on both 32-bit and 64-bit operating systems.

Update Manager Download Service

vSphere Update Manager Download Service (UMDS) is an optional module of Update Manager that you can use to download patch definitions. Install UMDS in case your deployment system is secured and the machine on which Update Manager is installed has no access to the Internet.

UMDS can be installed only on 64-bit Windows operating systems.

Installing UMDS 5.1 Update 3b in an Environment with Update Manager 5.1 Instances Only

In the UMDS 5.1 Update 3 installer wizard, you can select the patch store to be an existing download directory from an earlier UMDS 4.x installation and reuse the applicable downloaded updates in UMDS 5.1. You should uninstall existing UMDS 4.x instances before reusing the patch store. After you associate an existing download directory with UMDS 5.1 Update 3, you cannot use it with earlier UMDS versions. If you install UMDS with an existing download directory, make sure that you perform at least one download by using UMDS 5.1 Update 3 before you export updates.

Installing UMDS 5.1 Update 3 in an Environment with both Update Manager 4.x and Update Manager 5.x instances

You should not install UMDS 5.1 Update 3 with an existing UMDS 4.x download directory if your environment contains both Update Manager 4.x and Update Manager 5.x instances. In such a case, you need an UMDS 4.x and an UMDS 5.x installation on two separate machines, so that you can export updates for the respective Update Manager versions.

To use UMDS, the download service must be of a compatible version with the Update Manager server. For more information about the compatibility between Update Manager and the UMDS, see the Installing and Administering VMware vSphere Update Manager documentation.

Update Manager Utility

When you install Update Manager or UMDS, vSphere Update Manager Utility is silently installed on your system as an additional component.

The Update Manager Utility allows you to change the database password and proxy authentication, re-register Update Manager with vCenter Server, and replace the SSL certificates for Update Manager. For more information about reconfiguring the Update Manager settings by using the utility, see the Reconfiguring VMware vSphere Update Manager documentation.

Upgrade Notes

This release allows upgrades from Update Manager version 4.x and 5.0 that are installed on a 64-bit operating system. Direct upgrades from Update Manager 1.0 Update 6 and earlier, and Update Manager systems that are installed on a 32-bit platform are not supported. You must use the data migration tool that is provided with Update Manager 5.0 installation media to move your Update Manager system from 32-bit operating system to Update Manager 5.0 on a 64-bit operating system, and then perform an in-place upgrade from version 5.0 to version 5.1 Update 2. For detailed information how to use the data migration tool, see the Installing and Administering VMware vSphere Update Manager documentation for Update Manager 5.0.

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

Upgrade from UMDS 4.x to UMDS 5.x is not supported.

Interoperability and Software Requirements


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 ESXi, VMware vCenter Server, the vSphere Client, and the vSphere Web Client. In addition, this site also provides information about supported management and backup agents before installing ESXi or vCenter Server.


Operating Systems that Support Installation of the Update Manager server and the UMDS

To view supported host operating systems on which you can install Update Manager server and UMDS, select the Host OS option of the VMware Compatibility Guide.


Databases that Support Installation of the Update Manager server and the UMDS

To view information about the databases that are compatible with Update Manager server and UMDS, select the Solution/Database Interoperability option of the VMware Product Interoperability Matrix.


Update Manager can scan and remediate ESX/ESXi hosts, virtual machines, and virtual appliances.

  • Host patching
    • ESX/ESXi 4.x
    • ESXi 5.x
  • Host upgrades of ESX/ESXi 4.0, 4.1, and ESXi 5.0 and their respective update releases to ESXi 5.1 Update 3
  • Upgrades of VMware Tools and virtual hardware for virtual machines
  • Upgrades of virtual appliances

Supported Operating Systems for Upgrade of VMware Tools and Virtual Hardware

  • Windows Server 2012 [Standard/Datacenter] 64-bit
  • Windows Server 2012 R2 [Standard/Enterprise/Datacenter] 32-bit
  • Windows Server 2012 R2 [Standard/Enterprise/Datacenter] 64-bit
  • Windows XP Professional 32-bit (SP3 required)
  • Windows XP Professional 64-bit (SP2 required)
  • Windows 2000 [Professional/Server/Advanced Server/Datacenter Server] 32-bit
  • Windows 2000 [Professional/Server/Advanced Server/Datacenter Server] 64-bit
  • Windows Server 2003 [Standard/Enterprise/Datacenter] 32-bit (SP2 required)
  • Windows Server 2003 [Standard/Enterprise/Datacenter] 64-bit (SP2 required)
  • Windows Server 2003 R2 [Standard/Enterprise/Datacenter] 32-bit (SP2 required)
  • Windows Server 2003 R2 [Standard/Enterprise/Datacenter] 64-bit (SP2 required)
  • Windows Vista [Business/Enterprise] 32-bit (SP2 required)
  • Windows Vista [Business/Enterprise] 64-bit (SP2 required)
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 32-bit
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 64-bit
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 32-bit SP2
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 64-bit SP2
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 64-bit R2
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 64-bit R2 Service Pack 1
  • Windows Server 2012 [Standard/Enterprise/Datacenter] R2 U1
  • Windows Server 2012 [Standard/Enterprise/Datacenter] R2 U2
  • Windows 7 [Professional/Enterprise] 32-bit
  • Windows 7 [Professional/Enterprise] 64-bit
  • Windows 7 [Professional/Enterprise] 32-bit SP1
  • Windows 7 [Professional/Enterprise] 64-bit SP1
  • Windows 8 32-bit
  • Windows 8 64-bit
  • Windows 8.1 32-bit
  • Windows 8.1 64-bit
  • Windows 8.1 [Professional/Enterprise] U1
  • Windows 8.1 [Professional/Enterprise] U2
  • Red Hat Enterprise Linux 2
  • Red Hat Enterprise Linux 3
  • Red Hat Enterprise Linux 4
  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 5.11
  • Red Hat Enterprise Linux 6.4
  • Red Hat Enterprise Linux 6.6
  • Red Hat Enterprise Linux 7
  • CentOS 4
  • CentOS 5
  • CentOS 5.11
  • CentOS 6
  • CentOS 6.6
  • Debian 4
  • Debian 5
  • Debian 6
  • Ubuntu 7.x
  • Ubuntu 8.x
  • Ubuntu 9.x
  • Ubuntu 10.x
  • Ubuntu 11.x
  • Ubuntu 12.04.3
  • Ubuntu 12.04.4
  • Ubuntu 12.04.5
  • Ubuntu 13.04
  • Ubuntu 14.04
  • Ubuntu 14.04.1
  • SUSE Linux Enterprise Server 8
  • SUSE Linux Enterprise Server 9
  • SUSE Linux Enterprise Server 11 Service Pack 3
  • SUSE Linux Enterprise Server 12
  • Oracle Enterprise Linux 4
  • Oracle Enterprise Linux 5
  • Oracle Enterprise Linux 5.11
  • Oracle Enterprise Linux 6
  • Oracle Enterprise Linux 6.6
  • Asianux 3
  • Asianux 4

Known Issues

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


Installing and Upgrading

  • Update Manager Web Client is still present in the vSphere Web Client after Update Manager is uninstalled
    When you uninstall Update Manager, the Update Manager tab remains under the Monitor tab of the vSphere Web Client, and the Scan and Attach buttons are still visible. If you select the Update Manager tab in vSphere Web Client after uninstalling the Update Manager server, the following error message appears: There was an error connecting to VMware vSphere Update Manager.
    Workaround: Log out of the vSphere Web Client and log in to it again.
  • Installation of the Update Manager server and UMDS fails on Windows operating system with Turkish language pack
    Attempts to install the Update Manager server and UMDS on Windows operating system with Turkish language pack fail.
    Workaround: Install the Update Manager server and UMDS on Windows operating system with English language pack.
  • After an upgrade, the Update Manager plug-in might be disabled for the duration of a download task
    If Update Manager loses connection to vCenter Server while a download task is running, the Update Manager plug-in cannot be re-enabled. This problem might occur after an upgrade of Update Manager.
    Workaround: Wait for the download task to complete, and then enable the Update Manager plug-in.
  • After you upgrade from Update Manager 1.0 Update 6 to Update Manager 5.1, an error message appears when you switch tabs in the Administration view
    When you switch between tabs in the Update Manager Administration view, a dialog box that prompts you to save the changes might appear. If you click No, the following error message appears: Specified argument was out of the range of valid values. Parameter name: The value must be between MinimunTimeInSeconds and MaximumTimeInSeconds. You might encounter this problem after you upgrade Update Manager 1.0 Update 6 to Update Manager 5.1, if in the original Update Manager 1.0 Update 6 installation you selected Fail Task as the failure response on the ESX Host Settings page.
    Workaround: To work around the issue, perform one of the following tasks:
    • When the dialog box prompts you to save the changes, click Yes.
    • On the ESX/Host Cluster Settings page in the upgraded Update Manager 5.1, click Apply.
  • You might not be able to enable the Update Manager plug-in on the vSphere Client
    If the Update Manager database is located on a separate machine and the system DSN uses Windows authentication, you cannot enable the Update Manager plug-in on the vSphere Client. The error message you receive is There was an error connecting to VMware vSphere Update Manager. Database temporarily unavailable or has network problems.
    Workaround: Ensure that the Update Manager database uses SQL Server authentication.
  • 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.

Scanning, Staging, and Remediation

  • Upgrading VMware Tools on powered off virtual machines might fail
    Upgrading VMware Tools on powered off virtual machines using VMware vCenter Update Manager might fail. An error message similar to the following might be recorded in the log file:
    UfaVmMounter' 5792 INFO] [ufaDiskMounter, 337] Opening computer..
    'ChainedTaskContainer.ChainedTaskContainer{10}' 5792 ERROR]
    [singleVMToolsRemediateSuperTask, 383] Cannot access sysprep settings on the VMNAMEXXXX, error: vmodl.fault.SystemError
    'ChainedTaskContainer.ChainedTaskContainer{10}' 5792 ERROR]
    [singleVMToolsRemediateSuperTask, 503] VciTask { id: ChainedTaskContainer{10}, type: ChainedTaskContainer }: Remediation error: integrity.fault.SysprepAccessFailure
    [06784 error 'Default'] [diskWin32,199] Opening vpxa-nfc://[datastorename] VMNAMEXXXX/VMNAMEXXXX.vmdk@esxihostname:902!52 d0 75 c6 2a 53 e1 7e-e5 54 3a 4c 75 a0 e7 cc failed with error2338
    Workaround: For more information, see KB 2092073.
  • Update Manager fails to create baselines and download meta data about patches if you use Oracle databases of version 11.2.0.3 or 11.2.0.4
    When using Oracle databases of version 11.2.0.3 or 11.2.0.4, Update Manager fails to create baselines and download meta data about patches.
    Workaround: Use Oracle Instant Client Package - ODBC of version 11.2.0.4.10 for 32-bit Microsoft Windows to create a 32-bit DSN so that Update Manager connects and uses properly Oracle database servers of version 11.2.0.3 or 11.2.0.4.
    You can download Oracle Instant Client Package - ODBC of version 11.2.0.4.10 for 32-bit Microsoft Windows from the following link.
  • Product to vendor mapping in the New Baseline wizard is incomplete after new installation of the Update Manager server or after you download patches for the first time
    After you install the Update Manager server or after you download patches for the first time, when you are creating a new dynamic baseline, the Product text box of the Dynamic Baseline Criteria page of the New Baseline wizard, might not list all the products of the vendor selected in the Patch Vendor selection window.
    Workaround: Log out and log in to the vSphere Client.
  • During staging or remediation of patches a wrong warning message might appear
    During patch staging or remediation operations in Update Manager, you might be incorrectly warned that some patches are not available. The warning message displayed is: Some of the patches you selected for remediation are not available. Do you want to continue?.
    Workaround: Ignore the message, and click Yes to proceed with staging. All patches that you initially selected will be staged.
  • Update Manager reports the compliance status as Incompatible when scanning or remediating ESXi 5.x hosts that belong to an HA cluster
    When you perform an upgrade scan of ESXi 5.x hosts that belong to an HA cluster, Update Manager might report the compliance status of the hosts as Incompatible and might not allow the hosts to be remediated. The Incompatible compliance status is because of the way the FDM (HA) agent is installed on ESXi 5.x hosts. Starting with vSphere 5.0, the FDM agent is installed on ESXi hosts as a VIB. When a VIB is installed or updated on an ESXi host, a flag is set to signify that the bootbank on the host has been updated. Update Manager checks for this flag while performing an upgrade scan or remediation and requires this flag to be cleared before upgrading a host. The flag can be cleared by rebooting the host.
    Workaround: Reboot hosts that report the compliance status as Incompatible. Run the upgrade scan or remediation again after the host is back online.
  • Remediation of ESX 4.0 hosts against a custom image might fail
    When you scan an ESX 4.0 host against a custom ISO image, Update Manager might display a misleading Non-Compliant compliance status. By default ESXi installer images distributed by VMware require the host to have at least 2048MB free memory to boot. Custom ISO images contain custom VIBs that require the host to have additional memory resources to boot. When you remediate an ESX 4.0 host against a custom image, the remediation fails if the host does not have sufficient memory resources to boot, and Update Manager upgrade remediation task times out.
    Workaround: Verify that the ESXi 4.0 host has sufficient memory to boot when you perform an upgrade with a custom ISO image.
  • Recent Tasks pane displays error message during VM Hardware upgrade of powered-on virtual machines on ESXi 5.1 host
    When you perform a VM Hardware upgrade of powered-on virtual machines on an ESXi 5.1 host that is incompatible with VM Hardware version 9, the Recent Tasks pane displays the error message: The target host does not support the virtual machine's current hardware requirements. For incompatibilities other than cpuid.LM: if possible, use a cluster with Enhanced vMotion Compatibility (EVC) enables; see KB article 1003212. Requirements were not met for the following features:
    See the error stack for details on the cause of this problem.
    The remediation process completes successfully and the VM Hardware version is upgraded to match the ESXi 5.1 host.
    Workaround: Ignore the error message.
  • When you use the Remediate wizard, you can ignore some upgrade scan warnings and force a remediation even if the upgrade warnings are not related to third-party software
    On the ESXi 5.x Upgrade page of the Remediate wizard, you can select Remove installed third-party software that is incompatible with the upgrade, and continue with the remediation to remove third-party software installed on the host and to ensure a successful remediation. Selecting the option also forces Update Manager to ignore three potential issues that are not related to third-party software. The following warning messages are associated with the potential issues.
    • The root password is encrypted with DES encryption, causing it to be authenticated up to only 8 characters. For instructions on how to correct this, see VMware KB 1024500 at http://kb.vmware.com/kb/1024500.
    • VMkernel and Service Console network interfaces are sharing the same subnet <subnet_name>. This configuration is not supported after upgrade. Only one interface should connect to subnet <subnet_name>.
    • Unsupported devices <device_name> found on the host.
    Workaround: Before remediation, perform an upgrade scan and review the messages in the Upgrade Details window of Update Manager. Take the necessary actions recommended in the messages to ensure that the remediation succeeds.
  • Remediating ESXi 5.0 hosts against bulletins that are marked as requiring reboot might not reboot the hosts
    Some updates require the host to be rebooted during the remediation process. The information about whether a reboot is required is contained in the update metadata and is displayed in the Update Manager Patch Repository, under Impact. For ESXi 5.0 VIBs, the reboot requirement is not determined solely by the metadata, but instead depends on the VIB specification and whether a previous version of the VIB is installed on the host. This provides reboot optimization for some VIBs, where an initial installation does not require a host reboot and only subsequent patching of the VIB requires a reboot.
    Workaround: No workaround is required. Update Manager reboots hosts as necessary to ensure a successful remediation.
  • Host patch remediation fails when patch metadata is not available
    In the Update Manager 5.1 installer wizard, you can deselect Download updates from default sources immediately after installation. After installation, in the Configuration tab, you can choose to download only patch metadata from sources for specific ESX/ESXi versions, for example, only ESXi 5.1 patch metadata. In such a situation, if you attempt to remediate a container with ESX/ESXi hosts of different versions, and you have downloaded patch metadata for some and not all host versions, the remediation fails.
    Workaround: Download patch metadata for all host versions you have in your inventory.
  • Compliance status is Incompatible and remediation fails for ESX 4.1 Update 1 hosts when you scan or remediate the hosts against an ESXi 5.1 upgrade baseline
    When you perform an upgrade scan of ESX 4.1 Update 1 hosts against an ESXi 5.1 upgrade baseline, the compliance status might be Incompatible. The remediation of ESX 4.1 Update 1 hosts against an ESXi 5.1 upgrade baseline might fail. The scan and remediation problems are caused by third-party drivers in the ESX 4.1 Update 1 installation. After an upgrade scan of hosts, more information about third-party software is provided in the conflict details for the upgrade baseline.
    Workaround: Two different types of drivers might cause the problems.
    • Async drivers, for example oem-vmware-esx-drivers-scsi-3w-9xxx.
      The vendor releases drivers asynchronously for ESXi 5.1, and the drivers are made available in the VMware patch depot. If you require such drivers, you must download them, use Image Builder CLI to build a custom ESXi image that contains them, and remediate against the custom image. Without the ESXi 5.1 drivers, pertinent hardware devices might stop functioning.
    • Deprecated drivers, for example oem-vmware-esx-drivers-net-vxge.
      The driver is discontinued in ESXi 5.0 because the pertinent hardware is discontinued. In the Update Manager Remediate wizard, on the ESXi 5.x Upgrade page, click Remove installed third-party software that is incompatible with the upgrade, and continue with the remediation. You should be aware of the functional implications of third-party software removal, because pertinent hardware devices might stop functioning.
  • Host remediation might not complete if the host contains powered on fault tolerant virtual machines
    Host remediation might not complete if there are any Primary virtual machines with disabled FT on the host, and you select Fail Task or Retry on the Host Remediation Options page of the Remediate wizard. In such a scenario, powered on Primary virtual machines with disabled FT cannot be powered off or migrated in a DRS cluster. The host cannot enter maintenance mode while there are powered on virtual machines on it, and the remediation cannot be completed.
    Workaround: When you remediate hosts containing Primary or Secondary virtual machines, you can use one of the following workarounds:
    • Select Power Off virtual machines and Retry or Suspend virtual machines and Retry on the Host Remediation Options page of the Remediate wizard.
    • Manually migrate the fault tolerant virtual machine to another host before you start a remediation.
    • If EVC is enabled on a DRS cluster, virtual machines with disabled FT can be automatically migrated when the host tries to enter maintenance mode. This is possible only if DRS is not disabled on the particular host.
  • Host remediation might fail if vCenter Server does not properly update the power state of the host
    When a host is being powered on or exiting standby mode, the host power state might not get updated in vCenter Server and host remediation cannot finish or times out. When the power state of a host is not updated properly, in the vSphere Client inventory the host might be displayed as if it is in standby mode, even though it is powered on.
    Workaround: To remediate the host, remove the host from the inventory and add it again so that vCenter Server refreshes the power state of the host and then start the remediation process.
  • The Remediation Selection page might display an incorrect number of patches for the selected baselines
    When you remediate a vSphere inventory object against a patch or extension baseline preselected in Compliance view, the initial page of the remediation wizard might show an incorrect number of patches that need to be remediated. In this case, when the inventory object has multiple attached patch and extension baselines, the number of patches corresponds to the number of compliant patches from all attached baselines, and not just from the selected baselines.
    Workaround: Either change the selection of baselines or groups in the Remediation Selection page, or first click Next to go to the next page and then click Back to return to the selection page.
  • Host upgrade scan and remediation might fail if there is not enough free space on the host
    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 20MB free space in the /tmp directory of the host.
  • VMware Tools upgrade fails for virtual machines created on hosts running 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 Non-Compliant, 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 later, and ESX 3i version 3.5 or later.
    Workaround: Upgrade VMware Tools manually by right-clicking the virtual machine in the inventory and selecting Guest > Install/Upgrade VMware Tools.
  • Host remediation might fail for some patches because of irresolvable conflict with the patches on the host
    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 another patch to resolve the conflict. The recommendation might also contain many patches. Including one or all of the recommended patches into the baseline might resolve the conflict. For more information, refer to the KB article associated with patch A and the recommended patches.
  • 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 might fail. The Recent Tasks pane displays the error message: There are errors during staging operation. vSphere Update Manager supports staging patches only to hosts running ESX/ESXi 4.0 and later.

Internationalization Issues

  • Unlocalized text appears when Update Manager 5.1 Update 2 is installed on Simplified Chinese version of Windows Server 2012 or Windows Server 2012 R2
    If you install Update Manager on a Simplified Chinese version of Windows Server 2012 or Windows Server 2012 R2 operating system, some text in the user interface appears in English and is not localized.
  • When you double-click VMware vSphere Update Manager.msi, the hint message is not localized
    When you extract all components that are required for the installation of Update Manager to a local folder, either from a .zip file or an .iso image, you can run the VMware vSphere Update Manager.msi application by double-clicking it. When you run the application, the hint pop-up displays the message The installer should be started using VMware-UpdateManager.exe. The message is in English and not localized.
  • You cannot install Update Manager and download patches to directories with non-ASCII characters in their names
    In the installer 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.

Using Update Manager Web Client

  • Compliance state information inconsistencies might appear on Update Manager Web Client page
    When you select a baseline in Update Manager Web Client, you see compliance state information for the object in the Attached Baselines table, the Attached Baseline Groups drop-down menu, and compliance state details under the Attached Baselines table.
    If you or another user perform operations that affect the compliance state of an object, some inconsistencies might appear in the compliance state information that is displayed on the Update Manager Web Client page. For example, operations, such as remediating the object in Update Manager Client, updating the object directly, or changing the contents of the baseline in Update Manager Client, can affect an object's compliance state.
    When you select a baseline in the Update Manager Web Client, the compliance state details always must show information for the object's latest compliance state. However, the baseline displays the compliance state from the last scan operation initiated from the Update Manager Web Client or from the last time you refreshed the vSphere Web Client.
    Workaround: If you see compliance state inconsistencies between the baseline sections and an object's compliance details in Update Manager Web Client, manually refresh the vSphere Web Client to show the latest compliance states in all sections of the Update Manager Web Client page.
  • The attached baselines in the Update Manager Web Client differ from the attached baselines displayed in the Update Manager Client
    When you attach a baseline to a vSphere inventory object in the Update Manager Client, it does not appear in the Attached Baselines table of the Update Manager Web Client. When you detach a baseline in the Update Manager Client, it does not disappear from the Attached Baselines table in the Update Manager Web Client.
    If you start a scan from the Update Manager Web Client against a baseline that is already detached in the Update Manager Client but is still visible in the Update Manager Web Client, after the scan operation completes, the baseline disappears from the Attached Baselines table of the Update Manager Web Client.
    This behavior occurs because Update Manager Web Client does not automatically refresh all contents after performed operations from the Update Manager Client.
    This behavior is the same for baselines and baseline groups.
    Workaround: Manually refresh the vSphere Web Client.
  • Baselines and baseline groups with long names are truncated in Update Manager Web Client dialogs
    When you create a baseline or a baseline group with a very long name in Update Manager Client, this baseline or baseline group might appear with a truncated name in the Update Manager Web Client. As a result, you might not be able to distinguish baselines or baseline groups that have very long names and differ only by the last characters in their names.
    Workaround: None.

Using Update Manager

  • Updating SOAP port and HTTP port using the Network Configuration tab might display incorrect values
    When you update the SOAP port and HTTP port in Update Manager using the Network Configuration tab, you might have the following issues:
    1. Updating SOAP port: When you update the SOAP port using the Network Configuration tab, the new SOAP port might not get updated in the Update Manager server config file and VC database. Due to this the Update Manager Client and server might still use the old SOAP port.
    2. Updating HTTP port: When you update the HTTP port using the Network Configuration tab, the new HTTP port might not get updated in the Update Manager server config file leading to patch download failures.
      Workaround: For more information, see KB 2034138.
  • VMs and Templates view does not display virtual machines that are under a vApp in a resource pool
    When a resource pool contains a vApp, which contains virtual machines, the VMs and Templates list view of the vSphere Client or the vSphere Web Client does not display the virtual machines.
    Workaround: To perform a specific task for which you must see virtual machines under VMs and Templates view for vApps, you can reconfigure the vci-integrity.xml file.
    1. On the Windows machine where Update Manager is installed, go to the Update Manager server installation directory.
      The default location in 64-bit Windows is C:Program Files(x86) VMwareInfrastructureUpdate Manager
    2. Open the vci-integrity.xml file in an XML editor, and search for <inventorymonitorfilter><getresourcepoolupdates>
    3. Edit the <inventorymonitorfilter><getresourcepoolupdates> value from False to True, and save the vci-integrity.xml file.
    4. Restart the Update Manager Service for the configuration changes to take effect.
    5. Perform your task.
    6. Open vci-integrity.xml with an XML editor, search for the <inventorymonitorfilter><getresourcepoolupdates> tag and change its value to False.
  • Scan of a top-level inventory object against virtual machines baseline results in incorrect scan result, if a vApp option is enabled on a virtual machine
    When you scan a virtual machine or a set of virtual machines from a top-level inventory object, and the virtual machines have the vApp option enabled, the compliance information displayed for the top-level inventory object is incorrect. For example, if you have a folder with two virtual machines that have the vApp option enabled, and scan the folder against a virtual machine baseline, the result is Compliant compliance state. If you scan each virtual machine individually against the same baseline, you might see different scan results. The result of each individual virtual machine scan is the correct compliance state.
    Workaround: Individually scan each virtual machine that has the vApp option enabled.
  • Host remediation against bulletins that have only Reboot impact fails
    During the remediation process of an ESXi host against a patch baseline, which consists of bulletins that have only Reboot impact, Update Manager fails to power off or suspend the virtual machines that are on the host. As a result the host cannot enter maintenance mode, and the remediation cannot be completed.
    Workaround: Place the host in Maintenance Mode from the vSphere Client, and by using Update Manager remediate the host against the bulletins that have only Reboot impact.
  • VMware Update Manager does not use the configured proxy authentication
    When you initiate a patch download task, even though Update Manager is configured to use a proxy with authentication, Update Manager uses anonymous credentials to authenticate to the proxy server. If the proxy server does not accept anonymous credentials, the patch download task may fail.
    Workaround: Change Update Manager service to run using a local administrator account with local administrator rights or a domain account with local administrator rights.
  • The virtual machine that runs Update Manager might be powered off during a host upgrade
    Outside DRS clusters, Update Manager does not upgrade the host on which the vCenter Server or Update Manager virtual machine runs. In DRS clusters, if you start a remediation task on the host running the vCenter Server or Update Manager virtual machine, DRS attempts to migrate the virtual machine to another host, so that the remediation succeeds. If you remove the host on which the Update Manager virtual machine runs from a DRS cluster and then add it to a datacenter in the vSphere Client inventory, you can remediate the host and the Update Manager virtual machine is powered off.
    Workaround: Before remediation, ensure that the host on which the Update Manager virtual machine runs is in a DRS cluster or move the Update Manager virtual machine to another host.
  • You might be unable to view compliance information for a cloned virtual machine
    When you clone a virtual machine, enable Fault Tolerance for the machine, and power on the cloned virtual machine, you might not be able to view compliance information. When you open the Compliance view, the error Failed to retrieve data appears.
  • Missing patch type information in the Import Patches wizard
    On a new Update Manager installation, when you import offline patch bundles for the first time, patch type information is not displayed in the Import Patches wizard. The Type column on the Confirm Import page is empty.
    Workaround: Although the patch type information is not displayed, you can import the patches successfully by completing the wizard. This problem occurs only during the first import of offline patch bundles. Consequent import operations have the patch type information displayed correctly in the wizard.
  • Download patch definitions task might fail if Update Manager is configured to use authenticated proxy
    If the Update Manager server is configured to use a proxy server that requires authentication, the Download patch definitions task might fail to download patches.
    Workaround: Enable anonymous user access on the proxy server.
  • ESXi 5.0 does not support staging of a tools bulletin
    When you run a stage task with an ESXi 5.0 tools bulletin, the task completes successfully, but the tools bulletin is not staged.
    Workaround: You can remediate the Tools bulletin directly to install it. Host maintenance mode or reboot, and consequently host downtime, are not required during the remediation of the tools bulletin.
  • Update Manager cannot download updates from a valid download source
    A non-existent HTTPS URL might be incorrectly displayed as accessible in the Add Download Source window. For example, if you type https://mydepot.com instead of http://mydepot.com and click Validate URL, the validation might succeed even if the actual download source is an HTTP address. As a result, Update Manager cannot download updates from the specified HTTPS URL address.
    Workaround: Delete the URL and add it correctly.
  • Invalid email addresses in the email notification settings prevent Update Manager from sending email messages
    In the patch and notification download schedules, you can configure Update Manager to send emails when new patches or notifications are downloaded. If you enter invalid email addresses, Update Manager might not send emails. If you enter an invalid email address with the same domain name as the SMTP Server sender account in vCenter Server mail sender setting, Update Manager does not deliver emails to any of the email addresses (including the valid ones). If the domain name of the invalid email addresses is different from the SMTP Server sender account in vCenter Server mail sender setting, email notifications can be successfully delivered to the valid email addresses entered in the Update Manager email notification settings.
    Workaround: Remove the invalid email addresses from the email notification settings.
  • In Windows Vista, all Help buttons in the Update Manager Client open the default Update Manager help page
    If you are using Internet Explorer 7 browsers installed on Windows Vista machines, the vSphere Update Manager context-sensitive help does not display the relevant help pages. Instead, the help displays the default vSphere Update Manager help page.
    Workaround: Apply Service Pack 2 to Windows Vista. For more details, see the Microsoft KB article http://support.microsoft.com/kb/942172.
  • Notification emails might be blocked by antivirus software
    You might not receive any email notifications from Update Manager if you have certain antivirus software installed on your vCenter Server system. Update Manager can be configured to send email notifications, such as notifications for newly downloaded patches and other scheduled tasks. If you have installed antivirus software (for example, McAfee) that monitors and blocks email traffic, you might not be able to receive the notifications from Update Manager.
    Workaround: Disable the antivirus software rule that blocks the email traffic.
  • ESX 4.0 hosts might lose network connectivity after remediation if the VMkernel is configured to use DHCP
    When Update Manager patches ESX hosts, the patches might require host reboot. After rebooting, vCenter Server might be unable to add the ESX host to the vSphere inventory if the VMkernel of the host is configured to use DHCP.
    Workaround: Configure the VMkernel of the host to use a static IP address, or install patch ESX400-200906402-BG, which fixes the ESX 4.0 issues. You can find patch ESX400-200906402-BG in the ESX400-200906001.zip bundle.
  • Switching between Compliance view and Administration view might navigate you to the wrong location
    When you select a datacenter object in the VMs and Templates inventory of the vSphere Client and use the Admin view and Compliance view quick links to navigate to the Update Manager Administration view and the Update Manager Compliance view, you might go to the wrong vSphere Client inventory. For example, select Home > Inventory > VMs and Templates in the navigation bar. Select a datacenter object in the inventory and click the Update Manager tab to open the Update Manager Compliance view. When you click Admin view and then go back by clicking the Compliance view link, you navigate to the Host and Clusters inventory instead of the VMs and Templates inventory.
    Workaround: Manually navigate from the Hosts and Clusters inventory view to the VMs and Templates view by selecting Home > Inventory > VMs and Templates in the navigation bar.
  • Update Manager does not take snapshots of virtual machines on which FT is turned on before remediation
    You cannot take snapshots of virtual machines on which FT is enabled. If you remediate a virtual machine on which FT is turned on and in the Remediate wizard choose to take a snapshot before remediation, Update Manager ignores this setting and does not take a snapshot of the virtual machine.
    Workaround: Disable FT, configure Update Manager to take a snapshot of the virtual machine, and remediate the machine. If you want to turn on FT after the remediation, delete the snapshot and then enable FT.
  • Virtual hardware upgrade or VMware Tools upgrade might fail with error fault.com. - vmware.vc - Integrity.V - MToolsRemediationFault.summary
    The upgrade failure might occur on virtual machines migrated with vMotion from ESX 3.0.x hosts to ESX 4.0.x hosts. In this situation, the guest ID property of the virtual machine is unset, but a new ID is not assigned. Update Manager attempts to read the guest ID during VMware Tools upgrade, and the task fails. The same issue might occur on virtual machines that are reverted to a snapshot, or resumed from suspended state on ESX 4.0.x hosts.
    Workaround: Manually upgrade VMware Tools, and then upgrade the virtual hardware of the virtual machine.
  • When multiple users attempt to create a baseline with the same name simultaneously, Update Manager displays an ambiguous error message
    When multiple users attempt to create a baseline with the same name simultaneously, Update Manager displays the message The specified key, name, or identifier already exists. The message does not inform you explicitly that another user is attempting to create a baseline with the same name.
  • When you stage a baseline that contains multiple bulletins, some bulletins might be shown as missing
    After the successful staging of a baseline that contains multiple bulletins, some bulletins might be shown as Staged and others as Missing. For more information, see After you stage a baseline, a bulletin might be shown as Missing instead of Staged (KB 1018530).
  • Update Manager fails to install and upgrade the Cisco Nexus 1000V VEM, if the ESX host is running on an IPv6 networking stack
    When an ESX host is added to a Cisco Nexus 1000V DVS, Update Manager installs the Cisco Nexus 1000V VEM on the host. Upgrading the Cisco Nexus 1000V VSM to the latest version invokes Update Manager to upgrade the VEM on the host attached to the DVS. Both the installation and the upgrade operations might fail if the host is running on an IPv6 networking stack.
    Workaround: Install or upgrade the VEM on the host manually, by using the offline bundle.
  • 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.
  • Scheduling a remediation task generates a set of tasks
    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.
  • Administration view and Compliance view quick-switch links might not work properly if your environment is in linked mode
    If your vCenter Server system is part of a Linked Mode and you have a separate Update Manager instances registered with each vCenter Server system, the Admin view and Compliance view navigation links might not work properly. For example, consider a scenario in which Update Manager instance 1 is registered with vCenter Server system 1 and Update Manager instance 2 is registered with vCenter Server system 2. When you select an object managed by vCenter Server system 1, click the Update Manager tab, and then click Admin view in the upper-right corner, you see the Administration 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 Administration view of Update Manager instance 1 again.
    Workaround: Click Compliance view and then click Admin view again to see the Administration view of the second Update Manager instance.
  • 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.
  • Update Manager Service might fill the Temp directory with many temporary system 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:WINDOWSTemp).
    • 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), perform the following steps:
      1. Select Start > Run.
      2. In the Run window, type regedit and press Enter.
      3. In Registry Editor, navigate to the My ComputerHKEY_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 run the following command:
        del C:WindowsTempufa729F.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 are removed 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), perform the following steps:
      1. Open a command prompt window.
      2. Navigate to C: and run the following command:
        del C:WindowsTempufaFF50.tmp.LOG2