VMware Cloud Director Availability™ 4.1.1 | 13 JUL 2021 | Build 18280930 (Product version:

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

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


VMware Cloud Director Availability 4.1.1 supports an in-place upgrade from versions,, and 4.1.0.

Configuration Maximums

For the tested uptime, concurrency, and scale limits, see VMware Configuration Maximums.

Caveats and Limitations

For interoperability between paired sites with different VMware Cloud Director Availability versions, see Managing Connections Between Cloud Sites.

For interoperability between VMware Cloud Director Availability and other VMware products, see VMware Product Interoperability Matrices

Note: The VMware Cloud Director Availability vSphere Client Plug-In requires vSphere Client support. You can use the VMware Cloud Director Availability Portal if your vSphere environment does not support vSphere Client.

Supported Browsers

VMware Cloud Director Availability 4.1.1 supports the following browsers:

  • Google Chrome 91 and later
  • Microsoft Edge Chromium 91 and later
  • Mozilla Firefox 89 and later
  • Safari 14 and later

Resolved Issues

  • VDC group networks are not visible in vApp Replication Network settings page and in the recovery wizards

    VMware Cloud Director 10.2.0 introduces VDC groups. All of the new networks types will not be listed when configuring vApp Replication Network settings or in the failover, test failover, or migration wizards. This issue affects all VMware Cloud Director Availability 4.x versions.


  • Cannot set a limit of the number of configured replications when incoming protections are disabled

    When creating or editing a replication policy with incoming protections disabled, you cannot save the value of the Limit of the number of configured replications. With incoming protections enabled, this issue does not apply.

    For example, in the Default Policy the incoming protections by default are disabled, and to configure the value for this maxincoming limit, use the OpenApi Client.

  • Cannot assign a policy to an organization or sync with cloud by using the root user account with hundreds OrgVDCs

    If you have VMware Cloud Director 10.1.1 with hundreds of organizations, in multiple cases, VMware Cloud Director Availability shows errors, caused by the VMware Cloud Director response: BadMessageException: 500: Response header too large

    For example: 

    • After you log in as the root user, in the Assign Policy window after selecting a policy and clicking Sync with Cloud, you see Operation aborted due to an unexpected error.
    • Assigning any policy to an organization shows the same error.
    • Each hour, a scheduled task checks for organizations without an assigned policy and assigns the Default policy to them.
    • Updating any policy synchronizes the Default policy and increases the organization count in the Default policy view in time or after any policy is updated. Any organization without policy gets assigned the Default policy.
    • Installing the plug-in in VMware Cloud Director for eligible tenants: when connecting a Cloud Director instance with that many organizations to the Cloud Service during the plug-in install shows the error FailedToPublishPluginException: Unable to publish the vCloud Availability plugin to the eligible tenants. To install the plug-in, in the Cloud Service management interface, under Settings > Service endpoints > VMware Cloud Director Address click Edit, then Apply.
    • Similarly, under Settings clicking Remove plugin shows the error: FailedToUnpublishPluginException: Could not unpublish the vCloud Availability plugin for one or more tenants. The issue is the same and triggers in case any organization is left with the plug-in installed.


  • Cannot create new replications by using the VMware Cloud Director Availability vSphere Client Plug-In from 4.0.x on-premises sites when paired with a 4.1 cloud site

    After pairing an on-premises site running version 4.0.x with a cloud site running version 4.1, you cannot create new migrations or new protections, both incoming or outgoing, from on-premises to cloud or from cloud to on-premises.

    When you attempt to create a replication by using the VMware Cloud Director Availability vSphere Client Plug-In, you cannot complete the wizard and you see an error message that the action is not permitted by the assigned policy. For example,

    Replication policy 'XYZ' does not allow incoming replications to be configured.


  • Attempting to assign a policy when multiple pages of organizations are listed intermittently fails or replaces the existing policy assignments with the Default Policy

    In the Assign Policy dialog box, selecting organizations and clicking Assign, with more than one page of organizations listed, fails with Cannot read property 'id' of undefined or organizations listed on unvisited pages that were assigned with this policy become assigned with the Default Policy instead.

  • Cannot list the destination storage policies with thousands storage profiles

    When creating a replication to a site with several thousands of storage profiles, the destination storage policies cannot be listed and the replication cannot be created.


  • If configuring a replication fails during independent disk creation, this placeholder disk is not cleaned up from VMware Cloud Director

    The placeholder disk leftover is not cleaned up from VMware Cloud Director when configuring a replication fails at the creation of an independent disk. If, for example, the size of the placeholder named disk is larger than any datastore in the target storage policy can accommodate, you see a message Operation aborted due to an unexpected error. This placeholder disk, while consuming storage is not visible by using VMware Cloud Director query APIs and the independent disk in an error state is visible when browsing the destination OrgVDC.


  • Cannot display the MAC addresses in VM view for on-premises to cloud replications

    In VM view, after creating an on-premises to cloud replication, when attempting to change the network settings you cannot see the MAC addresses listed next to the network interfaces.


  • The vSphere Client Plug-in of the on-premises appliance is incompatible with vCenter Server 7.0 Update 3

    After registering VMware Cloud Director Availability On-Premises Appliance 4.0.x or 4.1.0 with vCenter Server 7.0 Update 3, the VMware Cloud Director Availability vSphere Client Plug-in is not operational. In vSphere, clicking the Availability plug-in shows a Service unavailable page.

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