Introduction
Omnissa Horizon View Composer is a feature in Horizon View that gives administrators the ability to manage pools of desktops that share a common virtual disk.
In the Omnissa Horizon View Composer, you first create a single "master" virtual desktop, which is referred to as the Parent VM. A snapshot is taken of this Parent VM, and then a replica is generated. From this replica, linked clones are created. The reason they are called linked clones, is that fundamentally the source of clone's information comes from the read-only replica.
The difference in this approach to virtual desktop deployment is that rather than using the template process to create a virtual desktop – merely a "differences" or "delta" file is created. Additionally, when changes are made to the Parent VM, these are proliferated to each of the linked clones, in a process called VMware recomposing. This reduces storage costs and deployment time.
This means that where the Omnissa Horizon View Composer is used, any issue that slows down virtual desktop deployment or management - be it a resource contention at the OS-level or an error in VMware recomposing at the composer-level - will not be viewed kindly! This is because, such issues, if allowed to persist, can shake user confidence in the composer, compelling them to favor the traditional template approach over the modern composer approach to desktop deployment. To avoid such eventualities, it is good practice to keep an eye on the performance of the composer, capture issues proactively, and fix them before users notice and complain. This is where eG Enterprise helps!
eG Enterprise offers a specialized monitoring model for the Omnissa Horizon View Composer. By monitoring every layer of every tier of a composer, this model alerts administrators to anomalies affecting composer performance, much before they impact user experience.
This
