vCenter Server 6.7 Update 3r | JUN 14 2022 | ISO Build 19832974

vCenter Server Appliance 6.7 Update 3r | JUN 14 2022  | ISO Build 19832974

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 6.7

New features, resolved, 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 upgrade, open source components and product support notices see the VMware vCenter Sever 6.7 Update 1 Release Notes.

Upgrade Notes for This Release

For more information on vCenter Server versions that support upgrade to vCenter Server 6.7 Update 3r, refer to VMware knowledge base article 67077.

Patches Contained in This Release

This release of vCenter Server 6.7 Update 3r delivers the following patch:

NOTE: vCenter Server 6.7 Update 3r does not provide a security patch to update the JRE component of vCenter Server for Windows and Platform Services Controller for Windows. Instead, you must download the VMware-VIM-all-6.7.0-19832974.iso file from VMware Customer Connect. For more information, see Download the vCenter Server Installer for Windows.

Full Patch for VMware vCenter Server Appliance 6.7 Update 3r

Product Patch for vCenter Server Appliance containing VMware software fixes, security fixes, and third-party product fixes (for example, JRE and tcServer).

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-
Build 19832974
Download Size 1993.1 MB
md5sum 3bee5a20bdf195766c808a766e3c0d3b
sha256checksum 18e256509a4ffe2f8df2990dacd68146789abba26b7c28a469655b91ff11faad

Download and Installation

To find the VMware vCenter Server 6.7 Update 3r patch at VMware Customer Connect, from the Select a Product drop-down menu, select VC and from the Select a Version drop-down menu, select 6.7.0, and click Search.

  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 Photon OS updates, see VMware vCenter Server Appliance Photon OS Security Patches

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.

Security Issues
  • vCenter Server 6.7 Update 3r delivers the following security updates:
    • The OpenSSL library is updated to version openssl-1.0.2zd.
    • The Oracle (Sun) JRE and JDK package is updated to version
    • Eclipse Jetty is updated to version 9.4.45.v20220203.
    • The Expat XML parser is updated to version 2.4.7.
    • The libxml2 library is updated to version 2.9.13.
    • cURL is updated to version to 7.81.0.
    • Apache Struts is updated to version 2.5.30.
    • Apache Tomcat is updated to version 8.5.75.
    • Apache log4j is updated to versions 2.12.4 for JDK 7 and 2.17.1 for JDK 8.
Installation, Upgrade and Migration Issues
  • In the Deploy OVF Template wizard, you get an error on vService bindings when you deploy vSphere Replication appliance of version 8.4 and earlier

    If you deploy vSphere Replication appliance of version 8.4 and earlier by using the vSphere Client, you might see a Page Unresponsive error on the vService bindings step in the Deploy OVF Template wizard. Deployment stops and ultimately fails.

    This issue is resolved in this release.

  • You cannot open the vCenter Server appliance GUI installer on a MAC OS

    When you try to open the vCenter Server appliance GUI installer on a MAC OS, you see errors such as Installer is damaged and can't be opened. You should eject the disk image or ovftool cannot be opened because the developer cannot be verified.

    Workaround: See VMware knowledge base article 79416.

Miscellaneous Issues
  • VMware Skyline Health screen shows an error instead of system health info

    In the vSphere Client, when you navigate to Monitor > Skyline Health under a vSAN or vSphere cluster, you see an error such as Unable to query vSphere health information. Check vSphere Client logs for details.. The issue occurs because in certain environments Skyline Health cannot discover the APIs it needs to collect data from the vCenter Server system and ESXi hosts.
    In the analytics service logs, you see errors such as:
    Error while getting the data providers list from: java.lang.IllegalStateException: Unable to locate VAPI URI.

    This issue is resolved in this release.

vSphere HA and Fault Tolerance Issues
  • VM Monitoring does not reset vSphere Fault Tolerance on virtual machines as expected when the guest OS fails

    When you enable VM Monitoring in your vCenter Server system, the Fault Domain Manager might not reset vSphere Fault Tolerance on virtual machines as expected when the guest OS fails.

    This issue is resolved in this release. The fix makes sure that VM Monitoring resets vSphere FT on a virtual machine in case of guest OS failure. 

  • vCenter Server High Availability replication displays an alarm that the replication is out of sync

    In environments with both Auto Deploy and vCenter HA enabled, in the vSphere Client you might see a false alarm for vCenter HA that replication is out of sync. When you set up your vCenter HA environment with an embedded Platform Services Controller, vCenter HA performs replication to ensure that the Passive node is synchronized with the Active node. vCenter HA might misinterpret certain Auto Deploy procedures, such as overwriting Certificate Revocation List (CRL) files, which triggers the false alarm.

    This issue is resolved in this release.

Virtual Machine Management Issues
  • VMware vSphere Storage DRS might schedule large amount of migrations

    In certain environments, you might see series of storage migrations scheduled by the vSphere Storage DRS load balancer without an obvious reason.

    Workaround: This issue is resolved in this release. For earlier versions of ESXi 6.7.x, you can set storage automation level to manual to make sure that even if the load balancer generates recommendations for migration, these do not execute automatically.

  • A Windows VM with virtualization-based security (VBS) fails with a blue diagnostic screen during migration or start/resume

    Only when using the mitigation for CVE-2018-12207 (MCEPSC), the Windows OS of virtual machines with enabled VBS might fail with a blue diagnostic screen during operations such as migration by using vSphere vMotion or start/resume a VM. 

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Auto Deploy Issues
  • PowerCLI cmdlets for vSphere Auto Deploy might throw errors

    In vCenter Server 6.7 Update 3r, cmdlets from the VMware.DeployAutomation module might throw error messages such as No sessionId found or vimSessionKey parameter is missing.

    Workaround: Update your PowerCLI package to 12.6.

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