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

VMware vCenter Server 6.7 Update 1b Release Notes

vCenter Server 6.7 Update 1b | JAN  17 2019 | ISO Build 11726888

vCenter Server Appliance 6.7 Update 1b | JAN 17 2019 | Build 11726888

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

The vCenter Server 6.7 Update 1b release addresses issues 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.

Upgrade Notes for This Release

IMPORTANT: Upgrade and migration paths from vCenter Server 6.5 Update 2d and vCenter Server 6.5 Update 2e to vCenter Server 6.7 Update 1b are not supported.

Patches Contained in This Release

vCenter Server 6.7 Update 1b 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 Update 1b

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.21000-11726888-patch-FP.iso
Build 11726888
Download Size 1933.1 MB
md5sum 9dec0f4580d26fef8186bbb55035e1d7
sha1checksum eae367a6edeb271d0d11e183f202150a3dae492d

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.21000-11726888-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.

Resolved Issues

The resolved issues are grouped as follows.

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.

  • The vpxd service might fail to start if certificates in the TRUSTED_ROOTS store exceed 20

    When certificates in the TRUSTED_ROOTS store on a vCenter Server Appliance pile to more than 20, the vpxd service might fail to start. The vSphere Web Client and vSphere Client display the following error:
    [400] An error occurred while sending an authentication request to the vCenter Single Sign-On server.

    This issue is resolved in this release for the vCenter Server Appliance. With this fix, the TRUSTED_ROOTS store can support up to 30 certificates. 

    The issue is not resolved for vCenter Server for Windows.

  • vCenter Server user permissions might be automatically removed on restart of the vpxd service

    Some vCenter Server user permissions might be automatically removed on restart of the vpxd service with a message similar to Reason: No reason given. You might also see Removing invalid permission logs in /var/log/vmware/vpxd/vpxd.log or %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\vmware-vpx\vpxd.log.

    This issue is resolved in this release.

  • Removing a virtual machine folder from the inventory by using the vSphere Client might delete all virtual machines

    In the vSphere Client, if you right-click on a folder and select Remove from Inventory from the drop-down menu, the action might delete all virtual machines in that folder from the disk and underlying datastore, and cause data loss.

    This issue is resolved in this release.

  • You might see health status warnings for low space in the archive partition

    You might see health status warnings in the Summary tab of the vCenter Server Appliance interface such as File system /storage/archive is low on storage space. Increase the size of disk /storage/archive. You might also see such warnings in the node status in the system configuration settings when using the vSphere Client. System health checks trigger the warning when the partition exceeds the limits specified in the statsMonitor.xml file, but the warning is not indicating a problem, since the archive service automatically cleans old segments, such as WAL history.

    This issue is resolved in this release.

vSAN Issues
  • vSAN UI might be slow when vCenter Server manages a large number of vSAN hosts

    When vCenter Server manages a large number of vSAN hosts, such as 1000 vSAN enabled hosts, the vSAN UI might be slow in rendering data. Furthermore, if you randomly browse various VSAN UI pages about these clusters and hosts, or add or remove hosts, cluster partition might be triggered. This is because vCenter Server might fail to update member info configuration to some hosts due to lacking file handlers for making connections.

    This issue is resolved in this release.

  • Health check warning for vSAN VUM baseline creation failure

    vCenter Server 6.7 Update 1 uses an outdated URL for the release catalog. This URL does not include ESXi 6.7 Update 1 builds. This issue can trigger a health check warning for baseline creation failure.

    This issue is resolved in this release.

Known Issues from Earlier Releases

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