VMware Horizon Instant Clone Enhancement

IU health has 18k Horizon Users spread across 14 desktop pools at peak and typically see 10-11k users in steadystate. The environment is designed to have large pools with little segmentation to unlock as much capacity as needed. The global entitlements are designed in a way to spread the load across multiple DC's.

We can achieve this today by applying the following policies to the platform but think these could be learned/discovered automatically:

pre-req: initial template has hot add enabled

1: Discovery of persistent vs non-persistent desktops and apply the appropriate policy to them out of the box.

2: UI representation of Global Entitlements and the relationships that exist from them.

3: Move Business User actions need to provide the AD/Entitlement group user will be moving from/to

3a: In the case there is no AD group on the destination, a blocked action could be generated indicating an AD group needs to be created/assigned to the entitlement.

4: An option to only use AD groups for moves and not direct or local entitlements

5: Actions to provision or suspend desktop pools

6: Disable storage moves for the clusters supporting instant clone pools

7: Disable host moves for the clusters supporting instant clone pools

8: Disable VM sizing on the cp-* (parent/replicat/template) instant clone VMs

9: vCPU scaling contraints to meet underlying OS limitations

Additionally, if the VM/pool sizing analysis can be propagated up the supply chain to the user entity, we'd have better insight into the proper sizing needed for individual users.

Ideally, IU Health would like to understand how to size the initial templates to be utilized within the desired state for 80% of the users and allow non-disruptive size ups for the users that may need additional resources from time to time. This would help improve performance and allow IU Health to better meet the needs of their healthcare staff while they're in critical situations.