VMware vCloud Automation Center® 6.1 Release Notes

vCloud Automation Center 6.1 | 09 SEP 2014 | Build 2077124

vCloud Automation Center Application Services 6.1 | 09 SEP 2014 | Build 2064245

Updated on: 16 Jan 2015

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

    Migrating a vCloud Automation Center version 5.2.1 or 5.2.2 deployment to version 6.1

    See Migrating to vCloud Automation Center 6.1 in the VMware vCloud Automation Center 6.1 Documentation Center.

    Upgrading from vCloud Automation Center 6.0.1 to 6.1

    To upgrade from vCloud Automation Center 6.0.1 to vCloud Automation Center 6.1, see Upgrading to vCloud Automation Center 6.1 in the VMware vCloud Automation Center 6.1 Documentation Center.

    Platform Support (Updated on: 09 OCT 10)-

    vCloud Automation Center now supports Windows Server 2012 R2 (.NET 4.5.1).

    Improvements in Reporting

    IaaS Chargeback by Allocated Resource by Group report displays cost for blueprint, CPU, memory, storage, days, and totals.

    Bulk Imports

    Machines are imported with defining data such as reservation, storage path, blueprint, owner, and any custom properties. The following administrative tasks are supported:

    • Import one or more unmanaged virtual machines so that they can be managed in a vCloud Automation Center deployment.
    • Migrate one or more managed virtual machines between vCloud Automation Center instances.
    • Make a global change to a virtual machine property, such as a storage path.


    vCloud Automation Center 6.1 offers the following programmatic interfaces for integrating with external systems:

    • Verb-oriented REST API that is fully integrated with SSO by using a bearer token mechanism for authentication of requests
    • Java SDK that provides native Java bindings for the public REST interfaces
    • Command-line tool for developers that supports scripting and interactive API exploration and troubleshooting
    • Reference documentation for the API and scenario-based documentation for common use cases such as submitting a service request, approving a request, listing provisioned items, and so on

    vCenter Orchestrator plug-in for vCloud Automation Center

    The vCenter Orchestrator plug-in for vCloud Automation Center 6.1 includes the following capabilities:

    • Enables workflow developers to call vCloud Automation Center functions from vCenter Orchestrator workflows
    • Exposes inventory and enables entities such as catalog items, requests, entitlements, approvals, blueprints, Advanced Service Designer blueprints, and actions to be used in vCO workflows
    • Enables scripting of vCloud Automation Center maintenance and administration tasks and supports multiple vCloud Automation Center instances simultaneously
    • Enables creation of administration self-service
    • Enables transparent SSO authentication and token handling

    User Interface Enhancements

    The user interface includes the following enhancements:

    • Advanced search
    • Display links in tables
    • Reorder columns
    • Adjustable column width
    • Sort order selection
    • Columns display selection
    • Actions relocated from drop-down menu to toolbar

    vApp Lease Synchronization Between vCloud Director or vCloud Air (formally vCloud Hybrid Service) and vCloud Automation Center

    A new scheduled workflow verifies whether synchronization of the vApp lease length is required between vCloud Automation Center and vCloud Director or vCloud Air. If a lease length conflict is found, the lease value is synchronized to match the lease length defined in vCloud Automation Center. Machines provisioned on a vCloud Director or vCloud Air endpoint are prevented from expiring before the lease period specified in vCloud Automation Center is reached.

    Advanced Service Designer

    Advanced Service Designer includes the following updates:

    • State-Aware resource actions that allow a service architect to define how resource actions such as Discard, Provision, or Change, affect the lifecycle of a resource.
    • vCenter Orchestrator plug-in that enables scripting of vCloud Automation Center, including Catalog, Approvals, Entitlements, Advanced Service Designer, and other entities.
    • Any IaaS resource type can be extended with Advanced Service Designer resource actions.
    • Feedback is provided to the user on the state of their requests.

    Application Services (Formerly VMware vCloud Application Director)

    Application Services, is now a component of vCloud Automation Center 6.1. To upgrade from Application Director 6.0.1 to vCloud Automation Center Application Services 6.1, see Using Application Services in the VMware vCloud Automation Center 6.1 Documentation Center.

    Marketplace access is not available in vCloud Automation Center Application Services 6.1.

    Application Services includes the following updates:

    • Logical network mapping to vCloud Automation Center pre-existing networks
      • Enables Application Services network mapping in a deployment profile to pre-existing networks in vCloud Automation Center reservations
      • Displays network details from vCloud Automation Center to ensure proper selection for the application blueprint
      • Enables mapping pre-existing networks to logical networks for each application
    • Composite deployment profiles let you perform the following actions:
      • Model and manage composite application blueprints
      • Model composite applications by linking Deployment Profiles of separate application blueprints
      • Define the sequence for deployment and property bindings across different blueprints
    • Application Services catalog renamed to Application Services library
    • Enables scale out, scale in, and teardown for regular applications in the vCloud Automation Center service catalog
    • Artifact management
      • Manages the physical build files and other software artifacts required by applications at different stages of deployment.
      • Allows deployment settings to specify artifacts by name only rather than by location, which can change.
    • Leverages new property types, Integer, Boolean, and List of Values, when modeling application services and blueprints that allow user-friendly consumption in the vCloud Automation Center service catalog.
    • Multitenancy
      • Application Services can be registered to a multitenant vCloud Automation Center server
      • Different vCloud Automation Center tenants can be accessed from Application Services by using tenant-based URLs, similar to vCloud Automation Center
      • Application Services dynamically fetches business groups, roles, and users from vCloud Automation Center
    • When Application Services fails a deployment, the user is provided with the following options to resume from deployment errors:

      • Re-execute the last failed component
      • Delete the failed node
      • Edit or review the configuration and resume
    • vCloud Automation Center and Application Services
      • Allows consumers to own a requested application stack, including underlying machines
      • Allows the management of actions for applications in the library
    • Puppet integration
      • Provides actions for puppet-based deployments
      • Enables Windows support for puppet applications
      • Provides tighter Puppet integration by including the following updates:
        • Ability to create multi-tier applications in Windows blueprints
        • Enables deployments to be updated with Puppet content
        • Enables teardown of Puppet deployments to remove registered nodes from the Puppet server
        • Enables scale out and scale in deployments with Puppet content
        • Enables customization of the Puppet agent, which includes the environment variable and the frequency at which the puppet agent runs
        • Enables support up to Puppet Enterprise 3.2.3 and Puppet Open Source 3.6.2
    • Data refresh
      • Duplicates the databases in production without increasing storage costs
      • Refreshes the external database backups in a golden database node, masks data in the golden database, and clones any number of database nodes from the golden database node
    • Deployment

      • Provides the ability to stop an ongoing Application Services deployment
    • Run custom task update

      • Lets users run arbitrary custom tasks in an existing deployment without changing any component properties

    NSX for vSphere Integration

    NSX for vSphere integration includes the following updates:

    • Connectivity
      • Connects the vCloud Automation Center multi-machine service to pre-created NSX for vSphere logical distributed router to optimize for east-west traffic
      • Supports NSX for vSphere edge router, which adds overlapping IP addresses across applications and other benefits
    • Security
      • Isolates multi-machine service to allow traffic only between virtual machines in a multi-machine service as a default option with NSX for vSphere.
      • Selects pre-created NSX for vSphere security policies, including support for NSX for vSphere distributed firewall, NSX for vSphere data security and third-party endpoint and networking security solution, for each component blueprint in multi-machine service. An on-demand security group container is created, and specified security policies are applied at deployment time.
      • Selects NSX for vSphere Security Tags for dynamic NSX for vSphere security group membership, for example, Database servers, PCI, and so on.
    • Availability
      • Provides support for NSX for vSphere load balancer in addition to vCloud Networking and Security load balancer
      • Allows the dynamic creation of on-demand NSX for vSphere load balancer instance in a one-armed model
      • Supports third-party NSX for vSphere Partner Load Balancing services
    • Extensibility
      • All NSX for vSphere and vCloud Networking and Security integration is now through vCenter Orchestrator (vCO) plug-in, including previously released and new functionality
      • Improved extensibility through vCO enablement

      • NSX for vSphere and vCloud Networking and Security vCenter Orchestrator workflows can be defined as actions in vCloud Automation Center Advanced Service Designer.


    Localization support in the user interface depends on your browser settings. See the documentation for your browser for details.

    The following components are localized:

    • Self-service catalog
    • Consumer and administration user interfaces for date, time, number, and currency formats
    • Language preference for notifications

    The following user interface components are not localized:

    • IaaS administrative user interface
    • Application deployment and update forms in Application Services are in English and not the language that is set in the browser
    • vCloud Automation Center Appliance management console

    If the locale selected for the server is different from the locale selected in the browser, a mix of languages appears in the user interface. To avoid seeing multiple languages in the user interface after you log in as an administrator, set the administrator's browser's language to US English.

    The following documents are localized:

    • Release Notes
    • Changes from vCloud Automation Center 5.2
    • Foundations and Concepts
    • Using Application Services

    vClould Automation Center is available in the following languages:

    • Dutch
    • French
    • German
    • Italian
    • Japanese
    • Korean
    • Portuguese (Brazilian)
    • Simplified Chinese
    • Spanish
    • Traditional Chinese
    • Russian
    • US English

    System Requirements and Installation

    For information about supported host operating systems, databases, and Web servers, see the vCloud Automation Center Support Matrix.

    For additional prerequisites and installation instructions, see vCloud Automation Center Installation and Configuration in the VMware vCloud Automation Center 6.1 Documentation Center.


    The vCloud Automation Center documentation set includes updates to support all of the new features and functionality introduced in version 6.1. This includes significant improvements in the installation process to deploy vCloud Automation Center in a distributed configuration, see Distributed Deployment Checklist in the VMware vCloud Automation Center 6.1 Documentation Center.


    To access the full set of vCloud Automation Center 6.1 documentation, go to the VMware vCloud Automation Center 6.1 Documentation Center.

    Resolved Issues

    The resolved issues are grouped as follows:

    Installation and Upgrade

    • Requirement for .NET 4.5 does not extend to .NET 4.5.1
      .NET 4.5.1 is now supported.

      This issue is resolved.

    • After patch upgrade, machines might need to be re-entitled
      When the 6.0.1 upgrade is installed, the entitlement for the action Connect by Using Virtual Desktop is removed for virtual machines.

      This issue is resolved.

    • Upgrading from vCloud Automation Center 6.0 to 6.0.1 resets the specified external vCenter Orchestrator to the embedded vCenter Orchestrator
      When the system administrator (administrator@vsphere.local) configures an external vCenter Orchestrator, the configuration is erroneously reset to the embedded vCenter Orchestrator after the upgrade process completes.

      This issue is resolved.

    • Modifications made to postgresql.conf are lost after upgrade to
      Any modifications that you have made to the storage/db/pgdata/postgresql.conf file are lost when you upgrade from 6.0.1 to Only the VA on which the database is installed is able to access it by using the localhost.

      This issue is resolved.


    • The Windows Preinstallation Environment (WinPE) builder fails to build if the ISO name or path contains high or extended ASCII characters for German and French locales
      The error message "The WinPE ISO failed to build. Please ensure there is enough disk space available for the build." appears if the ISO name or path contains high or extended ASCII characters in German and French locales. The resulting file name contains characters that cannot be read.

      This issue is resolved.

    Advanced Service Designer

    • Advanced Service Designer conditions are not applied to or triggered for fields that contain a defined default value
      When creating a conditional constraint between fields in Advanced Service Designer, the constraint is not triggered if a defined default value must be used when none of the conditions is met. As a result, some auto-calculated fields are not populated with their expected values. This behavior manifests somewhat differently depending on whether a field is added in the vCloud Orchestrator presentation or in Advanced Service Designer. This issue is resolved.

    Configuration and Provisioning

    • Names of custom menu operations are displayed incorrectly on Entitlements page and Actions menu
      When you register a new menu operation created by using vCloud Automation Center Designer, the display name for the new menu option appears in the Blueprint page, but the workflow name (for example, WF Machine Menu 1), rather than the display name, appears in the Entitlements page and the Actions menu in the catalog.

      This issue is resolved.

    • Malformed security token error appears when you suspends and restores client machine
      When a client machine is suspended and then restored after 7 or 8 hours of inactivity, an error message about a malformed security token shell appears.

      This issue is resolved.

    • Hyper-V System Center Virtual Machine Manager (SCVMM) data collection fails on Windows Server 2012
      Data collection fails when using the Microsoft System Center Virtual Machine Manager (SCVMM) on an installation of Windows Server 2012 that has been enabled for IaaS.

      This issue is resolved.

    • Provisioning fails when the VirtualMachine.Host.TpmEnabled custom property is set to True
      Provisioning fails when using the VirtualMachine.Host.TpmEnabled custom property set to True in a blueprint that is used to provision vSphere virtual machines on hosts that are TPM-enabled.

      This issue is resolved.

    • Daily costs for vApps and multi-machine services do not appear in reclamation reports
      vApp and multi-machine container blueprint daily costs are not accounted for in the IaaS reclamation reports. The daily cost values do not appear in the reclamation report savings column.

      This issue is resolved.

    • Approval requests result in an error when the approver is not a member of any business group or is a member of a different business group
      If an approval request is sent to a user who is not a member of the same business group as the requester, or is not a member of any business group, an Exception has been thrown error occurs when the approver clicks View Request on the Approval page. However, the approver should be able to see the request.

      This issue is resolved.

    • Unable to dispose of multi-machine service when orphaned NSX edge is using network
      If an NSX edge is not registered in the vCloud Automation Center environment, probably due to an NSX error, and if that edge is using the external network associated with the routed gateway of a multi-machine service, then an attempt to dispose of that service fails with multiple AppServiceDisposeVM workflow timeouts.

      This issue is resolved.

    • DHCP must be enabled with Private or NAT networks
      If DHCP is not enabled on a Private or NAT network profile within a multi-machine blueprint, the different multi-machine components cannot communicate with each other.

      This issue is resolved.

    • Provisioning of multi-machine blueprint fails if security group is specified as a custom property
      When working with multi-machine services, you cannot add machines to a security group if the security group name is specified as a custom property in the multi-machine blueprint. If you add a machine to a security group whose name is specified as a custom property in the multi-machine blueprint and attempt to provision the machine, the error message Request Failed: (machine name): Failed to assign one or more network and security settings. appears.

      This issue is resolved.

    • Unable to differentiate between the different destroy approval policies
      After navigating to Administration > Approval Policies and clicking the + icon, the different destroy action approval policy types are not classified according to the type of the endpoint.

      This issue is resolved.

    • The custom property, VirtualMachine.Admin.OverrideVncConsole, is deprecated
      The VirtualMachine.Admin.OverrideVncConsole that was used to specify how the consoles of virtual machines are accessed for KVM (RHEV) is no longer supported and was removed from the Custom Properties document. You can no longer select the type of console, and can use only the default of VNC.

      This issue is resolved.

    • A tenant administrator cannot reclaim a machine
      The Change Lease action does not appear to tenant administrators when they attempt to reclaim a machine.

      This issue is resolved.

    • Machines are not properly destroyed in the provisioning platform when prematurely destroyed in vCloud Automation Center
      If you start provisioning a machine in vCloud Automation Center, and before it is completely provisioned you destroy it, the machine might be destroyed and deleted from vCloud Automation Center without any errors or warnings. In some cases, the machine is provisioned in the provisioning platform although it is not under vCloud Automation Center management.

      This issue is resolved.

    • Secure Shell (SSH) connection fails to connect without a fully qualified domain name (FQDN)
      Making an SSH connection without a specified FQDN fails.

      This issue is resolved.

    • The message that appears when a virtual machine import fails is ambiguous
      When a business group manager with fabric administrator rights attempts to import a machine, if the import operation fails, the machine is not deleted from the hypervisor. However, the user event Machine name: has been destroyed! appears. In this situation, the machine is only destroyed in vCloud Automation Center, but remains viable on the hypervisor.

      This issue is resolved.

    • Network configuration is not applied when cloning from a vApp template with network set to "None"
      If a blueprint references a vApp template in vCloud Director or vCloud Air (formerly vCloud Hybrid Service) that has a network set to "None," the vApp is provisioned successfully but does not connect to the network specified in the vCloud Automation Center blueprint or reservation.

      This issue is resolved.

    Known Issues

    The known issues are grouped as follows:

    Known issues not previously documented are marked with the * symbol. A new issue was added to the end of the Configuration and Provisioning section on 16-JAN-2015.

    Installation and Upgrade

    • No message to restart the Identity Appliance after upgrade
      Workaround: Restart the identity virtual appliance after upgrade for identity virtual appliance to work properly.

    • Order of upgrade for vCloud Automation Center and Application Director or IT Business Management, Standard Edition
      If you are using vCloud Automation Center with VMware Application Director or VMware IT Business Management Standard Edition, you must ensure that all products are at the same patch level. Install the vCloud Automation Center upgrade before you install upgrades for Application Director or IT Business Management Standard Edition.

    • The vCloud Automation Center database cannot be installed to a custom directory by using the installation wizard
      In a distributed (custom) installation, the installer ignores changes you make to the default database and log directory. The database and logs are created in the default directory.

      Workaround: To install your database to a non default location, install the database using the DBinstall scripts before installing vCloud Automation Center.

    • Manual clean up is required after a failed installation*
      When you uninstall a partially installed IaaS component and run a new installation, you might see errors similar to the following:

      • The application repository exists.
      • The vcac application pools exist.
      • The 443 port is already in use.

      1. Uninstall IaaS and related components from the Programs and Features box on your Windows server.
      2. Start IIS Manager and delete the repository, vcac, wapi, and vcacreports sites.
      3. Delete vcac application pools from IIS.
      4. From the IIS Manager, remove the port binding to port 443.

    • IaaS Authentication Fails During IaaS Web and Model Management Installation due to an issue in IIS*
      When running the Prerequisite Checker, the message that the IIS authentication check failed because authentication is not enabled appears, but the IIS authentication check box is selected.


      1. Clear the Windows authentication check box.
      2. Click Save.
      3. Select the Windows authentication check box.
      4. Click Save.
      5. Rerun the Prerequisite Checker.

    • Single Sign-On certificate validation fails if the common name contains an uppercase letter*
      When you assign a certificate to a Single Sign-On appliance, all strings are converted to lowercase. Because the validation process is case sensitive, the process fails because the certificate name contains an uppercase letter and the validation process is searching for a name in all lowercase.

      Workaround: When you specify the SSO host address at vCAC Appliance > vCAC Settings > SSO, enter the address with the capitalization used when the certificate was assigned to the SSO appliance.

    • Installation fails when an incorrect host name is specified*
      Installation fails with an error similar to the following:
      Info : 2014-06-17 10 42 32 059 AM : System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'po-va-rtq8c.sqa.local'Cause: Cause: An incorrect name was entered in the VCAC HostName field at vCAC Settings > Host Settings.


      1. Edit the virtual appliance configuration file /etc/sysconfig/network/dhcp to include the correct host name.
      2. Reboot the virtual appliance.
      3. Log in to the virtual appliance management console.
      4. Open the vCAC Settings tab and click Host Settings.
      5. Enter the correct name in the vCAC Host Name text box.
      6. Click Save Settings.
        Note: Do not click Resolve Host Name.
      7. Complete the virtual appliance configuration steps and continue with the installation.


    • Pre-migration erroneously reports that agents are missing in target system
      Pre-migration performs a check to verify that agent names in the source system are present in the target system and it generates a message in the report when there is a mismatch. The pre-migration report might include the message, No matching agent found on the target system. Install an agent with a matching name on the target system, even when a matching agent exists in the target system.

      The message is generated, in error, if a matching agent is present in the target system but that agent has no endpoint configured.

      Workaround: If the message appears in the pre-migration report and a matching agent does exist in the target system, configure an endpoint for the agent in the target system and then rerun pre-migration. Otherwise, ignore the message and configure an endpoint when migration finishes.


    • Guest agent custom scripts that contain unicode characters remain in an infinite loop*
      If you use custom scripts with the guest agent that have unicode characters in the name of the script, the VM is not provisioned and the request remains in an infinite loop.

      Workaround: Do not include unicode characters in the name of your script.

    • Non-ASCII job name for Jenkins artifact repository causes application deployment to fail*
      If you assign a non-ASCII value to the JOB_NAME property of an artifact repository instance that is created from the supplied Jenkins artifact repository specification, and if you then deploy an application with a blueprint that uses an artifact located in that artifact repository instance, the deployment fails with an error message that starts with "Run failed due to failure of task...."

      Workaround: Use only ASCII characters in a Jenkins job name.


    • Various issues exist with vCloud Automation Center and VMware NSX integrations.
      If you are integrating vCloud Automation Center and VMware NSX, see KB 2088172 for more information on how to resolve known issues.

    • IP ranges in routed network profiles are listed as allocated although no IP addresses are in use
      If a multi-machine blueprint contains the routed external network profile but not an assignment for the routed network to component network adapters, machines are provisioned successfully but an IP address range from the routed network profile is allocated and not actually in use.

    • Incorrect network setting displayed for virtual multi-machine component in vCloud Automation Center after network reconfigured in vCenter
      You cannot reconfigure the vCloud Networking and Security (NSX) network of a virtual multi-machine component in vCloud Automation Center. Instead, you must use the vSphere Client to reconfigure the network in vCenter. Note that some network settings for the virtual multi-machine component do not appear correctly in vCloud Automation Center.

      Workaround: Update the network in vCenter Sever to restore proper network settings.

    • vCloud Networking and Security inventory synchronization fails and an error message appears*
      When you delete a transport zone that is assigned to a vCloud Automation Center reservation, a multi-machine blueprint, or a multi-machine instance from the VMware NSX user interface, vCloud Networking and Security inventory synchronization fails and an error message appears. The details of the error message depends on the entity that is using the transport zone.


      1. Unassign the transport zone from the vCloud Automation Center reservation or multi-machine blueprint.
      2. Delete the multi-machine instances provisioned with the transport zone.
      3. Repeat the vCloud Networking and Security inventory synchronization process.

    • Renaming, editing, or viewing an existing VMware vCenter Orchestrator or VMware vSphere endpoint with configured custom properties causes vCloud Automation Center to remove the hidden custom properties from the database*
      Without the endpoint hidden custom properties users cannot run the VMware vCloud Networking and Security plug-in workflows.

      Workaround: Perform data collection process on the endpoint to restore all the hidden custom properties in the database for that endpoint.

    Application Services

    • Unable to publish a blueprint from Application Director to vCloud Automation Center catalog by using vCloud Automation Center 6.1 version
      If you upgrade to vCloud Automation Center 6.1 from 6.0.1 and then attempt to publish a blueprint to the vCloud Automation Center catalog, the error message An unexpected error has occurred. Please contact you system administrator appears. This problem does not occur for newly registered instances of Application Director with vCloud Automation Center 6.1 version.

      Workaround: Unregister Application Director 6.0.1 from vCloud Automation Center 6.1 and then register Application Director again with vCloud Automation Center.

    • Access denied for fabric administrator destroying cross-tenant Physical, Application Service
      Fabric administrators receive an Access Denied message when destroying cross-tenant Physical, Application Service.

    • Workaround: Log in as a fabric administrator of the fabric group in the tenant where the machine resides to destroy it.

    • vCloud Automation Center does not support multiple hosts in the system with the same name
      Data collection updates hosts based on the host name. If two endpoints have identically named hosts, endpoints contend over ownership of the host.

      Workaround: Ensure that all host names are unique.

    • In Application Services, you cannot add a description to a disk in a blueprint canvas*
      If you are using Windows Internet Explorer 11, you cannot add a description to a disk on the Disks tab of a blueprint canvas.

      Workaround: To add a description to a disk in a blueprint canvas, you must use Chrome or Firefox.

    • You cannot update nodes that use Puppet services deployed with Application Director 6.0.1*
      Application Services 6.1 does not support the updating of nodes that use Puppet services that were deployed with Application Director 6.0.1. Application Services 6.1 creates a Puppet node manifest that allows you to update specific services, but it is not compatible with the node manifest files generated in Application Director 6.0.1.

    Advanced Service Designer

    • Unable to find vSphere or vCloud Director virtual machines by unique identifier using the vCenter Orchestrator Plug-In for vCloud Automation Center 6.1 or directly in vSphere API*
      The Workflow Runner helper workflow might fail to locate the VC:VirtualMachine inventory object. As a result, custom workflows invoked by the Workflow Runner workflow might fail with the error: TypeError: Cannot read property "datastore" from null. The VMUniqueID virtual machine entity property is changed from BiosUUID to InstanceUUID.

      Workaround: For more information on how to resolve this issue, see KB 2088838.

    • Number maximum value and String maximum length conditions are not populated from vCenter Orchestrator in the Advanced Service Designer form
      When a service architect creates a blueprint form in Advanced Service Designer and loads a vCenter Orchestrator workflow that contains a number field with an associated maximum value condition or contains a string field with an associated maximum length condition, the restrictions applied to these fields do not appear in the Constraints tab on the blueprint.

      Workaround: The service architect should re-enter the constraints manually as follows:

      1. Click the Edit option for the input parameter.
      2. Click the Constraints tab.
      3. Insert a restriction for the Maximum value if the parameter is a number or Maximum length if the parameter is a string.

    • Cannot create a service blueprint or resource action in the Advanced Service Designer when selecting a workflow that has an input of a string array type with a predefined answers action that could return null*
      In the Advanced Service Designer, during creating a service blueprint or resource action, if you select a vCenter Orchestrator workflow that has an input parameter of a string array type with a predefined answers property in the presentation that calls a scripting action that could return null, when you click Next, the procedure fails and the following error message is displayed:Internal ErrorAn internal error has occurred. If the problem persists, please contact your system administrator.When contacting your system administrator, use this reference: ...

      Workaround: From the Design perspective of the vCenter Orchestrator client, edit the predefined answers action by replacing null with an empty array. For example, if the action scripting code is:

      if (someCondition) {

      return ["a", "b", "c"];

      } else {

      return null;


      You must change the code to:

      if (someCondition) {

      return ["a", "b", "c"];

      } else {

      return [];


    • Unable to refresh submission form fields when requesting some catalog items with detected cyclic dependencies published by using the Advanced Service Designer*
      When all input parameters of a vCenter Orchestrator workflow have OGNL dependencies or validations, if you use this workflow to create and publish a service blueprint, when consumers request the catalog item, the form designer does not refresh the submission form fields because of detected cyclic dependencies. Example for cyclic dependency is when you have two input parameters and the value of every field depends on the value of the other field.

      Workaround: Edit the service blueprint submission form by adding a hidden field.

    • Resource actions for Hyper-V, SCVMM, and XenServer virtual machines might fail if based on resource mapping workflows that query the EXTERNAL_REFERENCE_ID property*
      If you create a resource mapping for a Hyper-V, SCVMM, or XenServer virtual machine based on a resource mapping workflow that queries the EXTERNAL_REFERENCE_ID property, when a resource action runs the workflow, it fails because the EXTERNAL_REFERENCE_ID property is not set in the Properties object passed to the workflow.

      Workaround: When creating resource mapping workflows for Hyper-V, SCVMM, and XenServer virtual machines query one of the other properties that are passed for the individual machines such as name, description, and so on.

    Configuration and Provisioning

    • Attempts to log in as the IaaS administrator with incorrect UPN format credentials fails with no explanation
      If you attempt to log in to vCloud Automation Center as an IaaS administrator with UPN credentials that do not include the @yourdomain portion of the user name, you are logged out of SSO immediately and redirected to the login page with no explanation.

      Workaround: The UPN entered must adhere to a yourname.admin@yourdomain format, for example if you log in using jsmith.admin@sqa.local as the user name but the UPN in the Active Directory is only set as jsmith.admin, the login fails. To correct the problem change the userPrincipalName value to include the needed @yourdomain content and retry login. In this example the UPN name should be jsmith.admin@sqa.local. This information is provided in the log file in the log/vcac folder.

    • Email template customization behavior has changed and extraneous templates are unusable
      In vCloud Automation Center 6.0 or later, only notifications generated by the IaaS component can be customized by using the email template functionality from earlier versions.

      Workaround: You can use the following XSLT templates:

      • ArchivePeriodExpired
      • EpiRegister
      • EpiUnregister
      • LeaseAboutToExpire
      • LeaseExpired
      • LeaseExpiredPowerOff
      • ManagerLeaseAboutToExpire
      • ManagerLeaseExpired
      • ManagerReclamationExpiredLeaseModified
      • ManagerReclamationForcedLeaseModified
      • ReclamationExpiredLeaseModified
      • ReclamationForcedLeaseModified
      • VdiRegister
      • VdiUnregister

      Email templates are located in the \Templates directory under the server installation directory, typically %SystemDrive%\Program Files x86\VMware\vCAC\Server. The \Templates directory also includes XSLT templates that are no longer supported and cannot be modified. For more information about configuring notifications, see Configuring Notifications in VMware vCloud Automation Center Documentation.

    • Access to embedded vCloud Orchestrator server impacted by changes to its administration group
      When the administration group of the embedded vCloud Orchestrator server is changed, the server can no longer be used in embedded mode.

    • Workaround: Use basic authentication to configure the vCloud Orchestrator server as an external server.

    • Actions on provisioned machines are marked complete before they finish
      Actions such as Reprovision or Power Off might appear as Complete on the Requests page when the operation might still be in progress. The actual status of the machine is reflected on the Items page.

    • Guest agent file SCCMPackageDefinitionFile.sms needs to be updated
      The guest agent file SCCMPackageDefinitionFile.sms contains outdated name and publisher information. This does not affect functionality.

    • Lease dates can be changed to fall outside of the Approval Policy value
      Lease dates can be changed by using the Change Lease resource action to a date that is later than the maximum lease range specified on the blueprint.

    • Deleted custom groups are not removed from entitlements*
      When a custom group that is linked to an entitlement is deleted, the custom group is not removed from the entitlement.

      Workaround: To delete a custom group and to remove it from the entitlement:

      1. Remove the custom group from the entitlement.
      2. Delete the custom group.

    • Removing the business group role from a custom group does not revoke entitlements*
      When a custom group that is linked to an entitlement is removed from the business group role, the custom group is not removed from the entitlement.

      Workaround: To remove the business group role from a custom group and to delete it from the an entitlement:

      1. Remove the custom group from the entitlement.
      2. Remove the custom group from the business group role.

    • Hyper-V endpoint is incorrectly listed as an unmanaged machine in Infrastructure Organizer*
      When a Hyper-V endpoint fails to provision, vCloud Automation Center reports the machine as destroyed, but it remains on the endpoint, and appears as an unmanaged machine in Infrastructure Organizer.

    • When provisioning a Citrix XenDesktop/Provisioning Service machine, the machine remains in the Unprovisioning state*
      This issue can occur with the VMware VDI agent, and any version of the VMware EPI agent, such as, Citrix, BMC, Opsware, VBScripts, and so on. It can also occur at various points throughout the master workflow machine provision cycle.

      It is possible that the agent was installed to use a specific server name rather than left blank to handle all third party server requests. If a specific server name is entered, this agent can handle requests only for a server that exactly matches that server name. vCloud Automation Center uses the value in the custom properies EPI.Server.Name or VDI.Server.Name to locate a corresponding agent to handle the request. If no matching agent is found, the machine remains in the EPIRegister/Machine Provisioned state during provisioning, or the Unprovisioning/DeactivateMachine state, until a corresponding agent is found.

      Workaround: Install a new EPI/VDI agent where the server value is exactly what was entered in EPI.Server.Name/VDI.Server.Name, or leave the server name blank.
      Optionally, you can update the agent config file of your current agent and change the server value by completing the following steps.

      1. Back up your agent config file, typically located at C:\Program Files (x86)\VMware\vCAC\Agents\agentName\VRMAgent.exe.config.
      2. Open a text editor as an administrator.
      3. To make the change for any agent type, replace SERVER_NAME_VALUE with your server name, or delete it to leave it blank.
        epiIntegrationConfiguration epiType="CitrixProvisioning" server="SERVER_NAME_VALUE"
        vdiIntegrationConfiguration vdiType="XenDesktop" server=""X
      4. Save your changes.
      5. Restart your agent service.
          1. Click Start > Administrative Tools > Services.
          2. Right-click your desired VMware vCloud Automation Center Agent service, and click Restart.
          3. After the agent restarts successfully, your job continues as expected.

    • XenDesktop machine registration times out if not completed in under 2.5 minutes*
      The value of $regTries in the XenDesktopFunctions script needs to be increased.


      1. Back up your XenDesktopFunctions.ps1 script, typically located at C:\Program Files (x86)\VMware\vCAC\Agents\\Scripts\XenDesktopFunctions.ps1.
      2. Open Notepad as an administrator.
      3. Increase the value in $regTries to the number of minutes you want to wait before registration times out.
        For example, $regTries = 60 sets the time out to 30 minutes.
      4. Save your changes.
      5. Restart your VDI agent service.

    • Approvals that were active before upgrading to 6.1 do not appear after upgrade*
      When you navigate to Inbox > Approvals, the default filter is set to Active and none of the active approvals appear. If you filter by any status other than All, none of the approvals that were active before upgrading to 6.1 appear.

      Workaround:To view active approvals, filter by selecting All.

    • Opening the Infrastructure tab fails when the administrator is a member of several hundred groups* 16-JAN-2015
      When using Active Directory and SSO, an IaaS administrator who is a member of many groups might be unable to display the Infrastructure tab. Attempting to do so may yield one of the following errors:
      • Bad Request - Request Too Long - HTTP Error 400. The size of the request headers is too long.
      • Service Unreachable - A required service cannot be reached at the expected address. Contact your system administrator for assistance. Reference error REPO404.

    • Workaround: The resolution is to increase the token limitations as in the following example.

      1. Determine and set the maximum Kerberos token size. To determine the correct Kerberos maximum token size for your deployment, use the following guideline:

      Kerberos MaxTokenSize = 1200 + 40d + 8s (bytes)

      This formula uses the following values:

      • d -- The number of domain local groups a user is a member of plus the number of universal groups outside the user's account domain that the user is a member of plus the number of groups represented in security ID (SID) history.
      • s -- The number of security global groups that a user is a member of plus the number of universal groups in a user's account domain that the user is a member of.
      • 1200 -- The estimated value for ticket overhead. This value can vary depending on factors such as DNS domain name length and client name.

      2. Determine if you need to modify the registry entry. If the token size that you calculate by using the above formula is less than 12,000 bytes (default size), you do not have to modify the MaxTokenSize registry value on domain clients. If the value is more than 12,000 bytes, adjust the MaxTokenSize registry value (reference http://support.microsoft.com/kb/263693). If you need to change the Kerberos MaxTokenSize value, modify the following registry entry:

      MaxTokenSize, REG_DWORD,
      <value> (the recommended value for the MaxTokenSize registry entry is 65535 decimal or FFFF hexadecimal)

      3. Determine and set the correct HTTP maximum request size for your deployment by using the following guideline, where T is the Kerberos MaxTokenSize as set above:

      MaxFieldLength = (4/3 * T bytes) + 200
      MaxRequestBytes = (4/3 * T bytes) + 200

      Set MaxFieldLength and MaxRequestBytes to the calculated values, as in the following example where they are set to the permitted maximum value:

      MaxFieldLength DWORD 65534
      MaxRequestBytes DWORD 16777216

      For related information about issues with Kerberos authentication when a user belongs to many groups, see the following support notes: