VMware KB: Unable to open a virtual machine console using the vSphere Web client in VMware vCenter Server 5.5 update 2

VMware KB: Unable to open a virtual machine console using the vSphere Web client in VMware vCenter Server 5.5 update 2.

This KB article restates an item from the vCenter 5.5 Update 2 release notes:

Virtual machines with HTML 5 console in vSphere 5.5 open connections with http:// instead of https://
When the HTML 5 console is launched on a virtual machine, it uses connections like http:// and web sockets like ws:// instead of secure connections like https:// and wss://.

This release resolves the issue by launching the virtual machine console with secure connection over port 7343 instead of the connection over port 7331.

This was a welcome change, but it introduces a potential connectivity issue for those who don’t read the release notes!

Here is a link to the release notes:  https://www.vmware.com/support/vsphere5/doc/vsphere-vcenter-server-55u2-release-notes.html#networkingissues

Here is the top level KB article for required TCP and UDP ports for vSphere products. Notice the left hand column where the version numbers are listed!
TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components

 

vSphere Client 5.5 Update 2 now has the capability to edit VMs with VM hardware version 10

With the release of vSphere 5.5 Update 2 last week, the vSphere client now has the ability to edit the properties of VMs with hardware compatibility level set to version 10.

With previous versions of the vSphere Client ( aka as the “C# Client”), the following error message is displayed when you attempt to edit a VM with hardware version 10:

You cannot use the vSphere client to edit the settings of virtual machines of version 10 or higher. Use the vSphere Web Client to edit the settings of this virtual machine.

The VMware vSphere Blog article: http://blogs.vmware.com/vsphere/2014/09/using-vsphere-5-5u2-client-edit-settings-virtual-machines-version-10-higher.html describes the capabilities and includes a link with a typo for the following KB article: http://kb.vmware.com/kb/2061336.

For more information on the resolved and known issues with vCenter 5.5 Update 2, see the release notes at: https://www.vmware.com/support/vsphere5/doc/vsphere-vcenter-server-55u2-release-notes.html