11-05-2021

Vmware Vcenter Server 41 Iso Download

Download the zip file for vCenter Server from the VMware product page at The installer filename is VMware-VIMSetup-xx-4.1.0-yyyyyy. Jul 12, 2010 - Get VMware vSphere Hypervisor 4.0 for free and get live migration features in a bare-metal hypervisor. Download VMware ESXi 4.1. Download the VMware vCenter Server Appliance 6.7 ISO from VMware downloads: v6.7.0. Mount the ISO on your computer. The VCSA 6.7 installer is compatible with Mac, Linux, and Windows. Browse to the corresponding directory for your operating system, e.g. Vcsa-ui-installer win32. Right click Installer and select Run as administrator. The iso is usually called - VMware-VIM-all-6.5.0-8307201.iso Source VMware vCenter Server and modules for Windows Installer for VMware vCenter Server, VMware Platform Services Controller, VMware vSphere Update Manager, Update Manager Download Service (UMDS) and other vCenter Server-related modules. Sep 30, 2013 - This is Dell Customized Image of VMware ESXi 4.1 Update 3 Installable Edition. For detailed instructions to install and use Dell OpenManage Server.

vCenter Server 6.0 Update 3g | 26 JUL 2018 | ISO Build 9146214

vCenter Server Appliance 6.0 Update 3g | 26 JUL 2018 | ISO Build 9146214

vCenter Server 6.0 Update 3g on vCenter Server Appliance Build 9109104

vCenter Server 6.0 Update 3g on Windows Build 9109103

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

Pivotal tc Server replacement: Pivotal tc Server is now replaced with Tomcat 8.5.24 and Tomcat 8.5.23.
Updates to time zones in the Linux guest operating system customization: vCenter Server Linux guest operating system customization supports latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Linux guest operating systems, see the Time Zone Database by the Internet Assigned Numbers Authority (IANA).
Updates to time zones in the Windows guest operating system customization: vCenter Server Windows guest operating systems customization supports the latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Windows guest operating systems, see the Microsoft Knowledge Base article 3182203, Microsoft Knowledge Base article 4015193 and Microsoft Knowledge Base article 4012864.
TLS support: vCenter Server 6.0 Update 3g supports TLS version 1.2 for encrypted connection to Microsoft SQL Server. For more information, see VMware knowledge base article 2149745.
External database support: vCenter Server 6.0 Update 3g supports the Microsoft SQL Server 2014 Service Pack 2, SQL Server 2016, SQL 2016 Service Pack 1 and SQL Server 2012 Service Pack 4.

Upgrade Notes for This Release

Important: Upgrade and migration paths from vCenter Server 6.0 Update 3g deployed with embedded Postgres DB to vCenter Server 6.5 Update 2d and 6.7 Update 1 are supported.

Earlier Releases of vCenter Server 6.0

For internationalization, compatibility, installation and upgrades, and product support notices, see the VMware vCenter Server 6.0 Update 3 Release Notes.

Patches contained in this release

Vmware Vcenter Server 41 Iso Download Free

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

Third Party (TP.iso) patches for vCenter Server Applicance containing Third Party Product fixes are not supported starting from vCenter Server 6.0 Update 3g.

Security Patch for VMware vCenter Server 6.0 Update 3g

Security fixes (for example: JRE). This patch is applicable for vCenter Server for Windows, Platform Services Controller for Windows, and vSphere Update Manager.

For vCenter Server and Platform Services Controller for Windows

Download Filename	VMware-VIMPatch-6.0.0-8814879-20180726.iso
Build	8814879
Download Size	87.4 MB
md5sum	083032b4f3ed92bc696aad959eff88ba
sha1checksum	0758851e576f5045debfacb90bcac757981e7721

These vCenter Server components depend on JRE and have to be patched:

Platform Services Controller
vSphere Update Manager
vCenter Server

Download and Installation

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

Mount the VMware-VIMPatch-6.0.0-8814879-20180726.iso to the system where the vCenter Server component is installed.
Double-click ISO_mount_directory/autorun.exe.
In the vCenter Server Java Components Update wizard, click Patch All.

Full Patch for VMware vCenter Server Appliance 6.0 Update 3g

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

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

NOTE: Third Party (TP.iso) patches for vCenter Server Applicance containing Third Party Product fixes are not supported starting from vCenter Server 6.0 Update 3g.

For vCenter Server and Platform Services Controller Appliances

Download Filename	VMware-vCenter-Server-Appliance-6.0.0.30700-9146216-patch-FP.iso
Build	9146216
Download Size	1806.0 MB
md5sum	c9690a41089a2a2249cabc156ad2efb5
sha1checksum	b05814733613244ab8085ac4bd7956a18e1b53c5

Download and Installation

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

Attach the VMware-vCenter-Server-Appliance-6.0.0.30700-9146216-patch-FP.iso file to the vCenter Server Appliance CD or DVD drive.
Log in to the appliance shell as root and run the commands given below:
- To stage the ISO:
  software-packages stage --iso
- To see the staged content:
  software-packages list --staged
- To install the staged rpms:
  software-packages install --staged

For more information on patching the vCenter Server Appliance, see Patching the vCenter Server Appliance

For more information on staging patches, see Stage Patches to vCenter Server Appliance

For more information on installing patches, see Install vCenter Server Appliance Patches

For issues resolved in this patch see the Resolved Issues section.
For more information on patching using the Appliance Management Interface, see Patching the vCenter Server Appliance by Using the Appliance Management Interface.

Resolved Issues

The resolved issues are grouped as follows.

Installation Issues

Stateful installations on hosts with a Cisco Nexus N1K VEM driver might fail
Stateful installations might fail during the creation of scratch partitions in a configuration with a Cisco Nexus N1K VEM driver. The n1k-vem service might stop before the stateful installation is complete, and start after the installation to apply the host profile.
This issue is resolved in this release.

Miscellaneous Issues

Creation of snapshots during backup operations takes long to complete and vCenter Server stops displaying event data about objects in the inventory
During backup operations that require the creation of snapshots, tasks that post events as part of their workflow might take long to complete. vCenter Server stops displaying event data about objects in the inventory.
This issue is resolved in this release.
SNMP displays CPU and memory utilization of a vCenter Server Appliance constantly at 100%
If you use the snmpwalk command to query the CPU and memory utilization of a vCenter Server Appliance, SNMP might consistently report 100% even though the actual utilization is lower.
This issue is resolved in this release.
Alarms might not respond to triggers with status Unset
If you set alarms using the vSphere Web Client and you leave a trigger with status Unset, such alarms might not prompt any actions. You might see the following error message: An internal error occurred in the vSphere Client. Details: The provided alarm status is invalid.
This issue is resolved in this release.
You cannot place an ESXi host into an empty Enhanced vMotion Compatibility (EVC) cluster even though the host meets the requirements
Adding hosts that are not patched with the hypervisor-assisted guest mitigation for guest operating systems to an empty EVC cluster might fail, because the patches contain new CPU features.
This issue is resolved in this release.
Third-party trap receivers might reject traps older than 497 days from a vCenter Server Appliance
Third-party trap receivers might reject traps older than 497 days from a vCenter Server Appliance, because at this point the parameter tracking time exceeds the limit of 4 bytes.
Тhis issue is resolved in this release.

Networking Issues

After you cancel the cloning of a virtual machine, the virtual machine directory continues to exist
vCenter Server might not remove the port file directory (.dvsData) in the virtual machine directory after the process for cloning a virtual machine ends. As a result, the virtual machine directory continues to exist.
This issue is resolved in this release.
Link Aggregation Groups (LAGs) might be lost during the import of a VMware vSphere Distributed Switch configuration
If you import a vSphere Distributed Switch (VDS) configuration with many LAGs, the vCenter Server daemon vpxd might fail to insert the corresponding LAG information into the vCenter Server database. As result, some LAGs might be missing after a restart of the vpxd.
This issue is resolved in this release. If you already face the issue, delete and re-import the VDS configuration, or create the missing LAGs manually.
Migration of virtual machines by using VMware vSphere vMotion might fail when you import ephemeral port groups
If you import ephemeral port groups or a VDS instance with such groups, migration of virtual machines by using vSphere vMotion might fail, because the ports might not exist after the migration. You might see an error similar to A general system error occurred: vim.fault.NotFound.
This issue is resolved in this release. If you already face the issue, after the migration you must delete the imported ephemeral port groups or VDS with such port groups, and re-import them.
The vSphere Web Client might display an error in the VDS topology after a restart of vpxd due to outdated LAGs data
The vSphere Web Client might display an error in the VDS topology after a restart of vpxd due to outdated LAGs data. The vCenter Server database might not be updated with data for physical adapters added to the LAGs before the restart, and the daemon might not be able to find it.
This issue is resolved in this release. If you already face the issue, you must reassign the physical adapters to the LAGs.
vSphere ESX Agent Manager (EAM) fails to map agents to new ESXi hosts in NSX host clusters
Due to synchronization issues in vpxd, EAM might fail to map agents to newly added ESXi hosts in NSX managed clusters.
EAM logs might contain entries similar to:
| ERROR | vc-callback | AgencyImpl.java | 1295 | Failed to add agent to agency (AgencyImpl(ID:'Agency:XXXXX')): java.lang.RuntimeException: Host is no longer in vCenter inventory | WARN | eam-0 | AgencyImpl.java | 1954 | Disposing agency: AgencyImpl(ID:'Agency:XXXXXXX') due to failed load up. |
ERROR | eam-0 | AgencyImpl.java | 1895 | Failed to load agent: ManagedObjectReference: type = Agent, value = f18cd000-dcd5-4d30-8d6b-5f12b04e46fa, serverGuid = b0827a9b-fccd-41dd-8b27-caf8418da719. Error: null java.lang.NullPointerException | ERROR | eam-0 | VcListener.java | 116 | An unexpected error in the changes polling loop
This issue is resolved in this release.
EAM might fail to start if an ESXi host is removed from an NSX host cluster
If you move an ESXi host out of an NSX host cluster while the EAM service is not working for some reason, EAM might fail to start. With this fix, EAM skips loading agents on hosts that are moved out of their previous agency and allows EAM to start. After EAM starts, you can move displaced hosts into other agencies and clusters. EAM logs might contain entries similar to:
| ERROR | eam-0 | VcListener.java | 116 | An unexpected error in the changes polling loop
| ERROR | eam-0 | AgencyImpl.java | 1895 | Failed to load agent: ManagedObjectReference: type = Agent, value = d6429441-6953-4795-81ff-efc455232e9a, serverGuid = b0827a9b-fccd-41dd-8b27-caf8418da719. Error: Host not covered by scope anymore
This issue is resolved in this release.
Adding a host to Cisco N1K DVS by using the vSphere Web Client might fail
Adding a host to Cisco N1K DVS by using the vSphere Web Client might fail with an error similar to The number of physical network adapter per host exceeds the number of uplink ports.
This issue is resolved in this release.
VMware vSphere High Availability might fail to power on a secondary virtual machine after а failover
vSphere High Availability might fail to power on a secondary virtual machine after a failover, due to missing port files. After an upgrade to vCenter Server 6.0 Update 3g, you must turn off vSphere Fault Tolerance and restart it to create port files in the datastores of both the primary and secondary virtual machines.
This issue is resolved in this release.

Security Issues

Pivotal tc Server license expired in March 2018
Pivotal tc Server license expired in March 2018. The server provides Apache Tomcat 8.5.24 access and runs multiple Tomcat runtime instances with a single physical installation. The current update removes tc Server dependency and all services on vCenter Server use Apache Tomcat directly.
This issue is resolved in this release.
Update to vPostgres
vPostgres is updated to 9.3.22 to resolve a security issue with identifier CVE-2018-1058.
Update to JRE
Oracle (Sun) JREis updated to version 1.7.0_181.
cURL in the vCenter Server Appliance is updated to 7.58
cURL in the vCenter Server Appliance is updated to 7.58 to address issues with identifiers CVE-2017-8818, CVE-2017-8817, CVE-2018-1000007 and CVE-2018-1000005.
Update to Python
The Python third party library is updated to version 2.7.14 to resolve security issues with identifiers CVE-2017-1000158 and CVE-2014-4616.
The default validity of VMware Certificate Authority (CA) certificates is reduced to two years
The default validity of all VMware CA certificates is reduced to 2 years from 10 years. VMware CA certificates expire within up to 825 days according to recommendations by the CA/Browser Forum.
Update of the Jackson library
The Jackson JavaScript Object Notation (JSON) processor package is updated to version 2.9.5.

Server Configuration Issues

Open cursors in the memory of the vCenter Server Appliance embedded database might cause performance and disk space issues
Failures to close SQL handles or free associated cursors and memory resources in the embedded PostgreSQL database in vCenter Server Appliance might cause indefinite expansion of tables and indexes. This might lead to reduced disk space and performance.
This issue is resolved in this release.
vCenter Server might stop responding if you remove a Pluggable Storage Architecture (PSA) path on an ESXi host
If you remove a PSA path on an ESXi host while vCenter Server is not running, it is added as a new path when vCenter Server restarts. This might cause vCenter Server to stop responding with the following error message: ERROR: duplicate key value violates unique constraint 'vpxi_psa_path”.
This issue is resolved in this release.
vSphere Storage DRS tasks in large datastore clusters might take long to complete
vSphere Storage DRS tasks in large datastore clusters might take long to complete due to slow querying of datastore tags. To mitigate the issue, vCenter Server 6.0 Update 3g introduces a SrmSupportNeeded flag as an advanced option setting for datastore clusters. The flag value is set to 1 and turned on by default. You can turn off the flag when Site Recovery Manager support is not needed by setting the parameter value to 0. As result, this boosts vSphere Storage DRS task performance. In addition, the BatchTagQuery advanced option is turned on by default, which also improves task performance.
This issue is resolved in this release.

Storage Issues

Storage alarm and event messages are displayed as Unknown event ID or Unknown message identifier
Storage alarm and event messages are not correctly transformed when posted to vCenter Server. As a result, they are displayed as Unknown event ID or Unknown message identifier.
This issue is resolved in this release.

Tools Issues

The SNMP v3 agent allows users with priv security level to access data by providing only an authentication key phrase or no security key phrase at all
The SNMP v3 agent allows users with priv security level to access data by providing only an authentication key phrase or no security key phrase at all. Users with priv security level must provide both an authentication key phrase and a privacy key phrase.
This issue is resolved in this release.
The vSphere Web Client might display a confusing status for VMware Tools
If you manually reinstall the same version of VMware Tools on a guest virtual machine more than once, the ESXi host might receive contradicting reports that VMware Tools is not installed, while at the same time VMware Tools operations are running. At this point, the vSphere Web Client displays a warning message similar to: VMware Tools: Running, version: 10304 (Not installed).
This issue is resolved in this release.
Replacing a machine SSL certificate with a custom certificate authority (CA) signed certificate might fail with an error
Using the option Replace Machine SSL certificate in the vSphere Certificate Manager utility might fail with a message error 20 at 0 depth lookup:unable to get local issuer certificate due to incorrect validation of host entries.
This issue is resolved in this release. If you are using an older version of vCenter Server 6.0, you can change the value of the parameter return isresult to return True at /usr/lib/vmware/site-packages/cis/certificateManagerHelper.py for the vCenter Server Appliance. For vCenter Server on Windows, the path is C:Program FilesVMwarevCenter Serverpython-modulesciscertificateManagerHelper.py .

vCenter Server, vSphere Web Client, and vSphere Client Issues

vCenter Server Appliance might run out of disk space due to piled dnsmasq logs
The dnsmasq logs might not be rotated and pile up to exceed the disk space of a vCenter Server Appliance.
This issue resolved in this release.
Group permissions might result in limited or revoked permissions for a user if one of the assigned roles is No Access
If a user belongs to two or more groups and one of the groups is assigned a No Access role, the user might have limited or no effective permissions.
This issue is resolved in this release.
The vpxd service might fail when you close the root folder from the Inventory View
If you add an ESXi host to a cluster and create a VMware vSphere vApp in this cluster, when you navigate to the vApp from the Inventory Viewin the vSphere Web Client, vpxd might fail with an error Panic: Assert Failed: 'openedInfo._activations 0' at the time you close the root folder.
This issue resolved in this release.

Virtual Machine Management Issues

A VMware vSphere Storage DRS task might run into a loop
A vSphere Storage DRS task might run into an infinite loop which blocks other vSphere Storage DRS tasks for the same storage cluster. You might observe high CPU usage or timeouts of vSphere Storage DRS tasks.
This issue is resolved in this release.
Deploying an OVF template exported from an ESXi 5.5 host to a content library on an ESXi 6.0 host might fail
Deploying an OVF template exported from an ESXi 5.5 host to a content library on an ESXi 6.0 host might fail with an error The operation failed due to Invalid configuration for device 8.
This issue is resolved in this release.
EAM might delete active agents during resource availability checks
EAM might delete active agent virtual machines during resource availability checks and cause data loss. This fix prevents EAM from deleting active agents to free resources if it fails to power on a service virtual machine due to resource limitations like CPU and memory allocation.
This issue is resolved in this release.
Performance of vSphere Storage DRS might drop due to excessive number of parallel tasks
You might trigger multiple tasks in parallel to handle threshold violation events in vSphere Storage DRS, because there is no check for such tasks. This might degrade the performance of vSphere Storage DRS.
This issue is resolved in this release.
vCenter Server might stop responding during virtual machine deployment
When you deploy a new virtual machine, vCenter Server might stop responding if a datastore becomes unavailable during the initial placement of virtual disks with vSphere Storage DRS.
This issue is resolved in this release.
Attempting virtual machine provisioning operations while IPv6 support is disabled causes ESXi hosts to disconnect
The Network File Copy daemon (NFCD) creates both IPv4 and IPv6 sockets on ESXi hosts. If you attempt virtual machine provisioning operations, such as cold migration or cloning, by using the provisioning TCP/IP stack while IPv6 support is disabled, the host might disconnect from the network without using the IPv4 socket.
This issue is resolved in this release.
vCenter Server might stop responding when you attempt to add а new disk to a virtual machine
When you attempt to add a virtual disk to a virtual machine, vSphere Storage DRS might cause vCenter Server to stop responding while generating datastore recommendations.
This is resolved in this release.
VMware Site Recovery Manager workflows might fail due to a race condition
Site Recovery Manager workflows, such as test a recovery plan, might fail due to a race condition with an error similar to java.util.concurrent.ExecutionException: com.vmware.vim.vmomi.client.exception.InternalException: Trying to override already set SSL user token with different one. In the vCenter Sever Appliance, you can find the error in var/log/vmware/workflow/workflow-manager.log.
This issue is resolved in this release.
DRS affinity rules might be disabled if virtual machines change clusters
If a virtual machine is subject of a VM-VM affinity or anti-affinity rule and you move it from one cluster to another, and later return the virtual machine to the first cluster, the affinity rule might no longer be active. In the vpxd logs, you might see reports for conflict of rules that cause the existing rules to be disabled.
This issue is resolved in this release.
Virtual machine operations fail with a compatibility error when a virtual machine hardware version upgrade is scheduled
When a virtual machine hardware version upgrade is scheduled, virtual machine operations might fail with the following compatibility error message: The destination host is not compatible with the hardware version to which the virtual machine is scheduled to be upgraded. For more information, see VMware Knowledge Base article 2080107.
This issue is resolved in this release.

vMotion and Storage vMotion Issues

vCenter Server might become unresponsive during migration of virtual machines by using vSphere Storage vMotion or XvMotion
When you try to perform Storage vMotion or XvMotion migration of a virtual machine with two or more snapshots that each contain the same independent disks, vCenter Server might become unresponsive.
This issue is resolved in this release.
Migrating virtual machines across vCenter Server systems might fail with a No Permission error
When you migrate virtual machines across vCenter Server systems, despite having System.Read privileges on the destination object, if you do not have System.Read privilege on the destination data center, the migration might fail with a No Permission error.
This issue is resolved in this release.

vSAN Issues

vSAN requires RVC to configure TLS protocol version for vSAN Observer
vSAN Observer can read the TLS protocol version only when you run it from RVC command-line interface. The TLS version is not stored in a configuration file. If you run vSAN Observer form vCenter Server, it cannot read the TLS version.
This issue is resolved in this release.
vSAN health service might fail to load when one site of a stretched cluster is down
When all of hosts in one site of stretched cluster are down, the vSAN health service might not be loaded and show any data due to an unexpected exception.
This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Installation, Upgrade and Migration Issues

Migration from vCenter Server on Windows 5.5.x and 6.0.x to vCenter Server Appliance 6.5.x might fail during data export
Migration from vCenter Server on Windows 5.5.x and 6.0.x to vCenter Server Appliance 6.5.x might fail during data export with an error such as The compressed zip folder is invalid or corrupted.
Workaround: Archive the data export folder manually:
1. In the source Windows system, create an environment variable MA_INTERACTIVE_MODE.
  - Go to Computer > Properties > Advanced system settings > Environment Variables > System Variables > New.
  - Enter MA_INTERACTIVE_MODE as variable name with value 0 or 1.
2. Start the VMware Migration Assistant and provide your password.
3. Deploy the .ovf file with the standalone installer to complete Stage 1 of the migration.
4. In Stage 2, the migration pauses and the Migration Assistant console displays the message To continue the migration, create the export.zip file manually from the export data (include export folder).
  NOTE: Do not press any keys or tabs on the Migration Assistant console.
5. Go to path: %appdata%vmwaremigration-assistant folder.
6. Delete the export.zip folder created by the Migration Assistant.
7. To continue the migration, manually create the export.zip folder from the export folder.
8. In the Migration Assistant console, type Y and press Enter.
Migration must start as usual.
Upgrade of vCenter Server for Windows might fail with error code 3010
Upgrade of vCenter Server for Windows to version 6.x might fail with an error Installation of component VMware vCenter Server failed with error code '3010'. Check the logs for more details, if the OpenSSL package is of higher version than the update release.
In the %TEMP%vminst.log file, you might see similar logs:
YYYY-MM-DD>T<time>| vcsInstUtil-5318198| E: wWinMain: MSI result of install of 'E:vCenter-ServerPackagesvmware-vpxd.msi' may have failed: 3010 (0x00000bc2)
YYYY-MM-DD>T<time>| vcsInstUtil-4541944| E: LaunchPkgMgr: Operation on vmware-vpxd.msi appears to have failed: 3010 (0x00000bc2)
YYYY-MM-DD>T<time>| vcsInstUtil-4541944| I: PitCA_MessageBox: Displaying message: 'Installation of component VMware vCenter Server failed with error code '3010'. Check the logs for more details.
YYYY-MM-DD>T<time>| vcsInstUtil-5318198| E: wWinMain: MSI result of install of 'E:vCenter-ServerPackagesvmware-openssl.msi' may have failed: 3010 (0x00000bc2)
YYYY-MM-DD>T<time>| vcsInstUtil-5318198| E: LaunchPkgMgr: Operation on vmware-openssl.msi appears to have failed: 3010 (0x00000bc2)
YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: PitCA_MessageBox: Displaying message: 'Installation of component VMware Open SSL components failed with error code '3010'. Check the logs for more details.'
In the pkgmgr-comp-msi.log file, you might see logs similar to:
YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: UpdatePackageList: File: Z:vCenter-ServerPackagesvmware-openssl.msi
YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: UpdatePackageList: VersionCompare - Version: 6.0.0.9090 VersionInstalled: 6.0.0.60000 Res: -1
YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: UpdatePackageList: ProductCodeCompare - ProductCode: {3D2B421E-617E-46F2-A83F-BF8AB22DBAAF} ProductCodeInstalled:{7CA4FE96-7C9E-40ED-ABF7-3EA5D78529D3} Res: -1
YYYY-MM-DD>T<time>| vcsInstUtil-5318198| I: UpdatePackageList: Disabling installation of package Z:vCenter-ServerPackagesvmware-openssl.msi (ProductCode is different but ProductVersion is smaller than the one already on the system)
Workaround:
1. Open the Windows Registry regedit.exe.
2. Search for key 7CA4FE96-7C9E-40ED-ABF7-3EA5D78529D3 in HKEY_LOCAL_MACHINESOFTWAREClassesInstallerProducts. If you find the key, back it up and remove it.
3. Search for value 6.0.0.60000 in HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData. If you find the value, back up the key and remove it.
4. Retry the upgrade.
Patching from vCenter Server 6.0, 6.0.0a and 6.0.0b to vCenter Server 6.0 Update 3g might take too long
When patching a vCenter Server Appliance from vCenter Server 6.0, vCenter Server 6.0.0a or vCenter Server 6.0.0b to vCenter Server 6.0 Update 3g, the process might take too long due to issues with the RPM update. All services might become temporarily unavailable.
Workaround: None. For more information on the issue, see KB 56625.
VMware vCenter Single Sign-On Security Token Service (STS) might not retain any custom TLS configuration after patching
STS services might not keep any custom TLS configuration after patching. Instead, TLSv1, TLSv1.1 and TLSv1.2 protocols are enabled.
Workaround: Use the TLS Configurator utility to restore the TLSv1.2 configuration.

Miscellaneous Issues

The Client Integration Plug-In might not work as expected if you log in to the vSphere Web Client using Firefox
When you log in to the vSphere Web Client using Firefox from a Windows or Mac OS, and perform tasks related to the Client Integration Plug-In, you might encounter the following issues:
- Export or import OVF files (.ovf) is not enabled.
- Upload or download files to datastores is not enabled.
- Windows Session Authentication (SSPI) login is not enabled.
- Upload to or download from the Content Library is not enabled.
You might also see a message such as Client integration plug-in is not installed. Please install and Refresh the browser.
Workaround: You can use alternative browsers, such as Google Chrome or Internet Explorer.
Client Integration Plug-In installation might fail
The installation of the Client Integration Plug-In might fail. The Microsoft Visual C++ Redistributable Packages for Visual Studio are not installed on the Windows host machine.
Workaround: Before installing the Client Integration Plug-in, download and install the missing Microsoft Visual C++ Redistributable Packages for Visual Studio that are supported by your system. You can check whether the packages are installed on your host machine by using Add/Remove Programs. You can check which packages you need depending on your Windows version in the System Requirements section for the different versions of Visual C++ Redistributable Packages on the Microsoft website. Install both x86.exe and x64.exe of Microsoft Visual C++ Redistributable Packages for Visual Studio.
Оlder versions of the vSphere Web Client might not detect the latest version of the Client Integration Plug-in
Оlder versions of the vSphere Web Client might not detect the latest version of the Client Integration Plug-in due to changes in the product builds for VMware vCenter Server 6.0 Update 3g. The changes are related to both the Client Integration Plug-in and the vSphere Web Client.
Workaround: Upgrade to the latest Client Integration Plug-in version while accessing VMware vCenter Server 6.0 Update 3g by using the vSphere Web Client.

Known Issues from Earlier Releases

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

The earlier known issues are grouped as follows.

vCenter Server for Windows Installation Issues

Upgrade failure on Windows vCenter Server 5.xwith high-ASCII or non-ASCII characters in the user name
Upgrading Windows vCenter Server 5.x with high-ASCII or non-ASCII characters in the user name might fail with an error code 1603 while uninstalling 5.x products.
Workaround: Ensure that user names contain ASCII characters only.
Upgrade on Windows vCenter Server 5.x with an external SQL database fails
Upgrade check on Windows vCenter Server 5.x with an external SQL database fails when the ODBC DSN is configured with a non-ASCII or high-ASCII name. It prompts the following message:
'The system name in vCenter Server 5.x SSL certificate and the vCenter Single Sign-On 5.x SSL certificates are not compatible. Please replace either the vCenter Server SSL certificates or the vCenter Single Sign-On SSL certificates so both vCenter Server and vCenter Single Sign-On SSL certificates use the same system name.'
Workaround: To work around this issue, perform the following steps:
1. Stop vCenter services.
2. Create DSN with ASCII characters.
  Note: The user name and password should be same.
3. Modify the DSN name in the Windows Registry Editor HKEY_LOCAL_MACHINESOFTWAREVMware, Inc.VMware VirtualCenterDB.
  Note: Back up your registry before performing step 1 to step 3.
4. Start vCenter services.
5. Upgrade to 6.0 Update 3.
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.
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:
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:ProgramDataVMwarevCenterServer or the installation directory under C:Program FilesVMwarevCenterServer 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 FilesVMwarevCenter Serverbinvc-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 FilesVMwarevCenter Serverbinvc-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

Deploying vCenter Server Appliance using Internet Explorer might fail
Deploying vCenter Server Appliance using Microsoft Internet Explorer fails on a virtual machine, if installation files are copied to a folder that contains High-ASCII or Non-ASCII characters. Attempts to open vcsa-setup.html using Microsoft Internet Explorer fails to load the page beyond Select appliance type.
Workaround: To work around this issue, perfrom one of the following actions:
- Use Chrome or Firefox to deploy the vCenter Server Appliance.
  or
- To use Microsoft Internet Explorer, place the vCenter Server Appliance installation files in a folder that contains only ASCII characters.
ovftool and filetransfer fail with an error during installation or migration to vCenter Server Appliance 6.0 Update 3 in Windows 8
While installing or migrating to vCenter Server Appliance 6.0 Update 3 in Windows 8 operating system using UI installer, ovftool.exe and filetransfer.exe fails with an exception.
While upgrading vCenter Server Appliance from 6.0.x to 6.0 Update 3, memory of the Platform Services Controller does not change
While upgrading Platform Services Controller of vCenter Server Appliance from 6.0.x to 6.0 Update 3, memory of the Platform Services Controller does not change and it remains 2 GB.
Workaround: To work around this issue, perform these steps:
1. Power off the Platform Services Controller of vCenter Server Appliance VM.
2. Increase the memory size manually by Edit Settings of the VM.
3. Power ON the Platform Services Controller of vCenter Server Appliance VM.
Upgrade on Windows vCenter Server 5.x with an external SQL database fails
Upgrade check on Windows vCenter Server 5.x with an external SQL database fails when the ODBC DSN is configured with a non-ASCII or high-ASCII name. It prompts the following message:
'The system name in vCenter Server 5.x SSL certificate and the vCenter Single Sign-On 5.x SSL certificates are not compatible. Please replace either the vCenter Server SSL certificates or the vCenter Single Sign-On SSL certificates so both vCenter Server and vCenter Single Sign-On SSL certificates use the same system name.'
Workaround: To work around this issue, perform these steps:
1. Stop vCenter services.
2. Create DSN with ASCII characters.
  Note: The user name and password should be same.
3. Modify the DSN name in the Windows Registry Editor HKEY_LOCAL_MACHINESOFTWAREVMware, Inc.VMware VirtualCenterDB.
  Note: Back up your registry before performing steps 1 through 3.
4. Start vCenter services.
5. Upgrade to 6.0 Update 3.
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: To work around this issue, perform these steps:
- 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 vCenter Server Appliance deployment is completed.
Workaround : The status of deployment can be checked in appliance console.
psc_restore command fails in multi-node Platform Controller Services environment
Attempts to run psc_restore command in a restored Platform Controller Services node fails in multi-node Platform Controller Services environment when there are two-way replication agreements among the Platform Controller Services nodes in the federation.
Workaround: In multi-node Platform Controller Services environment when there are two-way replication agreements among the Platform Controller Services nodes in the federation, make sure that at least one object on a Platform Controller Services node replicates with the other nodes before making a backup of the Platform Controller Services 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.
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:
1. Download help.war to the /usr/lib/vmware-virgo folder of your vCenter Server Appliance.
2. Change it to the following: owner vsphere-client and group users:
  chown vsphere-client help.war
  chgrp users help.war
3. Change your account to vsphere-client.
  
  If you stay root the copy operation changes the owner to root again.
  
  su vsphere-client
4. Verify that the server is already running and copy help.war to /usr/lib/vmware-virgo/server/pickup.
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:
1. Navigate to the Firefox Options menu.
2. Click Advanced, and click the Network tab.
3. Click Settings.
4. 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%AppDataLocalVMware.
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%AppDataLocalVMware.
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:ProgramDataVMware 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:WindowsSystem32driversetchosts.new, C:WindowsSystem32driversetchosts.
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.

Upgrade Issues

Upgrade of vSphere Client might fail with an error if Horizon View Client is installed
Upgrading to a new version of VMware vSphere Client might fail with an error Failed to install hcmon driver if VMware Horizon View Client is also installed, because versions of drivers that the vSphere Client tries to install in the VMware network install library, vnetlib64.dll, might be different from the drivers that the Horizon View Client has previously installed.
Workaround: To work around this issue you must uninstall the old version of vSphere Client and then install the new version.
NSX VIB installation through EAM might fail if it requires only maintenance mode and no reboot of the ESXi host
vSphere ESX Agent Manager (EAM) puts ESXi hosts in maintenance mode during the installation of NSX vSphere Installation Bundles (VIB), but might not take the hosts out of maintenance mode if the VIB requires only maintenance mode and no reboot.
Workaround:
To work around this issue, you must manually take the host out of maintenance mode.
Content Library creation might fail when vCenter Server is upgraded to 6.0 Update 3c
When vCenter Server is upgraded to 6.0 Update 3c, the Content Library creation might fail with an error.
Workaround:
Find the signing certificate and the root CA used by SSO from vmware-identity-sts.log or websso.log. Check whether the root CA is present in TRUSTED_ROOTS of VMware Endpoint Certificate Store. If it is not present in the VMware Endpoint Certificate Store, add the root CA to TRUSTED_ROOTS.
Alternatively we can also look into vmdir under DN: 'cn=TrustedCertificateChains,cn=fc8b434d-8404-4107-a28a-ffe027b1e623,cn=Ldus,cn=ComponentManager,dc=vsphere,dc=local' to identify all the signing certificates and their root CAs.
For vCenter Server Appliance:
1. Identify the root CA from the vmware-identity-sts.log file.
  Look for the Security Assertion Markup Language token KeyInfo element and the <ds:X509Certificate> tag
  For example:
  <ds:X509Certificate>MIIFEzCCA/ugAwIBAgIJAIhibbQofa1VMA0GCSqGSIb3DQEBCwUAMIGyMQswCQYDVQQGEwJVUzET MBEGA1UECBMKQ2FsaWZvcm5pYTESMBAGA1UEBxMJUGFsbyBBbHRvMRUwEwYDVQQKEwxWTXdhcmUs IEluYy4xNzA1BgNVBAMTLmJscjctN3RoLWRoY3AtNDctMjcuZW5nLnZtd2FyZS5jb20gQ0EgMzQw OWE0MGQxKjAoBgkqhkiG9w0BCQEWG3NzbC1jZXJ0aWZpY2F0ZXNAdm13YXJlLmNvbTAeFw0xNjAy MDEwOTMxMjdaFw0yNjAxMjkwOTMxMjdaMIGyMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZv cm5pYTESMBAGA1UEBxMJUGFsbyBBbHRvMRUwEwYDVQQKEwxWTXdhcmUsIEluYy4xNzA1BgNVBAMT LmJscjctN3RoLWRoY3AtNDctMjcuZW5nLnZtd2FyZS5jb20gQ0EgMzQwOWE0MGQxKjAoBgkqhkiG 9w0BCQEWG3NzbC1jZXJ0aWZpY2F0ZXNAdm13YXJlLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEP ADCCAQoCggEBANPkC1QUF79+cmgq6EZhrJL81UO6pH04fQQ9yM38o55TkFvtAapVBXq7uJ8T0nO4 a04JwiqW9El4hce/Z3+nOHOckWJ0VSCFoqox1FVpYW4fXSeHfuQ0ktVnyIyMz/vYTAWrnj493YIY QuiXMeNJwxvG/gHwz+TiRlMSVBiXCQeD9NNRCG8qljSgkrd2yW2rTCBL9h09XleKmtkt0HeGT0pf pM9fKQ7lM6JZQUN9WS8wP5YKASv5M029qGxPzSpq5YOp7EmFr5bbSXI9sb+/W5VrU1vdO6LVaYOK wKFHm8xe2hNyLAMCWzHVHyNNfcbTSNj/IZ1jE+EtAA6lSv0bgT0CAwEAAaOCASgwggEkMB0GA1Ud DgQWBBQiBchoMNnNgbc1vtiO1cuuZPNOOTCB5wYDVR0jBIHfMIHcgBQiBchoMNnNgbc1vtiO1cuu ZPNOOaGBuKSBtTCBsjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExEjAQBgNVBAcT CVBhbG8gQWx0bzEVMBMGA1UEChMMVk13YXJlLCBJbmMuMTcwNQYDVQQDEy5ibHI3LTd0aC1kaGNw LTQ3LTI3LmVuZy52bXdhcmUuY29tIENBIDM0MDlhNDBkMSowKAYJKoZIhvcNAQkBFhtzc2wtY2Vy dGlmaWNhdGVzQHZtd2FyZS5jb22CCQCIYm20KH2tVTAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIC BDANBgkqhkiG9w0BAQsFAAOCAQEAsn/F3Cc7iGLwSLr9EmjzmJtQVzGJBmcMsd/bNailOkzxwH2z ToPWrMxoh/jgFkV27PPxAg4adsHymDvxY+xcfdmAjU5pDsR9KG4jksTtcasO+fY219gapUbanApG 3weNeH8Nln9T4VBJfBYqxuVepvDoVFkiUD4iBY/caAKYJv84+JfrHQtaPcgCOidmN+iUVGO9XlQq bImRwXGER2vdOndXo5Ic1dFgzeiSc01jSN9uLYwrsc7n1NWBAkTcKDonQMC3Pgp+et/nR76aZYzd s30p6NWvXctc2iuv82bRAjX+p+DI1Kji3Ms/qDxn9rf3vDcT5zw+rwjA6qDXs9Lj8w</ds:X509Certificate></ds:X509Data></ds:KeyInfo>
2. Save the content between the tags <ds:X509Certificate> </ds:X509Certificate> to a file with a .crt extension.
  For example, enter 51root.crt as the file name.
3. Append -----BEGIN CERTIFICATE----- at the beginning and -----END CERTIFICATE----- at the end of the file.
4. Add the CA to TRUSTED_ROOTS on the Management Node as shown below:
  /usr/lib/vmware-vmafd/bin/vecs-cli entry create --store TRUSTED_ROOTS --alias roo51 --cert 51root.crt
5. Restart all services.
For Windows:
1. See workaround (steps 1 to 3) of vCenter Server Appliance.
2. Add the CA to TRUSTED_ROOTS on the Management Node as shown below:
  C:Program FilesVMwarevCenter Servervmafddvecs-cli.exe entry create --store TRUSTED_ROOTS --alias roo51 --cert 51root.crt
3. Restart all services.
vSphere Web Client might fail after upgrade of vCenter Server Appliance to 6.0 Update 3c if you click Manage > Access > Edit
You might lose connectivity of the vSphere Web Client when you navigate to System Configuration > Nodes > Manage > Access > Edit to change the shell and bash access on that node after an upgrade of vCenter Server Appliance to 6.0 Update 3c.
Workaround: To work around this issue, you must run a script to import a missing certificate into the VMware Endpoint Certificate Store. For more information on the issue, see https://kb.vmware.com/kb/000050861.
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 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:
1. Run the following command to Connect to vCenter Server:
  PowerCLI C:Program Files (x86)VMwareInfrastructurevSphere PowerCLI> Connect-VIServer -Server <FQDN_hostname or IP Address of vCenter Server>
2. Run the following command to check the current sslv3 status:
  PowerCLI C:Program Files (x86)VMwareInfrastructurevSphere PowerCLI> Get-DeployOption
3. Run the following command to disable sslv3:
  PowerCLI C:Program Files (x86)VMwareInfrastructurevSphere PowerCLI> Set-DeployOption disable-sslv3 1
4. Restart the Auto Deploy service to update the change.
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).
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,
1. Find the signing certificate and the root CA used by SSO from vmware-identity-sts.log or websso.log.
2. 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,
For Windows,
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:
1. Login to the VAMI interface for the 5.5 VCSA. https://<VC_IP>:5480
2. Click the Network tab and then the Address section.
3. Make sure the settings in here are all correct and then click Save Settings, even if you didn’t change anything.
4. SSH to the appliance and collect the output of the following command
  “cat /etc/sysconfig/network/ifcfg-eth0”
5. Make sure the source and destination are in the same subnet.
6. 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:
1. Remove the trailing white space from the DSN name.
2. 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:ProgramDataVMwareVMware VirtualCenterLogs 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%System32driversetchosts 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.
1. Access the CM Managed Object Browser using the following URL: https://VC_HOSTNAME/cm/mob.
2. In the Methods table, select Search.
3. 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>
4. Record each vCenter Server serviceId.
5. Select UnregisterService.
6. 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.
1. Log in into CM MOB: https://ip_addr/cm/mob using the Administrator@vsphere.local.
2. In the Methods table, use Search.
3. Find all service end points by entering empty searchCriteria as follows:
  <searchCriteria>
  </searchCriteria>
4. Record each serviceId for the 5.1 instance.
5. Select UnregisterService.
6. 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 vcsUpgradeUpgradeRunner.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.
1. Log in to vCenter Server through the vSphere Web Client.
2. Register the hardware version 3 VM on the legacy ESXi server or ESXi 6.0 server.
3. Right-click the VM and select All vCenter Actions.
4. Select Compatibility.
5. Select Upgrade VM Compatibility.
6. Click Yes.
7. Select Compatible with ESX 3.5 and later and click OK.
After upgrading the VM, you can perform power operations and VM migrations.

Licensing Issues

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.

Vmware Vcenter Server 41 Iso Download Windows 7

vCenter Single Sign-On and Certificate Management Issues

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.
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.
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.
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 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:
1. 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
2. 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 FilesVMwarevCenter Servervmdirdvmdird.exe -c -u -f
  C:ProgramDataVMwarevCenterServercfgvmdirdvmdirschema.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
3. Start the Directory Service and all dependent services that were automatically brought down, or reboot the system.
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.
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.
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
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.
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.

Storage Issues

Vmware Vcenter Server 41 Iso Download Windows 7

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:
1. Create a virtual machine on one datastore, for example, Virtual SAN.
2. 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.
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.

Server Configuration Issues

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

vCenter Server, vSphere Web Client, and vSphere Client Issues

Accounts with administrator privileges that contain multibyte characters might not be able to modify permissions
Accounts with administrator privileges that contain multibyte characters might not be able to modify permissions via the vSphere Web Client and you might see an error similar to An internal error has occurred – Error #1009 when you try to manage access to nodes under Administration > System Configuration.
Workaround:
To work around this issue, you must log in vSphere Web Client with accounts with administrator privileges that contain only ASCII characters.
After a minor upgrade, the new properties that are added are not available in webclient.properties file
After a minor upgrade of vSphere Web Client, the following properties that were added to webclient.properties file is not available.
sso.pending.password.expiration.notification.days = 30
cip.min.build=<cipBuildNumber>Note: If this property is set, then the build number specified is treated as the minimum required build for the Client Integration Plug-in. For any client that has a Client Integration Plug-in build less than this, an upgrade to Client Integration Plug-in will be required.
Workaround: Add the new properties manually to the webclient.properties file, and restart vSphere Web Client.
Support for encrypted TLS connection to an external Microsoft SQL Server or external Oracle database is not currently supported
vSphere Client fails to connect with TLSv1.0 disabled
vSphere Client fails to connect to the vCenter Server or ESXi with TLSv1.0 disabled.
Workaround: Microsoft updates are required to make vSphere Client function with TLSv1.2. For more information, see KB 2149000.
Some non-English keyboard layout keys do not work as expected in the VMware HTML Console
Some non-English keyboard layout keys are not mapped correctly in the virtual machine. When you press these keys with non-English Windows or Mac keyboard, the keys might not work or a wrong key might be entered in the console. For information about the keys, see Knowedge Base article 2149039.
Workaround: Use the VMware Remote Console.
Customizing time range might fail on non-ASCII Mac OS X guest operating system.
If you try to customize the Time Range in Monitor > Performance > Overview page for a data center, cluster, host, or datastore on a non-ASCII Mac guest operating system, vSphere Web Client might fail with an error similar to the following:
An internal error has occurred - Error #1009. Reloading the client is recommended, so as to clear any problems left by this error. Click Yes to reload the vSphere Web Client?
Workaround: Use the vSphere Web Client on Windows for customization.
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.
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.
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.
- 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.
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.
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:
- 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.
- 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 SynchronizationSettings 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:ProgramDataVMwarevCenterServerdatacore)
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)VMwareClient Integration Plug-in 6.0bifrost
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.
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.
1. In the address bar of Mozilla Firefox version 23.0 or later on your OS X client computer, type about:config and press Enter.
2. On the warning dialog that appears, click I'll be careful, I promise.
3. In the Search text box, enter security.mixed_content.block_active_content to filter the list of the available browser preferences.
4. Double-click on the security.mixed_content.block_active_content preference to change its value to false.
5. 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
Log in to vCenter Server by using the vSphere Web Client, and on the vSphere Web Client Home page, click System Configuration. Under System Configuration, click Services and select a service from the list. On the Summary tab in the Health Messages pane, the health status message might be missing or might be uninformative for some services.
Workaround: None.
After you log in to the vSphere Web Client by using Google Chrome in incognito mode, error messages appear every few seconds until the browser window is blocked
If you log in to the vSphere Web Client by using the incognito mode of Google Chrome, error messages cause the browser window to stop responding.
The incognito mode of Google Chrome might prevent vSphere Web Client from writing data to some objects.
Workaround: In Google Chrome, use the https://vcenter-server-hostname:9443/vsphere-client/?debug=true&logLevel=ERROR URL to access the vSphere Web Client.
The icon of the Dell Virtual Storage Manager (VSM) appliance is not displayed on the vSphere Web Client Home page
Deploy the Dell VSM appliance in your vSphere environment and power it on. If you register your VSM appliance with vCenter Server first and then log out and log in vCenter Server, the VSM appliance icon is not displayed on the Home page of the vSphere Web Client. As a result you cannot access and use the Dell Virtual Storage Manager by using the vSphere Web Client.
Workaround: Restart the vCenter Server system and log in to vCenter Server by using the vSphere Web Client.
When you launch a virtual machine Web console in full screen mode by using the vSphere Web Client, mouse operations inside the console do not work
In the vSphere Web Client, select a virtual machine, and on the Summary tab, click Launch console. In the new tab that opens in your Web browser, click Full Screen to view the Web console in full screen mode. Attempts to right-click inside the virtual machine Web console and select any option fail, because the mouse operations are not detected.
Workaround: Perform one of the following tasks:
- On the virtual machine Web console tab in your browser, press Esc to exit the full screen mode.
- Use keystroke combinations to run commands inside the guest operating system when you view the virtual machine Web console in full screen mode.
On Microsoft Windows 8, you might be unable to access the vSphere Web Client by using Microsoft Internet Explorer 10 with the integrated Adobe Flash Player
The Adobe Flash Player version 11.5 that is integrated in Microsoft Internet Explorer 10 does not meet the software requirements for vSphere Web Client.
Workaround: On Microsoft Windows 8, use a browser that has support for Adobe Flash Player version 11.9 or later to access the vSphere Web Client.
You cannot view the Solution tab of the EAM Sample Solution in the vSphere Web Client
When you click the Solution tab from the EAM Sample Solution in the vSphere Web Client, its content is not displayed. The default settings of your Web browser block Mixed Content, which prevents the Solution page from loading.
Workaround: Change your browser settings so that viewing blocked content is displayed:
- In Microsoft Internet Explorer, go to the bottom of the browser and click Show all content.
- In Mozilla Firefox, click the shield icon that appears on the left of the address bar and select the Disable Protection on This Page option from the drop-down menu.
- In Google Chrome, click the shield icon on the right side of the address bar and click Load anyway.
The vSphere Web Client might be inaccessible if you use Internet Explorer
When you try to log in to vCenter Server by using the vSphere Web Client on the same host Windows machine and you use Internet Explorer, the proxy settings of your Internet Explorer browser might prevent the communication between the vSphere Web Client and vCenter Server.
Workaround: Use Google Chrome or Mozilla Firefox as your default browser or access the vSphere Web Client from a remote machine. You can also disable the Internet Explorer enhanced security configuration on the Windows host machine:
1. Log in to the machine on which vCenter Server and the vSphere Web Client are installed.
2. Open the Server Manager by navigating to Start > Administrative Tools > Server Manager.
3. In the Security Information pane, click Configure IE ESC.
4. In the Internet Explorer Enhanced Security Configuration window, select the Off radio buttons for both administrators and user groups.
5. Click OK.
When you use vSphere Web Client to install a vCenter Server extension, all visible information it provides is displayed in a non-human readable format
If you install a vCenter Server extension for the first time by using the vSphere Web Client, all visible information it provides is not human readable.
Workaround: After installing a vCenter Server extension, log out of your vSphere Web Client and log back in.
You cannot view the real-time performance data or use the advanced performance charts for an inventory object in the vSphere Web Client
Log in to vCenter Server by using the vSphere Web Client and navigate to an inventory object. Click the Monitor tab and click Performance. When you try to collect real-time statistical data for the inventory object from the Overview performance charts view, the operation fails with an error and no data is displayed. The operation also fails with an error when you attempt to use the Advanced performance charts view. These operations involve sending queries to the vCenter Server instance, but the queries cannot run because you do not have the required privileges on vCenter Server.
Workaround: Ask the Administrator to assign the System.Read privilege to you on the vCenter Server system.
You cannot import OVF files from your local file system if you are logged in to vSphere Web Client with a user name that contains non-ASCII or high-ASCII characters
If you use non-ASCII or high-ASCII characters in your user name to log in to vSphere Web Client, you cannot select the option to import OVF files from your local storage system.
Workaround: Log in to vSphere Web Client by using a different user name that does not contain non- ASCII or high- ASCII characters.
When you migrate the storage of a virtual machine, the vSphere Web Client allows you to select an unsupported format for pRDM disk conversion
You migrate the storage of a virtual machine that has a raw device mapping disk in physical compatibility mode (pRDM) by using the Migration wizard of the vSphere Web Client. In the Advanced view of the Select storage page, for the pRDM disk you can configure a target disk format that is different from Same format as source without any compatibility warnings if you do not change the target datastore.
Converting a pRDM disk to a format different from the source is not supported. The migration is misleadingly shown as successful. The pRDM disk is not converted to the selected target format.
Workaround: None.
Unable to log in to the vSphere Web Client
If you do not use vSphere Web Client for an hour or longer, your session times out and the following popup message is displayed:
vSphere Web Client session is no longer authenticated. Click OK to attempt a new login.
When you click OK in the dialog, either the same dialog redisplays or an error message such as the following appears:
The vSphere Web Client cannot connect to the vCenter Single Sign-On server.
Workaround: Perform one of the following tasks:
- Open vSphere Web Client in a different browser.
- On the browser you use, delete your browser cookies associated with the vSphere Web Client session. The browser session can be identifies by the IP address of the vCenter Server instance.
Creating a new user fails if the description field contains certain special characters
When creating a new user with the Add New User dialog box in the vSphere Web Client, if you use the characters-- caret (^), less than (<), greater than (>), ampersand (&), percent (%), back quote (‘), or at sign (@), the operation might fail with the following message A vCenter Single Sign-On service error occurred.
Workaround: Avoid using the specified symbols.
Logging in to vSphere Web Client using earlier versions of Internet Explorer 10 or 11 redirects to a link with no information
After logging in to the vSphere Web Client using older versions of IE 10 or 11 on a Windows OS, you are redirected to an incorrect vSphere Web Client link containing no information. On a Windows OS that does not have Microsoft security patch MS14-065 (https://support.microsoft.com/kb/3003057) or is not running the latest versions of IE 10 or 11, the login process fails with a blank screen.
Workaround: Install the security patch from Microsoft or update IE 10 11 to the latest version.
Right-click menus are not usable in the vSphere Web Client on Mac OS with the Firefox browser
When using the vSphere Web Client on a Mac OS with the Firefox browser (versions 34 or later), the right-click menus are not usable because they disappear. A recent upgrade of Firefox results in issue with Flash player, and right-click menus are affected.
Workaround: Perform one of the following workarounds:
- Use Ctrl+left-click to access a right-click menu.
- Instead of using the right-click menu for an object, select the object and use the Actions drop-down menu. This is located in the top title area of the center workspace, next to the selected object's name.
- Use another supported browser or an earlier version of Firefox.
Administrative actions fail with permissions error when you are not a member of the Administrators or Users group
Any user of a subgroup that is a member of the Administrators or Users group has read-only access to administrative views and actions. If the user attempts administrative actions, they fail with an empty screen or one of the following error messages:
You do not have permissions to view this object
You do not have the required privilege for performing this task
Workaround: Add the user name to the Administrators or Users group to perform administrative actions.
Refreshing the Web browser when you are connected to the vSphere Web Client results in a blank display
When using the vSphere Web Client, refreshing the Web browser might result in a persistent blank screen with a spinning gear.
Workaround: Perform one of the following workarounds:
- Close the Web browser and reconnect to the vSphere Web Client on a new Web browser session.
- Delete the session cookies for you web browser.
The vCloud Air vSphere Client plug-in is not available in the vSphere Web Client Home page in vSphere 6.0
The vCloud Air vSphere Client plug-in is not available for install or upgrade in vSphere 6.0. vSphere environments that have a previous vCloud Air vSphere Client plug-in installation cannot access the plug-in when they upgrade to vSphere 6.0.
Workaround: vSphere 6.0 users can manage vCloud Air workloads using the vCloud Air portal at http://vchs.vmware.com.
Launch console fails when the virtual machine name contains non-ASCII or high-ASCII characters
When you click Launch console on a virtual machine with non-ASCII or high-ASCII characters in its name, the console fails to launch and you get the error message:
The console has been disconnected. Close this window and re-launch the console to reconnect.
Workaround: Use the Standalone VMware Remote Console or name virtual machines using ASCII characters during virtual machine creation.
If Network I/O Control is disabled on a vSphere Distributed Switch, attempts to migrate virtual machines that have bandwidth reservation configured by using vMotion fail
Attempts to migrate a virtual machine that is connected to a distributed switch with disabled Network I/O Control and has bandwidth reservation configured fail. Network I/O Control is disabled on all hosts on the switch and none of them can satisfy the bandwidth reservation of the virtual machine. In addition, you cannot change the network resource settings of the virtual machine in the vSphere Web Client if Network I/O Control is disabled.
Workaround: Perform one of the following workarounds :
- If Network I/O Control is still enabled, remove the network bandwidth reservation on all virtual machines that are connected to the switch before you disable Network I/O Control.
- If Network I/O Control is already disabled, enable it again, remove the reservation on the virtual machines, and disable it.
Powered on vApps might appear as powered off in wizards
In wizards where you can select an object, vApps appear powered off even if the vApps are powered on.
Workaround: Find the actual status of a vApp:
1. Minimize the wizard to the Work in Progress area.
2. Navigate to any view containing the vApp to view the vApp's status.
3. Resume the wizard from the Work in Progress area.
Connecting a USB device to a virtual machine fails without error when using the vSphere Web Client on Mac OS X Mavericks 10.9.5 and later
When you connect a USB device to a virtual machine using the vSphere Web Client on Mac OS X Mavericks 10.9.5 and later, the vSphere Web Client displays the device as attached even if the device fails to connect to the virtual machine. Connecting USB devices such as mass storage devices and USB smart card readers using the vSphere Web Client on any Web browser in Mac OS X Mavericks 10.9.5 or later fail.
Workaround: None.
The Use Windows session authentication check box is disabled in the vSphere Web Client when using Internet Explorer 11 on Windows 7 Enterprise
When you use Internet Explorer 11 on Windows 7 Enterprise to connect to the vSphere Web Client, the Use Windows session authentication check box is disabled. The check box is disabled with and without the Client Integration plug-in.
Workaround: Use the fully qualified domain name to connect to the vSphere Web Client:
1. In Internet Explorer, select Tools and then click Internet options.
2. In the Internet Options window, select the Security tab and click Local intranet.
3. Click Sites to open the Local intranet window.
4. In the Local intranet window, click Advanced.
5. Enter the fully qualified domain name of your vCenter Server into the Add this website to the zone text box and click Add.
6. Refresh the Web browser to reload the vSphere Web Client.
Clicking Launch Remote Console in the virtual machine Summary tab in the vSphere Web Client opens a blank browser window
When the VMware Remote Console is not installed and you click Launch Remote Console in the virtual machine Summary tab, a blank browser window opens.
Workaround: Perform one of the following workarounds:
- Download and install the Virtual Machine Remote Console.
- Right-click the virtual machine and select Open Console to use the HTML5 Web console.
- On the virtual machine Summary tab, click on the virtual machine's preview window located above Launch Remote Console.
After completing a task, the vSphere Web Client does not refresh to display the results
When you create, edit, or delete an entity in the vSphere Web Client, the current view does not refresh after the task completes. This might occur in the VMkernel Adapters Networking view, TCP/IP configuration Networking view, and the Virtual SAN Fault Domains view.
Workaround: Perform one of the following workarounds:
- Refresh the vSphere Web Client by clicking the refresh icon.
- Edit the large.inventory.mode setting in the webclient.properties file and restart the vSphere Web Client service. For large vSphere environments, changing the large.inventory.mode setting might impact performance.
When you connect to the vSphere Web Client using Firefox on Windows, you are asked to download the Client Integration Plugin even after the Client Integration Plugin has been installed
After installing the Client Integration Plugin on Windows, the plug-in is not recognized when you connect to the vSphere Web Client using Firefox. You cannot use any Client Integration Plugin functions including Use Windows session authentication to connect to the vSphere Web Client.
Workaround: To resolve this issue, you can try the following:
1. Uninstall Firefox, restart the machine, and install Firefox and the Client Integration Plugin.
2. If the issue occurs after you reinstall Firefox and the Client Integration Plugin, edit Firefox options to import the vmware-localhost certificate:
3. If the issue occurs after you import the certificate into Firefox, create a new user profile using the instructions at https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles#w_creating-a-profile and re-install the Client Integration Plugin.
4. If the issue occurs after a new user profile is created, use Microsoft Internet Explorer or Google Chrome to connect to the vSphere Web Client.
Clicking All Users' Tasks in the vSphere Web Client results in a warning dialogue
When you click All Users' Tasks in the vSphere Web Client Recent Tasks panel, a warning dialogue appears:
The All Users' Tasks view for Recent Tasks is currently disabled. To view tasks for all users, click More Tasks. Administrators can enable All Users' Tasks for Recent Tasks in the webclient.properties file for vSphere Web Client. It is only recommended for small to medium sized inventories and a limited number of concurrent users.
Workaround: Perform one of the following workarounds:
- Click More Tasks in the Recent Tasks panel to view all users' tasks.
- Edit the show.allusers.tasks setting in the webclient.properties file. For large vSphere environments, changing the webclient.properties file might impact performance.
Deploy OVF Template to a host using a vApp template results in an error message
After you launch the Deploy OVF Template wizard on a host and select a vApp template, when you click Next, an error message appears:
An internal error has occurred - Error #1006. Reloading the client is recommended, so as to clear any problems left by this error. Click Yes to reload the vSphere Web Client?
Workaround: Click No and complete the Deploy OVF Template wizard to deploy the vApp.
After a user initiated task has completed, the associated system tasks that are running might fail without updating the task status
The vSphere Web Client Recent Tasks panel might display a user initiated task as completed before system tasks associated with the task are completed. If the associated system tasks fail, the user initiated task fails and the task status in the Recent Tasks panel is not updated.
Workaround: Perform one of the following workarounds:
- Refresh the vSphere Web Client.
- Click More Tasks in the Recent Tasks panel to view all users' tasks in the Task Console.
- Click All Users' Tasks in the vSphere Web Client Recent Tasks panel if All Users' Tasks are enabled.
The Deploy OVF Template wizard in the vSphere Web Client 6.0 cannot proceed further from the Select a resource wizard screen
When you use the vSphere Web Client 6.0 to deploy an OVF template to vCenter Server 5.5 in an environment with both vCenter Server 5.5 and vCenter Server 6.0, the Deploy OVF Template wizard cannot proceed further from the Select a resource wizard screen.
Workaround: Perform one of the following workarounds:
- Use the OVF Tool to deploy the OVF template on vCenter Server 5.5 using the vCenter Server 5.5 endpoint.
- Use the vSphere Web Client 5.5 to deploy OVF templates to vCenter Server 5.5.
- Use the vSphere Client to deploy OVF templates to vCenter Server 5.5.
If the waiting period is more than 180 seconds when you connect or disconnect from the vSphere Web Client, an error message appears
The default load balancer timeout period is 180 seconds. When you connect to the vSphere Web Client, if the waiting period is more than 180 seconds, an error message appears:
A server error occurred, [400] while processing the authentication from SSO.
When you disconnect from the vSphere Web Client, if the waiting period is more than 180 seconds, an error message appears:
This page cannot be displayed.
Workaround: To resolve this issue, enable session persistence on the load balancer. For information about enabling session persistence on the load balancer, see the VMware vCenter Server 6.0 Deployment documentation.
When a user's permissions are changed from Administrator to No Access while using the VMware Remote Console, a error message appears
If a user with Administrator permissions has their permissions changed to No Access while using the VMware Remote Console, an error message appears:
Fatal Application Error: Null pointer dereference(class cui::NullPointerError).
Workaround: Do not change a user's permissions while the VMware Remote Console is running.
After you deploy the vSphere Web Client application server with a custom port, an error message appears when you launch the virtual machine console
When you launch the virtual machine console after deploying the vSphere Web Client application server with a custom port, an error message appears:
The connection has timed out The server at server_ip is taking too long to respond. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer's network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web. Try Again
You have to configure additional settings on vCenter Server, the vSphere Web Client application server, and the firewall when you deploy the vSphere Web Client application server with a custom port. The HTML5 virtual machine console requires these settings to route traffic to the custom port.
Workaround: Edit the vSphere webclient.properties file and restart the vSphere Web Client application server:
1. Locate the webclient.properties file.
2. Edit the file using a text editor and set show.allusers.tasks equal to the custom port number.
3. Restart the vSphere Web Client application server.
4. Configure your firewall to allow outbound TCP connections on the custom port.
The vSphere Web Client displays English when you connect using Internet Explorer configured for Simplified Chinese or Traditional Chinese on Windows
When you connect to the vSphere Web Client using Internet Explorer 10 or 11 configured for Simplified Chinese or Traditional Chinese on Windows 8 or Windows Server 2012, the vSphere Web Client displays English.
Workaround: Perform one of the following workarounds:
- Use Google Chrome or Mozilla Firefox to connect to the vSphere Web Client.
- Reinstall Windows 8 or Windows Server 2012 with only Simplified Chinese or Traditional Chinese configured. Other languages should not be configured.
The default gateway IP address for VMkernel adapters not using the default ESXi TCP/IP stack is incorrect when you connect to a host using the vSphere Client
When you connect to an ESXi host using the vSphere Client 6.0, you cannot view or edit DNS and Routing settings for system or custom TCP/IP stacks. The vSphere Client 6.0 only supports the default TCP/IP stack on ESXi hosts. If you choose a custom or system TCP/IP stack other than the default ESXi TCP/IP stack, when you navigate to Configuration > Networking > Properties > Ports, the IP Settings section will still display the address of the default ESXi TCP/IP stack. Similarly, when you navigate to Configuration > DNS and Routing, the Default Gateways displays the address of the default ESXi TCP/IP stack.
Workaround: Use the vSphere Web Client to view and edit DNS and Routing settings for other system and custom TCP/IP stacks.
Removing vCenter Host Gateway without unregistering it from the Platform Service Controller, leaves an invalid vCenter Host Gateway endpoint in the Platform Service Controller.
vCenter Host Gateway endpoints are selected at random. If you have an invalid endpoint in the Platform Infrastructure Controller, some of the operations with third-party hosts will fail.
Workaround: Unregister all vCenter Host Gateway endpoints which are invalid.
Frequency: Always, when Platform Controller Service has invalid vCenter Host Gateway endpoint.
Attempts to add a third-party host to a cluster that has enabled Enhanced vMotion Compatibility(EVC) or VSAN fail with the following error message: The requested operation is not implemented by the server.
vCenter Host Gateway 6.0 does not support adding a third-party host as part of a cluster, because EVC, VSAN, DRS and HA are not supported on third-party hosts. Attempts to add a third-party host to a cluster fail without any impact on the infrastructure.
Workaround: none.
Frequency: Always, if EVC or VSAN are enabled on the cluster. If none of DRS, HA, EVC, or VSAN is enabled, you can add a third-party host to a cluster.
Attempts to run third-party hosts in maintenance mode fail and return an error message.
When you try to run a third-party host in maintenance mode you see the following message: The requested operation is not implemented by the server. vCenter Host Gateway does not support maintenance mode for third-party hosts.
Workaround: none.
You cannot change the vCenter Host Gateway certificate through the appliance configuration UI.
vCenter Host Gateway supports only PEM certificates. To replace the automatically generated vCenter Host Gateway server certificate, you must access the vCenter Host Gateway appliance command line directly.
Workaround:
1. Verify that SSH is enabled for the vCenter Host Gateway appliance
  1. In a Web browser, log in to the Web interface of the vCenter Host Gateway appliance.
  2. Click the Admin tab.
  3. Select Enable SSH login and click Submit.
2. Upload the new certificate and the key pair to a temporary folder by using a SSH client.
  Filenames must be server.crt and server.key. You can name the folder /tmp.
3. Use a SSH client and log in to the vCenter Host Gateway appliance with administrative credentials.
  ssh <appliance admin>@<appliance address>
4. Copy the files to the correct directory:
  sudo cp /tmp/<filename> /usr/lib/vmware-vchg/wrapper/bin
5. Restart the vCenter Host Gateway server by running the command:
  service vmware-vchg restart.
6. Restart the vCenter Host Gateway web interface by running the command
  service vmware-vchg-wsetup restart.
7. In a web browser log in to the vCenter Host Gateway appliance.
8. Unregister the appliance and register it again.
Attempts to connect to a Hyper-V host with missing port definition result in error.
If you attempt to connect to a Hyper-V on port that is different from the default one, and you did not specify the port, you'll get this message:
Gateway server 'hyperv: ' cannot connect to Workaround: Make sure that your IE 11 browser allows running Scripts and ActiveX controls before you open the vcsa-setup.html.
Cannot install Client Integration Plug-in using the Internet Explorer When you click Install Client Integration Plugin using the Internet Explorer, an error message similar to the following is displayed: Cannot find ‘file:///x:/x:/vcsa/VMware-ClientIntegrationPlugin-6.0.0.exe’. Make sure the path or Internet address is correct.
Workaround: To resolve this issue, run the VMware-ClientIntegrationPlugin-6.0.0.exe from the vCenter Server Appliance folder at: ISO Extracted/mounted Location/vcsa/VMware-ClientIntegrationPlugin-6.0.0.exe
The vCenter Server Appliance installer reports an installation error When you deploy the vCenter Server Appliance with the large with increased disk option selected, the vCenter Server Appliance installer reports an error message similar to the following: Error occurred during installation You also see the following log entry in %AppData%/../Local/VMware/CIP..: + File [Datastore name] XXX/XXXX.vmdk is larger than the maximum size supported by datastore ' Your vmfs partition is below version 5.
Workaround: Upgrade to the VMFS version 5. For details on collecting logs, see KB 2106760.
Error message for wrong user credentials displayed as ESXi and not vCenter Server When migrating if you provide wrong user credentials selecting vCenter Server as the target in the UI instead of ESXi, an error message similar to the following is displayed: Please verify it's an ESXi host and that the credentials are correct. The error message displayed is for ESXi but is applicable for the vCenter Server instance.
Workaround: None. This error message is also applicable for the vCenter Server instance.
VMware Migration Assistant pre-checks take a long time to respond when the database machine is not accessible During migration, in very rare cases, if the database machine is not accessible, the Migration Assistant takes from 10 to 15 minutes to error out. The following error messages are logged in the UpgradeRunner.log file: error: [Errno 10054] An existing connection was forcibly closed by the remote host nnnn-nn-nnT00:09:40.358Z ERROR __main__ Cannot continue upgrade story because of -- General error: error(10054, 'An existing connection was forcibly closed by the remote host') (cause VC_GENERAL_ERROR) nnnn-nn-nnT00:09:40.359Z INFO output.requirements_result_producer Persisting preupgrade result :[ { Note: You might also encounter this issue when performing export operations.
Workaround: To resolve the issue, perform the following steps:
1. Bring the database machine back online.
2. Verify that all the vCenter Server services are running on the source vCenter Server instance.
3. Close the Migration Assistant.
4. Run the Migration Assistant again.
After migration from vCenter Server 5.5 to vCenter Server Appliance 6.0 Update 2, the Virtual SAN health event/alarm daemon might stop working After you migrate from vCenter Server 5.5 to vCenter Server Appliance 6.0 Update 2, the Virtual SAN health event and alarm daemon might stop unexpectedly due to slow start of the VPXD, specific to the migration process. Because the daemon stops, you cannot clean the existing Virtual SAN health alarms in the vCenter Server even after the actual problem is solved and also you cannot trigger new Virtual SAN health events and alarms.
Workaround: To resolve this issue, restart the Virtual SAN health service for the vCenter Server Appliance by logging in to the appliance and running the following command: /etc/init.d/vmware-vsan-health restart
Syslog Server or ESXi Dump Collector installed and configured on the same source vCenter Server 5.5.x machine causes an error in the vCenter Server settings After a successful migration, an error is seen in vCenter Server > Manage > Settings, if the Syslog Server or the ESXi Dump Collector is installed and configured on the same source vCenter Server 5.5.x machine.
Workaround: None.
VMware Migration Assistant fails on Windows vCenter Server 5.5 VMware Migration Assistant on Windows vCenter Server 5.5 with an external Oracle database fails when the ODBC DSN is configured with a non-ASCII or a high-ASCII name.
Workaround: Perform the following steps while vCenter Server service is running:
1. Modify ODBC DSN To view or modify the database server and/or database that vCenter Server is configured to use when using Oracle: Log in to the vCenter Server Windows OS as the Administrator. Navigate to Start > Control Panel > Administrative Tools > Data Sources (ODBC). Click the System DSN tab. Select the Data Source that the vCenter Server system is using. Change DSN by replacing Data Source Name with a name that contains only ASCII symbols. For example: vpxdsn Click OK to confirm change.
2. Change vpxd configuration In Windows Server 2008 and later, the vpxd.cfg file is located at C:ProgramDataVMwareVMware VirtualCentervpxd.cfg. Note: In Windows Server 2003 and later, the vpxd.cfg is located at %ALLUSERSPROFILE%Application DataVMwareVMware VirtualCentervpxd.cfg. Run the following steps to apply the change: Make sure to back up the original file, as the detailed logging fills the disk space very quickly. Revert any changes after troubleshooting is complete. Using a text editor, add these lines to vpxd.cfg file under the <config> element or if they exist, edit the <dsn> element. For example: <vpxd> <odbc> <dsn>vpxdsn</dsn> </odbc> </vpxd> Save the modifications and close the vpxd.cfg file.
Attempts to migrate to vCenter Server Appliance 6.0 Update 2 might fail if vCenter Orchestrator is installed Attempts to migrate a Windows vCenter Server 5.5 instance with an external database that is configured with vCenter Orchestrator (known as vRealize Orchestrator in vSphere 6.0) in the same database to vCenter Server Appliance 6.0 Update 2M on PostgreSQL might fail. The installation reports PostgreSQL firstboot failure and error messages similar to the following are displayed in the PostgreSQL log: nnnn-nn-nn 11:27:09.571 UTC nnnnnnnn.nnnn 0 vco postgres ERROR: INSERT has more expressions than target columns at character 4928 nnnn-nn-nn 11:27:09.571 UTC nnnnnnnn.nnnn 0 vco postgres STATEMENT: insert into VMO_ResourceElementContent values The issue occurs due to the different release cycles of vCenter Orchestrator and vCenter Server. For more information, see KB 2147264.
Workaround: Perform the following steps to prevent the migration of vCenter Orchestrator data by changing the table structure of VMO_ResourceElementContent table: Note: Backup the vCenter Server database before you start the procedure.
1. Log into the vCenter Server external database (MSSQL or Oracle) using the vCenter Server database user
2. Execute the following SQL statement: ALTER TABLE VMO_RESOURCEELEMENTCONTENT DROP COLUMN CHECKSUM;

Content Libraries IssuesImporting an OVF template to content library from URL over HTTPS protocol fails Attempts to import an OVF template to a content library from an URL through HTTPS connection, fail. The imported OVF file appears in status Ready but is inaccessible and you cannot use it for deploying a virtual machine to a host or a cluster. Workaround: Import an OVF template into content library over HTTP protocol. If you cancel an operation related to creating a new VM or vApp from a template in a library a misleading task appears in the Recent Tasks pane If you attempt to create a new virtual machine or a vApp from a template in a content library, but decide to cancel the operation, an Import OVF task appears in the Recent Tasks pane. The Import OVF task eventually times out. Workaround: None. Deleting a library does not delete the content from the datastore if the datastore is currently not accessible You create a content library and select to use datastore as a storage option. If the datastore is removed from the vSphere inventory and later added again, attempts to delete the library succeed, but the library contents remain on the datastore. vSphere Web Client does not display any warning that the library contents remain on the datastore. The same issue occurs if the datastore is inaccessible at the time you delete the content library. Workaround: Delete the contents of the library manually from the datastore. Tasks related to uploading files to a content library fail with an error about the file name being too long If you import a file to a content library, the task might fail with the following error: File open failed: The file name is too long. Workaround: Rename the source file you want to import so it uses fewer than 90 alphanumeric characters. If you are uploading an OVF file, rename both .ovf and the .vmdk files to use fewer than 90 alphanumeric characters each. Non-informative system error is displayed when a task to export a library item fails When you attempt to export a library item, the export task might fail with a general system error. The error message is very generic and does not reveal the cause of the task failure. A possible reason for the failure is that you might not have sufficient permissions to use the destination storage location where you attempted to export the item. Workaround: None. Attempts to import items with special characters in the file name from local file system to a library might fail When you import an item from local file system to a library, if the file name contains special characters (for example: space, percent, non-ASCII characters, and so on), the task fails with a general system error. The error message might contain a reason for the failed task similar to the following: The source or destination may be slow or not responding. Workaround: Rename the item to contain only alphanumeric characters, and import it to the library again. If you import an OVF file, remove any special characters in the name of the OVF file and all the files that are associated with it (such as the .vmdk file). Attempts to deploy virtual machines from VM templates in a library might fail if either the VM template or the resulting virtual machine contains special characters in its name If the name of a VM template contains special characters, deploying a virtual machine from that template might fail. If you deploy a virtual machine from a VM template in a library, and use special characters for the virtual machine name, the deployment might fail. The same behavior occurs if you use vApp templates in a library to deploy vApps in the vSphere inventory. Workaround: Avoid using special characters, such as #, /, _, , &, ^, and %, in the names of templates in a library, or when deploying a virtual machine or vApps from a template, which resides in a library. Synchronizing a library in the vSphere Web Client that is subscribed to a catalog from vCloud Director 5.5 fails You want to create a new library in the vSphere Web Client by subscribing to a catalog from vCloud Director 5.5. While you create the library in the vSphere Web Client, if you select the option to download content only when needed, the creation of the library succeeds, but later, any attempts to synchronize the subscribed library in the vSphere Web Client, or to deploy a template from that library, fail. Workaround: Edit the settings for the subscribed library so that it downloads content immediately instead of downloading content only when needed. Tasks related to uploading or exporting items to a content library might fail with an error message that is not human readable When you attempt to upload or export an item to a content library, if the task fails, the vSphere Web Client might display an error message similar to the following: file.not.exists Workaround: None. Attempts to import eager-zeroed thick or stream optimized VMDK disk file from a disk storage URL to a library backed by datastore fail When you import an eager-zeroed thick VMDK disk file or a stream-optimized VMDK disk file from a disk storage URL (ds:///vmfs/<path>/<name>.vmdk) to a library backed by a datastore, the task fails. The import task fails, when you attempt it from the VMware vCloud Suite API or from the vSphere Web Client. The issue affects importing a VMDK file, or importing an OVF file with an eager-zeroed thick or stream optimized VMDK file. Workaround: Convert the VMDK disk file to the thin provisioned disk format, and import the disk file again. If the VMDK disk was imported as part of OVF file, rename the converted disk file to match the name referenced in the OVF descriptor. Timeout errors when importing or exporting items to library When the server is busy with content transfers, if you are importing multiple items to a library, the items might get queued. If the queued item does not start to upload to the library before the session times out and expires, which is 5 minutes by default, the task fails with a timeout error. The same behavior occurs with tasks related to exporting items from a library. Workaround: To work around such tasks failures, perform one of the following tasks: Change the Content Library Service settings: In the vSphere Web Client, select Administration > System Configuration > Services > Content Library Service On the Manage tab, and click Edit. Change the value for the respective expiration timeout setting to a greater number. For import operations, change the Update Session Expiration Timeout (milliseconds) value. For export operations, change the Download Session Expiration Timeout (milliseconds) value. Wait for at least 2 minutes, and attempt the import or export operation again. Change the Transfer Service settings: In the vSphere Web Client, select Administration > System Configuration > Services > Transfer Service. On the Manage tab, click Edit. Change the value for the Maximum Number of Concurrent Transfers to a greater number, and click OK. Restart the Transfer Service. Note: If you are currently running any item transfers, wait until they are finished, and then change the settings of the services. Creating a content library backed by storage using UNC path fails if the UNC server and the vCenter Server running on Windows are not in the same windows domain The Content Library service running on a Windows server cannot access remote Windows network shares (UNC path) if they are not in the same Windows domain. If you try to create a library and associate it with storage in a UNC path but the UNC server is not in the same Windows domain, the task fails with an error message similar to the following: A specified parameter was not correct: The provided storage backing <unc-server><share-path> for library <library-name> does not exist, the storage backing might be removed, disconnected, or no longer accessible via <unc-server><share-path>. Workaround: Configure the UNC server and the vCenter Server instance that is running on Windows to join the same Windows domain, and attempt to create a library backed by storage in UNC path served by the UNC server. Error #1009 appears when you attempt to export an item from a library to local file system On a Windows machine, you log in to the vSphere Web Client and attempt to export an item from a library to the local file system. While browsing to select a destination folder, if you select any of the predefined Windows folders, after you click the OK button to confirm your selection, the following error appears: TypeError: Error #1009: Cannot access a property or method of a null object reference. For example, some predefined Windows folders are: Libraries, LibrariesVideo, LibrariesMusic, and Favorites. Workaround: Attempt to export the item again, and select a destination folder different than the Windows predefined folders. Assigning tags to content libraries or library items in deployment with multiple vCenter Server systems might fail You are using a deployment with multiple vCenter Server systems, which are registered to one vCenter Single Sign-On domain. By using the vSphere Web Client, you log in to one of the vCenter Server instances in the deployment, and attempt to assign a tag to a library that belongs to the vCenter Server instance you have currently logged in to. The task succeeds. If you attempt to assign a tag to a library that belongs to another vCenter Server instance that you are not logged in to, the task fails. The same behavior occurs with tasks to assign a tag to a library item. Workaround: To successfully assign a tag to a content library or an library item, log in to the vCenter Server instance to which the library belongs. Import and export operations of a library item from a vSphere Web Client that you access over IPv6 by using a static DNS fail You access a vCenter Server instance through the vSphere Web Client over IPv6 from a machine where the DNS name of the vCenter Server is statically resolved by using the hosts file (C:WindowsSystem32driversetchosts). If you attempt to import or export an item from a library in that vSphere environment, the task fails with a general system error. Workaround: Request a system administrator to add an entry on the DNS server for vCenter Server that you use. On the vCenter Server Appliance, you might be unable to upload content to a content library from an IPv6 HTTP server with host name in the HTTP URL If you try to upload content from an HTTP URL that contains a host name of an HTTP server that supports both IPv6 and IPv4, the vCenter Server Appliance might fail to identify the URL with a network unreachable error: Unable to connect to the source. It may be unavailable, there might a network issue, or the vCenter network configuration might prevent access. This problem might occur only on a pure IPv6 environment with the vCenter Server Appliance. Workaround: In the upload URL, use the IP address of the IPv6 server instead of its host name. For example, use http://[fc00:10:147:39::34]/data/xyz/test.ovf as an upload URL instead of http://hostname.companyname.com/data/xyz/test.ovf. vSphere Web Client displays vApp and VM templates as Unknown when you delete their content from a subscribed library For a subscribed library, if you have enabled the option for downloading library content only when needed, when you delete the content of a VM template, the vSphere Web Client displays the VM template as Unknown, and the item becomes unusable. The same behavior occurs for vApp templates in the subscribed library. Workaround: Synchronize the subscribed library. Users with high-ASCII or non-ASCII characters in their usernames cannot import or export items from content libraries If your username has high-ASCII or non-ASCII characters, you cannot import or export items from content libraries. Workaround: Log in with a user name that contains only ASCII characters, or request that your administrator rename your user name to contain only ASCII characters. Deploying VM Template from content library to a third-party host fails with an error in a non-human readable format If you use vCenter Server with vCenter Host Gateway to manage an environment with third-party hosts, when you attempt to deploy a virtual machine from a VM template in a content library to a third-party host, the operation fails with an error such as the following: A general system error occurred: Invalid fault. For example, a third-party host can be Microsoft Hypervisor. The error message is not in human readable format amd does not provide information what caused the task to fail. Workaround: None. Vmware Vcenter Server 6.5 vMotion and Storage vMotion Issues vSphere 6.0 does not support cross vCenter vMotion if a VM belongs to multiple data stores Attempts to migrate a virtual machine that belongs to more than one data store, to a host on a different vCenter Server is not supported in vSphere 6.0. This issue is seen only when you use Change compute resource only as the migrate option. Workaround: Use Change both compute resource and storage as the migrate option. VMware HA and Fault Tolerance IssuesVirtual Machine Fault Tolerance vLockStep interval Status Changed alarm is triggered when you power on a secondary VM in a symmetric multiprocessor (SMP) Fault Tolerance pair When you power on a secondary virtual machine, you might see the following alarm in the Alarms Definitions list: Virtual Machine Fault Tolerance vLockStep interval Status Changed Workaround: Ignore the alarm. It is irrelevant to vSphere 6.0. For a VM with thin-provisioned disks that is protected by legacy Fault Tolerance, storage migration from an NFS datastore to a VMFS datastore disables the FT protection. Storage migration for an FT-protected VM is supported only if legacy FT is used and the VM is powered off. The storage migration operation disables FT protection, migrates the disks, and then re-enables FT. Normally, a VM protected by legacy FT must have eager-zeroed thick-provisioned virtual disks but this requirement is not strictly enforced if the VM is running on an NFS datastore. However, when such a VM undergoes a storage migration to a VMFS datastore, the thick provisioning requirement is enforced on the destination. As a result, the operation fails to re-enable FT protection after migrating the disks and the VM is no longer FT-protected. Storage migrations from one NFS datastore to another or from one VMFS datastore to another do not encounter this issue. Workaround: Perform one of the following workarounds: When you submit the storage migration operation, select the Thick Provision Eager Zeroed option for the destination virtual disk format to ensure that the thick provisioning legacy FT requirement is met. Manually disable FT protection on the VM, perform a storage migration without powering off the VM, and then manually re-enable legacy FT protection. Doing so not only allows live storage migration of the VM, but also ensures that the virtual disks are converted to the eager-zeroed thick-provisioned format automatically during the legacy FT re-enablement. Turning on Fault Tolerance in the vSphere Client results in a configuration error When you turn on Fault Tolerance in the vSphere Client for a virtual machine with more than one virtual CPU, a configuration error occurs. For example, if the virtual machine has two virtual CPUs, you get the following configuration error: The virtual machine has 2 virtual CPUs and is not supported for Fault Tolerance.Workaround: Use the vSphere Web Client to turn on Fault Tolerance for a virtual machine with multiple virtual CPUs. The Start Secondary Fault Tolerance VM task is not shown in the My Tasks panel The Start FT secondary VM task is not shown in My Tasks in the following situations: FT VM is powered on FT is turned on for a powered-on VM The Resume FT task is issued on a VM where FT is disabled Workaround: Change the flag 'show.allusers.tasks' in the webclient.properties file to true. The file is located at: vCenter Server for Windows: C:ProgramDataVMwarevCenterServercfgvsphere-clientwebclient.properties vCenter Server Appliance: /etc/vmware/vsphere-client/webclient.properties Alternatively, view the More Tasks panel where you can see the task and its progress. Datastores affected by PDL are not present in the Datastore under APD or PDL grid in vSphere Web Client When a host experiences a Permanent Device Loss (PDL) condition, the faulty datastore is not shown in the 'Datastore under APD or PDL' grid available in the vSphere Web Client from Cluster > Monitor > vSphere HA. Workaround: Go to Cluster > Monitor > Events. Search the events list for Permanent. The list displays an event that refers to all PDL conditions for hosts in the cluster. A host previously selected as a dedicated failover host cannot be moved out of the cluster In the vSphere Web Client, if you remove a host from the 'Use dedicated failover hosts' list and then change the admission control policy from 'Use dedicated failover hosts' to 'Do not reserve failover capacity', the removed failover host is still visible in the list and cannot be moved out of the cluster. This issue does not affect the functionality of the vSphere HA feature. Workaround: Change the cluster's admission control policy to 'Define failover capacity by reserving a percentage of the cluster resources'. This clears the failover hosts list. You can then move the host out of the cluster, and change the admission control policy back to 'Do not reserve failover capacity' if required. After suspending Fault Tolerance and resetting the 'Virtual machine Fault Tolerance state changed' alarm to green, the Primary VM icon does not reflect this change After suspending Fault Tolerance and resetting the 'Virtual machine Fault Tolerance state changed' alarm to green, the Primary VM icon does not show that the virtual machine is no longer protected. The Fault Tolerance panel on the Summary page of the Primary VM does show the VM as Not Protected, which is the correct Fault Tolerance protection state. Also, in the Related Objects tab of the HA cluster, the Secondary VM is present with the expected warning icon and warning status. Workaround: None. The correct Fault Tolerance protection state is shown on the Fault Tolerance portlet on the Primary VM's Summary page. When turning Fault Tolerance on an inaccurate warning is present on the 'Choose host' page When turning Fault Tolerance on, if you select the same shared datastore for the Primary VM and the Secondary VM files, the following warning message is displayed on the 'Select host' page, after you select a host for the Secondary VM: Datastore [Datastore name] is being used for both primary and secondary VM's disks, which is not recommended. Even after you go back to the 'Select datastores' page and select different shared datastores for the Secondary VM's files, the 'Select host' page displays the warning message after you select a host. Workaround: None. An incorrect 'VM Monitoring Sensitivity' value for vSphere HA is displayed in the vSphere Web Client when 'VM Monitoring' is set to 'Use Cluster Settings' If you set 'VM Monitoring' to 'Use Cluster Settings', you see an incorrect value '--' in both the 'VM monitoring sensitivity' drop-down menu and in the 'VM monitoring sensitivity' column of the 'VM Overrides' settings grid, instead of the appropriate cluster setting. This is only a UI presentation issue. vSphere HA uses the correct cluster default settings. Workaround: None. Guest Operating System IssuesGuest OS customization specification created during cloning does not appear in the list of available Guest OS customization specification in the VM provisioning wizard Description: Typically, while cloning a virtual machine or deploying a virtual machine from template, you have the option to create a new customization specification and apply the newly created Guest OS settings to the virtual machine that you want to provision. However, in some cases, you cannot apply the newly created Guest OS customization specification because it is not displayed in the list of available customization specifications in the guest customization page of the VM provisioning wizard. Workaround: Perform the following steps: Minimize the VM provisioning wizard. Click the Global Refresh button to update the list of available customization specification in the VM provisioning wizard. Restore the VM provisioning wizard. ESXi is shown as Guest OS option when you create a new virtual machine When you create a new virtual machine, the Guest OS Version drop-down menu displays the options VMware ESXi 6.x, VMware ESXi 5.x, and VMware ESX 4.x. Running ESXi as a Guest OS and using these OS selections is unsupported. Consult KB 2009916 for a discussion of the constraints and risks. Refer to the VMware Compatibility Guide for the list of supported VMware guest operating systems. Workaround: Do not select these any of these options. Supported Hardware IssuesSensor state is not displayed on Windows The sensor state is not displayed under the Hardware Health tab on the Windows platform. The refresh button does not update the status. Workaround: None. When you run esxcli to get the disk location, the result is not correct for Avago controllers on HP servers When you run esxcli storage core device physical get, against an Avago controller on an HP server, the result is not correct. For example, if you run: esxcli storage core device physical get -d naa.5000c5004d1a0e76 The system returns: Physical Location: enclosure 0, slot 0 The actual label of that slot on the physical server is 1. Workaround: Check the slot on your HP server carefully. Because the slot numbers on the HP server start at 1, you have to increase the slot number that the command returns for the correct result. Auto Deploy and Image Builder IssuesCustom certificates for Auto Deploy are not retained after Auto Deploy upgrade After you upgrade a vCenter Server instance from version 5.x to version 6.0, you also upgrade Auto Deploy. When the upgrade completes, previous custom Certificate Authority certificates for Auto Deploy are not retained because the VMware Certificate Authority issues new certificates for Auto Deploy. Workaround: Configure the custom certificates to the VMware Certificate Authority for Auto Deploy after the Auto Deploy upgrade. The vSphere Client Auto Deploy plug-in might not work When you click the Auto Deploy plug-in icon on the Home page of the vSphere Client, an error message such as the following appears: The web page cannot be found. Workaround: None Miscellaneous IssuesVMware Client Integration Plug-In might not work as expected if you log in to the vSphere Web Client using Firefox 54When you log in to the vSphere Web Client using Firefox 54 and perform tasks related to Client Integration Plug-In, you might encounter issues listed here: Export or import OVF files (.ovf) is not enabled. Upload or download files to datastores is not enabled. Windows Session Authentication (SSPI) login is not enabled. Upload or download to the Content Library is not enabled. Workaround: To work around this issue, you must update the vmware-localhost certificate. Follow these steps: 1. Backup the following files: C:ProgramDataVMwareCIPcsdsslcert.der C:ProgramDataVMwareCIPcsdsslcert.pem C:ProgramDataVMwareCIPcsdsslserver.pem 2. Add section [v3_req] with content subjectAltName = DNS:vmware-localhost, DNS:vmware-plugin at the end of the configuration file. You must add 'vmware-plugin' in case both the Client Integration Plugin and the Enhanced Authentication Plugin are installed. 3. Create a new Certificate Signing Request from an elevated Command Prompt, vmware-csd.exe --install from C:Program Files (x86)VMwareClient Integration Plug-in 6.0 or C:Program FilesVMwareClient Integration Plug-in 6.0. 4. Remove the vmware-localhost certificate from the Trusted Root Certification Authorities store for the local computer, and import the new one you created (C:ProgramDataVMwareCIPcsdsslcert.pem). 5. Add the friendly name 'VMware-CSD Cert' to the new vmware-localhost certificate. NOTE: As a workaround you can also use alternative browsers like the latest versions of Google Chrome or Internet Explorer. vSphere Data Protection configuration fails in vCenter Server Appliance 6.0 Update 2a In vCenter Server Appliance 6.0 Update 2a, the vSphere Data Protection configuration fails. The configuration stops at 70 percent, or the legacy vSphere Data Protection stops working. Workaround: Edit the file /usr/local/avamar/lib/mcsutils.pm Add the following line to the $prefs variable in the mc perl module: '-Dsecurity.provider.rsa.JsafeJCE.position=last ' Restart the mcs service using the following command: mcserver.sh --restart vCenter Hyperic Agent installed on vCenter Server supports SSLv3 on port 2144 SSLv3 is disabled by default in ESXi 6.0 Update 1 and above. However, port 2144 still supports SSLv3 in the older vCenter Hyperic Agents (versions: 5.8.4, 5.8.4.2,5.8.3 and 5.8.2) installed on the vCenter Server. Workaround: None Оlder versions of vSphere Web Client might not detect the latest version of the Client Integration Plug-inОlder versions of vSphere Web Client might not detect the latest version of the Client Integration Plug-in due to changes in the product builds for VMware vCenter Server 6.0 Update 3f that are related to both Client Integration Plug-in and vSphere Web Client. Upgrade to VMware vCenter Server 6.0 Update 3f. To collapse the list of previous known issues, click here. vSphere 6.0!!!! Its GA now. The time has arrived now to download your hot VMware vSphere 6.0 software and it is available to download for public. Download the vSphere 6.0 software by login with your VMware account and Keep your hands dirty by evaluating the all new features of vSphere 6.0. Download the below list of vSphere 6.0 software using the VMware’s donwload page. Login with your My VMware Login if you have an existing account or register one to start your downloads. Standard VMware ESXi 6.0.0 VMware vCenter Server 6.0.0 VMware vSphere Replication 6.0 VMware vRealize Orchestrator Appliance 6.0.1 VMware vSphere Data Protection 6.0 VMware vRealize Operations Manager 6.0.1 Enterprise VMware ESXi 6.0.0 VMware vCenter Server 6.0.0 VMware vSphere Replication 6.0 VMware vSphere Data Protection 6.0 VMware vSphere Big Data Extensions 2.1.0 VMware vRealize Orchestrator Appliance 6.0.1 VMware vRealize Operations Manager 6.0.1 Enterprise Plus VMware ESXi 6.0.0 VMware vCenter Server 6.0.0 VMware vSphere Replication 6.0 VMware vSphere Data Protection 6.0 VMware vSphere Big Data Extensions 2.1.0 VMware vRealize Orchestrator Appliance 6.0.1 VMware vRealize Operations Manager 6.0.1 That’s it. Download all your vSphere 6.0 suite and start evaluating all the great new features released with vSphere 6.0. I hope this is informative for you. Thanks for Reading!!. Be social and share it in social media, if you feel worth sharing it. Vmware Vcenter Server 41 Iso Download Full Other vSphere 6.0 Related Articles: