Skip to content

VMware View Upgrade – Lesson Learned

by on March 12, 2013

Recently a customer upgraded their VMware View and vSphere environments to version 5.1 respectively.  The customer upgraded VMware View first, shut down and then upgraded vSphere 5.1.  Once the vSphere environment was upgraded the customer had to update the self-signed certificate within the connection for VMware vCenter.  The customer had configured the vCenter connection to point to the NETBIOS name of the vCenter Server.  I reproduced the environment in Gotham’s lab.

VMware View connection to vCenter Server (NETBIOS):

Host name

In order to communicate with the updated vCenter server; we need to import the updated vCenter SSL certificate.

vCenter Cert

Upon accepting the certificate we received the following error:

vCenter Cert Error

This was due to the implementation of VMware SSO. At this point we couldn’t do anything; we couldn’t edit the NETBIOS name, delete the vCenter connection, delete the pool assigned, etc. Our only option was to create a new vCenter connection pointing to the FQDN. This worked without any issue; however we then had to recreate the pools that were associated with the vCenter connection.

The only way around this is to update the vCenter connection configuration in VMware View prior to any update of either VMware View or vSphere 5.1. The ability to update the vCenter server address has been disabled in VMware View 5.1. VMware states to use either the FQDN or IP address to connect to vCenter; however this wasn’t a requirement in the past and is something that can be easily overlooked. Unfortunately this customer learned the hard way.

Once we established the vCenter connection from View and recreated the desktop pools, we still needed to clean up the old pools and NETBIOS vCenter configuration. We opened a call with VMware support, who guided us through running ADSI Edit to update the local ADAM database; it was a tedious task. Once we had removed the old desktops and pools, we could remove the NETBIOS vCenter connection.

Moral of the story, if you are running VMware View, prior to the upgrade verify that your vCenter configurations are set to FQDN or IP address.

Comments are closed.

%d bloggers like this: