Hot off the digital presses is vSphere 5.5 Update 2. This is a minor update, but with some important supported database updates. It’s great to see SQL Server 2014 now supported. I’m in fact surprised they supported SQL 2014 so fast, so kudos to VMware. Now if we can only get SQL AlwaysOn availability groups supported..maybe someday. You should also take note that SRM 5.8 requires vCenter 5.5 Update 2, so whenever SRM 5.8 comes out be sure to upgrade your vCenter prior to deployment. vSphere 5.5 update 2 also allows the “legacy” C# vSphere client to modify some properties (RAM, Change network port group, Remove devices, vCPU, Mount ISO, Increase disk space, reservations, Edit advanced settings) of HW v10 VMs. Thanks VMware! Full vCenter release notes are here.
vCenter Server database support: vCenter Server now supports the following external databases:
- Oracle 12c. Important: For pre-requisite requirements, see KB 2079443.
- Microsoft SQL Server 2012 Service Pack 1
- Microsoft SQL Server 2014
vCloud Hybrid Service: The vCloud Hybrid Service (vCHS) introduces a new container, Hybrid Cloud Service, on the vSphere Web Client home page. The Hybrid Cloud Service container contains the vCHS installer and the new vCloud Connector installer.
Customer Experience Improvement Program: The vSphere customer experience improvement program is introduced to collect configuration data for vSphere and transmit weekly to VMware for analysis in understanding the usage and improving the product.
And as expected, ESXi 5.5 Update 2 also came out today. No surprise here. The biggest new feature here, and which was revealed at VMworld, is the support for 6TB of RAM in an ESXi host. Not too many people will be running hosts that big, but nice to know VMware has fully tested such monster hosts. For the full ESXi release notes go here.
Each of the release notes has a very long list of resolved issues. So if you are experiencing a particular bug, be sure to see if it has been resolved in 5.5 Update 2. You may just get lucky. These updates include security patches, so better start testing them in your pre-production environments and planning prod updates in the near future. As always, test, test, test before pushing this to production hosts.