VMware Cloud Director Availability 4.4.1 | 11 AUG 2022 | Build 20153048 (Product version:

Check for additions and updates to these release notes.

What's new

VMware Cloud Director Availability 4.4.1 includes important resolved issues and updates of third-party libraries that provide security fixes.

Legacy migrations

VMware Cloud Director Availability 4.4.1 supports migrations from legacy vCenter Server versions 5.5 and 6.0. For information about the legacy migrations, see KB 89181.


VMware Cloud Director Availability 4.4.1 supports an in-place upgrade directly from versions 4.4, 4.3.1, and 4.2.1. When upgrading from earlier versions, first upgrade to either version 4.3.1 or 4.2.1, then upgrade to version 4.4.1.

For more information, see Upgrading in the cloud and Upgrading on-premises.

Configuration maximums

For the tested uptime, concurrency, and scale limits, see VMware configuration maximums.

Caveats and limitations

  • The VMware Cloud Director Availability vSphere Client Plug-In requires vSphere Client support. When using an earlier vSphere version:

    • To configure replications, use the VMware Cloud Director Availability Tenant Portal.

    • Alternatively, in VMware Cloud Director use the VMware Cloud Director Availability plug-in.

  • In sites backed by VMware Cloud Director, users only members of the VRADMINISTRATOR group in vSphere cannot use the VMware Cloud Director Availability vSphere Client Plug-In.

    • To use the plug-in, the users must be members of the Administrators group in vSphere.

For interoperability between paired sites with mismatching VMware Cloud Director Availability versions, see Managing pairing withcloud sites backed by VMware Cloud Director.

For interoperability between VMware Cloud Director Availability and other VMware products, see the VMware product interoperability matrix.

Resolved issues

The following issues have been resolved in this release.

  • Cannot select source vCenter Server instances in outgoing replications for vSphere DR and migration

    For vSphere DR and migration, when creating a replication from a source site with multiple vCenter Server instances, the Outgoing Replication wizard shows no source vCenter Server inventory selection. As a result, the wizard only shows the virtual machines from a single of the source vCenter Server instances.

  • Upgrading to 4.4 and skipping 4.3.1 after upgrading from 3.5 does not show the appliance console in vSphere

    After the 4.4 upgrade finishes and the appliance reboots, in vSphere, the virtual machine does not show a blue console that displays the appliance IP, service status, and other information. Instead, the virtual machine console outputs only a blank screen with a blinking cursor.

    This behavior is only visual and does not affect the appliance and its services.

    This issue only occurs when both: this appliance was upgraded once from version 3.0.x or 3.5.x, and then by skipping version 4.3.1 is upgraded to version 4.4. For example, upgrading from:

    • 3.5 -> -> 4.2.1 -> 4.4 does not display the blue console.

    • 3.5 -> -> 4.2.1 -> 4.3.1 -> 4.4 is not affected.

    • -> 4.2.1 -> 4.4 is not affected.

  • Datastore selection slows down when authenticated as a System Organization user

    When you log in with a user that is a member of the System Organization in VMware Cloud Director, the list of datastores populates slowly, cannot be filtered, and has no pagination. 

Known issues

  • Filtering VM replications by Overall Health or Replication State shows an error and no replications

    Attempting to filter the listed VM replications by either of the two columns Overall Health or Replication State does not list any replications and shows an error: The operation is not supported.

    Upgrade to VMware Cloud Director Availability 4.5.0.

check-circle-line exclamation-circle-line close-line
Scroll to top icon