6.0
Table Of Contents
- Using the Horizon vCenter Orchestrator Plug-In
- Contents
- Using the Horizon vCenter Orchestrator Plug-In
- Introduction to the Horizon vCenter Orchestrator Plug-In
- Installing and Configuring the Horizon vCenter Orchestrator Plug-In
- Horizon vCenter Orchestrator Plug-In Functional Prerequisites
- Install the Horizon vCenter Orchestrator Plug-In
- Configure the Connection to a View Pod
- Assigning Delegated Administrators to Desktop and Application Pools
- Best Practices for Managing Workflow Permissions
- Set a Policy for De-Provisioning Desktop Virtual Machines
- Using Horizon vCenter Orchestrator Plug-In Workflows
- Making the Workflows Available in vSphere Web Client and vCloud Automation Center
- Exposing Horizon vCenter Orchestrator Plug-In Workflows in vSphere Web Client
- Exposing Horizon vCenter Orchestrator Plug-In Workflows in vCloud Automation Center
- Create Business Groups for Delegated Administrators and End Users
- Create Services for Delegated Administrators and End Users
- Create Entitlements for Delegated Administrators and End Users
- Bind vCAC60 Workflows to Specific Pods and Pools in vCloud Automation Center
- Configure the Catalog Item for the Workflow
- Index
Desktop Recycle
Purpose This de-provisioning workflow removes user assignment or
entitlement from the specified virtual machine desktop.
Depending on the pool policy, the virtual machine might be
deleted and any persistent disks might be saved.
Inputs/parameters Pod, pool ID, user name
Scope Works for all types of pools.
Prerequisites Run the Add Pool Policy Configuration workflow before
running this workflow.
Binding
requirements
For the vCAC60 folder, the administrator must bind this
workflow to a pool and pod. For the vSphereWebClient
folder, no binding is required. If you do bind the workflow to
a pod, in vSphere Web Client, you see a drop-down list of
pools and the users entitled to each pool.
Results For floating pools, user entitlement is removed. For other
desktop pool types, user assignment is removed.
For dedicated linked-clone pools, the virtual machine is
deleted and persistent disks are saved according to the settings
used in the Add Pool Policy Configuration workflow.
For full-clone pools, if the virtual machine is deleted, the
persistent disk is also deleted.
Limitations
n
Saving a persistent disk (sometimes called a UDD, or user
data disk), works only for automated dedicated linked-
clone desktop pools.
n
Deleting the virtual machine is not supported for floating
pools or manual pools.
Desktop Refresh
Purpose Reverts a specific virtual machine to its base state.
Inputs/parameters Pod, pool ID, machine name
Scope Works only on automated View Composer linked-clone
pools.
Binding requirements
For the vCAC60 folder, the administrator must bind this
workflow to a pool and pod. For the vSphereWebClient
folder, no binding is required.
Results For View Composer linked-clone virtual machines, a warning
message is sent to the user if there is an active session, and the
user is automatically logged out after a certain amount of
time. A refresh operation then starts.
Remove Users from
Application Pool
Purpose Removes multiple users entitlements from an application
pool.
Inputs/parameters Pod, pool ID, users (selected from a default list)
Binding requirements
For the vCAC60 and vSphereWebClient folders, 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
Purpose Removes multiple users entitlements from a desktop pool.
Inputs/parameters Pod, pool ID, users (selected from a default list)
Chapter 3 Using Horizon vCenter Orchestrator Plug-In Workflows
VMware, Inc. 25