6.1

Results If you select Horizon View as the machine provider, this workflow behaves the same way as the
Desktop Allocation workflow.
If you select vRealize Automation as the machine provider, the workflow supports only manual
pools. The following tasks are performed, in the following order:
1 A machine is provisioned using vRealize Automation.
2 The machine is registered in a View desktop pool.
3 For a floating desktop pool, the end user gets entitled to the pool.
4 For a dedicated desktop pool, the end user gets assigned to the machine and gets entitled to
the pool.
5 The machine gets added to user's vRealize Automation Items tab as a vCAC machine, on the
Machines panel.
See also “Advanced Desktop Allocation Scenarios for Delegated Administrators and End Users,”
on page 64.
Limitations
n
Horizon View Agent must be installed and running in the template that is used in the machine
blueprint to provision the machines. See “Create Templates and Blueprints for Adding
Machines to Desktop Pools,” on page 60.
n
VMware recommends that VMware Tools be updated to latest version in the template that is
used in the machine blueprint to provision the machines. See “Create Templates and
Blueprints for Adding Machines to Desktop Pools,” on page 60.
n
For unmanaged machines, valid user credentials must be provided that have Administrator
access for the guest operating system on the machine.
n
For unmanaged machines, a vSphere customization specification must be provided in the
blueprint. This customization specification must include a configuration to change the host
name and SID of the machine so that each machine created from the template has a unique
host name and SID. See “Create Templates and Blueprints for Adding Machines to Desktop
Pools,” on page 60.
n
Guest credentials must be added by running the Add Guest Credentials workflow.
n
Delegated Admin permissions must be provided on credentials by running the Manage
Delegated Administrator Configuration for Registration workflow, located in the
Horizon/Configuration/Horizon Registration Configuration folder.
n
If the administrator does not bind a machine blueprint to the catalog item, the delegated
administrator must choose only those catalog items (blueprints) that are specified by the
administrator to provision machines. For instructions on binding catalog items, see “Import
the Advanced Desktop Allocation Workflow,” on page 54.
Application Entitlement
This workflow allows a delegated administrator to entitle users to an application pool and to remove users'
entitlements.
Inputs/parameters Pod, pool ID, users to entitle, and users to unentitle (selected from a default list)
Results Entitlements can be added and removed in the same workflow.
Assign User
This workflow assigns a user to a specific machine in a desktop pool. An option is provided to entitle the
user to a desktop pool as well.
Inputs/parameters Pod, pool ID, machine name, user name
Results The user is assigned to the specified machine. The existing assignment is removed and the existing
session (if any) is logged off forcibly.
Chapter 3 Using Horizon vRealize Orchestrator Plug-In Workflows
VMware, Inc. 29