VMware recently published an article describing the new functions and features on VMware vCenter Operations Manager for Horizon View 1.5. Here is the original article, but in summary:
- Easier Installation
- Greater Scalability
Previous versions of vC Ops for View were limited to a single environment of no more than about 3,000 desktops. To monitor more desktops, you had only two choices. You could monitor a subset (pool level generally) of the virtual desktop machines, or you could install an additional instance of vC Ops for View. This was limiting because multiple vC Ops for View monitoring environments were fragmented and did not provide a “single pane of glass” for monitoring, management, and control.
This new release of vC Ops for View supports up to 8,000 concurrent Horizon View virtual desktop users within a single instance of the vC Ops for View console. Multiple Horizon View pods can be monitored with the same vC Ops for View adapter instance, or you can install additional adapter instances on remote collector servers to collect data across different data centers. For additional scalability, multiple options for metrics collection are also now available. You can collect a partial set of metrics instead of the full set, which enhances scalability.
- Better Monitoring
VMware vC Ops for View comes with preconfigured dashboards that can be completely customized to the customer’s requirements. Monitoring personnel can customize the dashboards to view only the components they are responsible for or must focus on. Your monitoring teams can analyze individual user sessions that might be experiencing issues. They can monitor a whole picture of the individual user’s environment to check for impending problems, or problems currently affecting the end user’s virtual desktop session.
Below is a summary of the important new features in my opinion (if you prefer go the the Release Notes here).
- vCenter Operations Manager for Horizon View 1.5 provides scalability and deployment features extending its ability to support a considerably wider percentage of Horizon View 5.x deployments.
- vCenter Operations Manager for Horizon View 1.5 supports multiple Horizon View instances, spread across one or more datacenters, within the same instance of vCenter Operations Manager for Horizon View. Horizon View 5.x deployments upwards of 7,500 concurrent users can now be supported within a single instance of vCenter Operations Manager for Horizon View.
- New agent-based View data collection and aggregation for Horizon View 5.2 desktops.
The most important changes in vCenter Operations Manager for Horizon View 1.5 are the improved scalability and support to multiple View instances due to a complete software architecture overhaul. In version 1.0 there was a single View Adapter Server that was responsible for collecting the View Topography, View Events and Desktop metrics connecting to each individual desktop using WMI calls, then it would also be responsible for sending the updates to the vCenter Operations Servers via Http posts. The remote WMI calls to the desktops were very expensive from time, network and cpu cycles perspective.
For this new version, the vCenter Operations Manager team injected their brand new agent into the Horizon View 5.2 guest agent. Now, when you install or update the Horizon View guest agent you are also preparing your desktop to provide metrics to vCenter Operations Manager. The View Broker also has a built-in agent. The View Adapter Server that had to be installed by the administrator is now part the vCenter Operations 5.6 vApp and it will support multiple Horizon View instances. Additionally, the Horizon View Events are now also using this new V4V Broker Agent.
This new architecture allows for increased vCenter Operations Manager scalability while reducing the impact on the desktops and brokers.
This article was first published by Andre Leibovici (@andreleibovici) at myvirtualcloud.net.