September 20, 2012 - Sven Huisman

VMware View upgrade path – not so easy…

A customer is using VMware View 4.5 on ESX 4.1 and wants to upgrade to View 5.1.1 with ESX 5.0 U1. If you take a look at the following interoperability matrix, the upgrade path is not so easy:

The first step is to upgrade the View components to View 4.6.1. the next step is to upgrade ESX to 4.1 U3. Then the View components can be upgraded to View 5.1.1 and the final step is to upgrade the vSphere components to 5.0 U1. With every upgrade step, you have to be careful which component of View you upgrade first. Take a look at the following compatibility matrix for View 5.1 and 5.0:

As you can see, some components are only compatible during the upgrade and some components are not compatible at all. And this is just the 5.1/5.0 matrix. Always doublecheck the versions you are currently running and don’t forget the View clients, which also need to be at a certain version, before you can upgrade.

Alternatively, a new View infrastructure can be build next to the old one. Then the current master image(s) can be copied to the new environment and upgrade the VMware tools and the View agent. Then point the users to the new environment.

As you can see, the latest vSphere version (5.1) is not supported with any version of View at the moment. When the next update of View (5.1.2? 5.2? 5.5?) supports vSphere 5.1, you will first need to upgrade the View components, and then the vSphere components. Updating VMware View is always fun 🙂

Virtual Infrastructure migrate / upgrade / View 5 / View 5.1.1 / VMware View / vSphere /