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
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 desktop
pool.
Self-Service Desktop
Allocation
Purpose Allows end users to allocate a machine to themselves. A new
machine gets provisioned only for "specified naming" desktop
pools.
Inputs/parameters None
Scope Works only on automated pools.
Binding
requirements
For the vCAC60 folder, the administrator must bind this
workflow to a pool and pod. This workflow does not appear
in the vSphereWebClient folder.
Results
n
For floating desktop pools and session-based pools from
RDS hosts, the user is entitled to the pool.
n
For automatically assigned dedicated pools, the user is
entitled to the pool and assigned to an available machine
(if any).
n
For dedicated pools that do not use an automatic naming
pattern, a virtual machine is provisioned for the user with
the name the administrator specifies.
Self-Service Desktop
Recycle
Purpose Allows end users to de-provision their own virtual machine
from the specified pod and desktop pool. This workflow
removes user entitlement and assignment.
Depending on the pool policy, the virtual machine might be
deleted and any persistent disks might be saved.
Inputs/parameters None
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.
Binding
requirements
For the vCAC60 folder, the administrator must bind this
workflow to a pool and pod. This workflow does not appear in
the vSphereWebClient folder.
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.
Self-Service Desktop
Refresh
Purpose Reverts end user's virtual machine in the specified desktop
pool to a base state.
Inputs/parameters None
Scope Works only on automated dedicated View Composer linked-
clone pools.
Using the Horizon vCenter Orchestrator Plug-In
26 VMware, Inc.