Today, the highly anticipated VMware vSphere 7.0 release is now available for download. With it comes many new features and enhancements that I hope to write about in the near future. Until then, there are several items that you should be aware of before you begin upgrading your environments.
There are so many new features in vSphere 7.0 that a dedicated blog post would be required to cover them all. However, a few key features are:
Per VMware KB78487, the following VMware products are currently not supported by vSphere 7.0. If you use any of these solutions in your environment, you should not upgrade to vSphere 7.0 at this time:
This release of vSphere has removed support for several features. Based on the release notes, the following items have been removed or are no longer supported:
vSphere 7.0 no longer supports the following processors:
The following CPUs are supported in the vSphere 7.0 release, but they may not be supported in future vSphere releases. Please plan accordingly:
vSphere 7.0 is the first release to no longer include the Flash-based vSphere Web Client. This client has been replaced the vSphere Client (HTML5).
It is no longer necessary nor possible to deploy and use an external Platform Services Controller. All PSC services have been consolidated into vCenter Server, and deployment and administration have been simplified.
vCenter Server for Windows has been removed and support is not available. In order to upgrade to vSphere 7.0, you will be required to migrate to the vCenter Server Appliance (VCSA).
Image-based backup and restore for the vCenter Server appliance has been removed and support is not available. Instead, you must use the file-based backup and recovery capabilities included in the vCenter Server Appliance.
The ESXi built-in VNC server has been removed. Users will no longer be able to connect to a virtual machine using a VNC client by setting the
RemoteDisplay.vnc.enable configure to be true. Instead, users should use the VM Console via the vSphere Client, the ESXi Host Client, or the VMware Remote Console, to connect virtual machines. Customers desiring VNC access to a VM should use the VirtualMachine.AcquireTicket(“webmks”) API, which offers a VNC-over-websocket connection. The webmks ticket offers authenticated access to the virtual machine console. For more information, please refer to the VMware HTML Console SDK Documentation.
VMKLinux driver compatibility has been deprecated and removed. vSphere 7.0 will not contain support for VMKLinux APIs and associated VMKLinux drivers.
The Update Manager plugin used for administering vSphere Update Manager has been replaced with the Lifecycle Manager plugin. Administrative operations for vSphere Update Manager are still available under the Lifecycle Manager plugin, along with new capabilities for vSphere Lifecycle Manager.
The following features have been deprecated and will be removed in a future vSphere 7.0 release:
32-bit userworld support has been deprecated. Userworlds are the components of ESXi used by partners to provide drivers, plugins, and other system extensions (distributed as VIBs). Userworlds are not customer accessible.
Integrated Windows Authentication (IWA) is deprecated in vSphere 7.0 and will be removed in a future release.
In a future vSphere release, support for Smart Card Authentication in DCUI will be discontinued. In place of accessing DCUI using Personal Identity Verification (PIV), Common Access Card (CAC), or SC650 smart card, users will be encouraged to perform operations through vCenter, PowerCLI, API calls, or by logging in with a username and password.
Support for Coredump Partitions in Host Profiles has been deprecated. In place of Coredump Partitions, users should transition to Coredump Files.
As with every vSphere release, there is a specific sequence that should be followed when upgrading the various components in your environment. Per VMware KB78221, the sequence for vSphere 7.0 is:
Get Notified of Future Posts