Horizon vCenter Orchestrator Plug-In 1.1 Release Notes

|

Released 9 September 2014

Last Updated: 11 September 2014

These release notes include the following topics:

Key Features of the Horizon vCenter Orchestrator Plug-In

The Horizon vCenter Orchestrator 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 vCenter Orchestrator 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.

Top of Page

What's New in This Release

This release of the Horizon vCenter Orchestrator plug-in includes the following new features:

  • Support for vCloud Automation Center 6.1, in addition to 6.0.1.
  • Support for vCenter Orchestrator 5.5.2, in addition to 5.5.1.
  • Support for VMware Horizon 6.0.1, in addition to 6.0.0.
  • Support for VMware vSphere 5.5 Update 1 and Update 2.
  • Ability to add managed and unmanaged machines to existing manual pools. Unmanaged machines can include physical machines and vCenter virtual machines from a vCenter Server that has not been added to View.
  • New Session Management workflow for disconnecting, logging off, resetting, and sending messages to active View desktop sessions.
  • Ability to run one workflow to entitle multiple users to floating-assignment pools or RDS desktop pools.
  • Ability to provision multiple machines for multiple users.
  • New workflow for taking machines into and out of maintenance mode.

Top of Page

Before You Begin

Installing the Horizon vCenter Orchestrator plug-in is similar to installing other vCenter Orchestrator plug-ins. Configuring the Horizon vCenter Orchestrator 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

Internationalization

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.1 of this plug-in requires the following VMware products:

  • VMware Horizon 6 (with View): 6.0.0 or 6.0.1
  • vCenter Orchestrator 5.5.1 or 5.5.2
  • vCloud Automation Center 6.0.1 or 6.1
  • vCenter Server 5.5b with vCenter Single Sign-On 2.0: vSphere 5.5 Update 1 or Update 2

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

Top of Page

Resolved Issues

The following issues were resolved in this release

  • Previously, if an administrator removed a pod or pool by running the Remove View Pod Configuration workflow, the pod name and pool names sometimes still appeared in drop-down lists. This issue occurred if the Add Delegated Administrator Configuration workflow was run for the pool or pod. This issue has been resolved. The Remove View Pod Configuration workflow will remove all DA configurations as well.
  • Previously, if you set a pool policy for de-provisioning desktop virtual machines and specified that persistent disks were to be saved, the persistent disks were not saved if you used a Horizon vCenter Orchestrator plug-in workflow to assign a user to the desktop. This issue has been resolved if you use Horizon (with view) 6.0.1 and Horizon vCenter Orchestrator plug-in 1.1.

Top of Page


Known Issues

  • If you run the Remove View Pod Configuration workflow and there is no existing delegated administrator configuration for this pod, the workflow fails with error: TypeError: Cannot read property "length" from null (Workflow:Remove View Pod Configuration / Scriptable task (item1)#8)"
  • The Register Machines to Pool workflow registers any of the DNS names that are provided without performing any kind of validation. The administrator must manually push the returned registry token to the registered machine.
  • After you run the Add Guest Credentials workflow and the Manage Delegated Administrator Configuration for Registration workflow, it can take some time for the guest credentials to be populated in the vCloud Automation Center 6.1 service catalog. You might also need to log out of vCloud Automation Center and log back in to see the credentials.
  • 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 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 setenv.sh file; for example:

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

      -Dfile.encoding=UTF-8
    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