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.
Today at VMworld Europe, VMware announced vSphere 6.5. This highly anticipated release promises to deliver on several key features and components that have been in the works for some time. Among the anticipated features are native backup and restore of the vCenter 6.5 appliance, the HTML 5 vSphere Client, native HA for the vCenter 6.5 appliance, Update Manager integrated with the vCenter 6.5 appliance. This release also brings VMotion encryption, VM disk level encryption, vSphere integrated Containers, major enhancements to DRS, dramatic improvements to API and automation capabilities with enhancements to REST APIs and CLI’s as well as improvements to the logs and integrated GUI for Auto Deploy, to name a just a few.
For more information on the vSphere 6.5 announcements visit VMware’s vSphere Blog posts:
The vSphere 6.x product page at VMware.com also highlights the product versions and licensing:
With VMworld Europe 2016 underway, expect more announcements from VMware.
This is a terrific FAQ for the vSphere 6 PSC. I suggest you read this and refer to it as you begin to get more familiar with and plan upgrades or deployments of vSphere 6.
This KB article describes how to set the default shell for “root” to bash to facilitate file operations on vCenter 6.x virtual appliances.
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
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