Omnissa Horizon VM's do not use select templates storage profile on deployed pool VM's

Products

• VMware vCenter Server

Issue/Introduction

• When creating a VM template for Omnissa Horizon, a specific storage profile is selected
  
  
• When creating the pool on the Omnissa side, the Storage Profile Management that is selected is for vSAN
  
  
• Once the pool is created and starts deploying VM's, the VM is assigned one of the following storage policies:
  
  VM_HOME_ [GUID] (Note:This is always present for all Omnissa deployed VM's)
  
  FULL_CLONE_DISK_[GUID]
  
  FULL_CLONE_DISK_FLOATING_[GUID]
  
  OS_DISK_FLOATING_[GUID]
  
  REPLICA_DISK_[GUID]

Cause

This is expected behavior based on how Omnissa handles storage policies. Refer to the Omnissa documentation in the resolution for more information.

Resolution

The following workaround has been recommended, but has not be verified by Omnissa. For any questions or concerns, contact Omnissa:

1. Notate the storage policy that Omnissa is using (Default Storage Policy Profiles for vSAN Datastores)
   
   
2. Snapshot the vCenter in case you need to rollback.
   
   
3. Once you have the storage policy name notated, delete the storage policy that Omnissa uses.
   
   
4. Clone your "Default storage policy" or the policy that the template was using, and use the name of the Omnissa policy you just deleted.
   
   
5. Repeat steps 1 - 3 for the "VM Home" storage policy also.
   
   
6. Test a deployment of an existing pool after the change to make sure there are no issues.