Omnissa provisioned Instant Clone vms are being created with a UUID instead of friendly name

Products

• VMware vCenter Server

Issue/Introduction

• Horizon created Instant Clones show initial provision to a datastore with vm names that match the naming scheme. VM-1, VM-2, etc. 
• Creating a new snapshot and re-publishing the image shows the friendly VM name in the Horizon UI VM-1, but the datastore folder name and .vmx file name change to a UUID ########-####-####-####-############
• The Omnissa Connection Server is configured for Instant Clone provisioning mode B
• The vpxd log on the vCenter shows entries similar to:
  

  YYYY-MM-DDTDD:MM:SS verbose vpxd[422002] [Originator@6876 sub=VmProv opID=###########] Start vDT span in Full Clone workflow
  <snip>

  -->    },
  -->    name = " ########-####-####-####-############,
  -->    folder = 'vim.Folder:<guid>:group-v####',
  -->    spec = (vim.vm.CloneSpec) {

• The Horizon Connection Server debug log shows entries similar to:
  

  YYYY-MM-DDTDD:MM:SS DEBUG (1798-28C0) <WFE-02> [VcSubsystem25] {HIC} Creating clone with vm name ########-####-####-####-############ from vm vm-#####and snapshot snapshot-##### in folder group-v#### and thinProvisioned true

Resolution

• This is expected behavior with Omnissa Instant Clone provisioning mode B and is documented in this article: How to switch provisioning scheme for a Omnissa Horizon Instant Clone Pool or Farm
• If needed, contact Omnissa for further information.