VMware has released vCenter 5.5 Update 2 today. Most of the updates are basic product support updates, like support for Microsoft SQL Server 2014 and removing support for IBM DB2. There are a bunch of bug fixes in there as well. For the full list, check here.

One particular change was a bit buried in the release notes and was not mentioned in the blog post, which tries to say it’s not a major change. However, for VMware administrators, this might be the most important change in Update 2 and the reason they will upgrade; In Update 2, you will be able to edit virtual machines with hardware version 10 again!

Since the release of vSphere 5.5 and version 10 of the virtual machine hardware, you were confined to the vSphere Web Client for management of these virtual machines. It’s not a secret that the vSphere Web Client is not up to standards yet when it comes to speed and user experience and many administrators have shunned it after trying it and getting frustrated with it. It does not help that Update Manager is not available in the Web Client and you still need the vSphere Client to push updates.

Who hasn’t seen this message:

vcenter55-vm10-unavailable

I’m very excited to show that this is the new message you get, before the Virtual Machine Properties window pops out and you’re able to change it!

vcenter55u2-vm10-editable

One thing that’s kind of sneaky: if you connect a vSphere Client version 5.5 to a new vCenter 5.5 Update 2, is that the client simply connects. They are compatible, so the client does not prompt you to upgrade. You will not be able to edit VMs of version 10 unless you have upgraded the vSphere client.



Share the wealth!

Leave a Reply

Your email address will not be published. Required fields are marked *