Part 1: Multistep Upgrade To vCloud Director 9.1

The following describes a scenario of an existing customer environment:

  • VMware vCenter Server 6.0 Build 4541947 based on Microsoft Windows Server 2008 R2 SP1 Build 7601
  • VMware vSphere 6.0 Build Build 5224934
  • VMware NSX 6.2.4 Build 4292526
  • VMware vCloud Director 8.10.1 Build 4655196
  • Databases for vCenter and vCD are located on Microsoft SQL Server2012 Build 11.0.3156.0

This is what the customer wants to go to (from vCD point of view only):

  • VMware NSX 6.4
  • VMware vCloud Director 9.1
  • Database for vCD to be migrated to PostgreSQL 9.5

This post will be divided in part 1 and part 2. So let us start with the upgrade and part 1.

1. Upgrade from vCD 8.10.1 to 8.20

This process is pretty straight forward and did not come up with challenges. But don’t forget to backup / dump your database in case you run into issues and need to roll back. Also take a snapshot or full backup of vCD.

As I do have more or less nothing in the vCD database, the process went through in about ten to fifteen minutes. I have seen customers needing about an hour to startup vCloud Director cell.

2. Upgrade NSX from 6.2.4 to 6.4.0

Do a backup of your configuration data of the NSX Manager before you start. NSX 6.2.4:

After downloading the NSX upgrade file and providing it to the NSX Manager Virtual Appliance Management, it took me about five minutes to upload and upgrade. After the upgrade, restart your NSX Manager.


Once back, we see this:

After this step, you need to upgrade the edges:

This can be done manually with right-click and upgrade in the context of the edge or could also be done by script if you have several edges. After the upgrade you have:

It took me according to vCenter information less than a minute for an Edge upgrade which might be a lot if you have several hundred Edges. The good thing is, that you do not need to upgrade them immediately.



Console Access to VMware vCloud Director might not work after upgrade

When customers upgrade from VMware vCloud Director (vCD) 5.5.6 (or some other version) to f. ex. 8.0.2, they may run into the problem that console access to a virtual machine (VM) in a vApp doesn’t work (you see Disconnected in your browser). In the following, I used my testlab with vCD, Microsoft Server SQL Server (MS SQL), and a Microsoft Windows 7 (MS Win 7) client. By the way, I would recommend using Mozilla Firefox ESR (Extended Support Release). I have linked an ESR Overview and the Download location

There are two ways accessing the console of a VM in vCD:

  1. WebMKSConsole (recommended according to
  2. VMRC (requires VMware CIP and Browsers to use NPAPI)

Let us start.

1. WebMKSConsole

WebMKSConsole with Mozilla Firefox ESR:

Console displays DISCONNECTED – please see the versions involved:

According to you first need to insert some values into the SQL Server database:

As these settings are used for VMRC, you need to change them according to the article mentioned above (or as well):

But you may not be able to access the console. Following describes my steps:

Trust the certificate of the console proxy and with the help of Microsoft Internet Explorer 11 (MS IE), install/import the certificate with the corresponding assistant in Windows.

After you have installed/imported the certificate of the consoleproxy, you should be able to access the console:

WebMKSConsole with Microsoft Internet Explorer 11:

If you are using MS IE as well, you first need to change the database setting:

In MS IE you need to make sure to use compatibility views by adding the website of the consoleproxy. Then access should be fine:


Using VMRC with Mozilla Firefox ESR:

As the database values already exist in our case, we change them:

After restarting Mozilla Firefox ESR, you need to install the Client Integration Plug-in (see for more information):

Next, allow the plug-in:

Access should be fine now:

Using VMRC with Microsoft Internet Explorer 11:

As the database value already exists in our case, we change it:


In my previous post about Google Chrome I already described what you might need to do with your certificates to get connected to the console of a VM in a vApp.

Here you will find a step by step description for Firefox and Adobe Flash Player

Access your vCloud Director Portal:

Adobe Flash Player:


So here you need to configure Firefox to accept the Flash Plugin (enter about:config):

Create a Boolean entry:

Set to true:

After these steps, go ahead connecting to your console port proxy (8443 in my case):

If you see the white and empty browser window, everything is good. Go ahead with downloading and installing the Adobe Flash Player Plugin.

After restarting your browser you are finished:

Google Chrome: Console access to vCloud Director 8.20 via WebMKS

Access to your vCloud Director frontend is working but you may have had the following problem accessing a console of a VM in a vApp:


Assuming you use port 8443 for your console port, you get the following:


Click Advanced:


So let’s go to fix it:

You need to use Internet Explorer to deal with the certificates. So you start like described above. After you continue to the insecure webpage:


You see the Certificate error:


You need to be Administrator to import the certificate. Click on the untrusted certificate, View certificates:


Next is to install it:


Use the wizard:



Click Browse and select Trusted Root Certification Authorities:






After you have restarted your Internet Explorer, connecting again to the console port you see no longer a Certificate error:


Now you go back to Google Chrome, see version used here:


VMware vCenter Server 6.0 Upgrade

You need to plan your upgrade before you start. The following aspects need to be checked (but are not limited to them):

  • UDP / TCP ports used
  • DNS name resolution (Forward, Reverse, Short, FQDN)
  • NTP time services
  • Server certificates
  • Plug-ins
  • Valid backup
  • Additional VMware products (f. ex. vCenter Chargeback, vSphere Auto Deploy) in use?
  • 3rd party products (Cisco Nexus 1000v) in use?
  • Target Deployment Model to be achieved
  • Guest OS
  • Database interoperability
  • Linked Mode in use?
  • Multisite Single Sign-On (manual replication)
  • Document Single Sign-On configuration

If you have changed your server certificates or the server name after installing vCenter server you should fix that before starting the upgrade or you should expect more time to succeed. I have had that two times onsite and it can cost a lot of time. You should use the SSL Automation Tool because it helps you.

Some needful Knowledge Base articles:

Upgrading to vCenter Server 6.0 best practices

VMware Platform Services Controller 6.0 FAQs

Check the VMware vSphere 6.0 Documentation Center:

vCenter Server 5.1 upgrade to vCenter Server 6.0

Let us start with the following complex scenario:

  • VMware vCenter Server 5.1 Update 3 (Build 3070521)
  • Microsoft Windows Server 2008 R2 SP1 (Build 6.1.7601)
  • Microsoft SQL Server 2008 R2 SP3 (Build 10.50.6000.34)
  • Three geographical sites in Europe, Asia and USA
  • VMware vCenter Server, vCenter Single Sign-On, Inventory Service, Orchestrator, and Microsoft SQL Server 2008 R2 SP3 running on VMs 105, 106, 107
  • VMware vSphere Web Client and Update Manager running on VMs 102, 103, 104
  • VMware vCenter Server 5.1 Linked Mode configuration
  • VMware vCenter Server 5.1 Multisite Single Sign-On configuration
  • For each site, a Platform Services Controller is required

It is needed to reconfigure the environment before starting the upgrade process because it would result in an Embedded Deployment Model. For more information on that, check: and

This post is about upgrading from vCenter Server 5.1 Update 3 to vCenter Server 6.0 Update 1 devided in seven parts.

Upgrade vCenter Server 5.1 to vCenter Server 6.0 Part VII

In part seven we upgrade the servers to version 6 update 1.

Upgrade of first VMware vCenter Server 6.0 on sw000105:


1vcup01 1vcup02 1vcup03



For this message, please use and go ahead.


1vcup05 1vcup06 1vcup07


1vcup08 1vcup09 1vcup11


During the upgrade process (which takes quite a while), you can see the changes around the installed services:

1vcup12 1vcup14 1vcup16



Upgrade of second and third vCenter Server 6.0 on sw000106 and sw000107:

On server sw000106:

I only pasted the screenshots differing from the process described above.



On server sw000107:


3vcup01 3vcup02


Upgrade vCenter Server 5.1 SSO Nodes to vCenter Server 6.0 Platform Services Controller (PSC) Part VI

In part six we upgrade the servers to version 6 update 1.

Install first VMware vCenter Server 6.0 Platform Services Controller on sw000108:







Install second and third PSC on sw000109 and sw000110:

On server sw000109:

I only pasted the screenshots differing from the process described above.



On server sw000110:



The next steps describe the installation of the vCenter Server components.