6.1

Results Provided machine names are registered with the specified unmanaged desktop pool in View.
Limitations
n
This 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.
n
To add a new line in the DNS Names text box, so that you can add multiple DNS names, press
Ctrl+Enter. If you press only Enter, instead of adding a new line, the workflow is submitted.
n
To register a Windows Server 2008 R2 machine, you must first log in to View Administrator,
select View Configuration > Global Settings > General, click Edit, and select the Enable
Windows Server desktops check box.
Remove Users from Application Pool
This workflow removes multiple users' entitlements from an application pool.
Inputs/parameters Pod, pool ID, users (selected from a default list)
Binding requirements
For the vSphereWebClient folder, the administrator must bind this workflow to a pool and pod.
Results Specified users are no longer entitled to the specified application pool.
Remove Users from Desktop Pool
This workflow removes multiple users' entitlements from a desktop pool.
Inputs/parameters Pod, pool ID, users (selected from a default list)
Binding requirements
For the vSphereWebClient folder, the administrator must bind this workflow to a pool and pod.
Results Specified users are no longer entitled to the specified desktop pool.
Remove Users from Horizon Air Desktop Pool
This workflow allows a delegated administrator to remove users and groups from a Horizon Air desktop
pool.
Inputs/parameters Horizon Air instance alias, pool ID, users, user groups
Results Specified users are no longer entitled to the specified Horizon Air desktop pool.
Self-Service Advanced Desktop Allocation
This workflow allows end users to allocate machines to themselves, selecting either Horizon View or
vRealize Automation as the machine provider.
This workflow requires a set of configuration steps before using vRealize Automation as a provider. See
Chapter 6, “Creating Machines and Managing Pools in vRealize Automation,” on page 59, and especially
the topic “Configure a Machine Blueprint Service for Advanced Desktop Allocation,” on page 63.
Inputs/parameters Machine provider (Horizon View or vRealize Automation), pod, pool ID, vRealize Automation
catalog item (if you select vRealize Automation as the machine provider)
Binding
requirements
The administrator can bind the catalog item to a specific blueprint to avoid giving the end user
access to all catalog items in vRealize Automation.
Chapter 3 Using Horizon vRealize Orchestrator Plug-In Workflows
VMware, Inc. 33