This workflow allows a delegated administrator to allocate a machine to a user, by specifying 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 Creating Machines and Managing Pools in vRealize Automation, and especially the topic Configure a Machine Blueprint Service for Advanced Desktop Allocation.

Inputs/parameters

Machine provider (Horizon View or vRealize Automation), pod, pool ID, user name, 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 delegated administrator access to all catalog items in vRealize Automation.

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.

Limitations

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

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

  • For unmanaged machines, valid user credentials must be provided that have Administrator access for the guest operating system on the machine.

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

  • Guest credentials must be added by running the Add Guest Credentials workflow.

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

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