vCenter Server 6.0 Update 3c | 9 NOV 2017 | ISO Build 7040641

vCenter Server Appliance 6.0 Update 3c | 9 NOV 2017 | ISO Build 7040641

vCenter Server 6.0 Update 3c on vCenter Server Appliance Build 7037393

vCenter Server 6.0 Update 3c on Windows Build  7037394

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

Use of SMB2 is enabled for vCenter Server Appliance 6.0 Update 3c to overcome SMB1 vulnerability.

VMware vCenter Server 6.0 Update 3c is compatible only with VMware vSphere Replication 6.1.2.1 and VMware Site Recovery Manager 6.1.2.1.

Earlier Releases of vCenter Server 6.0

Patches contained in this release

This release of vCenter Server 6.0 Update 3c delivers the following patch. See the VMware Patch Download Center for more information on downloading patches.

Internationalization

VMware vSphere 6.0 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Spanish
  • Traditional Chinese

Components of VMware vSphere 6.0, including vCenter Server, ESXi, the vSphere Web Client, and the vSphere Client do not accept non-ASCII input.

Compatibility

ESXi, vCenter Server, and vSphere Web Client Version Compatibility

The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Web Client, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install ESXi or vCenter Server.

The vSphere Web Client is packaged with the vCenter Server. You can install the vSphere Client from the VMware vCenter autorun menu that is part of the modules ISO file.

Hardware Compatibility for ESXi

To view a list of processors, storage devices, SAN arrays, and I/O devices that are compatible with vSphere 6.0, use the ESXi 6.0 information in the VMware Compatibility Guide.

Device Compatibility for ESXi

To determine which devices are compatible with ESXi 6.0, use the ESXi 6.0 information in the VMware Compatibility Guide.

Some devices are deprecated and no longer supported on ESXi 6.0. During the upgrade process, the device driver is installed on the ESXi 6.0 host. The device driver might still function on ESXi 6.0, but the device is not supported on ESXi 6.0. For a list of devices that are deprecated and no longer supported on ESXi 6.0, see KB 2087970.

Third-Party Switch Compatibility for ESXi

VMware supports Cisco Nexus 1000V with vSphere 6.0. vSphere requires a minimum NX-OS release of 5.2(1)SV3(1.4). For more information about Cisco Nexus 1000V, see the Cisco Release Notes. As in previous vSphere releases, Cisco Nexus 1000V AVS mode is not supported.

Guest Operating System Compatibility for ESXi

To determine which guest operating systems are compatible with vSphere 6.0, use the ESXi 6.0 information in the VMware Compatibility Guide.

Virtual Machine Compatibility for ESXi

Virtual machines that are compatible with ESX 3.x and later (hardware version 4) are supported with ESXi 6.0. Virtual machines that are compatible with ESX 2.x and later (hardware version 3) are not supported. To use such virtual machines on ESXi 6.0, upgrade the virtual machine compatibility. See the vSphere Upgrade documentation.

Installation and Upgrades for This Release

Installation Notes for This Release

Read the vSphere Installation and Setup documentation for guidance about installing and configuring ESXi and vCenter Server.

Although the installations are straightforward, several subsequent configuration steps are essential. Read the following documentation:

vSphere 6.0 Recommended Deployment Models

VMware recommends only two deployment models:

  • vCenter Server with embedded Platform Services Controller. This model is recommended if one or more standalone vCenter Server instances are required to be deployed in a data center. Replication between these vCenter Server with embedded Platform Services Controller models is not recommended.

  • vCenter Server with external Platform Services Controller. This model is recommended only if multiple vCenter Server instances need to be linked or want to have reduced footprint of Platform Services Controller in the data center. Replication between these vCenter Server with external Platform Services Controller models is supported.

Read the vSphere Installation and Setup documentation for guidance on installing and configuring vCenter Server.

Also, read KB 2108548 for guidance on installing and configuring vCenter Server.

vCenter Host OS Information

Read the Knowledge Base article KB 2091273.

Backup and Restore for vCenter Server and the vCenter Server Appliance Deployments that Use an External Platform Services Controller

Although statements in the vSphere Installation and Setup documentation restrict you from attempting to backup and restore vCenter Server and vCenter Server Appliance deployments that use an external Platform Services Controller, you can perform this task by following the steps in KB 2110294.

Migration from Embedded Platform Services Controller to External Platform Services Controller

vCenter Server with embedded Platform Services Controller cannot be migrated automatically to vCenter Server with external Platform Services Controller. Testing of this migration utility is not complete.

Before installing vCenter Server, determine your desired deployment option. If more than one vCenter Server instances are required for replication setup, always deploy vCenter with external Platform Services Controller.

Migrating Third-Party Solutions

For information about upgrading with third-party customizations, see the vSphere Upgrade documentation. For information about using Image Builder to create a custom ISO, see the vSphere Installation and Setup documentation.

Upgrades and Installations Disallowed for Unsupported CPUs

vSphere 6.0 supports only processors available after June (third quarter) 2006. Comparing the processors supported by vSphere 5.x, vSphere 6.0 no longer supports the following processors:

  • AMD Opteron 12xx Series
  • AMD Opteron 22xx Series
  • AMD Opteron 82xx Series

During an installation or upgrade, the installer checks the compatibility of the host CPU with vSphere 6.0. If your host hardware is not compatible, a purple screen appears with an incompatibility information message, and the vSphere 6.0 installation process stops.

Upgrade Notes for This Release

For instructions about upgrading vCenter Server and ESX/ESXi hosts, see the vSphere Upgrade documentation.

VMware vSphere Web Client might fail if you you navigate to System Configuration > Nodes Manage Access Edit to change the shell and bash access on that node after an upgrade of vCenter Server Appliance to vCenter Server Appliance 6.0 Update 3c. For more information on the issue, see https://kb.vmware.com/kb/000050861

Upgrading from vCenter Server 6.0 Update 3c to vCenter Server 6.5 is not supported.

Open Source Components for VMware vSphere 6.0

The copyright statements and licenses applicable to the open source software components distributed in vSphere 6.0 are available at http://www.vmware.com. Log in to your My VMware account. Then, from the Downloads menu, select vSphere. On the Open Source tab, you can also download the source files for any GPL, LGPL, or other similar licenses that require the source code or modifications to source code to be made available for the most recent available release of vSphere.

Product Support Notices

  • vCenter Server database. VMware continues to support Oracle 11g and 12c as external databases in vSphere 6.0. VMware will cease to support for Oracle 11g and 12c external databases for vCenter Server Appliance in a future major release.

  • vSphere Web Client. The Storage Reports selection from an object's Monitor tab is no longer available in vSphere Web Client 6.0.

  • vSphere Client. The Storage Views tab is no longer available in the vSphere Client 6.0.

Resolved Issues

The resolved issues are grouped as follows.

Installation Issues
  • Slow login times observed for vCenter Server

    Slow login times observed for vCenter Server were optimized by updating the vmware-visl-integration file to include the kerberos config override.

    This issue is resolved in this release.

  • vCenter Server status alarms might turn red due to a race condition in pthreads-win32

    You might see vCenter Server status alarms to turn red and quickly restore to green due to a race condition in the POSIX Threads for Windows (pthreads-win32) that affects both VMware Authentication Framework Daemon (VMAFD) and VMware Directory service (VMDIR).

    This issue is resolved in this release.

Upgrade Issues
  • If an upgrade from vCenter Server 5.5 to 6.0 fails, further upgrade attempts might also fail due to expired SRP secret

    If an upgrade from vCenter Server 5.5 to 6.0 fails, further attempts for upgrade might also fail, because the Secure Remote Password protocol (SRP) secret, that is created during the upgrade, might not match.

    This issue is resolved in this release.

Networking Issues
  • vCenter Server fails due to аn ODBC error

    After a restart, vCenter Server tries to get data for the vSphere Distributed Switch Health Check from the Microsoft SQL Server database that does not support multiple statements on the same connection and this might result into an exception thrown in vCenter Server.

    This issue is resolved in this release. 

  • vSphere Web Client might show incorrect count of virtual machines in a port group

    When you navigate in an ESXi host to Manage > Networking > Virtual Switches view, using the vSphere Web Client, and you select a vSwitch to see the number of virtual machines on it, if you expand the view, the count of virtual machines might be less than the count that you see in the collapsed view.

    This issue is resolved in this release.

  • When you create a new port in a vSphere Distributed Switch you might get an error

    Because of a race condition, you might fail to create a new port in a VMware vSphere Distributed Switch (VDS). This problem might occur when you delete a portgroup and in the meantime reconfigure the virtual machine to connect to other portgroups in VDS. The number of ports might exceed 2,147,483,647 and you get an error similar to A general system error occurred: Cannot perform this operation, The maxPorts exceeds the limit 2,147,483,647.

    This issue is resolved in this release.

    NOTE: This fix works only for new VDS and not for existing DVS, where portgroups count might already be corrupted due to the race condition.

    Use this workaround if you are not able to add ports.

    Workaround:

    1. Stop the vCenter Server.
    2. Run the following script in SQL:
      ----------------------------------------------
      /* Adjust target DB below */
      use RVCDB07
      /* ^^^^^^^ */
      declare @DVSID int
      declare @NUMPORT int
      DECLARE @DVSNAME varchar(20)
      
      /* Adjust target vDS below */
      SET @DVSNAME = 'VC07-vDS03'
      /* ^^^^^^^^^^ */
      SET @DVSID = ( SELECT ID               
                     FROM dbo.VPX_DVS               
                     WHERE NAME like @DVSNAME )
      SET @NUMPORT = ( SELECT SUM(NUM_PORT)                
                       FROM dbo.VPX_DVPORTGROUP               
                       WHERE DVS_ID like @DVSID )
      
      PRINT @NUMPORT
      
      UPDATE dbo.VPX_DVS
      SET NUM_PORT = @NUMPORT WHERE NAME = @DVSNAME
      SELECT ID, NAME, NUM_PORT FROM dbo.VPX_DVS WHERE NAME = @DVSNAME
       
    3. Start the vCenter Server.
  • vNICs of VMs might lose connection after a refresh of VMware Horizon view pool

    The virtual network interface cards (vNIC) of virtual machines might lose connection after a refresh of a VMware Horizon view pool, because while VMs shut down and power on, the vCenter Server and the ESXi host might be out of sync, which might break the existing connection between vNICs and ephemeral port groups.

    This issue is resolved in this release.

Storage Issues
  • Storage DRS might place the thin provisioned disks into one datastore, instead of distributing them evenly

    During the initial placement of thin provisioned disks, the Storage Distributed Resource Scheduler (SDRS) might miscalculate the entitled space requirement by excluding the reserved space. As a result, SDRS might use only the committed megabytes for the entitled space calculation, causing a wrong placement recommendation on one datastore, instead of distributing them evenly.

    This issue is resolved in this release.

  • Storage DRS generates only one suitable datastore for initial virtual machine placement

    In case there are virtual machines with Raw Device Mapping (RDM) virtual disks, the Storage DRS might consider the actual mapping file size instead of the pointer file size, even though it does not consume any disk space. As a result, the Storage DRS might generate only one suitable datastore when creating new virtual machines.

    This issue is resolved in this release.

  • vCenter Server might become unresponsive while Storage DRS is enabled

    The vCenter Server daemon, vpxd, might become unresponsive while you enable Storage DRS that allows you to manage the aggregated resources of a datastore cluster.

    This issue is fixed in this release.

  • The Storage Usage field on the VM Summary page in the vSphere Web Client might not be updated when the disk usage of a VM changes

    The Storage Usage field on the VM Summary page in the vSphere Web Client might not be updated even when the disk usage of a virtual machine changes.

    This issue is resolved in this release.

  • Storage DRS might fail with incorrect NoDiskSpace error

    Storage DRS might throw an incorrect NoDiskSpace fault message when the actual problem is that Storage DRS does not have I/O bandwidth.

    This issue is resolved in this release.

  • vSphere Web Client might not properly display storage devices after EMC Powerpath 6.0.1. installation

    vSphere Web Client might not properly display storage devices after EMC Powerpath 6.0.1 installation if the ESXi host has only LUNs and the host is set up to boot from a SAN.

    This issue has been fixed in this release.

  • vCenter Server might fail in attempt to create a virtual machine on a Storage DRS cluster using script with null CPU or Mem Share values

    vCenter Server might fail if you attempt to create a virtual machine on a Storage DRS cluster using a script with null CPU or Mem Share values in a RecommendDatastores() API call.

    This issue is resolved in this release. 

Server Configuration Issues
  • Attempts to join Active Directory domains fail intermittently with error LW_ERROR_KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN

    Attempts to join Active Directory domains might fail intermittently with error LW_ERROR_KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN: Client not found in Kerberos database. The issue is fixed by adding retry logic in JoinDomain() in case of KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN and LW_ERROR_PASSWORD_MISMATCH with a sleep of 30 seconds.

    This issue is fixed in this release.

  • Joining of а vCenter Server or ESXi host to the Disjoint Active Directory domain might fail

    Disjoint Active Directory domains were not supported in vSphere 6.0 and above. The disjoint namespace is a scenario in which a computer's primary domain name system (DNS) suffix doesn't match the DNS domain name where that computer resides. You no longer need to modify hostnames of the joining host as part of domain join functionality.

    This issue is resolved in this release.

  • When the Active Directory environment has more than 100 trusted domains, the domain join might fail

    Тhe domain join in the Active Directory might fail, when the concatenation of domain names of all the trusted domains exceeds the maximum limit of 2048 bytes in the registry.

    This issue is resolved in this release.

  • VMAFD service might cause heap memory leaks

    The VMware Authentication Framework Daemon (VMAFD) might continue to allocate memory and not free it in time, which might cause a system to run out of heap memory.

    This issue is resolved in this release.

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • Hardware information on the Host Summary page might display an error

    In a multi-vCenter environment, you might see an error A specified parameter was not correct querySpec.metricId, while viewing the hardware information on the Host Summary page.

    This issue is resolved in this release.

  • Upgrade from Adobe to Apache BlazeDs in the vSphere Web Client

    The vSphere Web Client migrates from Adobe BlazeDS to Apache BlazeDS. The Apache Blaze DS is of version 4.7.3 which is the latest Apache BalzeDS patch available.

  • vSphere Web Client might not show the advanced performance charts to users with role privileges

    When you create users and assign them role privileges to operate on an ESXi host and virtual machines, they might not be able to see the advanced performance charts after they log in to the vSphere Web Client.

    This issue is resolved in this release.

  • vSphere Web Client might show wrong host datastores when you select the option Connect to CD/DVD image on a datastore

    After you migrate a virtual machine, if you select the option Connect to CD/DVD image on a datastore under the Summary tab in the vSphere Web Client, you might see the source host datastores, instead of the destination host datastores.

    This issue is resolved in this release.

  • Setup of a scheduled task to migrate VMs between vCenter Server instances might fail with an error

    If you attempt to create a scheduled task to migrate virtual machines between vCenter Server instances, the operation might fail with an error similar to Object has already been deleted or has not been completely created.

    This issue is resolved in this release.

  • A consecutive scheduled task for virtual machine configuration might fail

    When you create multiple scheduled tasks to configure a virtual machine, the second task might fail with an error similar to Cannot complete operation due to concurrent modification by another operation.

    This issue is resolved in this release.

Virtual Machine Management Issues
  • Shutdown or restart of a virtual machine with guest OS using vSphere Web Client might fail

    You might see the options Shutdown Guest and Restart Guest as unavailable (dimmed) in the vSphere Web Client in case of racing reboot and shutdown calls from an ESXi host and a virtual machine on it with a guest OS. For example, you might schedule a delayed start from Command Prompt inside the guest OS and at the same time attempt to shut down the virtual machine from the Web Client, which leaves the VM hanging in a shutdown state.

    This issue is resolved in this release. 

  • VPXD might fail due to an internal logic error

    In certain corner cases, the storage recommendation might fail to perform a check and its key might be removed. As a result, the VMware vCenter Server service VPXD might fail with an internal logic error like Win32 invalid_parameter.

    This issue is resolved in this release.

  • Virtual machine power on or vMotion migration might fail due to invalid state of an ESXi host

    Virtual machine power on or vMotion migration might fail if one of the ESXi hosts in a Storage DRS cluster is in an invalid state. This problem might occur regardless of virtual machine power on or vMotion migration.

    This issue is resolved in this release.

  • Cluster maintenance mode takes long to get DRS recommendations

    Cluster maintenance mode might take long to get recommendations from the VMware vSphere Distributed Resource Scheduler (DRS) on a large inventory of virtual machines and hosts, because during this task DRS makes some unnecessary copies of VM faults that might cause a slowdown.

    This issue is resolved in this release.

  • EAM agency for a VXLAN cluster might contain issues for which agents do not exist

    The vSphere ESX Agent Manager (EAM) might keep issues in the agency runtime for already destroyed agents.

    This issue is resolved in this release.

  • VM operations triggered while an ESXi host enters maintenance mode might fail without a warning

    If you attempt to run an operation with a virtual machine while an ESXi host enters maintenance mode, the host might not stop it in time and the operation might fail without a warning.

    This issue is resolved in this release.

  • Deployment and cloning of virtual machines and templates might fail as vCenter Server selects an invalid host

    When deploying or cloning virtual machines and templates of devices that require post-deployment configuration, like network devices, to a cluster, all ESXi hosts might show as incompatible and vCenter Server selects a random host for the deployment. If the selected host happens to be in maintenance mode, or invalid for some other reason, the deployment might fail.

    This issue is resolved in this release.

VMware HA and Fault Tolerance Issues
  • VMware vSphere High Availability status of newly deployed VMs shows as unprotected

    VMware vSphere High Availability (vSphere HA) might not capture the change in the protection state of a newly deployed virtual machine, because the firewall between vCenter Server and the primary ESXi host might affect the update. This issue is resolved with adding a timer that monitors the status update from the primary ESXi host to vCenter Server and restarts the connection if the firewall drops it.

    This issue is resolved in this release. 

Guest Operating System Issues
  • Guest customization might fail with an error GUESTCUST_EVENT_CUSTOMIZE_FAILED

    Starting with Windows Vista and Windows Server 2008, Microsoft deprecated SHFileOperation. As a result, guest customization for different Windows operating systems might fail intermittently. The log file might give the following information: Moving SysprepDir from sysprep to C: failed.Err:2.

    This issue is resolved in this release.

  • Guest customization might fail with an error GUESTCUST_EVENT_NETWORK_SETUP_FAILED

    Starting with Windows Vista and Windows Server 2008, Microsoft deprecated SHFileOperation. As a result, guest customization for different Windows operating systems might fail intermittently. The log file might give the following information: error number 80010106, No error message found for error code -2147417850 (0x80010106).

    This issue is resolved in this release.

  • Guest OS customization might fail when you use the vSphere API or the vCloud Director

    When you try to customize a guest operating system using the vSphere API or vCloud Director, the uploaded customization code might not detect the VMware Tools path and as a result, the operation might fail.

    This issue is resolved in the release. 

Miscellaneous Issues
  • Running a vCenter Server API script on a datastore cluster might cause a timeout

    Running an API script on a datastore to create, clone, relocate, or reconfigure might time out even if the operation is successful. The event processing on vpxd might be slow due to the database, for example. This fix includes code changes for asynchronous processing of events that prevents timeouts.

    This issue is resolved in this release.

  • vCenter Server 6.0 might stop responding, when a privileged user attempts to add a host to an incorrect folder through the vSphere Web Services API

    When you have the proper privileges and you use the vSphere API to add an ESXi host to the vCenter Server, but instead of the hostFolder you use the rootFolder, this might cause the vCenter Server 6.0 to stop responding.

    This issue is resolved in this release.

  • Agent virtual machines running on an ESXi host are powered off when the host enters a maintenance mode and cannot be restarted

    When the ESXi host enters a maintenance mode, the vpxd service might power off the agent virtual machines. As a result, these agent VMs cannot be restarted. To make this fix work:

    1. Log in to the vSphere Web Client.
    2. Locate the vCenter Server.
    3. Click the Manage tab and select Advanced Settings.
    4. Click Edit and add the following parameters:
      • config.vpxd.agentShutdownSecs (default value is 0) – specifies how long to wait the ESXi agent VM to shutdown
      • config.vpxd.forceAgentPowerOff (default value is TRUE) - specifies if the ESXi agent VM must be powered off if it is stil running after agentShutdownSecs.

    This issue is resolved in this release.

  • Extensions do not update after vpxd restart

    When you create extensions without specifying values for certain fields, for example extendedProductInfo to be null or unset, and after the extensions are registered with vCenter Server using the ExtensionManager.registerExtension API, and you restart vpxd, the null or unset values are replaced with empty string ("") values. As a result, these fields become invalid and you cannot update the extensions using the ExtensionManager.updateExtension method.

    This issue is resolved in this release.

  • Identity source edit for LDAP connections might fail if primary server stops responding

    You might not be able to edit the Identity Source of a LDAP connection like changing the primary server url with the url of the secondary server, if the primary server stops responding.

    This issue is resolved in this release.

  • VMware Client Integration Plug-In might not work as expected if you log in to the vSphere Web Client using Google Chrome 58 and 59, or Internet Explorer 10 and 11

    When you log in to the vSphere Web Client using Google Chrome 58, Google Chrome 59, Internet Explorer 10 or Internet Explorer 11 and perform tasks related to the Client Integration Plug-In (CIP), you might encounter issues listed here:

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

    This issue is resolved in this release.

  • SNMP shows CPU and memory utilization of a VCSA constantly at 100 percent

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

    This issue is resolved in this release. 

  • vCenter Server might fail with a vCenter Server Service error while using OptionManager

    vCenter Server might fail with an error similar to vpxd Panic: Assert Failed: "0 == _refCount @ d:/build/ob/bora-1378903/bora/vim/lib-vsan/vmacore/main/object.cpp:157 when you attempt to use the OptionManager managed object.

    This issue is resolved in this release.

  • VMware Directory Service might fail due to database overload during cleanup of tombstones

    The VMware Directory Service (vmdir) might stop responding due to a temporary overload during the cleanup of tombstones that might fail write operations and as a result, cause downtime of the entire service.

    This issue is resolved in this release.

  • Orphan data might pile in the vCenter Server database tables

    If monthly and yearly rollup jobs are disabled, orphan data in the vCenter Server database, specifically in the VPX_HIST_STAT2_X partition tables, might continue to pile.

    This issue is resolved in this release.

  • Upgrade and installation of IO filters might fail if the path to the IO Filter VIB is different from the original url

    If you attempt to upgrade or install IO filters to a new server in a cluster, the operation might fail if the path to the IO Filter VIB is different from the original url, due to a change in the original configuration for example.

    This issue is resolved in this release. 

Security Issues
  • Login of Active Directory domain user accounts ending with a dollar sign fails on vCenter Server and ESXi hosts

    Logins by Active Directory domain user accounts ending with a dollar sign might be treated as machine accounts by default and logins on vCenter Server and ESXi hosts might fail.

    This issue is resolved in this release.

  • Likewise stack on vCenter Server Cloudvm is not enabled to support SMBv2

    Windows 2012 domain controller supports SMBv2, whereas the Likewise stack on vCenter Server supports only SMBv1. With this release, the Likewise stack on vCenter Server is enabled to support SMBv2.

    This issue is resolved in this release.

  • Update to the Spring Framework

    vCenter Server 6.0 is updated to use the 4.3.5 jars of the Spring Framework.

  • Update to vPostgres

    vPostgres is updated to 9.3.17.

  • Update to OpenSSL

    OpenSSL is updated to version 1.0.2k.

  • Update to JRE

    The Oracle (Sun) JRE is updated to version JRE 1.7.0_151

  • Update to Python

    The Python third party library is updated to version 2.7.13

  • Update to Taglibs

    The third party library taglibs is updated to version 1.2.5

CIM and API Issues
  • vCenter Server might lose connectivity during a RPC via an API client if a user closes the TCP connection before the call ends and the operation fails  

    If you run a remote procedure call (RPC) via an API client and close the TCP connection before the call ends, and the requested operation fails, vCenter Server might lose connectivity while trying to report the error back to the API client.

    This issue is resolved in this release. 

  • vCenter Server might fail due to an excessive use of resources in concurrent calls to the blocking methods of the PropertyCollector  

    vCenter Server might fail if an API client makes two or more concurrent calls to the blocking methods of the PropertyCollector because the consumed resources to process the calls might exceed the limits. This scenario is possible when the concurrent calls use the same HTTP session with the PropertyCollector referenced by ServiceInstanceContent, or when they use the same dedicated PropertyCollector created by calling createPropertyCollector. The blocking calls are waitForUpdates, waitForUpdatesEx and checkForUpdates.

    This issue is resolved in this release.

Backup and Restore Issues
  • vCenter Server might stop responding and vpxd continuously to fail with multiple QueryHostReplicationCapabilities errors

    vCenter Server might stop responding and vpxd might continuously fail with multiple QueryHostReplicationCapabilities errors when a virtual machine is configured for replication and vCenter Server experiences connection issues with the ESXi host, where this VM resides.

    This issue is resolved in this release.

  • Attempts to configure vSphere Data Protection with vCenter Server might fail if only TLS 1.2 is enabled

    Attempts to configure vSphere Data Protection (VDP) with vCenter Server might fail if vCenter Server is enabled for only TLS 1.2 but not for TLS 1.0 and TLS 1.1.

    This is resolved in this release.

Auto Deploy Issues
  • Auto Deploy temporary log file might grow to a large size over time

    In the Auto Deploy service, the temporary log file autodeploy-service.log might grow to a quite large size over time. Even if you delete the file, restarting the Auto Deploy service creates the temporary file and increases the size indefinitely without rotation.

    This issue is resolved in this release.

  • Stateless booting and caching through Auto Deploy might fail on incorrect or null value of the Autodeploy.MachineIdentity parameter  

    Setting an incorrect or null value to the Autodeploy.MachineIdentity parameter of an ESXi host might result in failure of stateless booting and stateless caching through vSphere Auto Deploy.

    This issue is resolved in this release. 

Known Issues

The known issues are grouped as follows.

Upgrade Issues
  • Upgrade of vSphere Client might fail with an error if Horizon View Client is installed

    Upgrading to a new version of VMware vSphere Client might fail with an error Failed to install hcmon driver if VMware Horizon View Client is also installed, because versions of drivers that the vSphere Client tries to install in the VMware network install library, vnetlib64.dll, might be different from the drivers that the Horizon View Client has previously installed.

    Workaround: To work around this issue you must uninstall the old version of vSphere Client and then install the new version.

  • NSX VIB installation through EAM might fail if it requires only maintenance mode and no reboot of the ESXi host

    vSphere ESX Agent Manager (EAM) puts ESXi hosts in maintenance mode during the installation of NSX vSphere Installation Bundles (VIB), but might not take the hosts out of maintenance mode if the VIB requires only maintenance mode and no reboot.

    Workaround:
    To work around this issue, you must manually take the host out of maintenance mode.
     

  • Content Library creation might fail when vCenter Server is upgraded to 6.0 Update 3c

    When vCenter Server is upgraded to 6.0 Update 3c, the Content Library creation might fail with an error.

    Workaround: 
    Find the signing certificate and the root CA used by SSO from vmware-identity-sts.log or websso.log. Check whether the root CA is present in TRUSTED_ROOTS of VMware Endpoint Certificate Store. If it is not present in the VMware Endpoint Certificate Store, add the root CA to TRUSTED_ROOTS. 
    Alternatively we can also look into vmdir under DN: 'cn=TrustedCertificateChains,cn=fc8b434d-8404-4107-a28a-ffe027b1e623,cn=Ldus,cn=ComponentManager,dc=vsphere,dc=local' to identify all the signing certificates and their root CAs.

    For vCenter Server Appliance:

    1. Identify the root CA from the vmware-identity-sts.log file.
      Look for the Security Assertion Markup Language token KeyInfo element and the <ds:X509Certificate> tag 
      For example: 
      <ds:X509Certificate>MIIFEzCCA/ugAwIBAgIJAIhibbQofa1VMA0GCSqGSIb3DQEBCwUAMIGyMQswCQYDVQQGEwJVUzET
      MBEGA1UECBMKQ2FsaWZvcm5pYTESMBAGA1UEBxMJUGFsbyBBbHRvMRUwEwYDVQQKEwxWTXdhcmUs
      IEluYy4xNzA1BgNVBAMTLmJscjctN3RoLWRoY3AtNDctMjcuZW5nLnZtd2FyZS5jb20gQ0EgMzQw
      OWE0MGQxKjAoBgkqhkiG9w0BCQEWG3NzbC1jZXJ0aWZpY2F0ZXNAdm13YXJlLmNvbTAeFw0xNjAy
      MDEwOTMxMjdaFw0yNjAxMjkwOTMxMjdaMIGyMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZv
      cm5pYTESMBAGA1UEBxMJUGFsbyBBbHRvMRUwEwYDVQQKEwxWTXdhcmUsIEluYy4xNzA1BgNVBAMT
      LmJscjctN3RoLWRoY3AtNDctMjcuZW5nLnZtd2FyZS5jb20gQ0EgMzQwOWE0MGQxKjAoBgkqhkiG
      9w0BCQEWG3NzbC1jZXJ0aWZpY2F0ZXNAdm13YXJlLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEP
      ADCCAQoCggEBANPkC1QUF79+cmgq6EZhrJL81UO6pH04fQQ9yM38o55TkFvtAapVBXq7uJ8T0nO4
      a04JwiqW9El4hce/Z3+nOHOckWJ0VSCFoqox1FVpYW4fXSeHfuQ0ktVnyIyMz/vYTAWrnj493YIY
      QuiXMeNJwxvG/gHwz+TiRlMSVBiXCQeD9NNRCG8qljSgkrd2yW2rTCBL9h09XleKmtkt0HeGT0pf
      pM9fKQ7lM6JZQUN9WS8wP5YKASv5M029qGxPzSpq5YOp7EmFr5bbSXI9sb+/W5VrU1vdO6LVaYOK
      wKFHm8xe2hNyLAMCWzHVHyNNfcbTSNj/IZ1jE+EtAA6lSv0bgT0CAwEAAaOCASgwggEkMB0GA1Ud
      DgQWBBQiBchoMNnNgbc1vtiO1cuuZPNOOTCB5wYDVR0jBIHfMIHcgBQiBchoMNnNgbc1vtiO1cuu
      ZPNOOaGBuKSBtTCBsjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExEjAQBgNVBAcT
      CVBhbG8gQWx0bzEVMBMGA1UEChMMVk13YXJlLCBJbmMuMTcwNQYDVQQDEy5ibHI3LTd0aC1kaGNw
      LTQ3LTI3LmVuZy52bXdhcmUuY29tIENBIDM0MDlhNDBkMSowKAYJKoZIhvcNAQkBFhtzc2wtY2Vy
      dGlmaWNhdGVzQHZtd2FyZS5jb22CCQCIYm20KH2tVTAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIC
      BDANBgkqhkiG9w0BAQsFAAOCAQEAsn/F3Cc7iGLwSLr9EmjzmJtQVzGJBmcMsd/bNailOkzxwH2z
      ToPWrMxoh/jgFkV27PPxAg4adsHymDvxY+xcfdmAjU5pDsR9KG4jksTtcasO+fY219gapUbanApG
      3weNeH8Nln9T4VBJfBYqxuVepvDoVFkiUD4iBY/caAKYJv84+JfrHQtaPcgCOidmN+iUVGO9XlQq
      bImRwXGER2vdOndXo5Ic1dFgzeiSc01jSN9uLYwrsc7n1NWBAkTcKDonQMC3Pgp+et/nR76aZYzd
      s30p6NWvXctc2iuv82bRAjX+p+DI1Kji3Ms/qDxn9rf3vDcT5zw+rwjA6qDXs9Lj8w==</ds:X509Certificate></ds:X509Data></ds:KeyInfo>
    2. Save the content between the tags <ds:X509Certificate> </ds:X509Certificate> to a file with a .crt extension. 
      For example, enter 51root.crt as the file name.
    3. Append -----BEGIN CERTIFICATE----- at the beginning and -----END CERTIFICATE----- at the end of the file.
    4. Add the CA to TRUSTED_ROOTS on the Management Node as shown below:
      /usr/lib/vmware-vmafd/bin/vecs-cli entry create --store TRUSTED_ROOTS --alias roo51 --cert 51root.crt
    5. Restart all services.

    For Windows:

    1. See workaround (steps 1 to 3) of vCenter Server Appliance.
    2. Add the CA to TRUSTED_ROOTS on the Management Node as shown below:
      C:\Program Files\VMware\vCenter Server\vmafdd\vecs-cli.exe entry create --store TRUSTED_ROOTS --alias roo51 --cert 51root.crt
    3. Restart all services.

  • vSphere Web Client might fail after upgrade of vCenter Server Appliance to 6.0 Update 3c if you click Manage > Access > Edit

    You might lose connectivity of the vSphere Web Client when you navigate to System Configuration > Nodes > Manage > Access > Edit to change the shell and bash access on that node after an upgrade of vCenter Server Appliance to 6.0 Update 3c.

    Workaround: To work around this issue, you must run a script to import a missing certificate into the VMware Endpoint Certificate Store. For more information on the issue, see https://kb.vmware.com/kb/000050861

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

    When you log in to the vSphere Web Client using Firefox 54 and perform tasks related to Client Integration Plug-In, you might encounter issues listed here:

    • 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 or download to the Content Library is not enabled.

    Workaround:
    To work around this issue, you must update the vmware-localhost certificate. Follow these steps:

    1. Backup the following files:

    • C:\ProgramData\VMware\CIP\csd\ssl\cert.der
    • C:\ProgramData\VMware\CIP\csd\ssl\cert.pem
    • C:\ProgramData\VMware\CIP\csd\ssl\server.pem 

    2. Add section [v3_req] with content subjectAltName = DNS:vmware-localhost, DNS:vmware-plugin at the end of the configuration file. You must add "vmware-plugin" in case both the Client Integration Plugin and the Enhanced Authentication Plugin are installed.

    3. Create a new Certificate Signing Request from an elevated Command Prompt, vmware-csd.exe --install from C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0 or C:\Program Files\VMware\Client Integration Plug-in 6.0.

    4. Remove the vmware-localhost certificate from the Trusted Root Certification Authorities store for the local computer, and import the new one you created (C:\ProgramData\VMware\CIP\csd\ssl\cert.pem).

    5. Add the friendly name "VMware-CSD Cert" to the new vmware-localhost certificate.

    NOTE: As a workaround you can also use alternative browsers like the latest versions of Google Chrome or Internet Explorer.

Virtual Machine Management Issues
  • vMotion might not work in case of racing reboot and shutdown calls from an ESXI host and a guest OS

    Attempts to use vMotion might fail in case of racing reboot and shutdown calls from an ESXi host and a virtual machine on it with a guest OS. For example, you may schedule a delayed start from Command Prompt inside the guest OS and at the same time attempt to shut down the virtual machine from the Web Client, which leaves the VM hanging in a shutdown state. You can see the options Shutdown Guest and Restart Guest as unavailable (dimmed) in the vSphere Web Client as an indication of that state.

    Workaround:
    You must retry the shutdown or reboot operation to overrule the hanging shutdown state. vMotion will not be available until the virtual machine shutdown state is resolved.

Internationalization Issues
  • Accounts with administrator privileges that contain multibyte characters might not be able to modify permissions

    Accounts with administrator privileges that contain multibyte characters might not be able to modify permissions via the vSphere Web Client and you might see an error similar to An internal error has occurred – Error #1009 when you try to manage access to nodes under Administration > System Configuration.

    Workaround:
    To work around this issue, you must log in vSphere Web Client with accounts with administrator privileges that contain only ASCII characters.

Known Issues from Earlier Releases

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

check-circle-line exclamation-circle-line close-line
Scroll to top icon