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

vCenter Server 6.5 Update 3k | JUL 30 2020 | ISO Build 16613358
vCenter Server Appliance 6.5 Update 3k | JUL 30 2020 | ISO Build 16613358

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

The vCenter Server 6.5 Update 3k release includes the following list of new features.

  • To avoid unauthorized access to the Platform Services Controller Web interface, vCenter Server 6.5 Update 3k Release Notes introduces changes in the login. Any login attempt by a user without sufficient privileges triggers a new error page and such users must follow the prompt Please Click here to get back to the login page to revert to the login page.
  • HTML interface. The HTML5-based vSphere Client ships with vCenter Server alongside the Flex-based vSphere Web Client. The vSphere Client uses many of the same interface terminologies, topologies, and workflows as the vSphere Web Client. You can use the new vSphere Client, or continue to use the vSphere Web Client.
  • For Photon OS updates, see VMware vCenter Server Appliance Photon OS Security Patches.

Earlier Releases of vCenter Server 6.5

Features and known issues of vCenter Server are described in the release notes for each release. Release notes for earlier releases of vCenter Server 6.5 are:

For internationalization, compatibility, installation and upgrades, product support notices, and features see the VMware vSphere 6.5 Release Notes.

Patches Contained in This Release

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

NOTE: vCenter Server 6.5 Update 3k does not provide a security patch to update the JRE component of vCenter Server for Windows and Platform Services Controller for Windows. Instead, you must download the VMware-VIM-all-6.5.0-16613358.iso file from vmware.com.

Full Patch for VMware vCenter Server Appliance 6.5 Update 3k

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

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

For vCenter Server and Platform Services Controller Appliances

Download Filename VMware-vCenter-Server-Appliance-6.5.0.33000-16613358-patch-FP.iso
Build 16613358
Download Size 1708.3 MB
md5sum 99f851c269b4c5c2ace84233e8c3e11d
sha1checksum 3a895430a657822e6a19d44e2d8351db1f7d9222

Download and Installation

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

  1. Attach the VMware-vCenter-Server-Appliance-6.5.0.33000-16613358-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 Resolved Issues.

For Photon OS updates, see VMware vCenter Server Appliance Photon OS Security Patches

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

Upgrade Notes for This Release

Important: Upgrades and migrations from vCenter Server 6.5 Update 3k to vCenter Server 6.7 Update 3i and vCenter Server 7.0.0c are not supported. For more information on vCenter Server supported upgrade and migration paths, please refer to VMware knowledge base article 67077.

Product Support Notices

Import from file:// scheme URLs to a Content Library is no longer supported due to possible security vulnerability.

Resolved Issues

The resolved issues are grouped as follows.

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • If you use Internet Explorer, the vSphere Web Client might become unresponsive after an upgrade to vCenter Server 6.5 Update 3f

    After an upgrade to vCenter Server 6.5 Update 3f, if you use Internet Explorer, the vSphere Web Client might become unresponsive after entering credentials. The issue is not observed with browsers other than Internet Explorer for the vSphere Web Client or with the vSphere Client.

    This issue is resolved in this release.

Miscellaneous Issues
  • Applmgmt API calls might fail with authorization error because of periodical cleanup of the /tmp folder

    The /tmp folder in the vCenter Server appliance gets cleaned up periodically. If such a cleanup coincides with an applmgmt API call using vCenter Single Sign-On users, the request might fail with an authorization error. You might see an error message similar to: ERROR:vmware.appliance.extensions.authorization.authorization_sso:FindAllParentGroups Failed {[Errno 2] No such file or directory}.

    This issue is resolved in this release. Depending on your deployment, you might have to restart the applmgmt service to enable the fix. 

  • Rsyslog uses TLS1.2 by default

    In vCenter Server 6.5 Update 3k, the source of truth for TLS ciphers is the rsyslog.conf file and not the gnutls file, and the default setting is TLS1.2. You can reconfigure TLS by using the TLSReconfigurator tool.

    This issue is resolved in this release.

Upgrade Issues
  • You cannot open the vCenter Server Appliance installer app in Linux virtual machines by double-clicking it

    Linux file managers do not recognize the PIE format that some upgraded components of the vCenter Server Appliance installer app use. As a result, you cannot open the vCenter Server Appliance installer app in Linux virtual machines by double-clicking it.

    This issue is resolved in this release. To avoid opening the vCenter Server Appliance installer app by using the Linux terminal, vCenter Server 6.5 Update 3k introduces an installer-linux.desktop file that opens by a double-click in the same way as the original installer.

Security Issues
  • Update to JRE

    Oracle (Sun) JRE is updated to version 1.8.0_251.

  • Update to the libxml2 library

    The libxml2 library is updated to version 2.9.10 to resolve security issues with identifiers CVE-2019-19956, CVE-2019-20388 and CVE-2020-7595.

  • Update to the Python library

    The Python third-party library is updated to version 3.5.9/2.7.18.

  • Update to Simple Logging Facade for Java (SLF4J)

    The SLF4J package is updated to version 1.7.30.

  • Update of the Jackson package

    The Jackson package is updated to version 2.10.1.

  • Update to the Apache Tomcat server

    The Apache Tomcat server is updated to version 8.5.55.

  • Update to jQuery

    The jQuery version is updated to jquery-3.0.0 to resolve security issues with identifiers CVE-2012-6708, CVE-2015-9251 and CVE-2016-7103.

  • Update to AngularJS

    AngularJS is updated to version angular-1.5.0 to resolve a known security issue.

  • Update of the Fasterxml Jackson package

    The Jackson package is updated to version 2.10.3.

  • Update to Eclipse Jetty

    Eclipse Jetty is updated to version 9.4.28.v20200408.

  • Update to OpenSSL

    The OpenSSL package is updated to version 1.0.2v.

  • Update to VMware Postgres

    VMware Postgres is updated to version 9.4.26.

  • Update to the SQLite database

    The SQLite database is updated to version 3.32.2.

  • Update to the Spring framework

    The Spring package is updated to version 4.3.27.

  • Update to cURL

    cURL is updated to version 7.70.

Networking Issues
  • The vpxd service fails and the vCenter Server system becomes inaccessible due to a race condition in vSphere DRS

    A rare race condition between two networking functions in vSphere DRS causes one of the functions to access already released memory addresses. This leads to failure of the vpxd service and ultimately makes the vCenter Server system unresponsive.

    This issue is resolved in this release. Without the fix, you must manually restart the vpxd service by using the command vmon-cli -r vpxd.

  • After a restart or upgrade of the vpxd service, you cannot see IP addresses in the Summary tab of virtual machines

    After a restart or upgrade of the vpxd service, you cannot see IP addresses of virtual machines in the Summary tab in the vSphere Web Client and the vSphere Client.

    This issue is resolved in this release.

Virtual Machine Management Issues
  • vCenter Server does not report compatible datastores when datastores are mounted on multiple data centers

    If you have ESXi hosts across different data centers that use the same VMware vSphere Virtual Volumes datastore, you do not see compatible datastores when you run the Get-SpbmCompatibleStorage PowerCLI command or use the storage policy editor in the vSphere Client.

    This issue is resolved in this release.

  • You cannot log in to vCenter Server Appliance Manager Interface with a custom user account created by using the localaccounts command

    If you log in to the appliance shell as root and create a new user by using the localaccounts.user.add command, a user is not created. When you check the new account by using the localaccounts.user.get command, you see an error such as Error in method: Invalid local account name. As a result, you cannot log in to the vCenter Server Appliance Manager Interface by using the new account.

    This issue is resolved in this release.

  • In the vSphere Web Client, you cannot take snapshots of multiple virtual machines

    In the vSphere Web Client, if you select multiple virtual machines from a cluster or a datacenter under the Hosts and Clusters view, and follow the steps to take snapshots of the virtual machines, the operation does not complete and you see no error.

    This issue is resolved in this release.

Server Configuration Issues
  • If a trusted domain goes offline, Active Directory authentications for some user groups might fail

    If any of the trusted domains goes offline, Likewise returns none or a partial set of group membership for users who are part of any of the groups on the offline domain. As a result, Active Directory authentications for some user groups fails.

    This issue is resolved in this release. This fix makes sure Likewise lists all the groups from all the other online domains.

Backup Issues
  • ESXi host disconnects from the vCenter Server system due to a failure of the vpxa service during a backup operation

    When backing up certain disks of a virtual machine, the management agent on ESXi, vpxa, might fail with a core dump due to an unhandled error condition. As a result, the ESXi host disconnects from the vCenter Server system and any backup in progress fails.

    This issue is resolved in this release.

vSphere HA and Fault Tolerance Issues
  • Third-party certification chain might be missing on port 8182 that serves the Fault Domain Manager (FDM) process

    In some cases, the FDM process might not get a custom root certificate from a third-party CA. As a result, an ESXi host might have a missing chain on certificate at the FDM port 8182.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • You cannot access virtual machines with names that contain non-ASCII characters

    In the vSphere Web Client, when you try to access a virtual machine with a name that contains non-ASCII characters, you see the following error: The console has been disconnected. Close this window and re-launch the console to reconnect.

    In addition, the VM name might display unexpected characters.

    Workaround: Use the VMware Remote Console or vSphere Client to open such virtual machines. 

Upgrade Issues
  • If the URL of a custom repository cannot be verified, URL-based patching of the vCenter Server Appliance fails

    Starting with vCenter Server 6.5 Update 3k, if a custom repository URL cannot be verified, URL-based patching of the vCenter Server Appliance fails. In the /var/log/vmware/applmgmt/software-packages.log file you see a message such as ERROR:vmware.vherd.base.software_update:Download failed, please check the URL and the network connection.

    Workaround: You must add a trusted root certificate to the certificate store, as described in Add a Trusted Root Certificate to the Certificate Store.
    For more information, see VMware knowledge base article 79552.

Known Issues from Earlier Releases

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