check-circle-line exclamation-circle-line close-line

VMware vCenter Server 6.0 Update 3g Release Notes

vCenter Server 6.0 Update 3g | 26 JUL 2018 | ISO Build 9146214

vCenter Server Appliance 6.0 Update 3g | 26 JUL 2018 | ISO Build 9146214

vCenter Server 6.0 Update 3g on vCenter Server Appliance Build 9109104

vCenter Server 6.0 Update 3g on Windows Build 9109103

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Pivotal tc Server replacement: Pivotal tc Server is now replaced with Tomcat 8.5.24 and Tomcat 8.5.23.
  • Updates to time zones in the Linux guest operating system customization: vCenter Server Linux guest operating system customization supports latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Linux guest operating systems, see the Time Zone Database by the Internet Assigned Numbers Authority (IANA).
  • Updates to time zones in the Windows guest operating system customization: vCenter Server Windows guest operating systems customization supports the latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Windows guest operating systems, see the Microsoft Knowledge Base article 3182203, Microsoft Knowledge Base article 4015193 and Microsoft Knowledge Base article 4012864.
  • TLS support: vCenter Server 6.0 Update 3g supports TLS version 1.2 for encrypted connection to Microsoft SQL Server. For more information, see VMware knowledge base article 2149745.
  • External database support: vCenter Server 6.0 Update 3g supports the Microsoft SQL Server 2014 Service Pack 2, SQL Server 2016, SQL 2016 Service Pack 1 and SQL Server 2012 Service Pack 4.

Upgrade Notes for This Release

Important: Upgrade and migration paths from vCenter Server 6.0 Update 3g deployed with embedded Postgres DB to vCenter Server 6.5 Update 2d and 6.7 Update 1 are supported.

Earlier Releases of vCenter Server 6.0

For internationalization, compatibility, installation and upgrades, and product support notices, see the  VMware vCenter Server 6.0 Update 3 Release Notes.

Patches contained in this release

vCenter Server 6.0 Update 3g delivers the following patches. See the VMware Patch Download Center for more information on downloading patches.

Third Party (TP.iso) patches for vCenter Server Applicance containing Third Party Product fixes are not supported starting from vCenter Server 6.0 Update 3g.

Security Patch for VMware vCenter Server 6.0 Update 3g

Security fixes (for example: JRE). This patch is applicable for vCenter Server for Windows, Platform Services Controller for Windows, and vSphere Update Manager.

For vCenter Server and Platform Services Controller for Windows

Download Filename VMware-VIMPatch-6.0.0-8814879-20180726.iso
Build 8814879
Download Size 87.4 MB
md5sum 083032b4f3ed92bc696aad959eff88ba
sha1checksum 0758851e576f5045debfacb90bcac757981e7721

These vCenter Server components depend on JRE and have to be patched:

  • Platform Services Controller
  • vSphere Update Manager
  • vCenter Server

Download and Installation

You can download this patch by going to the VMware Patch Download Center and choosing VC from the Search by Product drop-down menu. 

  1. Mount the VMware-VIMPatch-6.0.0-8814879-20180726.iso to the system where the vCenter Server component is installed.  
  2. Double-click ISO_mount_directory/autorun.exe.
  3. In the vCenter Server Java Components Update wizard, click Patch All.

Full Patch for VMware vCenter Server Appliance 6.0 Update 3g

Product Patch for vCenter Server Appliance 6.0 containing VMware software fixes, security fixes, and Third Party Product fixes (for example: JRE).

This patch is applicable to the vCenter Server Appliance and Platform Services Controller Appliance.

NOTE: Third Party (TP.iso) patches for vCenter Server Applicance containing Third Party Product fixes are not supported starting from vCenter Server 6.0 Update 3g.

For vCenter Server and Platform Services Controller Appliances

Download Filename VMware-vCenter-Server-Appliance-6.0.0.30700-9146216-patch-FP.iso
Build 9146216
Download Size 1806.0 MB
md5sum c9690a41089a2a2249cabc156ad2efb5
sha1checksum b05814733613244ab8085ac4bd7956a18e1b53c5

Download and Installation

You can download this patch by going to the VMware Patch Download Center and choosing VC from the Search by Product drop-down menu.

  1. Attach the VMware-vCenter-Server-Appliance-6.0.0.30700-9146216-patch-FP.iso file to the vCenter Server Appliance CD or DVD drive.
  2. Log in to the appliance shell as root and run the commands given below:
    • To stage the ISO:

      software-packages stage --iso

    • To see the staged content:

      software-packages list --staged

    • To install the staged rpms:

      software-packages install --staged

For more information on patching the vCenter Server Appliance, see Patching the vCenter Server Appliance

For more information on staging patches, see Stage Patches to vCenter Server Appliance

For more information on installing patches, see Install vCenter Server Appliance Patches

For issues resolved in this patch see the Resolved Issues section.

For more information on patching using the Appliance Management Interface, see Patching the vCenter Server Appliance by Using the Appliance Management Interface.

 

Resolved Issues

The resolved issues are grouped as follows.

Installation Issues
  • Stateful installations on hosts with a Cisco Nexus N1K VEM driver might fail

    Stateful installations might fail during the creation of scratch partitions in a configuration with a Cisco Nexus N1K VEM driver. The n1k-vem service might stop before the stateful installation is complete, and start after the installation to apply the host profile. 

    This issue is resolved in this release.

Miscellaneous Issues
  • Creation of snapshots during backup operations takes long to complete and vCenter Server stops displaying event data about objects in the inventory

    During backup operations that require the creation of snapshots, tasks that post events as part of their workflow might take long to complete. vCenter Server stops displaying event data about objects in the inventory.

    This issue is resolved in this release.

  • SNMP displays CPU and memory utilization of a vCenter Server Appliance constantly at 100%

    If you use the snmpwalk command to query the CPU and memory utilization of a vCenter Server Appliance, SNMP might consistently report 100% even though the actual utilization is lower.

    This issue is resolved in this release. 

  • Alarms might not respond to triggers with status Unset

    If you set alarms using the vSphere Web Client and you leave a trigger with status Unset, such alarms might not prompt any actions. You might see the following error message: An internal error occurred in the vSphere Client. Details: The provided alarm status is invalid.

    This issue is resolved in this release.

  • You cannot place an ESXi host into an empty Enhanced vMotion Compatibility (EVC) cluster even though the host meets the requirements

    Adding hosts that are not patched with the hypervisor-assisted guest mitigation for guest operating systems to an empty EVC cluster might fail, because the patches contain new CPU features.

    This issue is resolved in this release.

  • Third-party trap receivers might reject traps older than 497 days from a vCenter Server Appliance

    Third-party trap receivers might reject traps older than 497 days from a vCenter Server Appliance, because at this point the parameter tracking time exceeds the limit of 4 bytes.

    Тhis issue is resolved in this release.

Networking Issues
  • After you cancel the cloning of a virtual machine, the virtual machine directory continues to exist

    vCenter Server might not remove the port file directory (.dvsData) in the virtual machine directory after the process for cloning a virtual machine ends. As a result, the virtual machine directory continues to exist.

    This issue is resolved in this release.

  • Link Aggregation Groups (LAGs) might be lost during the import of a VMware vSphere Distributed Switch configuration

    If you import a vSphere Distributed Switch (VDS) configuration with many LAGs, the vCenter Server daemon vpxd might fail to insert the corresponding LAG information into the vCenter Server database. As result, some LAGs might be missing after a restart of the vpxd.

    This issue is resolved in this release. If you already face the issue, delete and re-import the VDS configuration, or create the missing LAGs manually.

  • Migration of virtual machines by using VMware vSphere vMotion might fail when you import ephemeral port groups

    If you import ephemeral port groups or a VDS instance with such groups, migration of virtual machines by using vSphere vMotion might fail, because the ports might not exist after the migration. You might see an error similar to A general system error occurred: vim.fault.NotFound.

    This issue is resolved in this release. If you already face the issue, after the migration you must delete the imported ephemeral port groups or VDS with such port groups, and re-import them.

  • The vSphere Web Client might display an error in the VDS topology after a restart of vpxd due to outdated LAGs data

    The vSphere Web Client might display an error in the VDS topology after a restart of vpxd due to outdated LAGs data. The vCenter Server database might not be updated with data for physical adapters added to the LAGs before the restart, and the daemon might not be able to find it.

    This issue is resolved in this release. If you already face the issue, you must reassign the physical adapters to the LAGs.

  • vSphere ESX Agent Manager (EAM) fails to map agents to new ESXi hosts in NSX host clusters

    Due to synchronization issues in vpxd, EAM might fail to map agents to newly added ESXi hosts in NSX managed clusters.
    EAM logs might contain entries similar to:
    ​| ERROR | vc-callback | AgencyImpl.java | 1295 | Failed to add agent to agency (AgencyImpl(ID:'Agency:XXXXX')): java.lang.RuntimeException: Host is no longer in vCenter inventory | WARN | eam-0 | AgencyImpl.java | 1954 | Disposing agency: AgencyImpl(ID:'Agency:XXXXXXX') due to failed load up. |

    ERROR | eam-0 | AgencyImpl.java | 1895 | Failed to load agent: ManagedObjectReference: type = Agent, value = f18cd000-dcd5-4d30-8d6b-5f12b04e46fa, serverGuid = b0827a9b-fccd-41dd-8b27-caf8418da719. Error: null java.lang.NullPointerException | ERROR | eam-0 | VcListener.java | 116 | An unexpected error in the changes polling loop

    This issue is resolved in this release.

  • EAM might fail to start if an ESXi host is removed from an NSX host cluster

    If you move an ESXi host out of an NSX host cluster while the EAM service is not working for some reason, EAM might fail to start. With this fix, EAM skips loading agents on hosts that are moved out of their previous agency and allows EAM to start. After EAM starts, you can move displaced hosts into other agencies and clusters. EAM logs might contain entries similar to:

    | ERROR | eam-0 | VcListener.java | 116 | An unexpected error in the changes polling loop

    | ERROR | eam-0 | AgencyImpl.java | 1895 | Failed to load agent: ManagedObjectReference: type = Agent, value = d6429441-6953-4795-81ff-efc455232e9a, serverGuid = b0827a9b-fccd-41dd-8b27-caf8418da719. Error: Host not covered by scope anymore

    This issue is resolved in this release.

  • Adding a host to Cisco N1K DVS by using the vSphere Web Client might fail

    Adding a host to Cisco N1K DVS by using the vSphere Web Client might fail with an error similar to The number of physical network adapter per host exceeds the number of uplink ports.

    This issue is resolved in this release.

  • VMware vSphere High Availability might fail to power on a secondary virtual machine after а failover

    vSphere High Availability might fail to power on a secondary virtual machine after a failover, due to missing port files. After an upgrade to vCenter Server 6.0 Update 3g, you must turn off vSphere Fault Tolerance and restart it to create port files in the datastores of both the primary and secondary virtual machines.

    This issue is resolved in this release.

Security Issues
  • Pivotal tc Server license expired in March 2018

    Pivotal tc Server license expired in March 2018. The server provides Apache Tomcat 8.5.24 access and runs multiple Tomcat runtime instances with a single physical installation. The current update removes tc Server dependency and all services on vCenter Server use Apache Tomcat directly.

    This issue is resolved in this release.

  • Update to Apache Struts framework

    The Apache Struts framework is updated to version 2.5.16 to resolve a security issue with identifier CVE-2018-1327.

  • Update to vPostgres

    vPostgres is updated to 9.3.22 to resolve a security issue with identifier CVE-2018-1058.

  • Update to JRE

    Oracle (Sun) JRE is updated to version 1.7.0_181.

  • cURL in the vCenter Server Appliance is updated to 7.58

    cURL in the vCenter Server Appliance is updated to 7.58 to address issues with identifiers CVE-2017-8818, CVE-2017-8817, CVE-2018-1000007 and CVE-2018-1000005.

  • Update to Python

    The Python third party library is updated to version 2.7.14 to resolve security issues with identifiers CVE-2017-1000158 and CVE-2014-4616.

  • The default validity of VMware Certificate Authority (CA) certificates is reduced to two years

    The default validity of all VMware CA certificates is reduced to 2 years from 10 years. VMware CA certificates expire within up to 825 days according to recommendations by the CA/Browser Forum.

  • Update of the Jackson library

    The Jackson JavaScript Object Notation (JSON) processor package is updated to version 2.9.5.

Server Configuration Issues
  • Open cursors in the memory of the vCenter Server Appliance embedded database might cause performance and disk space issues

    Failures to close SQL handles or free associated cursors and memory resources in the embedded PostgreSQL database in vCenter Server Appliance might cause indefinite expansion of tables and indexes. This might lead to reduced disk space and performance.

    This issue is resolved in this release. 

  • vCenter Server might stop responding if you remove a Pluggable Storage Architecture (PSA) path on an ESXi host

    If you remove a PSA path on an ESXi host while vCenter Server is not running, it is added as a new path when vCenter Server restarts. This might cause vCenter Server to stop responding with the following error message: ERROR: duplicate key value violates unique constraint "vpxi_psa_path”.

    This issue is resolved in this release.

  • vSphere Storage DRS tasks in large datastore clusters might take long to complete

    vSphere Storage DRS tasks in large datastore clusters might take long to complete due to slow querying of datastore tags. To mitigate the issue, vCenter Server 6.0 Update 3g introduces a SrmSupportNeeded flag as an advanced option setting for datastore clusters. The flag value is set to 1 and turned on by default. You can turn off the flag when Site Recovery Manager support is not needed by setting the parameter value to 0. As result, this boosts vSphere Storage DRS task performance. In addition, the BatchTagQuery advanced option is turned on by default, which also improves task performance.

    This issue is resolved in this release.

Storage Issues
  • Storage alarm and event messages are displayed as Unknown event ID or Unknown message identifier

    Storage alarm and event messages are not correctly transformed when posted to vCenter Server. As a result, they are displayed as Unknown event ID or Unknown message identifier.

    This issue is resolved in this release.

Tools Issues
  • The SNMP v3 agent allows users with priv security level to access data by providing only an authentication key phrase or no security key phrase at all

    The SNMP v3 agent allows users with priv security level to access data by providing only an authentication key phrase or no security key phrase at all. Users with priv security level must provide both an authentication key phrase and a privacy key phrase. 

    This issue is resolved in this release.

  • The vSphere Web Client might display a confusing status for VMware Tools

    If you manually reinstall the same version of VMware Tools on a guest virtual machine more than once, the ESXi host might receive contradicting reports that VMware Tools is not installed, while at the same time VMware Tools operations are running. At this point, the vSphere Web Client displays a warning message similar to: VMware Tools: Running, version: 10304 (Not installed).

    This issue is resolved in this release. 

  • Replacing a machine SSL certificate with a custom certificate authority (CA) signed certificate might fail with an error

    Using the option Replace Machine SSL certificate in the vSphere Certificate Manager utility might fail with a message error 20 at 0 depth lookup:unable to get local issuer certificate due to incorrect validation of host entries.

    This issue is resolved in this release. If you are using an older version of vCenter Server 6.0, you can change the value of the parameter return isresult to return True at /usr/lib/vmware/site-packages/cis/certificateManagerHelper.py for the vCenter Server Appliance. For vCenter Server on Windows, the path is C:\Program Files\VMware\vCenter Server\python-modules\cis\certificateManagerHelper.py .

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • vCenter Server Appliance might run out of disk space due to piled dnsmasq logs

    The dnsmasq logs might not be rotated and pile up to exceed the disk space of a vCenter Server Appliance.

    This issue resolved in this release.

  • Group permissions might result in limited or revoked permissions for a user if one of the assigned roles is No Access

    If a user belongs to two or more groups and one of the groups is assigned a No Access role, the user might have limited or no effective permissions.

    This issue is resolved in this release.

  • The vpxd service might fail when you close the root folder from the Inventory View

    If you add an ESXi host to a cluster and create a VMware vSphere vApp in this cluster, when you navigate to the vApp from the Inventory View in the vSphere Web Client, vpxd might fail with an error Panic: Assert Failed: "openedInfo._activations == 0" at the time you close the root folder.

    This issue resolved in this release. 

Virtual Machine Management Issues
  • A VMware vSphere Storage DRS task might run into a loop​

    A vSphere Storage DRS task might run into an infinite loop which blocks other vSphere Storage DRS tasks for the same storage cluster. You might observe high CPU usage or timeouts of vSphere Storage DRS tasks.

    This issue is resolved in this release. 

  • Deploying an OVF template exported from an ESXi 5.5 host to a content library on an ESXi 6.0 host might fail

    Deploying an OVF template exported from an ESXi 5.5 host to a content library on an ESXi 6.0 host might fail with an error The operation failed due to Invalid configuration for device 8.

    This issue is resolved in this release.

  • EAM might delete active agents during resource availability checks

    EAM might delete active agent virtual machines during resource availability checks and cause data loss. This fix prevents EAM from deleting active agents to free resources if it fails to power on a service virtual machine due to resource limitations like CPU and memory allocation.

    This issue is resolved in this release.

  • Performance of vSphere Storage DRS might drop due to excessive number of parallel tasks

    You might trigger multiple tasks in parallel to handle threshold violation events in vSphere Storage DRS, because there is no check for such tasks. This might degrade the performance of vSphere Storage DRS.

    This issue is resolved in this release. 

  • vCenter Server might stop responding during virtual machine deployment

    When you deploy a new virtual machine, vCenter Server might stop responding if a datastore becomes unavailable during the initial placement of virtual disks with vSphere Storage DRS.

    This issue is resolved in this release.

  • Attempting virtual machine provisioning operations while IPv6 support is disabled causes ESXi hosts to disconnect

    The Network File Copy daemon (NFCD) creates both IPv4 and IPv6 sockets on ESXi hosts. If you attempt virtual machine provisioning operations, such as cold migration or cloning, by using the provisioning TCP/IP stack while IPv6 support is disabled, the host might disconnect from the network without using the IPv4 socket.

    This issue is resolved in this release.

  • vCenter Server might stop responding when you attempt to add а new disk to a virtual machine

    When you attempt to add a virtual disk to a virtual machine, vSphere Storage DRS might cause vCenter Server to stop responding while generating datastore recommendations.

    This is resolved in this release.

  • VMware Site Recovery Manager workflows might fail due to a race condition

    Site Recovery Manager workflows, such as test a recovery plan, might fail due to a race condition with an error similar to java.util.concurrent.ExecutionException: com.vmware.vim.vmomi.client.exception.InternalException: Trying to override already set SSL user token with different one. In the vCenter Sever Appliance, you can find the error in var/log/vmware/workflow/workflow-manager.log.

    This issue is resolved in this release.

  • DRS affinity rules might be disabled if virtual machines change clusters

    If a virtual machine is subject of a VM-VM affinity or anti-affinity rule and you move it from one cluster to another, and later return the virtual machine to the first cluster, the affinity rule might no longer be active. In the vpxd logs, you might see reports for conflict of rules that cause the existing rules to be disabled.

    This issue is resolved in this release. 

  • Virtual machine operations fail with a compatibility error when a virtual machine hardware version upgrade is scheduled

    When a virtual machine hardware version upgrade is scheduled, virtual machine operations might fail with the following compatibility error message: The destination host is not compatible with the hardware version to which the virtual machine is scheduled to be upgraded. For more information, see VMware Knowledge Base article 2080107.

    This issue is resolved in this release.

vMotion and Storage vMotion Issues
  • vCenter Server might become unresponsive during migration of virtual machines by using vSphere Storage vMotion or XvMotion

    When you try to perform Storage vMotion or XvMotion migration of a virtual machine with two or more snapshots that each contain the same independent disks, vCenter Server might become unresponsive.

    This issue is resolved in this release.

  • Migrating virtual machines across vCenter Server systems might fail with a No Permission error

    When you migrate virtual machines across vCenter Server systems, despite having System.Read privileges on the destination object, if you do not have System.Read privilege on the destination data center, the migration might fail with a No Permission error.

    This issue is resolved in this release.

vSAN Issues
  • vSAN requires RVC to configure TLS protocol version for vSAN Observer

    vSAN Observer can read the TLS protocol version only when you run it from RVC command-line interface. The TLS version is not stored in a configuration file. If you run vSAN Observer form vCenter Server, it cannot read the TLS version.

    This issue is resolved in this release.

  • vSAN health service might fail to load when one site of a stretched cluster is down

    When all of hosts in one site of stretched cluster are down, the vSAN health service might not be loaded and show any data due to an unexpected exception.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Installation, Upgrade and Migration Issues
  • Migration from vCenter Server on Windows 5.5.x and 6.0.x to vCenter Server Appliance 6.5.x might fail during data export

    Migration from vCenter Server on Windows 5.5.x and 6.0.x to vCenter Server Appliance 6.5.x might fail during data export with an error such as The compressed zip folder is invalid or corrupted.

    Workaround: Archive the data export folder manually:

    1. In the source Windows system, create an environment variable MA_INTERACTIVE_MODE.
      • Go to Computer > Properties Advanced system settingsEnvironment Variables > System Variables > New.
      • Enter MA_INTERACTIVE_MODE as variable name with value 0 or 1.
    2. Start the VMware Migration Assistant and provide your password.
    3. Deploy the .ovf file with the standalone installer to complete Stage 1 of the migration.
    4. In Stage 2, the migration pauses and the Migration Assistant console displays the message To continue the migration, create the export.zip file manually from the export data (include export folder).
      NOTE: Do not press any keys or tabs on the Migration Assistant console.
    5. Go to path: %appdata%\vmware\migration-assistant folder.
    6. Delete the export.zip folder created by the Migration Assistant.
    7. To continue the migration, manually create the export.zip folder from the export folder.
    8. In the Migration Assistant console, type Y and press Enter.

    Migration must start as usual.

  • Upgrade of vCenter Server for Windows might fail with error code 3010

    Upgrade of vCenter Server for Windows to version 6.x might fail with an error Installation of component VMware vCenter Server failed with error code '3010'. Check the logs for more details, if the OpenSSL package is of higher version than the update release.

    In the %TEMP%\vminst.log file, you might see similar logs:

    YYYY-MM-DD>T<time>| vcsInstUtil-5318198| E: wWinMain: MSI result of install of "E:\vCenter-Server\Packages\vmware-vpxd.msi" may have failed: 3010 (0x00000bc2)

    YYYY-MM-DD>T<time>| vcsInstUtil-4541944| E: LaunchPkgMgr: Operation on vmware-vpxd.msi appears to have failed: 3010 (0x00000bc2)

    YYYY-MM-DD>T<time>| vcsInstUtil-4541944| I: PitCA_MessageBox: Displaying message: "Installation of component VMware vCenter Server failed with error code '3010'. Check the logs for more details.

    YYYY-MM-DD>T<time>| vcsInstUtil-5318198| E: wWinMain: MSI result of install of "E:\vCenter-Server\Packages\vmware-openssl.msi" may have failed: 3010 (0x00000bc2)

    YYYY-MM-DD>T<time>| vcsInstUtil-5318198| E: LaunchPkgMgr: Operation on vmware-openssl.msi appears to have failed: 3010 (0x00000bc2)

    YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: PitCA_MessageBox: Displaying message: "Installation of component VMware Open SSL components failed with error code '3010'. Check the logs for more details."

     

    In the pkgmgr-comp-msi.log file, you might see logs similar to:

    YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: UpdatePackageList: File: Z:\vCenter-Server\Packages\vmware-openssl.msi

    YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: UpdatePackageList: VersionCompare - Version: 6.0.0.9090 VersionInstalled: 6.0.0.60000 Res: -1

    YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: UpdatePackageList: ProductCodeCompare - ProductCode: {3D2B421E-617E-46F2-A83F-BF8AB22DBAAF} ProductCodeInstalled: {7CA4FE96-7C9E-40ED-ABF7-3EA5D78529D3} Res: -1

    YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: UpdatePackageList: Disabling installation of package Z:\vCenter-Server\Packages\vmware-openssl.msi (ProductCode is different but ProductVersion is smaller than the one already on the system)

    Workaround: 

    1. Open the Windows Registry regedit.exe.
    2. Search for key 7CA4FE96-7C9E-40ED-ABF7-3EA5D78529D3 in HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\. If you find the key, back it up and remove it.
    3. Search for value 6.0.0.60000 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\. If you find the value, back up the key and remove it.
    4. Retry the upgrade.
  • Patching from vCenter Server 6.0, 6.0.0a and 6.0.0b to vCenter Server 6.0 Update 3g might take too long

    When patching a vCenter Server Appliance from vCenter Server 6.0, vCenter Server 6.0.0a or vCenter Server 6.0.0b to vCenter Server 6.0 Update 3g, the process might take too long due to issues with the RPM update. All services might become temporarily unavailable.

    Workaround: None. For more information on the issue, see KB 56625.

  • VMware vCenter Single Sign-On Security Token Service (STS) might not retain any custom TLS configuration after patching

    STS services might not keep any custom TLS configuration after patching. Instead, TLSv1, TLSv1.1 and TLSv1.2 protocols are enabled.

    Workaround: Use the TLS Configurator utility to restore the TLSv1.2 configuration.

Miscellaneous Issues
  • The Client Integration Plug-In might not work as expected if you log in to the vSphere Web Client using Firefox

    When you log in to the vSphere Web Client using Firefox from a Windows or Mac OS, and perform tasks related to the Client Integration Plug-In, you might encounter the following issues:

    •  Export or import OVF files (.ovf) is not enabled.
    •  Upload or download files to datastores is not enabled.
    •  Windows Session Authentication (SSPI) login is not enabled.
    •  Upload to or download from the Content Library is not enabled.

    You might also see a message such as Client integration plug-in is not installed. Please install and Refresh the browser.

    Workaround: You can use alternative browsers, such as Google Chrome or Internet Explorer.

  • Client Integration Plug-In installation might fail

    The installation of the Client Integration Plug-In might fail. The Microsoft Visual C++ Redistributable Packages for Visual Studio are not installed on the Windows host machine.

    Workaround: Before installing the Client Integration Plug-in, download and install the missing Microsoft Visual C++ Redistributable Packages for Visual Studio that are supported by your system. You can check whether the packages are installed on your host machine by using Add/Remove Programs. You can check which packages you need depending on your Windows version in the System Requirements section for the different versions of Visual C++ Redistributable Packages on the Microsoft website. Install both x86.exe and x64.exe of Microsoft Visual C++ Redistributable Packages for Visual Studio.

  • Оlder versions of the vSphere Web Client might not detect the latest version of the Client Integration Plug-in

    Оlder versions of the vSphere Web Client might not detect the latest version of the Client Integration Plug-in due to changes in the product builds for VMware vCenter Server 6.0 Update 3g. The changes are related to both the Client Integration Plug-in and the vSphere Web Client.

    Workaround: Upgrade to the latest Client Integration Plug-in version while accessing VMware vCenter Server 6.0 Update 3g by using the vSphere Web Client.

Known Issues from Earlier Releases

To view a list of previous known issues, click here.