By now, you may have heard, that vSphere 6.7 was released on April 17th which included many new features and enhancements. Customers who are currently on vSphere 6.0 (any version) or 6.5 (GA & Update 1 versions) have a direct upgrade path to vSphere 6.7. Keep in mind that vSphere 5.5 will be reaching its End of Support as of September 19th, 2018. Considering this, customers now have multiple options for upgrading vSphere. Today I would like to introduce vSphere 6.5 Update 2 which now includes backported features from vSphere 6.7.
Note: Upgrading from vSphere 6.5 Update 2 to vSphere 6.7 GA is not supported.
vCenter Server
vCenter Server 6.5 Update 2 now supports Enhanced Linked Mode (ELM) when deployed with an Embedded Platform Service Controller (PSC). This reduces the number of virtual machines to manage as well as removes the need for a load balancer for high availability. Enhanced Linked Mode (ELM) using an Embedded Platform Service Controller supports up to 15 vCenter Server Appliance instances in ELM.
It supports Greenfield deployments or an existing environment which has an existing embedded deployment. An additional embedded deployment can be added for Enhanced Linked Mode after the upgrade to either vSphere 6.5 U2 or vSphere 6.7.

vCenter Server 6.5 Update 2 also includes support for:
- A Windows vCenter Server that has custom HTTP & HTTPS ports are supported during migration to the vCenter Server Appliance.
- Using the TLS Configuration utility to configure SSL tunnels on port 8089.
- Backup and restore to Embedded Linked Mode with replication deployment topology API.
- vMotion and cold migration of virtual machines across vCenter Server versions 6.0 Update 3 and later, also includes VMware Cloud on AWS.
vSphere
Some additional features have been added to vSphere 6.5 Update 2 such as:
- IPv6 support for the Key Management Server (KMS) of VMware vSphere Virtual Machine Encryption (VM Encryption).
- Additional alarms for expiration of KMS certificates, missing hosts, and virtual machine keys.
- Customization of default network ports for the HTTP Reverse Proxy service via the GUI or CLI during the deployment of the vCenter Server Appliance.
- Management of multiple namespaces compatible with the Non-Volatile Memory Express (NVMe) 1.2 specification and enhanced diagnostic log.
- Adding tags to the Trusted Platform Module (TPM) hardware version 1.2 on ESXi using ESXCLI commands.
- New native driver to support the Broadcom SAS 3.5 IT/IR controllers with devices including the combination of NVMe, SAS, and SATA drives.
Upgrades
As noted above, upgrading to vSphere 6.5 Update 2 has limitations. Upgrading to vSphere 6.5 Update 2 from vSphere 5.5 requires a minimum version of vSphere 5.5 Update 3b prior to performing the upgrade.
Conclusion
As you can see, vSphere 6.5 Update 2 enables customers to take advantage of some backported features which were first seen in vSphere 6.7. This post highlighted some of the newest features within this release. For more information and to review other additional features, please review both sets of release notes for vCenter Server 6.5 U2 and ESXi 6.5 U2. My team will be creating some posts covering upgrades of vCenter Server and ESXi Hosts to vSphere 6.5 Update 2, stay tuned. Please do not hesitate to post questions in the comments section of this blog or reach out to me directly via Twitter @vCenterNerd.
Steve Anderson
Is there any hope for those of us on 6.0 VCSA with embedded PSC in Linked Mode that we will get a migration path to ELM? All these “Greenfield Deployment Onlies” are pretty frustrating.
Jack Bailey
Glad you pointed this out: “Note: Upgrading from vSphere 6.5 Update 2 to vSphere 6.7 GA is not supported.”
Before reading this, I would have upgraded to U2, then expected to be able to upgrade to 6.7 at some point. Thanks for the heads-up.
David Stamen
You will be able to upgrade to 6.7 at some point, just not to the current 6.7 GA release.
Matt Gladding
So why exactly can we not upgrade from 6.5 U2 to 6.7 later?
David Stamen
You will be able to. You just cannot currently upgrade to the current 6.7 GA release.
Arcangelo Cardozo
Hi Matt,
Back in time upgrades are not supported (i.e. 6.7 was released prior to 6.5 U2)
Regards,
Arcangelo
Lutragen
Of course, what a splendid site and instructive posts, I surely will bookmark your blog.Best Regards!
Tom
I am getting ready to upgrade from 5.5 to 6.5 in the nweek or two. Currently I have an embedded SSO on 4 linked vCenter servers (Windows), and I want to migrate to 4 VCSAs, all linked. To use the Migration Assistant do I still have to break out SSO externally?
Josh
Having a huge problem with Update 2. I just upgraded last Friday and now my hosts are showing a temperature status warning on my memory modules. They’ve been running for years with no problems until now. I have 5 hosts and every single one does this right after the upgrade so I know it’s not a single hardware problem. This has to do with the software.
Nigel Hickey
Hello Josh,
You should absolutely open a ticket with Global Support Services (GSS) to get the help you require. I am not able to provide technical support via the blog comments, nor would this be of any value to you and your team. Best to raise a ticket so that it can be addressed ASAP. Also please verify that your hardware is on VMware’s HCL for the version of vSphere you have installed (ie; vSphere 6.5 Update 2). Using incompatible hardware can cause unexpected results. – Nigel