VMware vCenter Server 6.7 U1b Released

Posted By Rajesh Radhakrishnan January 22 2019

VMware released vSphere 6.7 U1  and vCenter on 2018 and now in 2019 they have released update for vCenter  6.7 U1b .

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 ClientIf 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.
  • The vpxd service might fail to start if certificates in the TRUSTED_ROOTS store exceed 20When 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 100 certificates.

    Note:-The issue is not resolved for vCenter Server on Windows.

  • vCenter Server user permissions might be automatically removed on restart of the vpxd serviceSome 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.
  • Removing a virtual machine folder from the inventory by using the vSphere Client might delete all virtual machinesIn 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.
  • You might see health status warnings for low space in the archive partitionYou 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.

vSAN Issues

  • vSAN UI might be slow when vCenter Server manages a large number of vSAN hostsWhen 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.
  • Health check warning for vSAN VUM baseline creation failurevCenter 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.

Upgrade Note for this Release

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. Also refer the upgrade path and compatibility before performing upgrade

Reference