The release notes cover the following topics:

Note: It is applicable for vCenter Server Appliance only. The current setting may remain functional if no operation is performed.

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

VMware vSphere 6.0 is available in the following languages:

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

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.

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.

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.

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

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

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.

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 recommends only two deployment models:

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.

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.

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.

Read the Knowledge Base article KB 2091273.

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.

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.

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.

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:

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.

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

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

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.

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

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

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.

Installation and Upgrade Issues

This issue is resolved in this release, install, and upgrade subcommands are supported for the VCSA command-line installer on OS X.

Unable to deploy vCenter Server Appliance using CLI commands on an OS X client . Unable to deploy vCenter Server Appliance using vcsa-deploy CLI commands on an OS X machine. This issue occurs while running commands from vCenter Server Appliance 6.0 Update 2 ISO image.

Security Issues

Storage Issues

vCenter Server, vSphere Web Client, and vSphere Client Issues

This issue occurs when IPV6 has been disabled and the snmpd process does not start. Note: By default IPV6 is enabled.

<DATE STAMP><TIME STAMP> uscrkvcenter01 snmpd[12096]: 16:get_socket: socket(10, 2, 0) failed 97 Address family not supported by protocol <DATE STAMP><TIME STAMP> uscrkvcenter01 snmpd[12096]: 17:Error opening specified endpoint "UDP6:162", skipping <DATE STAMP><TIME STAMP> uscrkvcenter01 snmpd[12096]: 18:Initialization failure, Server Exiting with code 1 <DATE STAMP><TIME STAMP> uscrkvcenter01 watchdog-snmpd: '/bin/snmpd' exited after 1 seconds (quick failure 2) 1

This issue is resolved in this release as the VCSA send emails with the return-path of the configured email sender.

This issue is resolved in this release. For more information on fix for minor upgrades, see KB 2149028 .

Note : Hardware-Health Data was not displayed to users with minimum read privilege on the host object. Logging in to vSphere Web Client with Global Permissions, Hardware-Health under Hardware Status tab for the same host is displayed to the user.

This issue is resolved in this release. For more information on resolution, see KB 2148938 .

Virtual Machine Management Issues

Single-Sign on Issues

Authentication issues in SRM 6.1 with a federated SSO and PSC for domain users . When a domain user is logged in with a federated Single-Sign On environment, paired site displays status similar to the following: "Not connected to SRM server"

CIM and API Issues

VMware High Availability and Fault Tolerance Issues

Unable to complete vSphere HA agent configuration on the host . Configuring the vSphere HA agent on the host fails with an error similar to the following: Cannot complete the configuration of the vSphere HA agent on the host. Host network configuration is missing .

Networking Issues

Certificate Management Issues

vMotion and Storage vMotion Issues

Guest Operating System Issues

Miscellaneous Issues

The known issues are grouped as follows.

Installation and Upgrade Issues

If the issue persists after following the steps above, perform the steps:

Note: Platform Services Controller of vCenter Server Appliance is installed with 4 GB of memory by default in case of fresh install and while upgrading from 5.5.x to 6.0 Update 3.

Workaround: Microsoft updates are required to make vSphere Client function with TLSv1.2. For more information, see KB 2149000 .

Migration Issues

To view a list of known issues applicable from earlier releases, click here.

vCenter Server for Windows Installation Issues

If you uninstall vCenter Server, the embedded PostgreSQL database is removed

If you uninstall vCenter Server from a Microsoft Windows virtual machine or physical host, the embedded PostgreSQL database is also uninstalled and all the data stored in it is lost.

Workaround: To prevent losing the data from your database, back up the PostgreSQL database and then restore it. When you use a database server alias name to create a DSN, the installation of vCenter Server fails

When you use a database server alias name to create a DSN, the installation of vCenter Server with an external Microsoft SQL database fails. The following error appears during the installation of the inventory service: An error occurred while starting invsvc . Workaround: Use the IP address or the host name of the database server to create a DSN.

When you use a database server alias name to create a DSN, the installation of vCenter Server with an external Microsoft SQL database fails. The following error appears during the installation of the inventory service: . If you use a user name that contains high-ASCII or non-ASCII characters, you cannot install vCenter Server using SQL Server with Windows integrated authentication

When you use a user name that contains native high-ASCII or non-ASCII characters, the installation of vCenter Server using SQL Server with Windows integrated authentication fails. An error appears while a security operation is performed. Workaround: Use a user name with ASCII characters only.

If you use a password that contains high-ASCII or non-ASCII characters, you cannot install vCenter Server using SQL Server with Windows integrated authentication

When you use a password that contains native high-ASCII or non-ASCII characters, the installation of vCenter Server using SQL Server with Windows integrated authentication fails. An error appears while starting service invsvc . Workaround: Use password with ASCII characters only.

When you set up vCenter Server to use an external database from the vCenter Server installer, you might not be able to select a system DSN

When you configure vCenter Server to use an external SQL database from the vCenter Server installer, the system DSNs configured by using a SQL server driver are not displayed in the list of available DSNs. Workaround: When you configure a system DSN for the external SQL server database, use SQL Server Native Client.

If you have uninstalled the IPv4 stack, VMware vCenter Server 6.0.0 installation might fail

If you have uninstalled the IPv4 stack, the installation of VMware vCenter Server 6.0.0 might fail while trying to start the VMwareAfdService . The error messages similar to the following might be displayed: An error occurred while starting service 'VMwareAfdService' Failed to clean up VKS binaries, Error: 2 Please search these symptoms in the VMware Knowledge Base for any known issues and possible workarounds. If none can be found, please collect a support bundle and open a support request. Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details. Workaround: Before you install VMware vCenter Server 6.0.0, make sure the IPv4 stack is installed. If the command netsh interface ipv4 show interfaces results in a message: The request is not supported , the IPv4 stack has been uninstalled and should be reinstalled. To reinstall the IPv4 stack, run the netsh interface ipv4 install command and reboot the machine.

The vCenter Server installation or uninstallation process might fail or stop responding on Windows Server 2008 R1 SP2

The Windows Installer on Windows Server 2008 R1 SP2 has issues with handling multiple packages. Because of these issues the vCenter Server installation might stop responding, or if you attempt to install and uninstall vCenter Server a few times, the process might fail. Workaround: Apply the patch from Microsoft KB 981669 which addresses the Windows Installer issue.

Attempts to uninstall the Platform Services Controller might fail

If you attempt to uninstall a Platform Services Controller that has one or more active associated vCenter Server instances, the operation might fail with an error message similar to the following:



Setup Interrupted .



There is no clear message stating that the issue occurs because of vCenter Server instances registered with the Platform Services Controller. Workaround: Repoint the vCenter Server to another Platform Services Controller in the same vSphere domain as the Platform Services Controller you intend to uninstall.

Installation of vCenter Server might fail if the time skew between the machine on which you install vCenter Server and the Platform Services Controller is three minutes or more

vCenter Server installation might fail if there is no time synchronization between the Platform Services Controller and the machine on which you install vCenter Server. Time difference of more than 3 seconds, the wizard displays the time difference in seconds.

If the time skew is between 3 seconds and 2 minutes, a message informing you about the time difference is displayed. You can close the information dialog box and continue the installation. If the time skew is between 2 and 4 minutes, a message warning you about the wide margin time difference is displayed. If the time difference is more than 4 minutes, you cannot proceed with the installation. Workaround: If you see the warning message that the time difference is between 2 and 4 minutes, stop the vCenter Server installation and synchronize the clock of the machine on which you install vCenter Server with the clock of the Platform Services Controller. Run the vCenter Server installer again.

vCenter Server installation fails if the system name input (FQDN or IP address) does not exactly match the Platform Services Controller input as FQDN/FQDN or IP/IP

If you use an FQDN or IP address when you install the Platform Services Controller, the vCenter Server input should match with the Platform Services Controller input. If you provided a FQDN during the Platform Services Controller installation, when you register vCenter Server with that Platform Services Controller, you must provide the FQDN of the Platform Services Controller. If you provided an IP address during the Platform Services Controller installation, when you register vCenter Server with that Platform Services Controller, you must provide the IP address of the Platform Services Controller. Otherwise, the vCenter Server installation fails on first boot. Workaround: Make sure that the vCenter Server and Platform Services Controller inputs always match.

Installation of vCenter Server in pure IPv6 environment might fail if you do not have full DNS support

Attempts to install vCenter Server in a pure IPv6 environment might fail if you do not have full DNS support. This is because the Platform Services Controller installer does a reverse lookup to get the machine name. Workaround: If you do not have full DNS support, you must ensure that both forward and reverse lookup works in vCenter Server with embedded Platform Services Controller deployment.

You cannot uninstall vCenter Server for Windows by right-clicking the Windows installer package and selecting Uninstall

You can uninstall vCenter Server for Windows by using either Windows Add/Remove Programs, or the vCenter Server for Windows installer package. However, when you right-click the vCenter Server for Windows installer package and select Uninstall , no message is displayed. If you right-click the vCenter Server for Windows installer package and select Uninstall again, you receive a message stating that the product is already uninstalled. Workaround: Use Windows Add/Remove Programs to uninstall vCenter Server for Windows.

vCenter Server for Windows does not support user data source name (DSN) for external databases

Only system DSNs are supported for vCenter Server for Windows installations. If you add a user DSN, it is not displayed in the Database Configuration page of vCenter Server for Windows. Workaround: When you install vCenter Server for Windows, add a system DSN for the external database.

You cannot install vCenter Server for Windows if you use a custom user name service account containing non-ASCII or high-ASCII characters

vCenter Server for Windows installation fails to configure the vCenter Server service account if you log in to the Operating System as a user defined by a custom account policy, and the user name contains non-ASCII or high-ASCII characters. Workaround: The custom user account you log in with must consist only of ASCII characters.

Uninstalling or canceling an install of vCenter Server for Windows might not always clean up all directories and files in the user data directory or installation directory

If you attempt to uninstall or cancel an install of vCenter Server for Windows, before the services start, the user data directory under C:\ProgramData\VMware\vCenterServer or the installation directory under C:\Program Files\VMware\vCenterServer might not be deleted completely from your system. This might affect a subsequent attempt to install vCenter Server for Windows. Workaround: Reboot the machine before attempting a fresh install again.

No logs are generated after running vc-support.bat

When you attempt to generate logs by running the C:\Program Files\VMware\vCenter Server\bin\vc-support.bat command, an error occurs and the logs are not generated if the Operating System login user name contains high-ASCII or non-ASCII characters. Workaround: Run the C:\Program Files\VMware\vCenter Server\bin\vc-support.bat command after logging in to the operating system with a user name containing only ASCII characters.

vCenter Server installation fails if you add a service account with special characters @ or \

While installing vCenter Server, you can specify a service account instead of using the default Windows Local System account. If the account name you select has special characters @ or \ , the installation might fail with a vpxd first boot error. Workaround: During the installation of vCenter Server, create a service account without special characters @ or \ .

A first boot script fails during the deployment of vCenter Server with an external Platform Services Controller

When you attempt to deploy vCenter Server with an external Platform Services Controller, the first boot fails during the deployment when you enter the IP address or host name of the Platform Services Controller. Workaround: Enter the same system network name that you used during the deployment of the Platform Services Controller.

vCenter Server Appliance Deployment Issues

Silent upgrader prompts user to trust ESXi host

The silent scripted installer or upgrader might prompt the user to accept the fingerprint of the target ESXi host or vCenter Server on which the new vCSA is to be deployed, if the fingerprint is not in the known host file.



Workaround:

The silent scripted installer or upgrader might prompt the user to accept the fingerprint of the target ESXi host or vCenter Server on which the new vCSA is to be deployed, if the fingerprint is not in the known host file. Workaround: Add the public key of the target ESXi host or vCenter Server to the known host file.



Add the --no-esx-ssl-verify option to your CLI installer or upgrader command to disable the SSL fingerprint check.

Validation of the SSO FQDN/IP address field is not performed dynamically

While installing the vCenter Server Appliance 6.0 build using HTML 5 installer, validation of content in the SSO FQDN/ IP address field is not completed. The installer accepts the input in any given format, for example sso-hostname and allows complete installation. However during the first boot, execution of the script fails as the system is unable to find the certification with the host name in the required format, sso-hostname.xxx.yyy .



Workaround: Enter the details in the SSO FQDN/ IP address field in the accepted format, sso-hostname.xxx.yyy

Attempts to deploy vCenter Server Appliance using an ISO image file might display incorrect deployment status

When you deploy vCenter Server Appliance using an ISO image file, the deployment wizard might not display the actual process of the deployment. The wizard stops responding and displays as "Powering on appliance" even though the VCSA deployment is completed.



Workaround : The status of deployment can be checked in appliance console.

psc_restore command fails in multi-node PSC environment

Attempt to run psc_restore command in a restored PSC node fails in multi-node PSC environment when there are two-way replication agreements among the PSC nodes in the federation.



Workaround: In multi-node PSC environment when there are two-way replication agreements among the PSC nodes in the federation, make sure that at least one object on a PSC node replicates with the other nodes before taking backup of the PSC nodes in the federation.

Attempt to run command in a restored PSC node fails in multi-node PSC environment when there are two-way replication agreements among the PSC nodes in the federation. Workaround: In multi-node PSC environment when there are two-way replication agreements among the PSC nodes in the federation, make sure that at least one object on a PSC node replicates with the other nodes before taking backup of the PSC nodes in the federation.

Starting the vSphere Web Client by clicking the URL on the last page of the vCenter Server Appliance deployment wizard might fail

If you deployed a vCenter Server Appliance with an external Platform Services Controller and the Platform Services Controller is configured behind an F5 Load Balancer, after you click the URL on the last page of the vCenter Server Appliance deployment wizard, the vSphere Web Client interface does not appear and the following exception is generated:

HTTP Status 400 - BadRequest, Not able to respond to the request posted to /SAML2/SSOSSL/ Workaround: Refresh the Web page.

You cannot deploy the vCenter Server Appliance with an external Oracle database, if the database was used in a previous deployment attempt

The vCenter Server Appliance installer prevents deployment of the vCenter Server Appliance with an external Oracle database that has been used in a previous vCenter Server Appliance deployment and does not provide you with the option to reuse or delete the database. You receive an error message The vCenter Server database is locked. Another vCenter Server service is using this database and must be stopped. This issue occurs even if the vCenter Server Appliance that uses the database is powered off or removed from the ESXi host. Workaround: Use a new instance of an Oracle database or select to use the embedded database.

The vCenter Server Appliance installation fails when connecting to an External Platform Services Controller

The vCenter Server Appliance installation with an external Platform Services Controller might fail if the time between the existing Platform Services Controller and the ESXi host or NTP server, depending on the vCenter Server Appliance time configuration settings, is not synchronized. No warning messages are displayed during the vCenter Server Appliance installation to report the time skew. Workaround: Synchronize the clock of the deployed Platform Services Controller and the ESXi host on which the vCenter Server Appliance is to be deployed or the NTP server the vCenter Server Appliance is to use after installation.

If you restart the guest operating system of the vCenter Server Appliance, the vpxd service might fail to start

When you deploy the vCenter Server Appliance, you can decide whether to use VMware Tools-based or NTP server-based time synchronization. If you set up the vCenter Server Appliance to use NTP server-based time synchronization, the guest operating system of the vCenter Server Appliance is synchronized with an NTP server. If the host on which you deploy the vCenter Server Appliance is not configured to use the same NTP server or if the time on the ESXi host is different from the time on the guest OS of the vCenter Server Appliance, when you restart the vCenter Server Appliance, the NTP daemon starts early and sets the correct time. However, the VMware Tools service starts later than the NTP daemon, and sets the vCenter Server Appliance system time to the host system time. By the time the NTP daemon corrects the time again, the vpxd service already attempts to start and fails. Workaround: Set up the ESXi host to use the same NTP server for time synchronization as the vCenter Server Appliance and then deploy the vCenter Server Appliance.

You cannot enter an IPv6 address of the ESXi host in the vCenter Server Appliance deployment wizard

The vCenter Server Appliance deployment wizard does not accept an IPv6 address to connect to the ESXi host for deploying the vCenter Server Appliance. Workaround: Connect to the ESXi host by using an FQDN.

The vCenter Server Appliance scripted installer fails if more DNS servers are provided simultaneously

The scripted installation of vCenter Server Appliance fails if you provide more than one DNS server during the installation process. Workaround: You should use only one DNS server at a time, and after the installation has finished, you can add more DNS servers.

There is no pre-check function available for the network settings entered by you in the network configuration page and this could result in a firstboot error

There is no pre-check function available, to ensure that the values entered by you for text boxes such as static options (network address, subnet mask, network gateway, network DNS Servers, system name (FQDN or IP)) are valid. So if you enter a wrong value in any of these fields, a firstboot error might occur. Also, there is no pre-check function to ensure that the current FQDN, for the DHCP option, is already in use. Workaround: Ensure that the values provided for the different network settings are valid. These settings are static options (network address, subnet mask, network gateway, network DNS servers, system name (FQDN or IP)) and the DHCP option: FQDN (Optional).

The user interface installer of the vCenter Server Appliance might require the Client Integration plug-in to run, depending on browser type, this prompt may vary

When launching the vCenter Server Appliance installer, the tool may request an application to be launched. Workaround: If a prompt appears when opening the vCenter Server Appliance scripted installer, follow the instructions for each type of browser: Google Chrome. Allow the installer to launch the application. Mozilla Firefox. Select csd.exe and click OK . Internet Explorer. Click Allow .

The vCenter Server Appliance scripted installer does not support custom HTTPS port number for interacting with vCenter Server instance

vCenter Server 6.0 supports customization of the HTTPS port. When connecting the vCenter Server Appliance to vCenter Server, this port is necessary to connect to vCenter Server. Currently, this port cannot be customized in the vCenter Server Appliance scripted installer. Workaround: To use a custom HTTPS port, use the HTML5 user interface installer to install vCenter Server and Platform Services Controller.

vCenter Server 6.0 supports customization of the HTTPS port. When connecting the vCenter Server Appliance to vCenter Server, this port is necessary to connect to vCenter Server. Currently, this port cannot be customized in the vCenter Server Appliance scripted installer. The vCenter Server Appliance scripted installer allows you to proceed with the installation with less than 15 GB of available disk space, which is below the minimum requirement

When installing vCenter Server Appliance using the scripted installer, the tool proceeds to install the software on hosts with less than 15 GB space available on the datastore. The installer proceeds, but vCenter Server Appliance might fail to power on the virtual machine. Workaround: You should ensure that the ESXi host has at least 15 GB available space.

Help is not working for help.war file installation

The file help.war is downloaded as a root file that causes the permission error when you attempt to install it. The files under /pickup have owner vsphere-client and group users that are used by the Java Virtual Machine. Workaround: Perform the following steps: Download help.war to the /usr/lib/vmware-virgo folder of your vCenter Server Appliance. Change it to the following: owner vsphere-client and group users :

chown vsphere-client help.war

chgrp users help.war Change your account to vsphere-client.

If you stay root the copy operation changes the owner to root again.

su vsphere-client Verify that the server is already running and copy help.war to /usr/lib/vmware-virgo/server/pickup . If you start or restart the server after copying help.war to /pickup , the help does not work because /pickup is emptied each time.



On any Windows OS, if vcsa-setup.html is refreshed on Firefox browser, a blank banner message might appear after allowing the Client Integration Plugin to run

Refreshing the vcsa-setup.html file might result in a blank banner on top in the Firefox browser. This is an intermittent issue. The blank banner appears after allowing the Client Integration Plugin to run on the browser. For example, allowing the vmware-csd process to run on Firefox.

Workaround: While allowing vmware-csd process to run on Firefox for the first time, select the Remember my Choice option for vmware-csd links and refresh the vcsa-setup.html file. This should prevent the blank banner on refresh of the vcsa-setup.html file.

Alternatively, close Firefox browser and reopen vcsa-setup.html .

The Install and Upgrade buttons might not appear in the vCenter Server Appliance installer if you run it in Mozilla Firefox on a Windows 2008 Server OS, if the proxy settings are not configured properly

After you install the Client Integration Plug-in and open vcsa-setup.html in Mozilla Firefox on a Windows 2008 Server OS, you must allow the Client Support Daemon plug-in to run. After you select vmware-csd and click OK , the Install and Upgrade buttons might still not appear. The countdown for detecting the Client Integration Plug-in goes down to zero but nothing happens. This issue is related to the browser proxy settings. Workaround: Fix the Mozilla Firefox proxy settings: Navigate to the Firefox Options menu. Click Advanced , and click the Network tab. Click Settings . If Use system proxy settings is selected, click the Auto-detect proxy settings for this network radio button. If the Use manual proxy configuration is selected, set the proxy server for your network.

The vmware-csd process sometimes crashes if Windows updates are not installed, or if you do not have permission for the Client Integration Plugin log location

After launching vcsa-setup.html , the browser prompts you to allow the Client Integration plugin. For example, allow the vmware-csd process. After allowing the plugin to run, the vmware-csd process may crash. This issue could be produced if Windows updates are not installed or if you, as a Windows user, do not have permission to write in the Client Integration Log location. The log location is Users\%USER%\AppData\Local\VMware\ . Workaround: You need to install all Windows updates. Also you need to obtain permission to write in the Client Integration Plugin log location, which is Users\%USER%\AppData\Local\VMware\ .

After launching , the browser prompts you to allow the Client Integration plugin. For example, allow the process. After allowing the plugin to run, the process may crash. This issue could be produced if Windows updates are not installed or if you, as a Windows user, do not have permission to write in the Client Integration Log location. The log location is . Dynamic DNS is not supported when installing vCenter Server Appliance in an IPv6 environment

When you install vCenter Server Appliance in an IPv4 environment, you can use Dynamic DNS by entering a value in the FQDN Optional text box. When you install vCenter Server Appliance in an IPv6 environment, the FQDN Optional text box is available, but if you enter a value, the installation will fail. Workaround: Leave the FQDN Optional text box empty when you install vCenter Server Appliance in an IPv6 environment.

The command line deployment option --sso-ssl-thumbprint does not work for Platform Service Controller and vCenter Server Appliance

The command line deployment tool for vCenter Server Appliance provides the option --sso-ssl-thumbprint to verify the certificate of Platform Service Controller through a SHA1 checksum. Currently the option does not work. Workaround: Manually verify the SHA1 checksum before you deploy vCenter Server Appliance.

vCenter Server for Windows and vCenter Server Appliance Deployment Issues

Unable to log in to vSphere Client with the Use Windows Session Credentials option

Attempts to log in to vSphere Client with the "Use Windows Session Credentials" option might fail as the login takes more than the configured time out value. An error message similar to the following:



Windows session credentials cannot be used to log into this server.

Enter a user name and password.



A performance improvement has been made in this area, however, you might still encounter the issue under certain circumstances.



Workaround: None

vCenter Server for Windows and vCenter Server Appliance installations fail when using non-ASCII or high ASCII characters in text boxes

Entering non-ASCII or high ASCII characters such as (é,è, ä, ö) in text boxes during vCenter Server for Windows or vCenter Server Appliance installation causes the install process to fail. Workaround: When deploying vCenter Server for Windows or vCenter Server Appliance, use only regular ASCII characters in the text boxes, with the exception of the following characters: brackets, slash (/), backslash (\), caret (^), colon (:), semicolon (;), angle brackets (< and >), single quotation mark ('), double quotation mark ("), dollar sign ($), and ampersand (&).

When you deploy Platform Services Controller or vCenter Server in an IPv6 environment, or you connect it to an external database, provide only fully qualified domain names (FQDNs)

The installation of the Platform Services Controller or vCenter Server does not support the use of IPv6 addresses. In addition, to configure the Platform Services Controller or vCenter Server with an external database, provide the FQDN of the target database server. Workaround: None.

vCenter Server for Windows and vCenter Server Appliance installations fail when using an external database with manually customized database objects

If you attempt to use an external database with manually created database objects, the installation fails. The installer displays the error messages: install.vdcs.db.version.check.error and Installation of component VCSService Manager Failed with error code 1603 . Workaround: Do not use an external database with manually customized database objects or when prompted by the wizard choose to erase the custom schema and create a new schema.

Client Integration Plug-In Installation Issues

VMware-ClientIntegrationPlugin-6.0.0 cannot be installed using Window System Account credentials

InstallCertificate method does not create the CIP directory in C:\ProgramData\VMware folder when vmware-csd.exe runs with --install parameter using the Windows system account.

This results in installation failure of VMware-ClientIntegrationPlugin.

Workaround: None

Installation and uninstallation of the VMware Client Integration Plug-in might fail if some antivirus software is running

When you try to install or uninstall the VMware Client Integration Plug-in while some antivirus software, for example, Avira Antivirus is running, the operation might fail. The antivirus software might block access to the Windows host files. An error message might be displayed: Error overwriting hosts file: boost::filesystem::copy_file: Access is denied: C:\Windows\System32\drivers\etc\hosts.new, C:\Windows\System32\drivers\etc\hosts\ . Workaround: Disable the antivirus software before you install or uninstall the VMware Client Integration Plug-in.

vSphere Web Client login page might not detect correct version of Client Integration Plug-in

Although an earlier version of the Client Integration Plug-in might be installed on your system, the login page for the vSphere Web Client does not prompt you to upgrade the Client Integration Plug-in. After you log in to the vSphere Web Client, and select Help > About VMware vSphere, the dialog displays a link to upgrade the Client Integration Plug-in. Workaround: Log in to the vSphere Web Client, and select Help > About VMware vSphere. Click the Upgrade Client Integration Plug-in link to install the latest version of the plug-in.

VMware vSphere Authentication Proxy Installation Issues

VMware vSphere Authentication Proxy installation fails with error

When you log in with Active Directory domain administrator credentials to perform the installation, the VMware vSphere Authentication Proxy installation fails with the following error: Error 1920. Service VMware vSphere Authentication Proxy Adapter (vmware-cam-adapter) failed to start... Workaround: None.

Review also the Installation Issues section of the release notes. Many installation issues can also impact your upgrade process.

Attempts to upgrade vCenter Server Appliance or the Platform Services Controller Appliance from 6.0 Update 1 or 6.0 Update 1b to 6.0 Update 2 fail if IPv6 is disabled

Attempts to upgrade vCenter Server Appliance or the Platform Services Controller Appliance from 6.0 Update 1 or 6.0 Update 1b to 6.0 Update 2 fail if IPv6 is disabled. Workaround: Before the upgrade, enable IPv6 in the legacy setup and then perform the upgrade.

Attempts to upgrade vCenter Server Appliance or the Platform Services Controller Appliance from 6.0 Update 1 or 6.0 Update 1b to 6.0 Update 2 fail if IPv6 is disabled. Attempts to uninstall authentication proxy fail

Attempts to uninstall authentication proxy on vCenter Server 6.0 Update 2 fail. An error message similar to the following is displayed: Error 29455.vCenter Server version is not supported Workaround: Click OK to uninstall the authentication proxy successfully.

In vCenter Server 6.0, health message under the Summary tab does not display the previous month and year data

In vCenter Server 6.0, health message under the Summary tab does not display the previous month and year data. The Summary tab displays the following health message:

Performance statistics rollup from Past Week to Past Month is not occurring in the database For more information, see KB 2135488. Workaround: See KB 2135488.

Attempts to upgrade vCenter Server from 5.5 Update 3, 5.5 Update 3a, or 5.5 Update 3b to 6.0 Update 2 fail during pre-upgrade check

vCenter Server upgrade from 5.5 Update 3, 5.5 Update 3a, or 5.5 Update 3b to 6.0 Update 2 fail during the pre-upgrade check stage. This happens when you use SQL 2012 or 2014 AlwaysOn Availability Groups (AAG) setup.

When the pre-upgrade check fails, a message similar to the following can be seen:

Source vcenter server validation found an issue: ERROR:cannot execute statement(rc=-1). Workaround: Configure your database to meet the vCenter Server upgrade requirements. For more information, see KB 2144262.

SSLv3 remains enabled on Auto Deploy after upgrade from earlier release of vSphere 6.0 to vSphere 6.0 Update 1 and above

When you upgrade from an earlier release of vSphere 6.0 to vSphere 6.0 Update 1 and above, the SSLv3 protocol remains enabled on Auto Deploy. Workaround: Perform to the following steps to disable SSLv3 using PowerCLI commands: Run the following command to Connect to vCenter Server:



PowerCLI C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI> Connect-VIServer -Server <FQDN_hostname or IP Address of vCenter Server>



Run the following command to check the current sslv3 status:



PowerCLI C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI> Get-DeployOption



Run the following command to disable sslv3:



PowerCLI C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI> Set-DeployOption disable-sslv3 1



Restart the Auto Deploy service to update the change.

When you upgrade from an earlier release of vSphere 6.0 to vSphere 6.0 Update 1 and above, the SSLv3 protocol remains enabled on Auto Deploy.

vCenter Server Appliance installer is not supported by a 64-bit Firefox browser

When you attempt to install vCenter Server Appliance 6.0, the Client Integration Plugin detects an unsupported OS, and displays an error message similar to the following:

vCenter Server Appliance installer cannot run on this OS. It must be run on Windows Workaround: Use an alternative supported browser, or install a 32-bit version of the Mozilla Firefox browser. Supported browsers are: Microsoft Internet Explorer 10.0.19 and later. Google Chrome 39 and later (32-bit only). Mozilla Firefox 34 and later (32-bit only).

When you attempt to install vCenter Server Appliance 6.0, the Client Integration Plugin detects an unsupported OS, and displays an error message similar to the following:

Content Library creation might fail when vCenter Server is upgraded to 6.0 Update 2

When vCenter Server is upgraded to 6.0 Update 2, the Content Library creation might fail with an error. Workaround: To workaround the following,

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,

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>



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.

Append -----BEGIN CERTIFICATE----- at the beginning and -----END CERTIFICATE----- at the end of the file. 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 Restart all services.

For Windows,

See workaround (steps 1 to 3) of vCenter Server Appliance. 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 Restart all services.

After upgrading the N1 and M1 nodes from vCenter Server 5.5 to 6.0 Update 2, vSphere Web Client is unable to see the vCenter Server 5.5 Management node

After upgrading the N1 and M1 nodes from vCenter Server 5.5 to 6.0 Update 2, vSphere Web Client is unable to see the vCenter Server 5.5 Management (M2) node. Workaround: None.

Attempts to upgrade from VCSA 5.5 to 6.0 might fail with an error

When you attempt to upgrade the vCenter Server Appliance from 5.5 to 6.0, the installer fails with the following error message when attempting to apply network configuration to new vCSA 6.0:



"Fatal error during network configuration Migration Failed"



Workaround: Follow these steps to resolve the issue:

Login to the VAMI interface for the 5.5 VCSA. https://<VC_IP>:5480 Click the Network tab and then the Address section. Make sure the settings in here are all correct and then click Save Settings, even if you didn’t change anything. SSH to the appliance and collect the output of the following command

“cat /etc/sysconfig/network/ifcfg-eth0” Make sure the source and destination are in the same subnet. Attempt the upgrade again.

Unable to connect to vCenter Server through vSphere Web Client programs shortcut

After you upgrade from vCenter Server 6.0 GA to later versions of vCenter Server 6.0, attempts to connect to the vCenter Server through the vSphere Web Client shortcut (Start --> Programs) connects to URL https://vsphere-client and displays a blank page with Webpage is not available error.

Workaround: To workaround this issue, create a shortcut using the following steps: Login to vSphere Web Client using Chrome

On the top right corner of the browser, click More Tools

Create a shortcut to connect to vCenter Server



The shortcut will function as expected.

Database configuration firstboot fails during upgrade

Upgrade fails when starting ESXi dump collector with an error message similar to the following:

Error in accessing windows registry entry during DSN analysis: Error in accessing registry entry for DSN 'YOUR DSN NAME '. Please make sure the DSN is set up properly." Workaround: Before restarting the upgrade:

Remove the trailing white space from the DSN name. Restore the environment to state prior to the failed upgrade.

Policy tag and category merge during vCenter Server upgrade from 5.5 to 6.0 can cause a Rule-Set1 alert

When you upgrade vCenter Server 5.5 to 6.0, policy tags and categories with case-insensitive names are merged incorrectly. For example, if a vCenter Server database has two tags in two categories with different cases before upgrade, such as "One" and "one," with each tag belonging to a separate storage profile before the upgrade, the upgrade process merges the tags into a single tag and a single category, such as"One." As a result of the case-insensitive tag and category merge, the storage profile which has the tag that was removed, such as "one" in the example above, has a Rule-Set1 alert. Workaround: None.

Internal error during first boot phase of upgrade to vCenter Server with External Platform Service Controller

When you upgrade a vSphere 5.5.x environment that has been set up for High Availability to vSphere 6.0, an internal error might occur during first boot phase in rare cases during upgrade of the first management node. Workaround: Retry the management node upgrade.

No support for upgrading vCenter Server replicated configurations in the release

When upgrading a vCenter Server configuration with replication between two Single Sign-On infrastructure nodes, if the primary infrastructure node becomes inaccessible, the replicated infrastructure node does not fail over. Workaround: None. Do not upgrade replicated vCenter Server configurations.

Linked Mode is not supported after upgrade of vCenter Server 5.x with embedded vCenter Single Sign-On if the vCenter Sign-On is not replicated before the upgrade

When upgrading vCenter Server 5.x instances with an embedded vCenter Single Sign-On, the installer automatically upgrades the configuration to the embedded 6.0 deployment model: vCenter Server with an embedded Platform Services Controller. VMware supports linking between vCenter Server 6.0 instances only when using the external Platform Services Controller deployment model. Since the upgrade does not change the Platform Services Controller's replication configuration, it will not preserve the Linked Mode relationship of the vCenter Server instances if their embedded vCenter Single Sign-On is not replicated. Workaround: None.

vCenter Server for Windows installer does not detect products that are past their end of life

During upgrade to vCenter Server for Windows 6.0, the installer does not detect products such as the VMware Converter application if its running on a VM or integrated with legacy vCenter Server. This might prevent a successful upgrade to vCenter Server for Windows 6.0. Workaround: Before starting the vCenter Server upgrade, remove VMware Converter or any other products on the vCenter Server machine that are past their end of life date.

vCenter Server Appliance upgrade fails when using a static IP address which is not DNS resolvable

Upgrading vCenter Server Appliance fails when the static IP address for latest vCenter Server Appliance in the Setup Temporary Network wizard is not DNS resolvable. Workaround: Use a static IP address which is DNS resolvable for vCenter Server Appliance in the Setup temporary Network wizard.

vCenter Server Appliance upgrade fails with an internal error during data export

vCenter Server Appliance upgrade fails at the data export phase with one of the following errors: Internal error occurs during export Cannot upload UpgradeRunner via ssh tunnel Workaround for Internal error occurs during export : Check whether the static IP address and DNS you entered in the Setup Temporary Network wizard of the vCenter Server Appliance upgrade interface are valid and belong to the same VLAN. Workaround for Cannot upload UpgradeRunner via ssh tunnel : Check whether the static IP address entered in the Setup Temporary Network wizard of the vCenter Server Appliance upgrade interface is the same as the source 5.x vCenter Server IP address.

vCenter Server Appliance upgrade process does not preserve the /etc/hosts file

The vCenter Server Appliance upgrade process does not migrate the source /etc/hosts file to the newly deployed vCenter Server Appliance. Workaround: Make a backup of the /etc/hosts file on another machine before the upgrade process and apply it to the newly deployed vCenter Server Appliance after the upgrade.

vCenter Server authentication error during upgrade

If your legacy vCenter Server SSL certificates are expired, the installer provides a general error message instead of a specific one: There is a problem authenticating in to the legacy vCenter Server using the credentials provided by the user. Resolution: Check if vCenter server is up and running. Double check provided vCenter Server credentials. Workaround: If you encounter an authentication error, you can check the vpxd.log at C:\ProgramData\VMware\VMware VirtualCenter\Logs to discover the exact reason for the upgrade error message. Before upgrading, check for SSL certificate validity. Replace any expired SSL certificates for vCenter Single Sign-On, vCenter Inventory Services, vCenter Server, vSphere Web Client, or any other solution.

vSphere Web Client does not display Single Sign-On group members from trusted domains after install or upgrade of vCenter Server

During deployment, if you add a domain to vCenter Single Sign-On as an identity source, you can then add users from the domain and the users from the trusted domains to groups in vCenter Single Sign-On. For example, you add the domain myDomain1.com as an identity source and it has a forest level trust with myDomain2.com, then you add the users from the trusted domain user1@myDomain2.com. After a user from myDomain2.com becomes a member of the Single Sign-On group, that user has the corresponding privileges. However, that user is not displayed in vSphere Web Client. Workaround: Use tools for managing standard Directory Services (Open LDAP or Active Directory) to examine the Single Sign-On domain and verify users are in the appropriate groups.

Unable to open vSphere Web Client from a server outside the domain of vCenter Server using the IP address

After upgrading vCenter Server, vSphere Web Client does not open from a server outside the domain of vCenter Server. Workaround: Make the hostname (fully qualified domain name) resolvable from outside network. Add the fully qualified domain name IP address mapping in %WINDIR%\System32\drivers\etc\hosts file.

vCenter Server Inventory 5.1.x appears empty after upgrading vCenter Single Sign-On to 6.0 and before upgrading vCenter Server

When logging in to the vSphere 5.1.x Web Client using Administrator@vsphere.local or admin@System-Domain after upgrading only the Single Sign-On service to 6.0, the vCenter Server count and inventory display appear empty if you have a 5.1.x environment with vCenter Server 5.1.x installed on one system and a 5.1.x Single Sign-On service installed on another system, and you upgrade only the Single Sign-On service. Using a 6.0 Single Sign-On service with 5.1.x vCenter Server, vSphere Web Client, and Inventory Services is not supported. Workaround: Before logging in to the Administrator@vsphere.local account or admin@System-Domain account, upgrade vCenter Server to version 6.0. The vSphere Web Client and Inventory Services are upgraded to version 6.0 during the vCenter Server upgrade.

vSphere Web Client displays an empty inventory after upgrade

The vSphere Web Client sometimes shows the inventory as empty when you log in using the domain user account after upgrade. This can happen when you re-install vCenter Server on the same machine with the same IP address or fully qualified domain name. Workaround: Unregister the service using the Invoke Method link. Access the CM Managed Object Browser using the following URL: https://VC_HOSTNAME/cm/mob. In the Methods table, select Search. In the CmSearchCriteria text box, enter the information for your vCenter Server to list the vCenter Server 5.5 instances.

<searchCriteria>

<serviceType>

<productId>com.vmware.cis</productId>

<typeId>urn:vc</typeId>

</serviceType>

</searchCriteria> Record each vCenter Server serviceId . Select UnregisterService. To delete the services, enter the corresponding serviceIDs from step 4 and click the Invoke Method link.

vSphere Web Client displays an empty inventory after upgrade of vCenter Single Sign-On and vCenter Server 5.1.x in Multisite mode

The vSphere Web Client sometimes shows the Inventory as empty when logging in to vSphere Web Client after a sequential upgrade of vCenter Single Sign-On and vCenter Server in Multisite mode from 5.1.x to 6.0. You might receive the error: No matching LinkedVcGroup found This issue occurs if there are duplicate vCenter Server registration entries in the lookup service prior to upgrading to 6.0, and if Component Manager does not remove the stalled 5.1 vCenter Server end points during the upgrade. Workaround: You can remove the duplicate entries by connecting to the Managed Object Browser. Log in into CM MOB: https://ip_addr/cm/mob using the Administrator@vsphere.local. In the Methods table, use Search. Find all service end points by entering empty searchCriteria as follows:

<searchCriteria>

</searchCriteria> Record each serviceId for the 5.1 instance. Select UnregisterService. Unregister the 5.1.x instance by the serviceid .

UpgradeRunner fails to launch

When a 5.x vCenter Server uses an unsupported database and you attempt to upgrade it to vCenter Server 6.0, the Upgrade Wizard fails with an error: Failed to launch UpgradeRunner. Please check the vminst.log and vcsUpgrade\UpgradeRunner.log files in the temp folder for more details. Workaround: Upgrade the database to a supported database version. If you are using Microsoft SQL, upgrade to Microsoft SQL Server 2012 or Microsoft SQL Server 2008 R2 SP2. If you are using Oracle, upgrade to Oracle12g.

Virtual SAN host alarm after vCenter Server 5.5 to vCenter Server Upgrade 6.0

A virtual SAN host vendor provider registration alarm appears after upgrading a vCenter Server 5.5 instance with vSAN clusters: Default alarm that is triggered when Virtual SAN host vendor provider registration or deregistration is unsuccessful Virtual SAN host vendor registration is successful by this time and the alarm is not meaningful. Workaround: Ignore the alarm message.

Relocation of hardware 3 VM from legacy ESX hosts to ESXi 6.0 fails

Registering and upgrading a virtual hardware version 3 VM is supported on the ESXi 6.0 release. Migrating a hardware version 3 VM from or to ESXi 6.0 is not supported. Attempts to migrate a hardware version 3 VM fail with an error message: The virtual machine version is not compatible with the version of the host x Workaround: Upgrade the hardware 3 VM to virtual hardware version 4 or later before performing a migration. Log in to vCenter Server through the vSphere Web Client. Register the hardware version 3 VM on the legacy ESXi server or ESXi 6.0 server. Right-click the VM and select All vCenter Actions. Select Compatibility. Select Upgrade VM Compatibility. Click Yes. Select Compatible with ESX 3.5 and later and click OK. After upgrading the VM, you can perform power operations and VM migrations.

You might view licensing related alarms that are not relevant to vSphere 6.0

In the Alarm Definitions list for a vCenter Server system, you might view the following licensing alarms that are not applicable for the vSphere 6.0 release. License error License user threshold monitoring License capacity monitoring Host flash capacity exceeds the licensed limit for Virtual SAN Workaround: Ignore the licensing alarms that are not applicable for vSphere 6.0.



Firefox does not support the new SmartCard authentication feature for user login

Firefox browser does not support vSphere Web Client user login using the new SmartCard authentication feature.

Firefox browser does not support vSphere Web Client user login using the new SmartCard authentication feature. Workaround: Use Internet Explorer or Google Chrome as your browser. Attempts to log in to Platform Services Controller using RSA SecurID authentication fails if the user name contains high-ASCII or non-ASCII characters

Platform Services Controller login using RSA SecurID authentication fails if the user name contains high-ASCII or non-ASCII characters. The RSA authentication manager requires a User ID, which must be a unique identifier. The length of the User ID must be 1 to 255 ASCII characters. Characters such as ampersand (&), percent (%), greater than (>), less than (<), and single quote (`) are not allowed. Workaround: Use a User ID that meets the requirements of the RSA authentication manager.

Platform Services Controller login using RSA SecurID authentication fails if the user name contains high-ASCII or non-ASCII characters. The RSA authentication manager requires a User ID, which must be a unique identifier. The length of the User ID must be 1 to 255 ASCII characters. Characters such as ampersand (&), percent (%), greater than (>), less than (<), and single quote (`) are not allowed. vSphere 5.5 legacy SSO port 7444 performs the vSphere Web Client authentication when SmartCard authentication is enabled

When SmartCard authentication is enabled, the vSphere 5.5 legacy SSO service port 7444 is used to perform the vSphere Web Client authentication to allow SmartCard authentication. As a result, the legacy port 7444 support to other vSphere Web Clients is lost. By default, SmartCard authentication is disabled. Workaround: To turn on and configure SmartCard authentication, upgrade all vCenter Servers to 6.0 Update 2, which connect to an upgraded PSC 6.0 Update 2.

When SmartCard authentication is enabled, the vSphere 5.5 legacy SSO service port 7444 is used to perform the vSphere Web Client authentication to allow SmartCard authentication. As a result, the legacy port 7444 support to other vSphere Web Clients is lost. After you upgrade the vSphere version to 6.0 Update 2 using load balanced HA, the option to configure SmartCard authentication in the load balanced configuration is not available

After you upgrade vSphere version to 6.0 Update 2 using load balanced HA, you cannot configure SmartCard authentication in the load balanced configuration. SmartCard configuration for non-load balanced upgrades is available. A fix will be provided in the near future. Workaround: None.

After you upgrade vSphere version to 6.0 Update 2 using load balanced HA, you cannot configure SmartCard authentication in the load balanced configuration. SmartCard configuration for non-load balanced upgrades is available. After upgrading to vSphere 6.0 Update 1b, importing the vIDM's Service Provider Metadata into vSphere SSO fails

VMware Identity Manager (vIDM) uses different endpoints for its LogoutRequest and LogoutResponse. vSphere SSO handles this by introducing a new attribute to record the LogoutResponse endpoint. This data is stored in the Directory Service and requires a schema update. The existing Directory Service schemas are not automatically updated during an upgrade from a previous vSphere 6.0 version to vSphere 6.0 Update 1b. Workaround: To manually update the Directory Service schema, perform the following steps: Stop the Directory Service. This also stops any dependent services. On Windows, use the Services MMC snap-in to stop VMware Directory Service. On a vCenter Server Appliance, open a shell session and execute the following: /opt/likewise/bin/lwsm stop vmdir Patch the Directory Service with the vSphere 6.0 Update 1b schema: On Windows, execute the following as an Administrator in the command prompt:

C:\Program Files\VMware\vCenter Server\vmdird\vmdird.exe -c -u -f C:\ProgramData\VMware\vCenterServer\cfg\vmdird\vmdirschema.ldif On vCenter Server Appliance, execute the following under a root shell session: /usr/lib/vmware-vmdir/sbin/vmdird -c -u -f /usr/lib/vmware-vmdir/share/config/vmdirschema.ldif Start the Directory Service and all dependent services that were automatically brought down, or reboot the system.

VMware Identity Manager (vIDM) uses different endpoints for its LogoutRequest and LogoutResponse. vSphere SSO handles this by introducing a new attribute to record the LogoutResponse endpoint. This data is stored in the Directory Service and requires a schema update. The existing Directory Service schemas are not automatically updated during an upgrade from a previous vSphere 6.0 version to vSphere 6.0 Update 1b. Unable to add third party CA cert into TRUSTED_ROOTS store through Platform Services Controller UI

The Platform Services Controller (PSC) UI does not provide an option to add third-party CA certificates into TRUSTED_ROOTS store and replace the machine SSL and solution user certificates signed with this third-party CA.

The Platform Services Controller (PSC) UI does not provide an option to add third-party CA certificates into store and replace the machine SSL and solution user certificates signed with this third-party CA.

Workaround: To resolve this issue, you will need to use certificate-manager CLI to import the third-party root CA before proceeding with replacing the certificates through the PSC UI.



SSLv3 protocol disabled by default on port 7444 in vCenter Server 6.0 Update 1

When you install vCenter Server 6.0 Update 1, the SSLv3 protocol is disabled on port 7444 by default. When you upgrade from an earlier release of vCenter Server to vCenter Server 6.0 Update 1, the SSLv3 protocol remains enabled on port 7444.

When you install vCenter Server 6.0 Update 1, the SSLv3 protocol is disabled on port 7444 by default. When you upgrade from an earlier release of vCenter Server to vCenter Server 6.0 Update 1, the SSLv3 protocol remains enabled on port 7444. Workaround: To disable SSLv3 on port 7444 see KB 2131310 Multiple roles for a user with Global Permissions on permissions page

An administrator gives Global Permissions to a user, and assigns a specific role to that user. If the administrator assigns another role on a specific object, both roles are shown in the vSphere Web Client if you select the object, click Manage , and click Permissions . The user has the correct set of privileges on the object, but both the inherited and the local privileges are shown, which is confusing. Workaround: None

An administrator gives Global Permissions to a user, and assigns a specific role to that user. If the administrator assigns another role on a specific object, both roles are shown in the vSphere Web Client if you select the object, click , and click . The user has the correct set of privileges on the object, but both the inherited and the local privileges are shown, which is confusing. Cannot connect to VM console after SSL certificate upgrade of ESXi host

A certificate validation error might result if you upgrade the SSL certificate that is used by an ESXi host, and you then attempt to connect to the VM console of any VM running when the certificate was replaced. This is because the old certificate is cached, and any new console connection is rejected due to the mismatch.

The console connection might still succeed, for example, if the old certificate can be validated through other means, but is not guaranteed to succeed. Existing virtual machine console connections are not affected, but you might see the problem if the console was running during the certificate replacement, was stopped, and was restarted. Workaround: Place the host in maintenance mode or suspend or power off all VMs. Only running VMs are affected. As a best practice, perform all SSL certificate upgrades after placing the host in maintenance mode.

Networking Issues

The VM MAC address conflict alarm remains triggered even when the MAC address conflict issue is resolved

The VM MAC address conflict alarm remains triggered or the alarm status is red, even when the MAC address conflict issue that triggers the alarm is resolved. Workaround: Manually acknowledge or clear the alarm after the MAC address conflict issue is rectified.

Disable the alarm if you do not wish to trigger the alarm.

Certain vSphere functionality does not support IPv6

You can enable IPv6 for all nodes and components except for the following features:



IPv6 addresses for ESXi hosts and vCenter Server that are not mapped to fully qualified domain names (FQDNs) on the DNS server.

Workaround: Use FQDNs or make sure the IPv6 addresses are mapped to FQDNs on the DNS servers for reverse name lookup.

Virtual volumes

PXE booting as a part of Auto Deploy and Host Profiles

Workaround: PXE boot an ESXi host over IPv4 and configure the host for IPv6 by using Host Profiles. Connection of ESXi hosts and the vCenter Server Appliance to Active Directory

Workaround: Use Active Directory over LDAP as an identity source in vCenter Single Sign-On. NFS 4.1 storage with Kerberos

Workaround: Use NFS 4.1 with AUTH_SYS. Authentication Proxy Connection of the vSphere Management Assistant and vSphere Command-Line Interface to Active Directory.

Workaround: Connect to Active Directory over LDAP. Use of the vSphere Client to enable IPv6 on vSphere features

Workaround: Use the vSphere Web Client to enable IPv6 for vSphere features.

You can enable IPv6 for all nodes and components except for the following features: In the vSphere Web Client, the direction of the traffic filtering and marking rules is inverted compared with vSphere Web Client 5.5

The direction of a traffic rule appears inverted in the vSphere Web Client in the following cases:

After you upgrade vSphere Web Client 5.5 to vSphere Web Client 6.0, the direction of existing traffic rules on a distributed switch is inverted. If you manually redefine traffic rules from a vSphere 5.5 environment into a vSphere 6.0 environment, the traffic rules are applied to traffic in the opposite direction. In vSphere Web Client 5.5, the meaning of "ingress" and "egress" in traffic marking rules is reversed compared with "ingress" and "egress" in the other features of distributed switches, such as traffic shaping, where the direction is determined with regard to the switch. For example, "ingress" in traffic rules stands for traffic leaving the switch while for the other features it stands for traffic entering the switch. The vSphere Web Client 6.0 inverts ingress and egress directions so that they match the meaning in the other distributed switch features. Workaround: If you manually redefine traffic rules from a vSphere 5.5 environment in a vSphere 6.0 environment, reverse the traffic direction of the rules.

The direction of a traffic rule appears inverted in the vSphere Web Client in the following cases:

Virtual Volumes Issues

Attempts to upload files directly to a virtual datastore fail

When you use the Upload the File to the Datastore option of the vSphere Web Client, the upload operation fails for a virtual datastore. Workaround: Virtual Volumes do not support uploading files directly to the virtual datastores. You must first create a folder on the virtual datastore, and then upload the files into the folder.

If you use VIM APIs to create a virtual disk on Virtual Volumes storage and do not to specify a value for the VirtualDisk.FlatVer2BackingInfo.thinProvisoned parameter, a thick provisioned disk is created

The default value for the VirtualDisk.FlatVer2BackingInfo.thinProvisoned parameter is false . If you leave this parameter unspecified, a thick provisioned virtual disk is created.

However, certain Virtual Volumes arrays might support only the thin provisioned disk type. On these arrays, virtual disk creation through VIM APIs might fail if you do not set the parameter to true . Workaround: Perform the applicable workaround: If you use VIM APIs to create virtual disks on Virtual Volumes storage, make sure to explicitly set the VirtualDisk.FlatVer2BackingInfo.thinProvisoned parameter to true . Use the vSphere Web Client to create virtual machines on virtual datastores. By default, the vSphere Web Client creates thin provisioned virtual disks.

Attempts to create a virtual machine might fail if you place a VM configuration file and virtual disk on different datastores, Virtual SAN and Virtual Volumes, and attach different storage policies

This problem might occur if you use the following datastore combinations for your VM configuration file and virtual disk placement at the VM creation time: Virtual SAN and Virtual Volumes, Virtual Volumes and Virtual SAN, Virtual Volumes and Virtual Volumes (with different storage policy support).

You might also experience problems when migrating a single virtual disk out of Virtual SAN VM onto Virtual Volumes datastore. Workaround: Create a virtual machine on one datastore, for example, Virtual SAN. Use the Edit Settings wizard of the vSphere Web Client to add a new virtual disk and place it to another datastore, for example, Virtual Volumes.

This problem might occur if you use the following datastore combinations for your VM configuration file and virtual disk placement at the VM creation time: Virtual SAN and Virtual Volumes, Virtual Volumes and Virtual SAN, Virtual Volumes and Virtual Volumes (with different storage policy support). You might also experience problems when migrating a single virtual disk out of Virtual SAN VM onto Virtual Volumes datastore. Virtual Volumes do not support Storage DRS

In this vSphere 6.0 release, Storage DRS ignores virtual datastores. Workaround: None.

General Storage Issues

Renamed tags appear as missing in the Edit VM Storage Policy wizard

A storage policy can include rules based on datastore tags. If you rename a tag, the storage policy that references this tag does not update the tag automatically, and shows it as missing. Workaround: Remove the tag marked as missing from the storage policy and then add the renamed tag. Reapply the storage policy to all out of date entities.

When a virtual disk is shared across different virtual machines, changes to the disk's storage policy on an individual virtual machine might not be reflected on other virtual machines

Consider the following example. In vSphere, create a virtual disk that is shared across different virtual machines, VM1 and VM2. Edit VM1 settings and assign a storage policy, for example SP1, to the shared virtual disk. You can then switch to VM2 and change the disk's storage policy from SP1 to SP2. However, though the change is shown for VM2, it might not be seen through VM1 settings. For VM1, the disk's storage policy incorrectly continues to be SP1. Workaround: If you need to change a VM storage policy for a virtual disk that is shared across different virtual machines, make sure to make your changes for all virtual machines through the VM Storage Policies interface.

Storage arrays present in the vSphere environment disappear from the database after you restart vCenter Server

After a restart, vCenter Server might take longer to rebuild its inventory. This delay might cause miscommunication between the Storage Monitoring Service (SMS) and VASA providers that represent storage arrays. As a result, VASA providers fail to report that arrays are available. Workaround: Restart the vSphere Profile-Driven Storage service.

You cannot install legacy vCenter Server plug-ins and extensions on vCenter Server 6.0

Due to a security-related change in vCenter Server 6.0, your attempts to install legacy extensions on vCenter Server 6.0 might fail. The extensions include those that were implemented by a third party against older versions of vCenter Server, such as version 5.5, 5.0, and so on. Workaround: vCenter Server does not maintain backward compatibility between major releases. Third parties must upgrade their vCenter Server plug-ins and extensions to a later version compatible with vCenter Server 6.0.

Icon that marks storage devices as flash or HDD is not updated in the Storage Devices view of the vSphere Web Client

You can navigate to ESXi host > Manage > Storage > Storage Devices view, and use an appropriate icon to mark a storage device as flash or HDD. When the task completes successfully, the icon is expected to change to its opposite. However, the icon is not updated correctly even when the task is successful. Workaround: Click Global Refresh button to update the icon.

OCSP URL setting points to the old URL even after it is set to null

The optional Online Certificate Status Protocol (OCSP) URL property for SmartCard authentication in the Platform Services Controller (PSC) configuration, cannot be removed or cleared after set without restarting the Identity management service. This is a limitation with Java security API. Workaround: On PSC appliance:

Restart the Identity Manager daemon service using the following command:

service vmware-sts-idmd restart On PSC Windows:

Restart the VM or the machine, as an IDM service restart requires the shutdown of other dependent services. If you change the previously set OCSP URL to a non-null value, the issue does not occur. The limitation is only for removing the optional setting for SmartCard authentication.

VMware Authentication Proxy supports insecure protocols and ciphers for connection to ESXi hosts

VMware Authentication Proxy uses IIS for hosting services, where insecure protocols are used to maintain connections with clients (ESXi host). Workaround: To resolve this issue, you need to disable insecure protocols such as SSLv3. See KB 2136184 for detailed steps.

VMware Authentication Proxy uses IIS for hosting services, where insecure protocols are used to maintain connections with clients (ESXi host). Remediation fails when applying a host profile from a stateful host to a host provisioned with Auto Deploy

When applying a host profile from a statefully deployed host to a host provisioned with Auto Deploy (stateless host) with no local storage, the remediation attempt fails with one of the following error messages: The vmhba device at PCI bus address sxxxxxxxx.xx is not present on your host. You must shut down and then insert a card into PCI slot yy. The type of card should exactly match the one in the reference host. No valid coredump partition found. Workaround: Disable the plug-in that is causing the issue (for example, the Device Alias Configuration or Core Dump Configuration) from the host profile, and then remediate the host profile.

Workaround: Disable the plug-in that is causing the issue (for example, the Device Alias Configuration or Core Dump Configuration) from the host profile, and then remediate the host profile.

Applying host profile with static IP to a host results in compliance error

If you extract a host profile from a host with a DHCP network configuration, and then edit the host profile to have a static IP address, a compliance error occurs with the following message when you apply it to another host: Number of IPv4 routes did not match. Workaround: Before extracting the host profile from the DHCP host, configure the host so that it has a static IP address.

vSphere Client Integration Plug-in is not recognized when you use browser proxy

The vSphere Client Integration Plugin is not recognized when vmware-localhost is in the proxy inclusions of the operating system and the browser.



Workaround:

Add vmware-localhost in the proxy exclusions of the operating system and the Mozilla Firefox browser. Enable the Bypass the proxy server for local addresses option in the browser settings.



The vSphere Client Integration Plugin is not recognized when vmware-localhost is in the proxy inclusions of the operating system and the browser. Workaround: In vSphere Web Client, the context menu of the Web page intermittently overrides the context menu of the Guest Operating System within the console

In vSphere Web Client, the context menu of the Web page intermittently overrides the context menu of the Guest Operating System within the console.



Workaround: Switch to full screen mode. To switch to full screen mode, click View Full screen at the top right corner of the console.





In vSphere Web Client, the context menu of the Web page intermittently overrides the context menu of the Guest Operating System within the console. Workaround: Switch to full screen mode. To switch to full screen mode, click at the top right corner of the console. Internet Explorer 10 does not support full screen view

When you start a console in vSphere Web Client from Internet Explorer 10, the View Full screen button does not support the full screen view.



Workaround: Use one of the following workarounds.

When you start a console in vSphere Web Client from Internet Explorer 10, the button does not support the full screen view. Workaround: Use one of the following workarounds. Use the latest version of Google Chrome or Firefox, or upgrade to Internet Explorer 11.



Upgrade Windows 8 to Windows 8.1, or Windows Server 2012 to Windows Server 2012 R2, where Internet Explorer 11 is available by default.

When vSphere Web Client 6.0 is used to move or copy a Virtual Machine Disk (VMDK) between folders, the descriptor is the only file that is moved or copied

When vSphere Web Client 6.0 is used to move or copy a Virtual Machine Disk (VMDK) between folders, the descriptor is the only file that is moved or copied. The flat file is retained in the source folder.



Workaround: None.





When vSphere Web Client 6.0 is used to move or copy a Virtual Machine Disk (VMDK) between folders, the descriptor is the only file that is moved or copied. The flat file is retained in the source folder. Workaround: None. If multiple Virtual Network Adapters (NICs) use the same gateway, connectivity problems might be seen on all NICs

If multiple Virtual Network Adapters (NICs) use the same gateway, connectivity on all the NICs might be affected due to kernel's Reverse Path filtering. The browser displays a connection failure error message.



Workaround: If there are two NICs, set the rp_filter value as 2 in the following locations:

/etc/sysctl.conf [net.ipv4.conf.all.rp_filter] and [net.ipv4.conf.default.rp_filter] . /proc/sys/net/ipv4/conf/default/rp_filter and /proc/sys/net/ipv4/conf/all/rp_filter .



If multiple Virtual Network Adapters (NICs) use the same gateway, connectivity on all the NICs might be affected due to kernel's Reverse Path filtering. The browser displays a connection failure error message. Workaround: If there are two NICs, set the rp_filter value as in the following locations: In vCenter Server, browser cache might allow a user to login using the SmartCard Authentication of a prior user

In vCenter Server, browser cache might allow a user to login using the SmartCard Authentication of a prior user. During the next consecutive login, the login page suggests to restart the browser, and clear the cache. However, with Google Chrome, the session cookie introduced to resolve this might still be active after the browser is closed, and prevents the login with a Close the browser warning.

If you use Google Chrome for vSphere SmartCard Authentication, you must change the browser settings. Note: This issue occurs only in Google Chrome when the required browser setting is not selected. Workaround: Following are the available workarounds:

Use the following steps to change the cookie settings of your browser: Click Settings > Show advanced settings > Privacy > Content settings . Under Cookies , select Keep local data only until you quit your browser .

In vCenter Server, browser cache might allow a user to login using the SmartCard Authentication of a prior user. During the next consecutive login, the login page suggests to restart the browser, and clear the cache. However, with Google Chrome, the session cookie introduced to resolve this might still be active after the browser is closed, and prevents the login with a warning. If you use Google Chrome for vSphere SmartCard Authentication, you must change the browser settings. Workaround: Following are the available workarounds: Navigate to browser Settings > On Start up, and select Open New Tab Page.

VMware vCenter Server Appliance displays incorrect SSO information in the Virtual Appliance Management Interface

When you are using a vCenter Server Appliance connected to an external Platform Service Controller, the vCenter Server Appliance incorrectly displays SSO as not initialized in the Virtual Appliance Management Interface.

For more information, refer KB 2140849.



Workaround: None.





Attempts to repoint VMware vCenter Server 6.0 between sites within your vSphere domain fail

In a multi site environment, attempts to repoint a vCenter Server 6.0 instance to an external Platform Services Controller in a different site, might fail.

For more information, refer KB 2131191.



Workaround: See KB 2131191 for more information about using the new CMSSO-Util CLI to move your vCenter Server 6.0.





When you use vCenter Server Appliance Management Interface for minor upgrade or patching, the Web session might time out, and user does not get a Reboot is required alert message

When you use the vCenter Server Appliance Management Interface for a minor upgrade or patching process, the Web session might time out. The user does not receive the Reboot is required alert message, although the minor upgrade or patching process is successful.

Reboot the vCenter Server Appliance, after the log file /storage/log/vmware/applmgmt/software-packages.log is updated with the following message:

Packages upgraded successfully, Reboot is required to complete the installation.



Workaround: None.

Keyboard input into text boxes fails when you use vSphere Web Client with a 64-bit Firefox browser

When you use vSphere Web Client with a 64-bit Mozilla Firefox browser, keyboard input into the text boxes fails. Workaround: Use an alternative supported browser, or install a 32-bit version of the Mozilla Firefox browser. Supported Windows browsers are: Microsoft Internet Explorer 10.0.19 and later.

Google Chrome 39 and later (32-bit only).

Mozilla Firefox 34 and later (32-bit only).

Changing the IP address of vCenter Server through the vCenter Server Appliance Management Interface causes incorrect start of services

Changing the IP address, and not the Primary Network Identifier (PNID) of vCenter Server Appliance through the vCenter Server Appliance Management Interface, causes failures across multiple services that can be seen in vSphere Web Client. The vSphere Web Client displays an error message similar to the following:

A server error occurred.

[500] SSO error: Cannot connect to the VMware Component Manager https://FQDN_of_vCenter/cm/sdk?hostid=2752b8d1-e68b-49f8-8c92-ce3f042bf487

Check the vSphere Web Client server logs for details.



Workaround: Update the IP address in the Hosts file ( /etc/hosts ) on vCenter Server Appliance, so that it reflects the new IP address of the system.

When Ipv6 is disabled through DCUI on a vCenter Server Appliance 6.0, errors are seen in the vSphere Web Client network settings

Disabling Ipv6 through DCUI on vCenter Server Appliance 6.0 causes the following:

vmware-perfcharts service does not start: IPV6 is disabled on the vCenter Server Appliance, and affects the service start. For more information, see KB 2118223.

service does not start: IPV6 is disabled on the vCenter Server Appliance, and affects the service start. For more information, see KB 2118223. Errors in the vSphere Web Client network settings. Workaround: Start the vmware-perfcharts service. See KB 2118223.

To fix the network setting error in vSphere Web Client , enable IPv6 from the DCUI console.



Updating vCenter Server Appliance from a previous 6.0.x version might affect the default update settings in the vCenter Server Appliance Management Interface

In the vCenter Server Appliance Management Interface, the default update settings' option Use default repository is not selected, when we update vCenter Server Appliance from a previous 6.0.x version.



Workaround: Select the Repository settings as per the requirement.

The vCenter Server Appliance Management Interface (VAMI) service might fail after applying a third party patch on VMware vCenter Appliance

After applying a third party patch (TP) on a VMware vCenter Appliance version 6.0 GA or 6.0.0a or 6.0.0b, the vCenter Server Appliance Management Interface (VAMI) service might fail to start.



Workaround: Apply full patch.

Defined permissions behave differently in vSphere Client and Web Client

Moving VMs between the folders is disabled in the Web Client when permission are defined only at the folder level and displays an error similar to the following:

This action is not available for any of the selected objects at this time

Workaround: None

Content for Edit Time Synchronization Settings in VAMI UI dialog fails to load

Content for Edit Time Synchronization Settings for non-English in VAMI UI dialog fails to load and drop-down dialog appears empty.



Workaround: Use the ESX documented CLI option to edit Time Synchronization:

/usr/sbin/vpxd_servicecfg timesync

Tag operations allowed for users without assigned permission

In the vSphere Web Client, you can manage user privileges for tags and categories. For example, you can deny permission for common tag operations for tag objects and for specific users. However, the user who was denied permission continues to see the tag and can perform various operation, including deleting the object. Workaround: None.

Not all services restart after you stop multiple services in vCenter Server for Window

After you stop multiple services in vCenter Server for Windows, some services do not restart after 20 minutes. The services that do not restart might include PostgreSQL, invsvc, and vpxd. Workaround: Run the service-control command to start the services.

IIAD generates log bundles in different locations

Interprocess Interrogation and Activation Daemon (IIAD) generates the log bundles for vCenter Server during service remediation if the service does not respond to API calls. These log bundles can be found in the following locations: For vCenter Server Appliance: /storage/core

For vCenter Server for Windows: VMWARE_DATA_DIR/core (for example, C:\ProgramData\VMware\vCenterServer\data\core ) Workaround: None.

The Alarm Definition list contain deprecated alarm definitions

In the vSphere Web Client, if you click on a vCenter Server instance, then click the Manage tab, and click Alarm Definitions. You can see the Host service console swap rates alarm in the Alarms Definition list. The alarm is deprecated, because vSphere 6.0 supports ESXi and not the service console. Workaround: none.

When you export customized performance charts in .jpeg or .png format, part of the legend is missing

When you work with multiple counters in the advanced performance charts, if a scroll bar appears, the exported image is truncated. As a result, you cannot see all counters in the legend. Workaround: Scroll manually and export the diagram when you can see the counters you need on the screen.

Some anti-virus software detect an executable from the vCenter Client Integrations Plug-in as a threat

When you attempt to install the vCenter Client Integrations Plug-in, your anti-virus software might display a warning about a Trojan Horse threat. This occurs because one of the Client Integration Plug-in executable components has the same name as a Trojan Horse. The name of the component is Bifrost.

This issue only occurs if you access vSphere Web Client from a Windows system. Workaround: Get the Bifrost component of the Client Integration Plug-in back into its original location. Depending on the behavior of your antivirus software, you can do that by performing one of the listed workarounds: Ignore the warning of your anti-virus software and proceed with installing the Client Integration Plug-in.

On the Windows system, navigate to the directory where your anti-virus software places quarantined files and copy the bifrost.exe to its former location C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\bifrost

Attempts to assign a tag to vCenter Server objects fail after you install or upgrade to vCenter Server 6.0

After you install or upgrade to vCenter Server 6.0, you cannot assign tags to an object if you are logged in as a domain user. Workaround: Log in to vSphere Web Client as administrator@vsphere.local to assign tags on vCenter Server objects.

The hyperlinks of target objects of a task are inactive in the Recent Tasks pane at the bottom of the vSphere Web Client

When you perform tasks in vSphere Web Client, the target object of the task is displayed in the Recent Tasks pane with a hyperlink, which you can use to directly navigate to the target object after the task completes. In case you use Recent Tasks pane at the bottom of the page of vSphere Web Client, the hyperlinks are inactive and you cannot navigate to the target object of the task. Workaround: Use the Recent Tasks as a side-pane, or manually navigate to the target object from the object navigator.

You cannot isolate a vCenter Server system from a Linked Mode group

After you join vCenter Server systems to form a Linked Mode group, you cannot isolate a vCenter Server system from the Linked Mode group. All of the vCenter Server systems appear as linked in the vSphere Web Client. Workaround: None.

You cannot update and reset the data for the hardware sensors and reset the system event logs for an ESXi host in the vSphere Web Client

When you navigate to an ESXi host in the vSphere Web Client, click the Hardware status tab, and under CIM data select Sensors or Alerts and warnings. When you try to update the displayed information or clear the collected sensors data, the operations fail. When you select System event log and attempt to clear the listed event logs or update the pane with the latest logged events for the host hardware sensors, the operations fail too. Workaround: None.

You cannot upload sysprep files in the vCenter Server Appliance by using the vSphere Web Client

In earlier vSphere releases, you could upload a sysprep file to the vCenter Server Appliance by using the vCenter Server Appliance Web console. With vSphere 6.0 the vCenter Server Appliance Web console is deprecated and you cannot upload the sysprep files. Workaround: To manually upload sysprep files, enable the Bash shell of the vCenter Server Appliance and upload the files manually. For information about enabling the vCenter Server Appliance Bash shell, see the vCenter Server Appliance Configuration documentation.

On an OS X client computer, attempts to connect USB devices to a virtual machine in the vSphere Web Client by using Mozilla Firefox version 23.0 or later fail with an error message

After installing the Client Integration Plug-in on your OS X client computer, log in to the vSphere Web Client by using Mozilla Firefox version 23.0 or later. Add a USB Controller to a powered on virtual machine and connect a USB device to the client computer. The attempt to add the USB passthrough device from the OS X client computer to the virtual machine results in the error message:



An internal error has occurred. Error #1132. Reloading the client is recommended...



The Mixed Active Content preference of Mozilla Firefox 23.0 and later is enabled by default, which blocks the communication between the vSphere Web Client and the browser. Workaround: Change the default settings of the security.mixed_content.block_active_content preference from the configuration editor of Mozilla Firefox. In the address bar of Mozilla Firefox version 23.0 or later on your OS X client computer, type about:config and press Enter. On the warning dialog that appears, click I'll be careful, I promise. In the Search text box, enter security.mixed_content.block_active_content to filter the list of the available browser preferences. Double-click on the security.mixed_content.block_active_content preference to change its value to false . Log in to the vSphere Web Client by using Mozilla Firefox 23.0 or later and add the connected USB device from the OS X client computer to the powered on virtual machine.

Attempts to edit the settings, restart, and stop a node with vCenter Server hosted on a Windows machine from the System Configuration page of the vSphere Web Client fail with an error message

Log in to a vCenter Server instance on a Windows host machine by using the vSphere Web Client. From the vSphere Web Client Home page, click System Configuration and click Nodes. Select a node with vCenter Server hosted on a Windows machine, and from the Actions drop-down menu, click Edit Settings, Reboot, or Power Off. The operations fail with an error message similar to the following: An internal error has occurred - Error #1009 . To close the error message, click Cancel. You must use the System Configuration page to edit the settings, restart, and power off only vCenter Server in the vCenter Server Appliance. Workaround: You are not allowed to configure, restart, and power off a node with vCenter Server hosted on a Windows machine from the System Configuration page of the vSphere Web Client. For a vCenter Server system on a Windows host machine, use the Windows interface.

Attempts to configure and view information about the vCenter Server Appliance by using the System Configuration page in the vSphere Web Client fail with errors

Log in to the vCenter Server instance in the vCenter Server Appliance with a user who is in a custom-named (different from the default vsphere.local) Single Sign-On domain by using the vSphere Web Client. On the vSphere Web Client Home page, click System Configuration and under System Configuration select Nodes. If you attempt to edit the settings, restart or power off a node of the vCenter Server Appliance, the operation fails with one of the following errors: An internal error has occurred - Error # 1009 and Not authorized to use this API . If you click the Summary, Monitor, or Manage tabs, some information about the appliance might not be displayed. Workaround: Deploy the vCenter Server Appliance only by using the default Single Sign-On domain: vsphere.local.

In a mixed environment that consists of vCenter Server 5.5.x and 6.0 systems, you cannot use the System Configuration page of the vSphere Web Client to view, manage, and configure vCenter Server 5.5.x instances

If you have a mixed environment that consists of vCenter Server 5.5.x and 6.0 instances, log in to your system by using the vSphere Web Client. On the vSphere Web Client Home page, click System Configuration and select the Objects tab. You can view, configure, and manage only vCenter Server 6.0.

To configure and manage the vCenter Server Appliance version 5.5.x, you can use the VMware vCenter Server Appliance Web Console. To configure and manage the vCenter Server 5.5.x instances that run on a Windows host machine, you can use the Windows interface. Workaround: None.

Adding or removing datastores might fail with an error during host configuration after vCenter Server installation or upgrade

When attempting to add or remove datastores on a host, the operation might fail with an error. This is due to a problem with retrieving host configuration information. Workaround: Remove and restore the affected host from the inventory before proceeding to configure the datastore.

Health status messages for some services might not be displayed in the vSphere Web Client

