Updating vCenter Server 5.5 to Update 3 fails with the error: Warning 32014. A utility for phone home data collector couldn’t be executed successfully (2134141) | VMware KB

While there are great expectations for vSphere 6.5; we are still taking care of a number of 5.5 sites. This is just a reminder to check on the deploypkg.dll before the 5.5 update 3e upgrades.

Source: Updating vCenter Server 5.5 to Update 3 fails with the error: Warning 32014. A utility for phone home data collector couldn’t be executed successfully (2134141) | VMware KB

VMware KB: NSX for vSphere 6.1.3 is compatible with vSphere 6.0, but new vSphere 6.0 features have not been tested with NSX

VMware KB: NSX for vSphere 6.1.3 is compatible with vSphere 6.0, but new vSphere 6.0 features have not been tested with NSX.

We have been waiting for this update to be released since it was mentioned at PEX in February. Now to get it into the lab!

VMware KB: Default behavior of DRS has been changed to make the feature less aggressive

VMware KB: Default behavior of DRS has been changed to make the feature less aggressive.
VMware has released vCenter Server 5.5 Update 2 version D today. In the release notes, VMware called out that a new configuration parameter has been added to adjust DRS aggressiveness when a host is going into maintenance mode.

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