Important Update - On Mar 20 2018, VMware VMSA-2018-0004.3 announced that CVE-2017-5715 (Spectre-2) mitigation is now included in the latest patch that you should be using instead of the older patch featured in the original article below. You'll find the newer article here:
- How to easily update your VMware vCenter Server Appliance from 6.5.x to 6.5 Update 1g (VCSA 6.5 U1g) with Spectre mitigation
Article below as it originally appeared.
vCenter Server Appliance 6.5.0d | 18 APRIL 2017 | ISO Build 5318154
vCenter/VCSA 6.5 should be upgraded to 6.5.0d (aka 6.5 b) before upgrading your host(s) to ESXi 6.5.0d.
There's a huge benefit to 6.5.0d, it introduces vSAN 6.6! See also:
- vSAN 6.6 arrives just 6 months after the last big release, baked right into those vSphere 6.5.0d bits that went GA today!
VMware vSAN 6.6 | 18 April 2017 | ISO Build 5310538
Check for additions and updates to these release notes.
Once in a while, things are easy. One of the selling points of making the big move from vCenter + Windows to VCSA (vCenter Server Appliance) has been the ease of VCSA upgrades through the handy VAMI web UI. Emad even calls it sexy, who am I are argue? Yep, works as advertised, just like it did when going from 6.5 to 6.5.0a back in February, and to 6.5.0b in March, and to 6.5.0c just yesterday. This is a very easy upgrade, as shown screen-by-screen walk through below, and in the video below.
- VCSA 6.5.x with Internet access/DNS configured
If your VCSA has no internet access, consider downloading this offline update bundle instead:
- You need to do your homework before upgrading, if you're wondering why, read this.
- Do this VCSA 6.5.0d upgrade in a test environment first! Before attempting, you should be sure to have a full backup, such as the simple native VCSA backup button seen at top-right. You can also use a 3rd party backup solution such as NAKIVO or Veeam.
- At a minimum, do a snapshot (or backup) of this VCSA VM before upgrading, then make sure everything works alright after the upgrade, then remove the snapshot within a few days, to avoid performance degradation.
If you're looking for how you get from 6.0.x to 6.5, that's more of a migration, and the right article for you is over here:
- vSphere 6.5 Core Storage white paper - one home virtualization lab enthusiast's perspective
Dec 07 2016