Upgrading vSphere 6.0 U2 to vSphere 6.5d – Part 1

With vSphere 6.5 being GA in November 2016, I thought it’s finally time I upgraded my home lab to this version.

My home lab is currently at vSphere 6.0 U2 using externally load balanced PSC’s with a Management and Payload vCenter appliances in the same SSO domain, the topology as below:


I do not have NSX or vSAN installed in my home lab yet, but there are some KBs which are worth noting before embarking on an upgrade and check the product interoperability matrix.

Important information before upgrading to vSphere 6.5 (2147548)

Best practices for upgrading to vCenter Server 6.5 (2147686)

Update sequence for vSphere 6.5 and its compatible VMware products (2147289)

VMware Product Interoperability Matrices

The PSC 6.5 appliance upgrade is broken into two stages, the first stage is to deploy a new appliance and the second stage is to copy the data from the 6.0 appliance to the new 6.5 appliance. Following the update sequence, I need to upgrade my PSCs first followed by my vCenter appliances then the ESXi hosts.

I’ll assume you know how to download the required ISOs from the VMware website.

Stage 1 – Deploy the new Platform Services Controller Appliance

In stage 1, I will deploy the OVA file of the Platform Services Controller 6.5 appliance. Mount the ISO and navigate to the \vcsa-ui-installer\ directory and then to the required subdirectory for your OS:

  • For Windows OS, go to the win32 subdirectory, and run the installer.exe
  • For Linux OS, go to the lin64 subdirectory, and run the installer
  • For Mac OS, go to the mac subdirectory, and run the Installer.app

Ensure you have a full backup or snapshots of all the required machine before commencing.

I’m running my upgrade from a Windows machine so I will run \vcsa-ui-installer\ win32\installer.exe


Select Upgrade from the vCenter Server Appliance 6.5 Installer


The introduction provides an overview of the stages required to complete the upgrade. Click Next.


Accept the End User License Agreement and click Next


Enter the FQDN of the existing Platform Service Controller, this is the first PSC 6.0 I installed, along with the required credentials. Then enter the ESXi host for the source PSC. Click Next.


Click Yes on the Certificate Warning to continue.


Enter the ESXi host FQDN where you would like the new PSC 6.5 appliance deployed. Click Next.


Click Yes on the Certificate Warning to continue.


Enter the name for the PSC appliance VM and set a root password. Click Next.


Select a datastore for the PSC appliance and if you would like to enable Thin Disk Mode. Click Next.


Now select a network with ephemeral port binding, this is temporary and the new PSC appliance can be moved to another network after the upgrade has completed.

Enter the temporary network identity in the required fields. It’s worth noting at this point that the temporary names and IP addresses used during the upgrade all need to be resolvable by DNS. Once the upgrade has completed, the appliance frees the temporary IP address and assumes the network settings of the source 6.0 appliance.


Review the summary on the Ready to complete stage 1 page, verify the settings and then click Finish


Once the deployment has completed, click Continue to progress to Stage 2. If you close, you can continue with Stage 2 by navigating to the VAMI of the newly deployed PSC appliance, https://psc01tmp.testlab.com:5480

Stage 2 – Copy Data from source Platform Services Controller to the PSC 6.5 appliance

After completing stage 1, you will be taken to stage 2 and the introduction page. Click Next.


A pre-upgrade check will run and display it’s results. The check highlighted below that DRS should not be set to Fully Automated on the cluster where the ESXi host resides during the upgrade process. I configured the DRS Automation Level to manual.


Select if you want to participate in VMware’s Customer Improvement Program (CEIP), click Next


Review the summary information on the “Ready to complete” page, check I have backed up the source Platform Services Controller and all the required data from the database and click Finish


At this point, the installer will display a notice stating the source PSC will be shutdown once the network configuration has been enabled on the new PSC 6.5 appliance. As this is my second upgrade attempt, due to upgrade issues with my first VCSA in part 2 and time constraints, this feature proved very useful to revert back to my vSphere 6.0  home lab for another day or so.

Click OK.


If all goes well, the data should be copied and the source PSC shutdown. The new PSC 6.5 should be powered on and accessible with your source network identity. At this point I rename the VMs in vCenter for convenience.

You now need to upgrade all PSCs in your environment before proceeding to upgrade the vCenter appliances. I followed the same procedure to upgrade my second PSC.


I will continue from here in Upgrading vSphere 6.0 U2 to vSphere 6.5d – Part 2 where I will upgrade my vCenter 6.0 appliances and ESXi 6.0 hosts.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

/> vi Kernel

All things SDDC

Default Reasoning

Construction of sensible guesses when some useful information is lacking and no contradictory evidence is present…


Cloud Automation, vRA, vRO, API and more...

Virtual-Stones Blog

Virtualisation and Cloud Ramblings

Welcome to The Virtually Connected!

All Things Cohesity and VMware Related

%d bloggers like this: