check-circle-line exclamation-circle-line close-line

VMware vCenter Server 6.7.0c Release Notes

vCenter Server 6.7.0c |  26 JUL 2018 | ISO Build 9232925

vCenter Server Appliance 6.7.0c | 26 JUL 2018 | Build 9232925

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

vCenter Server 6.7.0c addresses issues that have been documented in the Resolved Issues section. 

Earlier Releases of vCenter Server 6.7

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

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

Patches Contained in This Release

vCenter Server 6.7.0c delivers the following patches. See the VMware Patch Download Center for more information on downloading patches.

Full Patch for VMware vCenter Server Appliance 6.7.0c

Product Patch for vCenter Server Appliance 6.7 containing VMware software fixes.

This patch is applicable to the vCenter Server Appliance and Platform Services Controller Appliance.

For vCenter Server and Platform Services Controller Appliances

Download Filename VMware-vCenter-Server-Appliance-6.7.0.13000-9232925-patch-FP.iso
Build 9232925
Download Size 1998 MB
md5sum fc28fa271c90cf5cdc9816232e652758
sha1checksum ce2d58fc4ac005f49e7a96f00f6df77eb0006f2f

Download and Installation

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

  1. Attach the VMware-vCenter-Server-Appliance-6.7.0.13000-9232925-patch-FP.iso file to vCenter Server Appliance CD or DVD drive.
  2. Log in to the appliance shell as root and run the commands given below:
    1. To stage the ISO:
      software-packages stage --iso
    2. To see the staged content:
      software-packages list --staged
    3. To install the staged rpms:
      software-packages install --staged

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.

Upgrade Notes for This Release

Important: Upgrade and migration paths from vCenter Server 6.5 Update 2 and above to vCenter Server 6.7 are not supported.

Resolved Issues

The resolved issues are grouped as follows.

Upgrade Issues
  • A VMware vCenter Server Appliance using a DNSSEC enabled DNS server might fail to upgrade

    A vCenter Server Appliance using a DNS server with enabled DNSSEC might fail to upgrade, because while resolving the host name, the vCenter Server system might pick the resource record digital signature (RRSIG) of the DNSSEC instead of the IP address.

    This issue is resolved in this release.

  • The GUI installer might become unresponsive while you deploy a vCenter Server Appliance from a Windows host machine

    The GUI installer might become unresponsive while you deploy a vCenter Server Appliance from a Windows host machine after stage 1 of the deployment and you might not be able to move on to stage 2.

    This issue is resolved in this release.

  • Upgrade of an externally deployed VMware Platform Services Controller by using the GUI installer might fail with authentication error

    You might see the error Failed to authenticate with the guest operating system using the supplied credentials while upgrading an externally deployed Platform Services Controller by using the GUI installer.

    This issue is resolved in this release.

Installation Issues
  • Deployment of a second external Platform Services Controller in an existing VMware vCenter Single Sign-On domain might fail with an error

    During the installation of vCenter Server 6.7, you might not be able to deploy a second external Platform Services Controller in an existing vCenter Single Sign-On domain. You might see the following error:

    Failed to validate sso.(log_info() takes 1 positional argument but 2 were given).

    This issue is resolved in this release.

  • Deployment of a Platform Services Controller by using the GUI or CLI installer might fail if you use the backslash special character in a vCenter Single Sign-On password

    If you set a vCenter Single Sign-On password that contains the backslash (\) special character, while you install a Platform Services Controller by using the GUI or CLI installer, the installation might fail. You might see the following error:

    Analytics Service registration with Component Manager failed.

    This issue is resolved in this release.

Miscellaneous Issues
  • The vSphere Certificate Manager utility fails to replace a machine SSL certificate if it contains extra details in the Subject Alternative Name (SAN) field

    The vSphere Certificate Manager utility might fail to replace a machine SSL certificate if you specify additional details in the SAN field, such as sites, IP addresses and common names. With this fix, the vSphere Certificate Manager only checks the system name in the SAN field of machine SSL certificates.

    This issue is resolved in this release.

  • Login to vCenter Server 6.7 systems with smartcard or token might fail

    If you try to log in to a vCenter Server 6.7 system by using a smartcard or token, authentication might fail with the following error:

    Unable to validate submitted credential

    You might see logs similar to:

    [2018-06-02T08:53:07.112Z tomcat-http--20 vsphere.local ad645dff-9edc-4277-a921-f239b816aaad
    ERROR com.vmware.identity.idm.server.ServerUtils] Exception 'com.vmware.identity.idm.IDM
    Exception: Failed in account linking using certificate SAN: 3401943042228SLK@vmw'com.vmware.identity.idm.IDM
    Exception: Failed in account linking using certificate SAN: 3401943042228SLK@vmw...

    This issue is resolved in this release.

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • You cannot add permissions for a user or group beyond the first 200 security principals in an Active Directory domain by using the vSphere Client

    If you grant permissions to a user or group from an Active Directory domain by using the vSphere Client, the search for security principals is limited to 200 and you cannot add users to any principal beyond that list.

    This issue is resolved in this release.

  • Configuring VMware vSphere Update Manager by using the vSphere Client might prompt a user certificate error

    If you configure vSphere Update Manager by using the vSphere Client, the SAN field might be blank in the vpxd-extensions solution user certificate. This prompts an error Server certificate assertion not verified and thumbprint not matched when you first log in to the vSphere Client after you complete the configuration.

    This issue is resolved in this release.

  • After an upgrade to vCenter Server 6.7, you might not be able to access the vSphere Update Manager by using the Sphere Client

    After an upgrade to vCenter Server 6.7, you might not be able to access the vSphere Update Manager by using the Sphere Client due to a race condition in the Java API calls to the user session. You might see the following error:
    VUM failed to authenticate.

    This issue is resolved in this release.

Known Issues from Earlier Releases

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