VMware vRealize Operations for Horizon View 6.1 Release Notes
VMware

VMware vRealize Operations for Horizon 6.1 Release Notes

vRealize Operations for Horizon 6.1 | 12 March 2015

Last Document Update: 12 March 2015

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

Key Features

VMware vRealize™ Operations for Horizon™ extends the functionality of VMware vRealize™ Operations Manager™ to monitor and manage VMware Horizon™ with View™ environments.

vRealize Operations for Horizon collects data about your resources and presents that data in preconfigured dashboards for both real-time and predictive analysis.

What's New in This Release

vRealize Operations for Horizon 6.1 includes the following new features.

  • vRealize Operations Manager 6.0.x support - vRealize Operations for Horizon 6.1 is compatible with vRealize Operations Manager 6.0.x. It does not support earlier vCenter Operations Manager versions.
  • VMware Horizon 6 version 6.1 support - vRealize Operations for Horizon 6.1 is compatible with VMware Horizon 6 version 6.1.
  • Support multiple desktop sessions by the same user in the same VDI pool
  • 30 day activity report - with vRealize Operations for Horizon 6.1 you can get information about unique users, desktops used.
  • Improved licensing - With vRealize Operations for Horizon 6.1, you can manage VDI and server resources within the same vRealize Operations Manager instance. You can further extend vRealize Operations Manager by installing additional management pack solutions.
  • Improved internationalization - Both the user interface and documentation are now available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, and Korean.

Limitations

vRealize Operations for Horizon has the following limitations.

  • Physical desktops in a pool are not monitored
    Physical desktops included in a desktop pool are not monitored or shown in the user interface. However, physical RDS hosts are monitored and shown in the user interface.
  • 32-bit View Connection Server 5.0 instances are not supported
    vRealize Operations for Horizon 6.1 supports only 64-bit View Connection Server 5.0 instances.
  • High availability (HA) is not supported
    vRealize Operations for Horizon 6.x does not support high availability (HA). If a View adapter instance is moved to a different cluster node, the broker and desktop agents can no longer communicate with the View adapter and the vRealize Operations for Horizon solution stops functioning. For solutions to this problem, see KB: 2092874: Best practices for configuring vRealize Operations for Horizon when HA is enabled.

Top of Page

Licensing Notes

This section contains notes on the licensing of vRealize Operations for Horizon 6.1.

  • To run vRealize Operations for Horizon, customers need to enter two keys.
    • A single vRealize Operations Manager license key.
    • A 10 pack or 100 pack vRealize Operations Manager license key that monitors your desktop virtual machines.
    • The VMs must be part of the appropriate licensing groups in order to ensure accurate licensing. For detailed licensing instructions, see Adding a vRealize Operations for Horizon License Key and Associate View Objects with Your vRealize Operations for Horizon License Key in the vRealize Operations for Horizon Installation guide.
    • Customers upgrading from vCenter Operations Manager to vRealize Operations Manager may perceive this licensing change as a reduction in the number of virtual machines they can manage. This is not the case - following the above steps and the steps in the vRealize Operations for Horizon Installation guide will ensure that all your VMs are monitored and are license compliant.
  • The vRealize Operations Manager component license that is included is for Horizon-supporting infrastructure monitoring. A separate vRealize Operations Manager license is required for non-Horizon infrastructure monitoring.

Installation Notes

This section contains notes on the installation process for each vRealize Operations for Horizon component. For complete installation instructions, see the vRealize Operations for Horizon Installation document.

  • vRealize Operations Manager for Horizon 6.1 is compatible with the following View and vRealize Operations Manager versions:
    • VMware View 5.0 or 5.1.x
    • VMware Horizon View 5.2.x or 5.3.x
    • VMware Horizon with View 6.0.x or VMware Horizon 6 version 6.1
    • VMware vRealize Operations Manager 6.0.1
  • You download the vRealize Operations for Horizon installation files from the VMware download page.
  • You can download the preconfigured View dashboards file (Dashboards_V4VAdapter-6.1.0-xxx.zip) and report templates file (Reports_V4VAdapter-6.1.0-xxx.zip) from the VMware download page. View dashboards and reports are installed automatically when you install vRealize Operations for Horizon. These files are provided in case problems occur during or after installation and you need to restore the dashboards or reports to their original state. For information about importing dashboards and reports, see the vRealize Operations Manager documentation.
  • You install the View adapter on a vRealize Operations Manager 6.0.1 cluster node or remote collector.
  • You install the vRealize Operations for Horizon broker agent on a View Connection Server host in your View environment. You cannot install the broker agent on a 32-bit View Connection Server 5.0 host.
  • Your View version determines how you install the desktop agent component of vRealize Operations for Horizon.
    • For View 5.0 and 5.1 environments, you must manually install the desktop agent on each remote desktop.
    • For View 5.2 and later environments, the desktop agent is included in the View Agent installer and does not need to be manually installed.
  • For sizing and scaling guidelines, see KB 2098051: vRealize Operations for Horizon sizing guidelines.

Upgrade Notes

This section contains notes of the upgrade and data migration processes. For complete upgrade instructions, see the vRealize Operations for Horizon Installation document.

  • You can upgrade to vRealize Operations for Horizon 6.1 from vCenter Operations Manager for Horizon 1.6 (vCenter Operations Manager 5.8.2) or vCenter Operations Manager for Horizon 1.7 (vCenter Operations Manager 5.8.3).
  • To upgrade from vCenter Operations Manager for Horizon View 1.5.1 (vCenter Operations Manager 5.7.2) to vRealize Operations for Horizon 6.1, you must first upgrade to vCenter Operations Manager for Horizon 1.6 or 1.7.
  • During the migration process, dashboards are copied from your original vCenter Operations Manager for Horizon 1.6 or 1.7 instance. You must manually delete these migrated dashboards and use the new dashboards that are created when you install the vRealize Operations for Horizon PAK file.  Some of the migrated dashboards can be identified by the number 1, which is appended to the dashboard name. Other migrated dashboards can be identified by the Expand for help widget, which is not included in the new dashboards.
  • Due to an existing limitation, vRealize Operations Manager cluster must be restarted after the upgrade for the process to complete.
  • Sessions that were active during upgrade may not report data after the upgrade is complete unless you re-issue the Desktop Authentication tokens using the View Broker Agent Configuration utility or Restart the Desktop-Agent for the active sessions that are not reporting.

Internationalization (I18N) Support

The vRealize Operations for Horizon user interface and documentation are both available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, and Korean.

Top of Page

Prior Releases of vCenter Operations Manger for Horizon

Features that were introduced in prior releases of vCenter Operations Manager for Horizon are described in the release notes for each release, along with existing known issues

Resolved Issues

This section contains resolved issues for this release.

  • You can use the Session Processes widget on the View Remote Session Details dashboard to obtain information about in-guest processes and their resource usage for View session objects. For detailed information see KB: 2099962: Displaying in-guest process data for View session and host objects in vRealize Operations Manager.
  • You can now use the same vRealize Operations Manager instance to monitor both VDI and other infrastructure resources.
  • Previously, if there were multiple sessions on an RDS host, the desktop agent returned the same session metrics (CPU, memory, and so on) for each of the sessions. This problem has been resolved in the 6.0.1 version of View Agent.

Known Issues

This section contains known issues for this release.

  • Metric units are not seen in vRealize Operations Manager 6.0.1/vRealize Operations Manager for Horizon 6.1 View Overview dashboard
    In vRealize Operations Manager 6.0.1/vRealize Operations Manager for Horizon 6.1 View Overview dashboard, the scoreboard widget can not show the metric units.
    Workaround: Use vRealize Operations Manager 6.0 with vRealize Operations Manager for Horizon 6.1.
  • When vRealize Operations for Horizon solution is upgraded to 6.1, duplicate session objects would appear
    When vRealize Operations for Horizon solution is upgraded to 6.1, duplicate session objects would appear. Newer object will have a machine_id and the older object is without a machine_id. Only the session objects containing a machine_id will fetch the metrics. Session Objects without machine_id are stale and will not fetch any metrics (because of vRealize Operations Manager limitation of not deleting stale objects immediately). This is applicable to VDI session objects only.
  • Heatmap not configured appears on View Infrastructure dashboard
    When migrating from vCenter Operations Manager 5.8.2/vCenter Operations Manager for Horizon1.6 to vRealize Operations Manager 6.0.1/vRealize Operations Manager for Horizon 6.1, Heatmap not configured might appear on View Infrastructure dashboard.
    Workaround: Once the pairing between the adapter and the broker agent is done, this issue should be resolved.
  • View pods that are no longer being monitored still appear in the View dashboards
    If you stop monitoring a View pod, the View pod resource continues to appear in the View dashboards.
    Workaround: Manually delete the View pod resource and all View Connection Server, security server, and pool resources related to this View pod from the vRealize Operations Manager user interface.
  • Existing linked-clone desktops must be recomposed
    If you created desktop pool images that utilize linked clones prior to installing vRealize Operations for Horizon, you must to recompose the linked clones to include the vRealize Operations for Horizon desktop agent in the image.
  • User names that include multibyte characters might not appear correctly in the vRealize Operations Manager user interface
  • Network-related alerts are not generated for user sessions that were established before the View adapter was set up
    The following alerts are not generated for user sessions that were initiated before the configuration of a View adapter instance: PCoIP|Round Trip Latency (ms) and PCoIP|Packet Loss Percent. See KB 1030695: PCoIP performance is slower than expected for troubleshooting high latency and packet loss issues.
  • Changing the adapter name causes the View Adapter Status dashboard to display incorrect data
    If the name of the View adapter instance is changed, the health of the View Adapter in the Select View Adapter widget and the health of the objects in the View Adapter Status widget are unknown on the View Adapter Status dashboard. These problems occur because the View Adapter Collector resource does not automatically update to reflect the name change of the vCenter Operations for Horizon View adapter instance.
    Workaround: Do not change the adapter name. If the adapter name has already been changed, update the adapter name in the vRealize Operations for Horizon user interface.
  • Objects deleted from View are not automatically deleted from vRealize Operations Manager
    For example, if you delete a desktop pool in View Administrator, that object still appears in vRealize Operations Manager. Object relationships are removed in vRealize Operations Manager.
  • Desktop agent in the 6.0.1 View Agent stops on RDS servers that have more than 60 sessions
    Workaround: Manually install the vRealize Operations for Horizon 6.0 desktop agent over the desktop agent that is included in the 6.0.1 View Agent. This problem affects only desktop virtual machines running on RDS hosts. All other desktop virtual machines can use the desktop agent that is included with the 6.0.1 View Agent.
  • Certain View reports return inconsistent or incorrect results
    The View Desktop Pool Usage and View Application Pool Usage reports return inconsistent or incorrect results in the Connected and Disconnected Desktop Sessions sections.
    Workaround: None.
  • Top-N Analysis widgets in the application pools column on the View RDS Pools dashboard are always empty
    The affected widgets include Top Application Session PCoIP Latency, Top Application Session PCoIP TX Bandwidth, Top Application Session TX Packet Loss, and Top Application Session Logon Time.
    Workaround: None.
  • If a View adapter receives data from more than 1,000 desktop agents, the ARP cache on the vRealize Operations Manager collector node is not large enough to handle all of the necessary entries in the cache.
    Workaround: For a solution to this problem, see KB 2096607: Adjusting the ARP cache on a vRealize Operations Manager remote collector node.
  • Scoreboard widgets on the View Overview, View Remote Session Details, View RDS & TS Host Details, and View Adapter Self Health dashboards do not refresh
    Most scoreboard widgets are configured to refresh every two minutes, but this problem prevents auto-refreshing. This problem is most apparent if the affected dashboards are always kept open.
    Workaround: Click the Perform Multi-Select Interaction button on master widget's toolbar to reinitiate interactions and refresh the corresponding scoreboard widgets. For example, on the View Overview dashboard, click the Perform Multi-Select Interaction button on the View Pods widget toolbar to refresh the Pod Indicator Metrics scoreboard widget.

Top of Page