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

VMware vCenter Server 6.5 Update 1d Release Notes

vCenter Server 6.5 Update 1d | 19 DEC 2017 | ISO Build 7312210

vCenter Server Appliance 6.5 Update 1d | 19 DEC 2017 | Build 7312210

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

  • vCenter Server 6.5 Update 1d addresses issues that have been documented in the Resolved Issues section and Photon OS security vulnerabilities. For more information, see VMware vCenter Server Appliance Photon OS Security Patches.
  • Update of the Oracle (Sun) JRE package to version 1.8.0_141.
  • vCenter Server 6.5 is updated to use the 4.3.9 version of the Spring Framework.
  • The OpenSSL package is updated to version openssl-1.0.2l.
  • The Tomcat package is updated to version 8.5.15.
  • Apache Struts is updated to version 2.5.13 to resolve CVE-2017-9805, CVE-2017-9804 and CVE-2017-9793.
  • Eclipse Jetty is upgraded to version 9.2.22.

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 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 1 delivers the following patches. See the VMware Patch Download Center for more information on downloading patches.

Internationalization

VMware vSphere 6.5 is available in the following languages:

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

Components of VMware vSphere 6.5 Update 1, including vCenter Server, ESXi, the vSphere Web Client, the vSphere Client, and the vSphere Host 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 and vSphere Client are packaged with vCenter Server.

Hardware Compatibility for ESXi

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

Device Compatibility for ESXi

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

Guest Operating System Compatibility for ESXi

To determine which guest operating systems are compatible with vSphere 6.5, use the ESXi 6.5 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.5. 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.5, upgrade the virtual machine compatibility. See the vSphere Upgrade documentation.

Installation and Upgrade Notes 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:

VMware Tools Bundling Changes in ESXi 6.5

In ESXi 6.5, only a subset of VMware Tools ISO images are bundled with the ESXi 6.5 host.

The following VMware Tools ISO images are bundled with ESXi:

  • windows.iso: VMware Tools image for Windows Vista or higher

  • linux.iso: VMware Tools image for Linux OS with glibc 2.5 or higher (for example, RHEL 5 or later, SLES 11 or later, Ubuntu 10.04 or later)

  • winPreVista.iso: VMware Tools image for Windows 2000, Windows XP, and Windows 2003

The following VMware Tools ISO images are available for download from My VMware:

  • solaris.iso: VMware Tools image for Solaris

  • freebsd.iso: VMware Tools image for FreeBSD

  • winPre2k.iso: VMware Tools image for pre Windows 2000

  • linuxPreGlibc25.iso: VMware Tools image for Linux OS with glibc less than 2.5

  • darwin.iso: VMware Tools image for OS X 10.11 or later

  • darwinPre15.iso: VMware Tools image for Pre-OS X 10.11

  • netware.iso: VMware Tools image for Netware

Follow the procedures listed in the following documents to download VMware Tools for operating systems not bundled with ESXi:

Migrating Third-Party Solutions

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

Upgrades and Installations Disallowed for Unsupported CPUs

Comparing the processors supported by vSphere 6.0, vSphere 6.5 no longer supports the following processors:

  • Intel Xeon 51xx series
  • Intel Xeon 30xx series
  • Intel core 2 duo 6xxx series
  • Intel Xeon 32xx series
  • Intel core 2 quad 6xxx series
  • Intel Xeon 53xx series
  • Intel Xeon 72xx/73xx series

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

Upgrade Notes for This Release

Important: vCenter Server 6.5 Update 1 supports upgrades and migrations from vCenter Server 6.0 Update 3 and above to vCenter Server 6.5 Update 1.

Important: Upgrades or migration of vCenter Server earlier than 5.5 Update 3b when the environment is with an external vCenter Single Sign-On to vCenter Server 6.5 Update 1 with an external Platform Services Controller are unsupported. For example, to upgrade or migrate vCenter Server 5.5 with an external vCenter Single Sign-On to vCenter Server 6.5 Update 1 with an external Platform Services Controller, you must first update to vCenter Server 5.5 Update 3b and then perform the upgrade or migration to vCenter Server 6.5 Update 1.

vCenter Server 5.5 Update 3b build numbers are:

  • vCenter Server 5.5 Update 3b, build 3252642
  • vCenter Server Appliance 5.5 Update 3b, build 3255668

Upgrades or migration of vCenter Server 5.5 and later with an embedded vCenter Single Sign-On to vCenter Server 6.5 Update 1 with an embedded Platform Services Controller are supported scenarios.

There is a change in the upgrade process when you upgrade to vCenter Server 6.5 Update 1. For instructions about upgrading vCenter Server and ESX/ESXi hosts, see the vSphere Upgrade documentation. 

Open Source Components for VMware vSphere 6.5

The copyright statements and licenses applicable to the open source software components distributed in vSphere 6.5 are available at http://www.vmware.com. You need to 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.

Functionality Caveats

The vSphere Client is written in an HTML5-based language and frameworks supported by all browsers. However, different browsers have different performance characteristics regarding the HTML5 standard. In particular, performance with Internet Explorer 11 can be slower than with other browsers, because of the rendering engine that Internet Explorer 11 uses. If you experience such issues, try using another supported browser.

Product Support Notices

  • The VMware Lifecycle Product Matrix provides detailed information about all supported and unsupported products. Check the VMware Lifecycle Product Matrix also for further information about the End of General Support, End of Technical Guidance, and End Of Availability.

  • VMware is announcing discontinuation of its third party virtual switch (vSwitch) program, and plans to deprecate the VMware vSphere APIs used by third party switches in the release following vSphere 6.5 Update 1. Subsequent vSphere versions will have the third party vSwitch APIs completely removed and third party vSwitches will no longer work. For more information, see FAQ: Discontinuation of third party vSwitch program (2149722).

  • As of vSphere 6.5, VMware is discontinuing the installable desktop vSphere Client, one of the clients provided in vSphere 6.0 and earlier. vSphere 6.5 does not support this client and it is not included in the product download. vSphere 6.5 introduces the new HTML5-based vSphere Client, which ships with vCenter Server alongside the vSphere Web Client. Not all functionality in the vSphere Web Client has been implemented for the vSphere Client in the vSphere 6.5 release. For an up-to-date list of unsupported functionality, see Functionality Updates for the vSphere Client Guide.

  • Cross vCenter Server provisioning, which was introduced in vSphere 6.0, is not supported across vCenter Server versions. The cross-vCenter provisioning operations not supported across different versions of vCenter Server include vMotion, cold migration, and cloning. For example, a vMotion operation from vCenter Server 6.0 to vCenter Server 6.5, and vice versa, are not supported.

  • VMware vCenter Operations Foundation 5.8.x is no longer offered, interoperable or supported with the release of vSphere 6.5. If you want to continue using vCenter Operations Foundation 5.8.x products, you can do so only with vSphere 5.5 and vSphere 6.0.

  • vSphere 6.5 is the final release that supports binary translation mode virtualization of operating systems. Future vSphere releases will not include binary translation mode. For more information, see https://kb.vmware.com/kb/2147608.

  • vSphere 6.5 is the final release that supports Software-Based Memory Virtualization. Future vSphere releases will not include Software-Based Memory Virtualization.

  • You cannot create new legacy (Record & Replay / uni-processor) Fault Tolerance virtual machines on vCenter Server 6.5 and ESXi 6.5 hosts. If you want to continue running legacy Fault Tolerance virtual machines, remain with ESXi 6.0 or earlier. Existing legacy Fault Tolerance virtual machines continue to be supported on ESXi hosts earlier than 6.5 and managed by vCenter Server 6.5.

    If you wish to upgrade ESXi hosts to 6.5, turn off legacy Fault Tolerance (do not only disable Fault Tolerance) on the protected VMs prior to upgrading. SMP-FT (multiprocessor Fault Tolerance) is not automatically enabled on the VM. You must manually turn on Fault Tolerance (which becomes SMP-FT) for VMs on the newly upgraded 6.5 ESXi host.

Resolved Issues

The resolved issues are grouped as follows.

Installation, Upgrade, and Migration Issues
  • vCenter Server might hang when adding an ESXi host to a cluster with associated Host Profile

    vCenter Server might hang showing progress at zero percent when you attempt to add an ESXi host to a cluster that already has an associated Host Profile.

    This issue is resolved in this release.

  • Cloning or cold migration might fail when a virtual machine picks an invalid host

    When you try cloning or cold migration of a virtual machine to a cluster, the VM might consider all hosts as invalid and randomly select a host, which might fail the operation. You may observe the issue if a host is in maintenance mode and is not eligible for a target host, but the VM picks it, or if a VM has devices referencing the source host.

    This issue is resolved in this release.

  • VMware vCenter Server Appliance configured with VMware vCenter Server High Availability might fail after an upgrade to 6.5 Update 1

    A vCenter Server Appliance configured with vCenter Server High Availability might fail after an upgrade to 6.5 Update 1, because the hostname of the appliance might change to the default localhost.localdomain.

    This issue is resolved in this release.

  • Select deployment size page of vCenter Server Appliance Installer might show irrelevant size values

    When prompted to select a value from the storage size drop-down on the Select deployment size page of the vCenter Server Appliance Installer wizard, you might see irrelevant values, because results are returned from a lookup against the total size and not against the sub-partition sizes of the source appliance, such as Stats, Events, Alarms and Tasks (SEAT) data.

    This issue is resolved in this release.

  • After upgrade to vCenter Server 6.5 the Hardware Status tab in vSphere Web Client might show error that no host data is available

    After an upgrade to vCenter Server 6.5 from vCenter Server 5.5 or vCenter Server 6.0, you might not be able to see hardware details for ESXi hosts as the Hardware Status tab in vSphere Web Client might show error No host data available. With this fix, you can monitor host hardware details after an upgrade.

    This issue is resolved in this release.

  • Default settings for root password expiration might be restored after minor upgrades

    After minor upgrades you might see previous settings for root password expiration reverted to default values.

    This issue is resolved in this release.

Miscellaneous Issues
  • The Email Address field in the vSphere Web Client alarm configuration wizard does not accept certain top level domains

    In the alarm configuration wizard of the vSphere Web Client, the Email Address field does not accept an email if the top-level domain is with 5 or more than 6 characters, only emails with top-level domains with 2, 3, 4 or 6 characters are allowed. This is a default validation in Flex applications for email addresses, but you cannot enter email addresses such as admin@example.systems or admin@example.services.

    This issue is resolved in this release.

  • vCenter Server might fail with in attempt to use 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.

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

  • Domain join might fail if concatenation of domain names in Active Directory environment with many trusted domains exceeds string length limit

    Domain join in Active Directory might fail if the concatenation of domain names of all the trusted domains exceeds the limit of 2048 bytes in the registry.

    This issue is resolved in this release.

  • vCenter Server might lose connectivity in attempt to mount or unmount an ISO image

    When you attempt to mount or unmount an ISO image from a CD-ROM via the vSphere Web Client, you might temporary lose connection to the vCenter Server due to a background process that might hang while establishing connection to the device. This usually occurs when you have vCenter Server installed on a virtual machine that runs on an ESXi host that is managed by the same vCenter Server.

    This issue is resolved in this release.

  • VPXD might fail due to a possible circular dependency in VMware DRS clusters with enabled VMware Distributed Power Management

    In DRS clusters with enabled VMware DPM, DRS might generate a recommendation to power off a host and create associated tasks to move the virtual machines out of this host, but in certain cases there might be a circular dependency between the tasks that might cause VPXD to fail.

    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.

  • SNMP manager of vCenter Server might fail to receive traps older than 497 days from a vCenter Server Appliance

    A SNMP manager of vCenter Server might fail to receive traps older than 497 days from a vCenter Server Appliance, because if the systemUptime parameter exceeds four bytes, it nullifies the time.

    Тhis issue is resolved in this release.

  • Log in to vSphere Web Client might fail if the fully qualified domain name of a vCenter Server contains the string .swf

    Log in to vSphere Web Client might fail if the fully qualified domain name (FQDN) of a vCenter Server system contains the string “.swf”.

    This issue is resolved in this release.

  • Attempt to export all matching events using vSphere Web Client might deliver a limited list of events

    In vSphere Web Client, if you navigate to File > Export > Export Events > Limits and select All matching events without specifying a limit, you still might get a limited list of events.

    This issue is resolved in this release.

Networking Issues
  • Host profile might fail to extract after import of a VMware vSphere Distributed Switch from a backup file

    If you import a vSphere Distributed Switch (VDS) by previous backup file with Preserve original distributed switch and port group identifiers option selected, in case vCenter Server restarts, it does not load the port group from the database correctly, and the operation to extract the host profile might fail. You might see an error similar to A specified parameter was not correct: dvportgroup-XXXXX Error: specified value.

    This issue is resolved in this release.

    NOTE: If you have already encountered this issue, after you upgrade to vCenter Server 6.5 Update 1d, you must disconnect and reconnect the respective host.

  • vNICs of virtual machines 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. 

  • vMotion of virtual machines with imported ephemeral port groups might fail as ports are not created after migration

    You might see vMotion of virtual machines with imported ephemeral port groups, or a VMware vSphere Distributed Switch (VDS) with such port groups, fail with an error similar to A general system error occurred: vim.fault.NotFound, because the ports might not be created after the migration.

    This issue is resolved in this release.

    NOTE: If you already can not migrate virtual machines due to this issue, after the upgrade to vCenter Server Update 1d you must delete the imported ephemeral port groups or DVS with such port groups and reimport them. 

  • vCenter Server does not accept SNMP users with non-alphanumeric characters

    With this fix you can create users on vCenter Server SNMP configuration with non-alphanumeric characters. Previously, only SNMP configurations for ESXi allowed users with non-alphanumeric characters.

    This issue is resolved in this release.

  • vSphere Web Client might show error in vSphere Distributed Switch topology after a restart of vpxd due to outdated Link Aggregation Groups data

    vSphere Web Client might show an error in the vSphere Distributed Switch topology after a restart of vpxd due to outdated Link Aggregation Groups (LAG) data, as the vCenter Server database might not be updated with data for physical adapters added to the LAG before the restart, and the daemon might not be able to find it.

    This issue is resolved in this release.

    NOTE: If you already face the issue, you must reassign the physical adapters to the LAG.

Security Issues
  • Update to the Spring Framework

    vCenter Server 6.5 is updated to use the 4.3.9 version of the Spring Framework.

  • Update to OpenSSL

    The OpenSSL package is updated to version openssl-1.0.2l.

  • Unlimited calls to list recent tasks in vSphere Client might lead to system outage

    In vSphere Client, users can get a list of recent tasks within the managed virtualization infrastructure and previously the number of tasks could be modified, which allowed attackers to submit such requests repeatedly to consume all available system resources and potentially cause a system outage. This fix reduces the maximum number of records that can be returned to 100.

    This issue is resolved in this release.

  • Update to Tomcat

    The Tomcat package is updated to version 8.5.15.

  • Update to Apache Struts

    Apache Struts is updated to version 2.5.13 to resolve CVE-2017-9805, CVE-2017-9804 and CVE-2017-9793.

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

    Previously, logins by Active Directory domain user accounts ending with a dollar sign were treated as machine accounts by default and logins on vCenter Server and ESXi hosts failed.

    This issue is resolved in this release.

  • Upgrade of Eclipse Jetty

    Eclipse Jetty is upgraded to version 9.2.22.

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

Storage Issues
  • 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 is resolved in this release.

  • Datastores might falsely appear as incompatible for a storage policy that includes I/O filter rules

    When you create or edit an existing storage policy, containing I/O filter common rules, and while checking for storage compatibility, you might observe messages like Datastore does not match current VM policy or Datastore does not satisfy compatibility since it does not support one or more required properties. Some of the datastores that you expect to be compatible, might appear in the incompatible list when you are checking for storage compatibility. This might also happen when you provision a virtual machine with a storage policy, containing I/O filter rules.

    This issue is resolved in this release.

  • Map Disk Region task might fill up the vCenter Server database task table

    The Map Disk Region task might alone fill up the vpx_task table in the vCenter Server database, which might cause vCenter Server to become unresponsive or other performance issues.

    This issue is resolved in this release. 

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • Memory leak in Ehcache might cause VMware Performance Charts service to fail and large java_pid.hprof files might pile in the storage

    A memory leak in Ehcache might cause the Overview Performance Charts service of vCenter Server to fail with OutOfMemory error and as a result, large java_pid.hprof files might pile in the storage partition.

    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.

  • VPXD might fail if you try to use a Host Profile from a host with version lower than vSphere ESXi 5.1  

    VPXD might fail if you try to use a Host Profile from a host with version lower than vSphere ESXi 5.1, because of an issue with the metadata.  

    This issue is resolved in this release.

  • vSAN license expiration alerts might continue even if vSAN is disabled

    You might continue to receive vSAN license expiration alerts similar to Expired vSAN license even if vSAN is disabled, because the License Service continues to exist and keeps its license state.

    This issue is resolved in this release.

  • vCenter Server Content Library service might fail to start after an upgrade

    vCenter Server Content Library service might fail to start after an upgrade due to a firstboot failure.

    This issue is resolved in this release.

Virtual Machine Management Issues
  • 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.

  • Attempts to edit a scheduled task for virtual machine snapshots via the vSphere Web Client might fail with error 1009

    In vSphere Web Client, attempts to modify a scheduled task for virtual machine snapshots might fail with error TypeError: Error #1009 and you might be prompted to reload the client in order to clear problems caused by this error.

    This issue is resolved in this release.

  • vCenter Sever might not propagate updated data for CPU and memory reservation to vCloud Director

    In the UI of VMware vCloud Director, you might not see changes in the memory and CPU usage for a provider Virtual Datacenter although virtual machines on the provider change their power status, because vCenter Server might not propagate updated CPU and memory reservation information.

    This issue is resolved in this release. 

  • Mass provisioning of virtual machines in VMware vCloud Director for Service Providers triggers multiple alarms on vCenter Server

    If you provision a virtual machine in VMware vCloud Director for Service Providers from a template, which has static MAC addresses already assigned, to a vCenter Server, you might see a VM MAC Conflict alarm and if you provision many VMs at a time, there might be multiple alarms that can only be handled manually. With this fix, the VM MAC Conflict alarm is removed from the default vCenter Server alarms to avoid massive generation of such alarms.

    This issue is resolved in this release.

vMotion and Storage vMotion Issues
  • vCenter Server might block restricted user accounts to perform migrations across vCenter Server systems

    When you attempt to migrate virtual machines across vCenter Server systems, vCenter Server might require Read permissions for all arguments used as part of the migration, including the destination datacenter, even though it is populated by default, and this might fail the operation for restricted user accounts such as ones with Folder permissions.

    This issue is resolved in this release.

CIM and API Issues
  • 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.

Internationalization Issues
  • User interface elements without translation in non-English locales show as undefined in vCenter Server Appliance Installer

    In vCenter Server Appliance Installer, user interface elements without translation in non-English locales might show as undefined, but with this fix, the element will display in English.

    This issue is resolved in this release.

  • vSphere Web Client might display non-localized content for recent tasks

    In vSphere Web Client, when monitoring recent tasks, you might see non-localized content such as internal labels instead of properly localized strings, for example something similar to Drm.ExecuteVMotionLRO.label, due to an issue with the plug-in NetBackup, versions 7.7.2 and 7.7.3.

    This issue is resolved in this release.

    NOTE: If you already face the issue, you must uninstall the plugin as a workaround. 

Auto Deploy Issues
  • Creation of new deploy rules from a customized image might fail in vSphere ESXi Image Builder

    Creation of new deploy rules from a customized image with the Image Builder UI in vSphere Web Client might fail with an error similar to Unable to obtain XML schema: Failed to load external entity /usr/lib/vmware-imagebuilder/etc/schemas/vib20-extensibility.rng.

    This issue is resolved in this release.

vSAN Issues
  • vSAN iSCSI messages might flood the Tasks view of vSphere Web Client

    If you upgrade a vSAN cluster from a vSphere 6.0 environment to a vSphere 6.5 environment, a message like Edit vSAN iSCSI target service in cluster might flood the Tasks view in the vSphere Web Client, even if the vSAN iSCSI feature is not enabled in this cluster.

    This issue is resolved in this release.

  • New icon for vSAN witness appliances

    This release introduces a new icon for vSAN witness appliances. When you deploy a vSAN witness appliance, you will see a nested host with a new icon in the UI, which indicates that this host can only be used as a witness in a stretched cluster.

    This issue is resolved in this release.

  • vSAN Health Service logs might eat up all log storage space in vCenter Server on Windows

    vSAN Health Service logs might eat up all log storage space in vCenter Server on Windows if log rotation coincides with a running task for collecting support bundle or phone home data for Customer Experience Improvement Plan (CEIP).

    This issue is resolved in this release.

  • vSphere Update Manager baselines might change from patch to upgrade when only one node in a cluster is remediated

    vSAN build recommendation for system baselines and baseline groups for use with vSphere Update Manager might not work if there is a vCenter Server system-wide http proxy. With this fix, vSAN build recommendations in a system-wide http proxy set up are as available and consistent as the vSAN build recommendations created with direct Internet connection.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Backup and Restore Issues
  • vCenter Server Appliance restore might fail if you modify DNS setting

    If you modify the DNS setting in the Configure network settings page of the vCenter Server Appliance 6.5 Installer, while attempting to restore a vCenter Server Appliance, you might see an error for the loopback addresses on the DNS Servers field.

    Workaround: To workaround this issue, you must remove the loopback address 127.0.0.1 or ::1 from the DNS Servers field in the network settings page.

  • A tilde symbol in backup file paths might cause failure of vCenter Server Appliance restore

    If you use a tilde symbol as a shortcut to the home directory in a backup file path for a vCenter Server Appliance like <ip>/~/<backupFolder>, you might see an error Folder path is incorrect when you attempt to restore the vCenter Server Appliance.

    Workaround: To work around this issue, you must provide the full path to the home directory like <ip>/home/<username dir>/<backupFolder>.

Miscellaneous Issues
  • Users with root or object-level permissions in vCenter Server might not be able to create Tags and Tag Categories

    Users with root or object-level permissions in vCenter Server might not be able to create Tags and Tag Categories as the Tag Categories field might remain blank regardless of changes.

    Workaround: To work around this issue you must assign global permissions to users. 

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • Login to vSphere Web Client with Windows Session authentication might fail with Mozilla Firefox browser

    Login in the vSphere Web Client with Windows session authentication, using Firefox 54 or higher version, might fail because the VMware Enhanced Authentication Plugin might not find your user name.

    Workaround: To work around this issue, you must use other browsers like Internet Explorer, Google Chrome or Mozilla Firefox equal to or lower than version 53.

  • Keyboard mapping in the HTML5-based vSphere Web Client WebMKS console might not be correct

    Some keys in the HTML5-based vSphere Web Client WebMKS console might not be mapped correctly and in both English and non-English keyboards symbol keys like “!”, “@”, “#” and “$” might not output as expected.

    Workaround: To work around this issue, you can use either of the following options:

    1. Install and use the VMware Remote Console for the guest operating systems, instead of the WebMKS console.
    2. Set the locales in the WebMKS console URL for the guest operating system as follows:
      •     For English(United States)[en-US]: locale=en-US
      •     For Japanese(Japan)[ja-JP]: locale=ja-JP
      •     For German(Germany)[de-DE]: locale=de-DE
      •     For French(France)[fr-FR]: locale=fr-FR
      •     For Italian(Italy)[it-IT]: locale=it-IT
      •     For Spanish(Spain)[es-ES]: locale=es-ES
      •     For French(Switzerland)[FR-CH]: locale=fr-CH
      •     For German(Switzerland)[DE-CH]: locale=de-CH
      •     For Portuguese(Portugal)[pt-PT]: locale=pt-PT
    3. Use the Flex-based vSphere Web Client to open the console for the guest operating systems.

Known Issues from Earlier Releases

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