VMware vsphere FAQ Rollup (21)

196. if VCenter Single sign-on installation fails and is rolled back, the vCenter Server Java Components (JRE) and the vCenter TC Server the component will still be installed (5.5)

Fault Status:

If the single sign-on installation is canceled or fails, the installation rolls back to the pre-installation state, and a message appears stating that the system has not been modified. However, the vcenter Server Java components (JRE) and vcenter TC server components are still installed.

Solution:

Manually remove these components from the Windows Control Panel in programs and features.

197. in the vSphere Web Client and the VCenter Single sign-on Upgrade to version 5.5 after the vCenter Server 5.1 not visible (5.5)

Fault Status:

Assume that you upgrade vsphere single sign-on and vsphere Web Client from version 5.1 to version 5.5, but do not upgrade the VCenter Server system. If you log on to the VSphere Web Client after the upgrade, VCenter Server System version 5.1 will not be visible. This issue applies only to Windows upgrade and does not occur when you upgrade VCenter Server Appliance

Solution:

Restart the VCenter Server system and VSphere Inventory Service ( services.msc). To view the VCenter Server 5.1 checklist, log in as [email protected] . See VMware Knowledge Base article 1003895.

198. in the vSphere Web Client from version 5.1.0 to version 5.5 Error during display 29108 (5.5)

Fault Status:

When you upgrade VSphere 5.1 Web Client to version 5.5, error 29108 appears, prompting you to unregister an existing single sign-on user before installing or upgrading.

Solution:

Click [ OK ] to close the error dialog box. The upgrade process will continue to work as expected.

199. VSphere Client and the VSphere powercli may not be able to connect to vCenter Server 5.5 , and there is a handshake error (5.5)

Fault Status:

After you install on a Windows XP or Windows Server 2003 host, vsphere Client and vsphere powercli may not be able to connect to VCenter Server 5.5 and a handshake error occurs. VSphere 5.5 uses the Open SSL Library, which, for security purposes, is configured by default to accept only connections that use strong cipher suites. On Windows XP or Windows Server 2003, vsphere Client and vsphere powercli do not use a strong cipher suite to connect to VCenter Server. There will be errors on the server side with no matching cipher suite (no matching cipher suite)and handshake errors on the vsphere Client or vsphere powercli side.

Solution:

For Windows Server 2003 or 64-bit Windows XP, apply the Microsoft hotfix that applies to your platform:

x64 platform: Http://hotfixv4.microsoft.com/Windows%20Server%202003/sp3/Fix192447/3790/free/351403_ENU_x64_zip.exe

IA64 platform: Http://hotfixv4.microsoft.com/Windows%20Server%202003/sp3/Fix192447/3790/free/351397_ENU_ia64_zip.exe

I386 platform: Http://hotfixv4.microsoft.com/Windows%20Server%202003/sp3/Fix192447/3790/free/351385_ENU_i386_zip.exe

For Windows XP 32-bit, Windows XP 64-bit, or Windows Server 2003, do one of the following.

Before installing vsphere Client or vsphere powercli on the host, upgrade the Windows operating system to Windows Vista or later.

On the VCenter server host, reduce the implied security by allowing the server to communicate using a weak cipher suite. To do this, include the following in the VCenter Server vpxd.cfg file:
<config>
...
<vmacore>
...
<ssl>
...
<cipherList>ALL</cipherList>
...
</ssl>
...
</vmacore>
...
</config>

VMware vsphere FAQ Rollup (21)