Released 31 May 2016 | Build 3902983
Last Updated: 31 May 2016
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 7. 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.
This release of the Horizon vRealize Orchestrator plug-in includes the following new features:
- Instant Clones - Automated desktop pool types with floating user assignment that are created through Instant Clones are supported.
Note: There are no specific workflows for Push Image and Recover functionalities. However, the existing workflows are supported for Instant Clone pools.
- Support for vRealize Automation 6.2.4.
- Support for vRealize Orchestrator 6.0.4.
- Support for VMware Horizon 7.0 and 6.2.2.
- Support for VMware vSphere 6.0 Update 2, Update 1, and 6.0.
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 7 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.3 of this plug-in requires the following VMware products:
- VMware Horizon 7.0 or 6.2.2
- vRealize Orchestrator 6.0.4
- vRealize Automation 6.2.4
- vSphere 6.0 Update 2, Update 1, and 6.0
Note: Horizon vRealize Orchestrator 1.3 plug-in does not support Horizon Air.
For more information about functional prerequisites, see Using the VMware Horizon vRealize Orchestrator Plug-In.
The following issues were resolved in this release
- 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.
When executing Add View Pod in Horizon configuration from vRealize Orchestrator that is in-built in vRealize Automation, the workflow passes instead of failing. However, the handshake failure errors are captured in the logs.
Workaround: You must enable TLSv1.1 and TLSv1.2 manually. See Enabling TLSv1.1 and TLSv1.2.
- 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 vRealize Automation 6.2.4 service catalog. You might also need to log out of vRealize Automation 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.