VMware vCenter Operations Manager for Horizon View 1.5.1 Release Notes
VMware

VMware vCenter Operations Manager for Horizon 1.7 Release Notes

vCenter Operations Manager for Horizon 1.7 | 09 September 2014

Last Document Update: 02 October 2014

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

Key Features

VMware vCenter™ Operations Manager for Horizon™ extends the functionality of VMware vCenter™ Operations Manager™ to monitor and manage VMware Horizon™ with View™ 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 in This Release

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

  • Support for vCenter Operations Manager 5.8.3
    vCenter Operations Manager for Horizon 1.7 is compatible with vCenter Operations Manager 5.8.3. It does not support earlier vCenter Operations Manager versions.
  • In-guest process data collection for remote desktops
    You can use the new Data Collection Results widget to collect and display in-guest process data for remote desktops. In-guest process data is separate from and in addition to the desktop metrics that the vCenter Operations Manager for Horizon adapter typically collects.
  • Recent task information
    You can use the new Recent Tasks tab on the vCenter Operations Manager Support page (Admin > Support) to view a list of recent tasks, display detailed and associated object information for selected tasks, and filter tasks and detailed information based on selected criteria.
  • View dashboard enhancements
    The new Data Collection Results widget has been added to the View Remote Session Details and View RDS Host Details dashboards.

Limitations

vCenter Operations Manager 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 Horizon View 5.0 View Connection Server instances are not supported
    vCenter Operations Manager for Horizon 1.7 supports only 64-bit View Connection Server 5.0 instances.

Top of Page

Licensing Notes

This section contains notes on the licensing of vCenter Operations Manager for Horizon 1.7.
  • vCenter Operations Manager for Horizon 1.7 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

This section contains notes on the installation process for each vCenter Operations Manager for Horizon component. For complete installation instructions, see the vCenter Operations Manager for Horizon 1.7 Supplement document.

  • You download the vCenter Operations Manager for Horizon installation files from the VMware download page.
  • You install the vCenter Operations Manager for Horizon adapter in a vCenter Operations Manager 5.8.3 vApp. You install the adapter PAK file through the vCenter Operations Manager Administration Portal.
  • You install the vCenter Operations Manager 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 vCenter Operations Manager 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.

Top of Page

Upgrade Notes

You can upgrade to vCenter Operations Manager for Horizon 1.7 from vCenter Operations Manager for View 1.5.1 or vCenter Operations Manager for Horizon 1.6. To upgrade from an earlier version, you must upgrade to 1.5.1 and then upgrade to 1.7.

This section contains notes on the upgrade process. For complete upgrade instructions, see the the vCenter Operations Manager for Horizon 1.7 Supplement document.

  • You must first update the vCenter Operations Manager for Horizon adapter. Next, you must uninstall the broker agent before you install the new broker agent. Your existing vCenter Operations Manager for Horizon installation configuration is saved.
  • Additional configuration steps are required when you configure vCenter Operations Manager for Horizon to monitor a View 5.0 or 5.1 environment. (See the vCenter Operations Manager for Horizon 1.7 Supplement document for these additional steps.) If you later upgrade your monitored View environment to Horizon View 5.2, Horizon View 5.3, or Horizon 6.0 with View, you must revert these steps by performing the following tasks.

    Re-enable RMI authentication:
    1. Connect to the Analytics VM of the vApp where you installed the vCenter Operations Manager for Horizon adapter and log in as the root user.
    2. In a text editor, open the the /usr/lib/vmware-vcops/user/plugins/inbound/V4V_adapter3/work/msgserver.properties file and remove the line disable-authentication = true.
    3. 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 of time.
    4. On the View Connection Server host 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 host where you installed the broker agent, open the broker agent configuration dialog box.
    2. Under Service status, click Stop and then click Start.
    (Optional) Disable or remove the remote desktop GPO: Optionally, you can disable or remove the GPO that you created for 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 complies with I18N Level 1. Although vCenter Operations Manager for Horizon is not localized, it can run on non-English operating systems and handle non-English text.

Top of Page

Prior Releases

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

Documentation Resources

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

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

Top of Page

Resolved Issues

This section contains resolved issues for this release.

  • The default database schema name is now used to access the View Events database according to the database account. Previously, "dbo" was assumed.
  • A potential conflict caused View Connection Server JMS timeouts. 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.

  • Changing the adapter name causes the View Adapter Status dashboard to display incorrect data
    If the name of the vCenter Operations for Horizon 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, perform these steps in the vCenter Operations Manager Custom user interface:
    1. Select Environment > Environment Overview.
    2. Expand Resource Kinds and select View Adapter Collector.
    3. Select the View Adapter object in the right pane and click the Edit Resource icon.
    4. Update the V4H Adapter Instance name with the current name of the adapter instance.
    5. Click OK to save your changes.

  • Desktop agent returns the same metrics for each session on an RDS host
    If there are multiple sessions on an RDS host, the vCenter Operations for Horizon desktop agent returns the same session metrics (CPU, memory, and so on) for each of the sessions. This problem applies only to Horizon 6.0 with View installations.
    Workaround: Upgrade to the 6.0.1 View Agent, or manually install the desktop agent included with vCenter Operations Manager for Horizon 1.7. (The desktop agent included with vCenter Operations Manager for Horizon 1.7 is the same as the desktop agent included with the 6.0.1 View Agent.)

  • Pod Session Metrics and Health Status widgets show incorrect data if a desktop user switches from RDP to PCoIP
    If a user connects to a remote desktop with the RDP display protocol, logs off from the remote desktop, and then reconnects to the remote desktop with the PCoIP display protocol, the Pod Session Metrics widget on the View Overview dashboard does not report the correct number of RDP and PCoIP sessions. The number of connections reported by the Health Status widget on the vCenter Operations Manager Resource Detail page is also incorrect.

  • 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