Released 12 March 2015
Last Updated: 12 March 2015
These release notes include the following topics:
- Key Features
- What's New in This Release
- Before You Begin
- Compatibility Notes
- Resolved Issues
- Known Issues
The Horizon vRealize Orchestrator plug-in allows interaction between vRealize 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 vRealize Orchestrator plug-in integrates with vRealize Automation 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 vRealize Automation 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.
This release of the Horizon vRealize Orchestrator plug-in includes the following new features:
- Unified provisioning - Provisioning from vRealize Automation with the Horizon vRealize Orchestrator plug-in now supports creation of both Horizon and vRealize Automation machines.
- Unified management - Horizon desktops and pools can now be managed through vRealize Automation for pool-level functions and day-2 management by using action buttons such as Manage Assignment, Manage Session, and Recompose.
- Support for Horizon Air desktop pools - Administrators can perform allocation and entitlement actions against Horizon Air desktops or provide self-service through vRealize Automation.
- Ability to add and remove users from global entitlements in a cloud pod architecture.
- New Recompose workflow - Delegated administrators can perform recompose operations using vRealize Automation or vRealize Orchestrator against one or more View Composer linked-clone desktop pools.
- New workflow for using vRealize Automation IAAS blueprints to provision machines and then add the machines to manual desktop pools in VMware Horizon 6.
- Support for vRealize Automation 6.2.1, in addition to vCloud Automation Center 6.1.1.
- Support for vRealize Orchestrator 6.0 and 6.0.1, in addition to vCenter Orchestrator 5.5.2.
- Support for VMware Horizon 6.1, in addition to Horizon 6.0.1.
- Support for VMware vSphere 6.0, in addition to VMware vSphere 5.5 Update 1 and Update 2.
- Support for VMware Horizon Air 6.2.
Installing the Horizon vRealize Orchestrator plug-in is similar to installing other vRealize Orchestrator plug-ins. Configuring the Horizon vRealize Orchestrator plug-in involves running various configuration workflows to connect to VMware Horizon 6 components and to configure roles and permissions. For instructions, see Using the VMware Horizon vRealize Orchestrator Plug-In.
The Horizon vRealize Orchestrator plug-in user interface and product documentation are available in Japanese, French, German, simplified Chinese, traditional Chinese, and Korean.
Version 1.2 of this plug-in requires the following VMware products:
- VMware Horizon 6: 6.0.1 or 6.1
- vCenter Orchestrator 5.5.2 or vRealize Orchestrator 6.0 or 6.0.1
- vCloud Automation Center 6.1.1 or vRealize Automation 6.2.1
- vSphere 6.0 or vSphere 5.5 Update 1 or Update 2
- VMware Horizon Air Desktops 6.2 (Optional)
For more information about functional prerequisites, see Using the VMware Horizon vRealize Orchestrator Plug-In.
The following issues were resolved in this release
- Previously, if you ran the Remove View Pod Configuration workflow and there was no existing delegated administrator configuration for the pod, the workflow failed with error: TypeError: Cannot read property "length" from null (Workflow:Remove View Pod Configuration / Scriptable task (item1)#8)". This issue has been resolved.
- Previously, if you used the Clone Localization Resources workflow (in the Horizon/Configuration folder) by using the virtual appliance version of the vRealize Orchestrator server, you were required to log in to the appliance and edit the setenv.sh file before using the Clone Localization Resources workflow. This issue has been resolved.
- When running the Add Delegated Administrator Configuration workflow, if you add a user name for a delegated administrator and the user name contains any special characters, the workflow will report success, but the delegated administrator configuration will not be added for that user.
- 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.