VMware vCenter Operations Manager for Horizon View 1.5.1 Release Notes
VMware

VMware vCenter Operations Manager for Horizon 1.6 Release Notes

vCenter Operations Manager for Horizon 1.6 | 19 June 2014

Last Document Update: 02 October 2014

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

Introduction to VMware vCenter Operations Manager for Horizon

VMware® vCenter™ Operations Manager for Horizon® extends the functionality of VMware vCenter Operations Manager to monitor and manage VMware Horizon 6.0 environments.

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

What's New

vCenter Operations Manager for Horizon 1.6 includes the following new features.

  • Support for vCenter Operations Manager 5.8.2.
  • Monitoring of Horizon 6.0 environments, in addition to View 5.0, View 5.1, Horizon View 5.2, and Horizon View 5.3 environments.
  • Monitoring of Terminal Services pools in pre-Horizon 6.0 environments.
  • Monitoring of RDS (Microsoft Remote Desktop Session) hosts, farms, RDS desktop pools, RDS desktops, application pools, and applications in Horizon 6.0 environments.
  • New dashboards have been added and several existing dashboards have been modified to monitor resources in Horizon 6.0 environments. See the vCenter Operations Manager for Horizon 1.6 Supplement document for details.
  • New adapter self health, connectivity-related, and certificate-related alerts have been added:
    • not receiving data from broker agent
    • not receiving data from desktop agent
    • Connection Server Status down
    • Domain Access has been lost
    • vCenter access has been lost
    • Events database access has been lost
    • Security Server certificate is invalid
    • Connection Server certificate is invalid
    • vCenter server certificate is invalid

Limitations in vCenter Operations Manager for Horizon 1.6

vCenter Operations Manager for Horizon View 1.6 has the following limitations.

  • vCenter Operations Manager for Horizon 1.6 does not support physical desktops within a pool
    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 Horizon View 5.0 View Connection Server instances are not supported in vCenter Operations Manager for Horizon 1.6
    vCenter Operations Manager for Horizon 1.6 supports only 64-bit Horizon View 5.0 View Connection Server instances.

Top of Page

Licensing

This section contains notes on the licensing of vCenter Operations Manager for Horizon 1.6.
  • vCenter Operations Manager for Horizon 1.6 is licensed by concurrent View user. Licenses are available in 10 or 100-user packs.
  • If you purchase vCenter Operations Manager for Horizon as part of the Horizon Enterprise suite, concurrent named user licensing is also an option.
  • The vCenter Operations Manager component license that is included in per-user licensing is for Horizon-supporting infrastructure monitoring.
  • A separate vCenter Operations Manager license is required for non-Horizon infrastructure monitoring.
  • You can view license compliance for the past 30 days on the View Adapter Status dashboard in the View Licensed Session Count widget.

Installation Notes

  • You can download vCenter Operations Manager for Horizon 1.6 from the VMware download site.
  • You install the vCenter Operations Manager for Horizon 1.6 Adapter on a vCenter Operations Manager 5.8.2 vApp.
  • You can install the Broker Agent and Desktop Agent components of vCenter Operations Manager for Horizon 1.6 on Windows operating systems, depending on the View version.
    • For environments that run View 5.1, Horizon View 5.2, or 64-bit View 5.0, use the _64 broker installation file and the Desktop Agent file that corresponds to the guest operating system of the desktop.
    • You do not have to install the Desktop Agent on Horizon View 5.2 or later desktops because it is installed with View Agent.
    • The Desktop Agent component of vCenter Operations Manager for Horizon 1.6 can be manually deployed to View 5.0 and 5.1 virtual machines for complete View deployment coverage with vCenter Operations Manager for Horizon 1.6.

    Read the vCenter Operations Manager for Horizon 1.6 Supplement document for step-by-step guidance on installing and configuring vCenter Operations Manager for Horizon 1.6.

Top of Page

Upgrade Notes

This section contains notes on the upgrade process of vCenter Operations Manager for Horizon View 1.5.1 to vCenter Operations Manager for Horizon 1.6 and View 5.0 or View 5.1 to Horizon View 5.2, Horizon View 5.3, or Horizon 6.0 with View.

Note: You can upgrade to vCenter Operations Manager for Horizon 1.6 only from vCenter Operations Manager for Horizon View 1.5.1. To upgrade from a earlier version of vCenter Operations for Horizon View, you must upgrade to 1.5.1 first and then upgrade to 1.6.

  • When you upgrade vCenter Operations Manager for Horizon View 1.5.1 to vCenter Operations Manager for Horizon 1.6, you must first update the Adapter by installing the PAK file from the vCenter Operations Manager Administration Portal. Next, you must uninstall the vCenter Operations Manager for Horizon View 1.5.1 Broker Agent and run the vCenter Operations Manager for Horizon 1.6 Broker Agent installation file. Your vCenter Operations Manager for Horizon View 1.5.1 installation configuration will be saved.
  • Additional configuration is required when upgrading the monitored environment from View 5.0 or 5.1 to Horizon View 5.2 or 5.3 or Horizon 6.0 with View
    The vCenter Operations Manager for Horizon 1.6 Supplement document describes the additional configuration required to enable monitoring of View 5.0 or 5.1 environments. If you upgrade the monitored View 5.0 or 5.1 environment to Horizon View 5.2, Horizon View 5.3, or Horizon 6.0 with View, you must revert the changes that you applied by performing the following steps.
    Re-enable RMI authentication.
    1. In the vSphere Client, locate the vCenter Operations Manager vApp on which you installed the vCenter Operations Manager for Horizon View adapter.
    2. Open the console of the Analytics VM of the vApp, and log in as the root user.
    3. Remove the line "disable-authentication = true" from the /usr/lib/vmware-vcops/user/plugins/inbound/V4V_adapter3/work/msgserver.properties file.
    4. Run the command "service vcops restart collector" to restart the collector service. Restarting the collector service interrupts the data collection in vCenter Operations Manager for a short period.
    5. On the View Connection Server machine where you installed the broker agent, open the broker agent configuration dialog box and pair the broker agent with the adapter.
    Restart the broker agent
    1. On the View Connection Server machine where you installed the broker agent, open the broker agent configuration dialog box.
    2. Under Service status, click Stop.
    3. Under Service status, click Start.
    Optionally, you can disable or remove the GPO that you created for configuring the remote desktops. If you do not remove or disable the assigned GPO, the configuration propagated from the broker agent overrides the GPO configuration.

Internationalization (I18N) Support

vCenter Operations Manager for Horizon 1.6 complies with I18N Level 1. Although vCenter Operations Manager for Horizon 1.6 is not localized, it can run on non-English operating systems and handle non-English text.

Top of Page

Prior Releases of vCenter Operations Manager for Horizon View

Features and issues from earlier releases of vCenter Operations Manager for Horizon View are described in the release notes for each release. To review release notes for earlier releases of vCenter Operations Manager for Horizon View, click one of the following links:

vCenter Operations Manager for Horizon 1.6 Documentation

The vCenter Operations Manager for Horizon 1.6 Supplement document contains step-by-step instructions for installing and configuring vCenter Operations Manager for Horizon 1.6, upgrading to vCenter Operations Manager for Horizon 1.6, and using the vCenter Operations Manager for Horizon 1.6 dashboards.

IMPORTANT: The vCenter Operations Manager for Horizon 1.6 Supplement document does not replace all of the information provided in the vCenter Operations Manager for Horizon View 1.5.1 documentation. You might need to refer to the following 1.5.1 documents for additional information:

Top of Page

Resolved Issues

This section contains resolved issues for this release.

  • PCoIP metrics were not available for some View resources in the vCenter Operations Manager dashboards
    Occasionally, the PCoIP Windows performance counters that should be installed as part of View Agent were missing on a remote desktop. When this happened, no PCoIP metrics were available in vCenter Operations Manager dashboards for View resources, including user desktop, Horizon client, View client network, or pool or pod aggregate metrics. This issue has been resolved.

Known Issues

This section contains known issues for this release.

  • RMI communication errors might occur when monitoring View environments of 6000 or more desktop sessions
    By default, the Analytics VM in the vCenter Operations Manager vApp is configured for 10K open file descriptors per process. As the total number of concurrent desktop sessions approaches 10K, the system runs out of open file descriptors for the collector process which causes communication errors and other problems.
    To avoid these issues, increase the number of open file descriptors supported by the vCenter Operations Manager Analytics VM.
    Workaround: Increase the number of open file descriptors on the Analytics VM to 20480, and the arp cache size.
    1. Open an SSH connection to the Analytics VM, or open the console in vCenter Server.
    2. Log in with the root user account.
    3. Open the /etc/security/limits.conf file for editing.
    4. Locate the line that reads admin - nofile 10240 and update it to admin - nofile 20480.
    5. Open the /etc/sysctl.conf file for editing.
    6. Modify the following lines if they exist, or add the lines if they do not exist.
      • Original configuration:
        # sysctl net.ipv4.neigh.default.gc_thresh3
        net.ipv4.neigh.default.gc_thresh3 = 1024

        # sysctl net.ipv4.neigh.default.gc_thresh2
        net.ipv4.neigh.default.gc_thresh2 = 512

        # sysctl net.ipv4.neigh.default.gc_thresh1
        net.ipv4.neigh.default.gc_thresh1 = 128
      • Updated configuration:
        # Setup DNS threshold for arp
        net.ipv4.neigh.default.gc_thresh3 = 4096

        net.ipv4.neigh.default.gc_thresh2 = 2048

        net.ipv4.neigh.default.gc_thresh1 = 1024
    7. Run service vcops restart collector to restart the vCenter Operations Manager Collector service.
      Note: vCenter Operations Manager does not collect data while the Collector service restarts.

  • Slow loading of dashboards for large View environments
    The View Infrastructure and the View VDI Pools dashboards might take a long time to load when monitoring View environments that have several thousand desktops.

  • 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 vCenter Operations Manager for Horizon 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 vCenter Operations Manager Custom user interface.

  • Existing linked-clone desktops must be recomposed
    If you created desktop pool images that utilize linked clones prior to installing vCenter Operations Manager for Horizon 1.6, you must to recompose the linked clones to include the vCenter Operations Manager for Horizon View 6.0 Desktop Agent in the image.

  • User names that include multibyte characters might not appear correctly in the vCenter Operations Manager Custom user interface

  • Network related alerts are not generated for user sessions that were established before the vCenter Operations Manager for Horizon View adapter was set up
    The following alerts are not generated for user sessions that were initiated before the configuration of an adapter instance:
    • PCoIP|Round Trip Latency (ms)
    • PCoIP|Packet Loss Percent
    See PCoIP performance is slower than expected (KB 1030695) for troubleshooting high latency and packet loss issues.

  • "General error occurred." appears on the Update tab in the Administration Console after you install the Adapter
    Although this message indicates that an error occurred, the Adapter is installed successfully and the adapter instance is created. You can ignore this message.

  • View Administrator commands do not run in vCenter Server (JMS issue)
    View Administrator commands do not run in vCenter Server when the vCenter Operations Manager for Horizon broker agent is installed on the View Connection Server host. The problem occurs when message security is turned off for the JMS. See View Administrator commands do not run in vCenter Server when the V4H Broker Agent is installed (KB 2090736) for solutions to this problem.

    To change the JMS log level for troubleshooting:
    1. Create a v4v-jmslistener.properties configuration file in the \ProgramData\VMware\vCenter Operations for View\conf folder on the View Connection Server host.
    2. Add the following 1 line to v4v-jmslistener.properties:
      Log4j.rootLogger=TRACE
    3. Restart the broker agent by using the broker agent configuration utility or the service manager.
      Logs are in \ProgramData\VMware\vCenter Operations for View\logs\v4v_jmslistener.log.

    To turn off the JMS listener in the broker agent:
    1. Stop the vCenter Operations for View Broker Agent service.
    2. Edit the \ProgramData\VMware\vCenter Operations for View\conf\v4v-brokeragent.config configuration file.
    3. Change the value of <jms_monitor_interval> to 0.
      For example:  <jms_monitor_interval>0</jms_monitor_interval>
    4. Save the configuration file.
    5. Restart the vCenter Operations for View Broker Agent service.

Top of Page