Horizon vRealize Orchestrator Plug-In 1.4 Release Notes

|

Released 16 March 2017 | Build 5131887

Last Updated: 16 March 2017

These release notes include the following topics:

Key Features of the Horizon vRealize Orchestrator Plug-In

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.

Top of Page

What's New in This Release

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

  • Introduction of the Request a Remote Application Self-Service workflow.
  • Introduction of the AppStack Assignment Self-Service workflow.
  • Introduction of the Duplicate Pool workflow.
  • Support for vRealize Automation 7.2 release.
  • Support for vRealize Orchestrator 7.2 release.
  • Support for VMware Horizon 7 version 7.1 release.
  • Support for Spanish locale.

Top of Page

Before You Begin

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.

Top of Page

Internationalization

The Horizon vRealize Orchestrator plug-in user interface and product documentation are available in Japanese, French, German, simplified Chinese, traditional Chinese, Korean, and Spanish.

Top of Page

Compatibility Notes

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

  • VMware Horizon 6 version 6.2.3 or VMware Horizon 7 versions 7.0.3 and 7.1.
  • vRealize Orchestrator 7.2 or later.
  • vRealize Automation 7.2
  • vSphere 6.0 or later

Note: Horizon vRealize Orchestrator 1.4 plug-in does not support Horizon Air.

For more information about functional prerequisites, see Using the VMware Horizon vRealize Orchestrator Plug-In.

Top of Page

Resolved Issues

The following issues were resolved in this release

  • 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.
  • 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.

Top of Page

Known Issues

  • 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.
  • 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.
  • When duplicating a pool with the Duplicate a Pool workflow, the underscore ‘_’ is not supported in pool naming pattern for  Horizon 7 version 7.1. However, this is supported in Horizon 7 version 7.0.3 and earlier versions.

Top of Page