vCenter Server 7.0.0a | MAY 19 2020 | ISO Build 16189094

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

Earlier Releases of vCenter Server 7.0

Features and known issues of vCenter Server are described in the release notes for each release. Release notes for earlier releases of vCenter Server 7.0 are:

For internationalization, compatibility, installation, open source components and product support notices, see the VMware vSphere 7.0 Release Notes.

Upgrade Notes for This Release

IMPORTANT: Upgrade from vCenter Server 6.7 Update 3g to vCenter Server 7.0.0a is not supported. For more information on vCenter Server versions that support upgrade to vCenter Server 7.0.0a, see VMware knowledge base article 67077.

Patches Contained in This Release

This release of vCenter Server 7.0.0a delivers the following patch. See the VMware Patch Download Center for more information on downloading patches.

Patch for VMware vCenter Server Appliance 7.0.0a

Product Patch for vCenter Server Appliance containing VMware software fixes, security fixes, and third-party product fixes.

This patch is applicable to vCenter Server.

Download Filename VMware-vCenter-Server-Appliance-
Build 16189094
Download Size 5041.4 MB
md5sum 3f25d1e0029474dca2a0dfe1428e4035
sha1checksum 8f09aedcccd44ab1b59995ed9d61cbd36e88062a

Download and Installation

You can download this patch by going to the VMware Patch Download Center and selecting VC from the Select a Product drop-down menu.

  1. Attach the VMware-vCenter-Server-Appliance- file to the vCenter Server Appliance CD or DVD drive.
  2. Log in to the appliance shell as a user with super administrative privileges (for example, root) and run the following commands:
    • To stage the ISO:
      software-packages stage --iso
    • To see the staged content:
      software-packages list --staged
    • To install the staged rpms:
      software-packages install --staged

For more information on using the vCenter Server Appliance shells, see VMware knowledge base article 2100508.

For more information on patching the vCenter Server Appliance, see Patching the vCenter Server Appliance.

For more information on staging patches, see Stage Patches to vCenter Server Appliance.

For more information on installing patches, see Install vCenter Server Appliance Patches.

For issues resolved in this patch see Resolved Issues.

For more information on patching using the Appliance Management Interface, see Patching the vCenter Server Appliance by Using the Appliance Management Interface.

Resolved Issues

The resolved issues are grouped as follows.

vSAN Issues
  • vSphere Lifecycle Manager and vSAN File Services cannot be simultaneously enabled on a vSAN cluster

    In vCenter Server 7.0 systems, if vSphere Lifecycle Manager is enabled on a vSAN cluster, vSAN File Services cannot be enabled on the same cluster and vice versa. 

    With vCenter Server 7.0.0a, the vSAN File Services and vSphere Lifecycle Manager are interoperable. You can enable both services at the same time.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

vSphere Client Issues
  • NEW: You do not see the VLAN ID in the port properties page of a VMkernel network adapter in the vSphere Client

    In the vSphere Client, when you follow the path Host > Add Networking, after you select a VMkernel network adapter and an existing standard switch, in the Port properties page you might not see the VLAD ID. The issue occurs because the VLAN ID component is part of the network-ui module, which is lazy loaded and needs a trigger to refresh.

    Workaround: Go to Host > Configure > Networking > Virtual Switches to trigger the loading of the network ui module and the VLAD ID appears.

Upgrade Issues
  • Patching witness or passive nodes of environments with VMware vCenter Server High Availability enabled might fail

    In environments with vCenter Server High Availability enabled, patching a witness or passive node might fail with a message similar to:
    ​RuntimeError: unidentifiable C++ exception.

    Workaround: Disable vCenter Server High Availability. Apply patches to your vCenter Server system. Re-enable vCenter Server High Availability.

  • After patching your vCenter Server system to vCenter Server 7.0.0a, the TLS version of the VC Storage Clients might revert to the default

    If you have a TLS configuration for the VC Storage Clients service different from the default TLS 1.2 only, the TLS version might revert to the default after patching your vCenter Server system to vCenter Server 7.0.0a.

    Workaround: Use the TLS Configuration utility to enable or disable TLS versions on your vCenter Server system after the update.

Known Issues from Prior Releases

To view a list of previous known issues, click here.

check-circle-line exclamation-circle-line close-line
Scroll to top icon