VMware vsphere 6.0 Upgrade Known Issues

Official links

Known Issues

Known issues are grouped into the following categories. Installation Issue upgrade issue License vcenter single SIGN-ON and certificate management issues network connectivity issues storage issues Server configuration Issues vcenter Server, vsphere Web client, and vsphere client issues virtual Computer Management issues VMware HA and Fault tolerance problem client operating system problem supported hardware problems Auto Deploy and Image Builder problem installation problem

Vcenter Server for Windows installation issues

If the Administrator account password for Platform Services Controller contains non-ASCII characters or high ASCII characters, Windows installer for vcenter Server will stop
During installation, you cannot specify a Platform Services Controller administrator password that contains non-ASCII characters or high ASCII characters, but you can change this password after installation. If you then install the Vcenter Server system and connect the system to Platform Services Controller, the installation will fail.

Workaround: Configure the Platform Services Controller to use passwords that meet the following requirements:

Contains at least 8 characters, but no more than 20 characters

Contains at least 1 uppercase characters

Contains at least 1 lowercase characters

Contains at least 1 digits

Contains at least 1 special characters, that is, any character other than 0-9, A-Z, and A-Z

Contains only the visible ASCII characters (for example, no spaces are used)

If you uninstall Vcenter Server, the embedded PostgreSQL database will be removed
If you uninstall Vcenter Server from a Microsoft Windows virtual machine or a physical host, the embedded PostgreSQL database will also unload, and all data stored in this database will be lost.

Workaround: To prevent data loss in the database, back up the PostgreSQL database, and then restore it.

If you create a DSN using the database server alias, the vcenter server installation will fail
If you use a database server alias to create a DSN, the operation of installing Vcenter server through an external Microsoft SQL database will fail. The following error occurred during the installation of the Inventory Service: Error starting INVSVC (an error occured while starting invsvc).

Workaround: Use the IP address or host name of the database server to create the DSN.

After you install VMware Tools on Windows 8 or Windows Server 2012, you may not be able to use the syntax command to start Telnet
After installing VMware Tools on a Windows 8 or Windows Server 2012 client operating system, the default host application is set to VMware tools. You cannot use the start telnet://xx.xx.xx.xx command to open telnet. The following error message is displayed: Ensure that the configuration of the virtual machine allows the client to open the host application (make sure the virtual machine ' s configuration allows the guest to open host application s).

Workaround: At the Windows command prompt, run cmd->telnet to open the Telnet interactive message, and then start the Telnet session.

If the user name contains high ASCII characters or non-ASCII characters, you cannot use SQL Server with Windows integrated authentication to install Vcenter server
If the user name used contains local high ASCII characters or non-ASCII characters, the installation of Vcenter server with SQL Server with Windows Integrated authentication will fail. An error occurred while performing a security operation.

WORKAROUND: Use a username that contains only ASCII characters.

If the password contains high ASCII characters or non-ASCII characters, you cannot use SQL Server with Windows integrated authentication to install Vcenter server
If the password you use contains local high ASCII characters or non-ASCII characters, the installation of Vcenter server with SQL Server with Windows Integrated authentication will fail. An error occurred while starting the INVSVC service.

WORKAROUND: Use a password that contains only ASCII characters.

If you set vcenter server to use an external database from Vcenter Server Setup, you may not be able to select a system DSN
If Vcenter server is configured to use an external SQL database from Vcenter Server Setup, the System DSN configured through the SQL Server driver will not appear in the list of available DSNs.

WORKAROUND: When you configure the system DSN for an external SQL Server database, use SQL Server Native Client.

If the IPV4 stack is unloaded, the VMware vcenter Server 6.0.0 installation may fail
If the IPV4 stack is unloaded, the VMware vcenter Server 6.0.0 installation may fail when you try to start Vmwareafdservice. The following error message is displayed:

Error starting "Vmwareafdservice" service (an error occurred while starting service ' Vmwareafdservice ')

Unable to clean VKS binaries, error: 2

Search for these symptoms in the VMware knowledge Base to understand any known issues and possible solutions.

If you cannot find any workaround, gather the support package and open the support request (Failed to clean up vks binaries, error:2 please search this symptoms in the VMware knowledge Base for any known issues and possible workarounds. If None can is found, please collect a support bundle and open a support request).

Vcsservicemanager Component installation failed, error code "1603" displayed. Please check the log for more information (installation of component Vcsservicemanager failed with error code ' 1603 '). Check the logs for more details).

WORKAROUND: Ensure that the IPV4 stack is installed before installing VMware vcenter Server 6.0.0. If you run the netsh interface IPv4 show interfaces command, a message appears: This request is not supported. (The request is not supported.), the IPV4 stack is uninstalled and should be reinstalled. To reinstall the IPV4 stack, run the netsh interface ipv4 install command, and reboot the computer.

The vcenter server installation or uninstall process on the Windows Server 2008 R1 SP2 may fail or stop responding
Windows Server 2008 R1 SP2 is having problems processing multiple packages. Because of these problems, the vcenter Server installer may stop responding. Or, if you try to install and uninstall Vcenter Server several times, this process may fail.

Workaround: Apply the hotfix in Microsoft Knowledge Base article 981669, which fixes Windows Installer issues.

Operation may fail while attempting to uninstall Platform Services Controller
If you attempt to uninstall Platform Services Controller with one or more associated active vcenter Server instances, the operation may fail with an error message installation interrupted (Setup interrupted). There is no clear message that the problem is due to a vcenter Server instance registered with the Platform Services Controller.

Workaround: Before uninstalling Platform services Controller, first uninstall all vcenter Server instances associated with the Platform services Controller.

If the time offset between the computer in which Vcenter server is installed and the Platform Services Controller is 3 minutes or longer, the vcenter Server installation may fail
If the time between the computer in which Vcenter server is installed is not synchronized with the Platform Services Controller, the installation of Vcenter server may fail. When the time difference exceeds 3 seconds, the wizard displays the time difference, in seconds.
If the time offset is between 3 seconds and 2 minutes, a message is displayed to tell you the time difference displayed. You can close this information dialog box and continue with the installation. If the time offset is between 2 minutes and 4 minutes, a warning message is displayed about the significant time difference. If the time offset exceeds 4 minutes, the installation cannot continue.

WORKAROUND: If you see a warning message about the time offset between 2 minutes and 4 minutes, stop the vcenter Server installation and synchronize the computer where you want to install Vcenter server with Platform Services Controller Minutes. Run the vcenter Server setup again.

If the system name input (FQDN or IP address) does not exactly match the Platform Services Controller input to Fqdn/fqdn or IP/IP, the vcenter Server installation will fail
If the FQDN or IP address is used when installing Platform services Controller, vcenter Server input should match the Platform Services Controller input. If the FQDN is provided when installing Platform services Controller, you must provide vcenter Service when registering Platform Server in this Platform services Controller The FQDN of the S Controller. If you are providing an IP address when you install Platform services Controller, you must provide vcenter when you register Platform Server in this Platform services Controller Servic ES Controller IP address. Otherwise, the vcenter Server installation will fail on the first boot.

Workaround: Make sure that vcenter Server and Platform Services Controller input always match.

Vcenter Server installation that executes in a pure IPV6 environment may fail without full DNS support
If you do not have full DNS support, the attempt to install vcenter Server in a pure IPV6 environment may fail. This is because the Platform Services Controller installer obtains the computer name by reverse lookup.

WORKAROUND: If you do not have full DNS support, you must ensure that you can perform forward and reverse lookups in vcenter Server with embedded Platform Services Controller deployment.

You cannot uninstall vcenter Server for Windows by right-clicking the Windows Installer package and choosing Uninstall
You can uninstall Vcenter Server for Windows through 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 then choose Uninstall, no messages are displayed. If you right-click the vcenter Server for Windows installer again and then choose Uninstall, you receive a message that prompts you that the product has been uninstalled.

Workaround: Uninstall vcenter Server for Windows by using Windows Add/Remove Programs.

Vcenter Server for Windows does not support user data source name (DSN) for external databases
Vcenter Server for Windows installation only supports system DSN. If you add a User DSN, this DSN does not appear on the database Configuration page of vcenter Server for Windows.

WORKAROUND: When you install vcenter Server for Windows, add a system DSN to the external database.

If you are using a custom username service account that contains non-ASCII characters or high ASCII characters, you cannot install vcenter Server for Windows
The vcenter server for Windows installer cannot configure the Vcenter Server service account if you are using the user logon operating system defined by a custom account policy and the user name contains non-ASCII characters or high ASCII characters.

Workaround: The custom user account that you use when you log on can only contain ASCII characters.

Uninstalling or canceling the installation of vcenter Server for Windows may not always erase all directories and files in the user data directory or installation directory
If you try to uninstall or cancel the installation of Vcenter Server for Windows, you may not be able to completely remove the user data directories or C:\Program from the system from the C:\ProgramData\VMware\vCenterServer before the service starts The installation directory under Files\vmware\vcenterserver. This may affect future vcenter Server for Windows installation attempts.

Workaround: Reboot the computer before attempting a new installation again.

No logs were generated after running Vc-support.bat
If the operating system logon username contains high ASCII characters or non-ASCII characters, an error occurs when the log is generated by running the C:\Program files\vmware\vcenter server\bin\vc-support.bat command. And no log is generated.

Workaround: Run the C:\Program files\vmware\vcenter server\bin\vc-support.bat command after you log on to the operating system using a username that contains only ASCII characters.

If you add a service account that contains a special character @ or \, the vcenter Server installation will fail
When you install Vcenter Server, you can specify a service account instead of using the default Windows Local System account. If the selected account name contains a special character @ or \, the installation may fail and generate the VPXD first boot error.

Workaround: When installing vcenter Server, create a service account that does not contain a special character @ or \.

The first boot script will fail during the deployment of vcenter Server with external Platform Services Controller
When you try to deploy a vcenter Server with external Platform services Controller, the first boot fails when you enter an IP address or host name for the Platform services Controller during deployment.

Workaround: Enter the same system network name that is used when deploying Platform Services Controller.

Vcenter Server Appliance Deployment issues

The URL on the last page of the new Vcenter Server Appliance Deployment Wizard may not start vsphere Web Client
If you have deployed a vcenter Server appliance with external Platform services Controller and have configured the F5 services Platform behind the Controller load balancer, click VCe After the URL on the last page of the Nter Server Appliance Deployment Wizard, the vsphere Web Client interface is not displayed and the following exceptions occur:
HTTP status 400-error request, unable to respond to the request published to/saml2/ssossl/(HTTP status 400-badrequest, not able to respond to the request posted to /saml2/ssossl/)

Workaround: Refresh the Web page.

If you have attempted to use an external Oracle database in a previous deployment, you cannot deploy the vcenter Server appliance that uses the database
The Vcenter Server Appliance installer does not allow you to deploy a vcenter server appliance that has an external Oracle database that was used in a previous vcenter Server appliance deployment, and does not provide for reuse or The option to delete the database. You will receive an error message: The vcenter Server database is locked. The other Vcenter Server service is using this database and must be stopped (the Vcenter server database is locked. Another vcenter Server Service is using this database and must to be stopped). This problem can occur even if the vcenter Server appliance that uses the database has been shut down or removed from the ESXi host.

WORKAROUND: Use a new Oracle database instance, or choose to use an embedded database.

Vcenter Server Appliance installation failed while connecting to external Platform Services Controller
If an existing Platform service Controller is not synchronized with the ESXi host or NTP server (depending on the vcenter Server appliance Time configuration setting), there is an external Platform services Co Ntroller vcenter Server Appliance installation may fail. No warning message will be displayed during the Vcenter Server Appliance installation to report this time offset.

WORKAROUND: Synchronize the deployed Platform Services Controller, the ESXi host in which vcenter Server appliance is deployed, or the NT that will be used by Vcenter Server appliance after installation P server between the clocks.

If you restart the client operating system for Vcenter Server Appliance, the VPXD service may not start
When deploying Vcenter Server appliance, you can determine whether to use a time synchronization based on VMware Tools or an NTP server. If you set the Vcenter Server appliance to use time synchronization based on an NTP server, the client operating system of Vcenter Server appliance synchronizes with the NTP server. If the host deploying Vcenter Server appliance is not configured to use the same NTP server, or if the time of the ESXi host differs from the time of the Vcenter Server Appliance client operating system, restart the Vcenter When Server appliance, the NTP daemon starts early and sets the correct time. However, the VMware Tools service starts after the NTP daemon starts and sets the vcenter Server appliance system time to the host system time. The VPXD service has attempted to start and fail before the NTP daemon corrects the time again.

Workaround: Set the ESXi host to use the same NTP server as the vcenter Server appliance for time synchronization, and then deploy Vcenter Server appliance.

Unable to enter IPV6 address for ESXi host in the Vcenter Server Appliance Deployment Wizard
The Vcenter Server Appliance Deployment Wizard cannot connect to the ESXi host using the IPV6 address to deploy Vcenter Server appliance.

Workaround: Connect to the ESXi host using the FQDN.

If multiple DNS servers are available, the Vcenter Server Appliance script Installer will fail
If you provide multiple DNS servers during the installation process, the Vcenter Server Appliance script installation will fail.

Workaround: Use only one DNS server at a time. After the installation is complete, you can add more than one DNS server.

There are no preflight features available for the network settings that you entered in the Network Configuration page, which may cause the first boot error
There are no preflight features available to ensure that the values you enter in a text box, such as a network address, subnet mask, gateway, network DNS server, system name (FQDN, or IP), are valid. Therefore, if you enter an error value in either of these fields, the first boot error may occur. In addition, there is no preflight feature to ensure that the current FQDN used by the DHCP option is already in use.

Workaround: Make sure that you provide a valid value for each network setting. These settings are static options (network address, subnet mask, gateway, network DNS server, system name (FQDN or IP)), and DHCP options: FQDN (optional).

The user interface installer for vcenter Server appliance may require that the client integration plug-in be run. This hint may vary depending on the type of browser
When you start vcenter Server Appliance Setup, the tool may require that you start an application.

Workaround: If prompted when you open the Vcenter Server Appliance Script Installer, follow the instructions for each browser:

Google Chrome. Allows Setup to start this application.

Mozilla Firefox. Select Csd.exe and click OK.

Internet Explorer. Click Allow.

Vcenter Server Appliance Scripting Installer does not support custom HTTPS port numbers for interacting with the Vcenter server instance
Center Server 6.0 supports the customization of HTTPS ports. When you connect the vcenter Server appliance to vcenter server, you need to connect to Vcenter server using this port. Currently, the port cannot be customized in the Vcenter Server appliance Scripting Installer.

Workaround: To use the custom HTTPS port, install vcenter Server and Platform Services Controller using the HTML5 user interface installer.

Vcenter Server Appliance Scripting Installer allows installation with less than GB of free disk space (below minimum requirements)
When you install vcenter Server appliance with a scripted installer, the tool installs the software on a host that has less than GB of data storage free space. Setup continues to execute, but vcenter Server appliance may not be able to start the virtual machine.

WORKAROUND: Ensure that the ESXi host has at least GB of free space.

Help features are not available when installing Help.war files
File Help.war is downloaded as a root file, so you can cause permissions errors when you try to install the file. /pickup the following files have owner Vsphere-client and group users for use by the Java virtual machine.

Workaround: Perform the following steps:

Download the file Help.war to the/usr/lib/vmware-virgo folder in Vcenter Server appliance.

Change it to: Owner Vsphere-client and group users:
Chown vsphere-client Help.war
CHGRP Users Help.war

Change your account to vsphere-client.
If you are still performing a copy operation using the root account, change the owner to root again.
Su vsphere-client

Verify that the server is already running and copy the Help.war to/usr/lib/vmware-virgo/server/pickup. If you start or restart the server after you copy Help.war to/pickup, the Help feature will not work because/pickup will be emptied each time it is started.

On any Windows operating system, if vcsa-setup.html is refreshed in the Firefox browser, a blank banner message may be displayed when the client integration plug-in is allowed to run
Refreshing the vcsa-setup.html file may cause a blank banner to appear at the top of the Firefox browser. This is a matter of intermittent. A blank banner is displayed when the client integration plug-in is allowed to run on the browser. For example, the VMWARE-CSD process is allowed to run on Firefox.

WORKAROUND: When you first allow the VMWARE-CSD process to run on Firefox, select Remember my options for the VMWARE-CSD link, and then refresh the vcsa-setup.html file. This prevents you from refreshing the Vcsa-setup.h