vCenter Server 6.7 Update 3s | OCT 06 2022 | ISO Build  20540798

vCenter Server Appliance 6.7 Update 3s | OCT 06 2022  | ISO Build 20540798

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 3s, refer to VMware knowledge base article 67077.

Patches Contained in This Release

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

NOTE: vCenter Server 6.7 Update 3s 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-20540798.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 3s

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 20540798
Download Size 2002.7 MB
md5sum a55e49ad4c9ab7f8407b21901dbf7c9c
sha256checksum c87f16fc5f42fc1f34ecc8f612e1e342b0d14b4fe76df091158701feda5a15db

Download and Installation

To find the VMware vCenter Server 6.7 Update 3s 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.

Networking Issues
  • In vSphere environments with Cisco Application Centric Infrastructure (ACI) installed, the vpxd service might become unresponsive

    In vSphere environments with Cisco Application Centric Infrastructure ACI installed, the vpxd service might not properly handle ESXi host local ports and become unresponsive. In the vpxd.log, you see errors such as: ODBC error: (22003) - ERROR: numeric field overflow;.

    This issue is resolved in this release.

Miscellaneous Issues
  • NFC file copy operations intermittently fail in an IPv6 environment

    During NFC copy in IPV6 environment, if IPv6 addresses in the NFC Copy Spec for the source and destination contain uncompressed sequence of zeroes, the spec validation fails because IPv6 addresses do not match with that of the hosts stored values. As a result, the NFC copy and the operation that invoked the NFC copy fail. For example, when you attempt to deploy a template from Content Library. The issue does not affect IPv4 environments.

    This issue is resolved in this release.

  • After update to vCenter Server 6.7 Update 3r, the vpxd service might not start due to lack of disk space, caused by content-library-runtime.log.stdout logs

    After update to vCenter Server 6.7 Update 3r, you might see logs in the content-library-runtime.log.stdout file to grow quickly and cause space shortage in the drive of your vCenter Server installation. As a result, vpxd.cfg might not function properly and the vpxd service cannot start, which makes vCenter Server unresponsive.

    The issue is resolved in this release.

vSAN Issues
  • You cannot change the vSAN storage policy of powered-on virtual machines

    If a powered-on VM has a virtual IDE controller, the hostd service prevents any changes to the device on that controller, including changes in the vSAN storage policy. As a result, when you try to change the storage policy of such a VM, the operations fails with a message in the vSphere Client such as:
    The attempted operation cannot be performed in the current state ("Powered on").

    This issue is resolved in this release. The fix makes sure that powered-on VM with an IDE disk can be reconfigured with a new storage policy.

vMotion Issues
  • After a migration operation, Windows 10 virtual machines might fail with a blue diagnostic screen and reports for a microcode revision mismatch

    After a migration operation, Windows 10 virtual machines might fail with a blue diagnostic screen and report a microcode revision mismatch error such as:- MICROCODE_REVISION_MISMATCH (17e)
    The issue occurs when a scan of the CPUs runs during the migration operation and the firmware of the source CPUs does not match with the firmware of the destination CPUs.

    This issue is resolved in this release.

Security Issues
    • cURL is updated to version 7.84.0.
    • The Apache Tomcat server is updated to version 8.5.81.
    • The XStream library is updated to version 1.4.19.
    • The OpenSSL library is updated to version openssl- 1.0.2zf.
    • The Expat XML parser is updated to version 2.4.8.
    • The Sqlite database is updated to version 3.39.0.
    • Jackson is updated to version 2.12.7/2.13.2.
    • Jackson-databind is updated to version 2.12.7/
    • Eclipse Jetty is updated to version 9.4.48.v20220622.
    • The struts2-core library is updated to version 6.0.0.
    • The Oracle (Sun) JRE and JDK package is updated to version
Networking Issues
  • VM clone fails with an error and newly created dvPort remains in vCenter Server database

    If a virtual machine clone spec has the guestinfo.resync.mac.addr key in the extraConfig elements, such as the following:
    <ovf:Info>Virtual hardware requirements</ovf:Info><vmw:ExtraConfig vmw:key="guestinfo.resync.mac.addr"/>, a cloning operation might fail, because in some cases, a value for the key might not pass and remain unset. In the vpxd logs, you see with an error such as vmodl.fault.InvalidArgument and error messages like "A specified parameter was not correct: config.extraConfig["guestinfo.resync.mac.addr"]". As a result, the newly created dvPort for the failed clone remains unused in the vCenter Server database.   

    This issue is resolved in this release. The fix makes sure to remove unused dvPort from the vCenter Server database. If the error persists, you must remove the guestinfo.resync.mac.addr key in the extraConfig elements or set a valid MAC address as value. 

Known Issues

The known issues are grouped as follows.

vMotion Issues
  • You see false alerts that a virtual machine is removed from the inventory while it is migrated

    In rare cases, in the VM events reporting you might see an event Migrating off host followed by a VM removed event during a migration operation between ESXi hosts. As a result, if you use a monitoring tool for vCenter alerts, you might see false alerts that the VM is removed from the inventory, while it is just migrated.

    Workaround: None

Installation, Upgrade and Migration Issues
  • You see error messages for failed protocol updates after a TLS reconfiguration or update operation

    After you complete a TLS reconfiguration or update to a supported TLS version by using the TLS Configuration utility, when scanning vCenter Server TLS endpoints, you might see an error messages such as:
    Service vmcam with endpoint ('localhost', 7476), was not configured correctly to the requested protocol(s) and The update to protocol(s) failed at the end of the console output. However, these messages do not indicate an issue with the TLS reconfiguration or update and the task completes correctly.

    Workaround: Repeat the TLS scan to display the correct output with all services updated. To verify the TLS versions are updated properly, scan enabled TLS versions by using the TLS Configuration utility as described in Enable or Disable TLS Versions on vCenter Server Systems.
    For more information, see VMware knowledge base article Managing TLS protocol configuration for vSphere 6.5/6.7.

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