With the Add Pool Policy Configuration workflow, administrators can set safeguards for delegated administrators and end users regarding de-provisioning, or recycling, desktops. Administrators can choose whether to delete the virtual machine and can choose how to manage any associated persistent disks.
You must run this workflow once for each pool that has an active de-provisioning workflow. When de-provisioning the virtual machines in a desktop pool, you have several options:
- You can delete the virtual machine or you can simply unassign and unentitle the user.
- If you choose to delete the virtual machine and the virtual machine has a View Composer persistent disk, you can save the disk or delete it too.
- If you choose to save View Composer persistent disks, you can save them on their current datastore or save them to a different datastore.
Prerequisites
- Verify that you have administrator credentials for the vRealize Orchestrator server. The account must be a member of the vRealize Orchestrator Admin group configured to authenticate through vCenter Single Sign-On.
- Configure the connection to the Horizon pod.
- Determine what you might like the policy to be regarding deleting the virtual machines and saving persistent disks. For information about persistent disks, see the topics about managing View Composer persistent disks in the Horizon 7 Administration document.
If you choose to delete the virtual machine, you must choose whether to save any persistent disks. If you choose to save the disk to a different datastore, verify that you have the name of the datastore and the path to the folder that stores the persistent disk.
Procedure
What to do next
If you must remove or update a pool policy, you can run the Remove Pool Policy Configuration workflow or the Update Pool Policy Configuration workflow.