vCenter Server 6.7.0a | MAY 22 2018 | ISO Build 8546234 vCenter Server Appliance 6.7.0a | MAY 22 2018 | ISO Build 8546234 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.0a addresses issues that have been documented in the Resolved Issues and Known Issues sections.

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.0a 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.0a

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.11000-8546234-patch-FP.iso Build 8546234 Download Size 2094.5 MB md5sum 3b95789b6ed40140b42b1ee7d26fcdf4 sha1checksum ef3fabfc4f2d395cde1ec0a206edda933f2d62e2

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.

Attach the VMware-vCenter-Server-Appliance-6.7.0.11000-8546234-patch-FP.iso​ file to vCenter Server Appliance CD or DVD drive. Log in to the appliance shell as root and run the commands given below: 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 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 to vCenter Server 6.7 are not supported.

Resolved Issues

The resolved issues are grouped as follows.

Upgrade to vCenter Server 6.7 might fail with an error Upgrade to vCenter Server 6.7 might fail with an error Failed to check the status of VMware Directory Service because port 11711 is no longer used. VMware Directory Service (vmdir) uses port 11711 in vSphere 5.5. The 11711 port remains in use in vSphere 6.0 and vSphere 6.5 for backward compatibility. In vSphere 6.7, certain upgrade paths still bind vmdir to port 11711 and this fix updates the port to 389 if an LdapPort registry is present. This issue is resolved in this release.

The GUI installer might display one and the same error message caused by firstboot failures during stage 2 of the vCenter Server Appliance upgrade The GUI installer might display one and the same error message caused by firstboot failures during stage 2 of the vCenter Server Appliance upgrade. The message is: The installation of vCenter Server failed due to an internal error . Unique firstboot error messages are generated properly in the /var/log/firstboot directory of the vCenter Server Appliance. However, this issue does not allow the unique messages to propagate to the UI if the upgrade fails. This issue is resolved in this release.

Installation or upgrade to vCenter Server 6.7 might fail with an error "Failed to register Auto Deploy" during firstboot Duplicate versions of OpenSSL in the system environment Path variable might cause vSphere Auto Deploy firstboot to fail on Windows virtual machines. Duplication might result from third-party applications that add OpenSSL to the system path. This issue is resolved in this release.

The vSphere Web Client might stop responding when you try to log in Plug-ins installed on vSphere Web Client 6.7 might cause the vSphere Web Client to stop responding when you try to log in. The issue might also occur in case you installed the plug-ins on an earlier version of the vSphere Web Client and then upgraded to vSphere 6.7. This issue is resolved in this release. If you have followed the steps in KB 54751 to whitelist the compatible plug-ins on vCenter Server 6.7, you must revert the whitelist after patching to vCenter Server 6.7.0a, referring to the same KB.

You might not be able to disable the deduplication or encryption features by using the Allow Reduced Redundancy option in the Configure vSAN wizard in the vSphere Client If you have enabled deduplication or encryption features in a vSAN cluster and you use the Configure vSAN wizard in the vSphere Client to disable the features, if the Allow Reduced Redundancy option is selected, the operation might fail. This issue is resolved in this release. If you are patching from vCenter Server 6.7, make sure that you remove all cached plug-ins, following these steps: Stop the vSphere Client. Remove all cached plug-ins. Remove the working directory of the vSphere Client. Restart the vSphere Client.



In a deployment without Internet connection, the VMware vSAN health service might alert that the Hardware Compatibility List (HCL) database is out of date In a vCenter Server 6.7 deployment without Internet connection, the vSAN health service check vSAN HCL DB up-to-date might be red. This issue is resolved in this release. If you have already encountered the problem, you can either allow online updates or manually update the HCL database. For more information, see https://kb.vmware.com/54945.

Known Issues

The known issues are grouped as follows.

Patch history might be improperly displayed after a you patch to vCenter Server Appliance 6.7.0a by using the vCenter Server Appliance Management Interface After you patch to vCenter Server Appliance 6.7.0a by using the vCenter Server Appliance Management Interface, and run the software-packages list --history command in the appliance shell, the system might not display the full list of applied patches. Workaround: Track patch history in the /var/vmware/applmgmt/patch-history/ directory.

When you start patching to vCenter Server Appliance 6.7.0a, you might be logged out of the vCenter Server Appliance Management Interface When you start a patching operation from vCenter Server Appliance 6.7 to vCenter Server Appliance 6.7.0a by using the vCenter Server Appliance Management Interface, you might be logged out from the interface and lose connectivity. You cannot log in again until the operation completes. Workaround: Wait until the operation completes and log in to the vCenter Server Appliance Management Interface.

Patching of vCenter Server 6.7 on Windows to vCenter Server 6.7.0a might fail with error code 3010 If you reconfigure a vCenter Server 6.7 system on Windows with an Embedded Platform Services Controller and repoint it to an External Platform Services Controller, a patching operation from vCenter Server 6.7 to vCenter Server 6.7.0a might fail with an error Installation of component VMware Directory Service client failed . Workaround: After you reconfigure the vCenter Server 6.7 system to use an External Platform Services Controller, you must reboot the system and then start the upgrade process.

vCenter Server Appliance Management Interface might not display the vCenter Server 6.7.0a patch The vCenter Server Appliance Management Interface might not display the vCenter Server 6.7.0a patch and you might not be able to perform an upgrade. Workaround: If you do not perform a fresh install, but use the vCenter Server Appliance Management Interface to patch your vCenter Server system to vCenter Server 6.7.0a, you must: In the vCenter Server Appliance Management Interface, go to Update > Settings and configure the custom URL to https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/6.7.0.10000.latest/ . Re-try the upgrade.



Known Issues from Earlier Releases

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