check-circle-line exclamation-circle-line close-line

Released 19 June 2014

Last Updated: 19 June 2014

These release notes include the following topics:

Key Features of the Horizon vCenter Orchestrator Plug-In

The Horizon vCenter Orchestrator (vCO) plug-in allows interaction between vCenter Orchestrator and VMware Horizon 6. The plug-in contains a set of standard workflows that accomplish basic goals that are ordinarily performed in View Administrator or other View interfaces.

You can use this plug-in to expand the settings and methods for provisioning remote desktops and applications.

  • Self-service - For end user enablement, the Horizon vCO plug-in integrates with vCloud Automation Center to provide self-service access to applications and desktops. The plug-in workflows can be integrated with the request and approval processes that are built into the vCloud Automation Center service catalog.
  • Automation - Automating and distributing tasks for delegated administration reduces the need for email correspondence and exception handling. The requests are routed into processes that are pre-defined and only flagged for approval if justification is needed.

These standardized controls and processes allow administrators to deliver Desktops-as-a-Service (DaaS) with a one-to-many model of administration across multi-tenant or highly distributed environments.

Before You Begin

Installing the Horizon vCO plug-in is similar to installing other vCenter Orchestrator plug-ins. Configuring the Horizon vCO plug-in involves running various configuration workflows to connect to View components and to configure roles and permissions. For instructions see Using the Horizon vCenter Orchestrator Plug-In.

Top of Page


The Horizon vCenter Orchestrator Plug-In user interface and product documentation are available in Japanese, French, German, simplified Chinese, traditional Chinese, and Korean.

Top of Page

Compatibility Notes

Version 1.0 of this plug-in requires the following VMware products:

  • VMware Horizon 6 (with View)
  • vCenter Orchestrator 5.5.1
  • vCloud Automation Center 6.0.1
  • vCenter Server 5.5b with vCenter Single Sign-On 2.0

For more information about functional prerequisites, see Using the Horizon vCenter Orchestrator Plug-In

Top of Page

Known Issues

  • In the Application Entitlement workflow, if you accidentally supply a desktop pool ID rather than an application pool ID, the workflow runs and does not display an error message. This issue occurs regardless of whether you manually supply the pool ID or whether you bind the workflow to a desktop pool ID.
  • If you set a pool policy for de-provisioning desktop virtual machines and specify that persistent disks are to be saved, the persistent disks are not saved if you used a Horizon vCO plug-in workflow to assign a user to the desktop.
    Workaround: Use the View Administrator UI to assign users who will have persistent disks.
  • If an administrator removes a pod or pool, by running the Remove View Pod Configuration workflow, the pod name and pool names might still appear in drop-down lists. This issue occurs if the Add Delegated Administrator Configuration workflow has been run for the pool or pod.
    Workaround: After removing the pod or pool, the administrator can run the Remove Delegated Administrator Configuration workflow to remove the delegated administrator access from deleted pod and pools.
  • If you attempt to use a German or French version of vSphere Web Client to run a workflow, if the workflow contains a drop-down list or check box, which causes the workflow UI to reload, some characters are garbled and appear as HTML code.
  • If you plan to use the Clone Localization Resources workflow (in the Horizon/Configuration folder) by using the virtual appliance version of the vCenter Orchestrator server, you must first perform the following steps:
    1. Log in to the appliance and edit the file; for example:

      vcoserver:/var/lib/vco/app-server/bin # vi
    2. In the JVM_OPTS section, add the following parameter:

    3. Restart the VCO service.

    You can use the Clone Localization Resources workflow to duplicate the localization files after you duplicate a workflow.

Top of Page