VMware vRealize Operations for Published Applications 6.2.1 Release Notes

|

VMware vRealize Operations for Published Applications 6.2.1 | 17 Mar 2016

Last Document Update: 21 NOV 2016

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

About vRealize Operations for Published Applications 6.2.1

This section contains information about vRealize Operations for Published Applications

VMware vRealizeTM Operations for Published ApplicationsTM extends the functionality of VMware vRealizeTM Operations ManagerTM to monitor and manage Citrix Xen Desktop/XenApp 7.6 environments. vRealize Operations for Published Applications collects data about your resources and presents that data in pre-configured dashboards for both real-time and predictive analysis.

What's New in This Release

vRealize Operations for Published Applications focuses on the following features.

Installation Notes

This section contains notes on the installation process for each vRealize Operations for Published Applications component.

  • vRealize Operations for Published Applications is compatible with the following vCenter Server, and vRealize Operations Manager.
    • VMware vCenter Server 5.5 and 6.0
    • VMware vRealize Operations Manager 6.0.3, 6.1, and 6.2.
    • Citrix XenDesktop 7.6 FP3 for Windows 10 VDI support and Windows Server 2012
  • You download the vRealize Operations for Published Applications 6.2.1 installation files from the VMware download page.
  • You install the vRealize Operations for Published Applications Adapter on a vRealize Operations Manager 6.2 cluster node or remote collector.
  • You install the vRealize Operations for Published Applications Broker agent on the Active Delivery Controller.
  • You install the vRealize Operations for Published Applications desktop agent on all Citrix Delivery Controllers, RDS Host servers, Licensing Server, and all VDI Hosts.
  • Controller's certificate should be added as trusted, if SSL is enabled for ODATA (monitoring service).

Limitations

vRealize Operations for Published Applications has the following limitations.

  • Upgrade from vRealize Operations for Published Applications 6.1.0 to 6.2.1 is not supported.
  • Creating more than one vRealize Operations for Published Applications adapter instance per cluster node or remote collector is not supported.
  • High availability (HA) is not supported.

Resolved Issues

The following issues were resolved in vRealize Operations for Published Applications 6.2.1.

  • The vRealize Operations for Published Applications Broker Agent that released with VMware vRealize Operations for Published Applications 6.2.1 in March 2016 uses a digital signature that has since expired. As a result, the broker agent service cannot start up correctly, which will cause errors. To resolve the issue, update to the new vRealize Operations for Published Applications Broker Agent . See KB 2147906 for more information.

Known Issues

  • There is an error in the log files if an application name has special characters.
    If an application name has special characters, there is an error in the desktop agent log "Skip collect sample for Application".
    Workaround: None.

  • The Broker Agent cannot communicate with Citrix PVS Servers if a firewall is enabled on them.
    Workaround: Apply the following rules to the firewalls of all PVS servers:
    • Ping should be enabled using the File and Printer Sharing (Echo Request -ICMPv4-In) rule.
    • Remote WMI should be enabled using the Windows Management Instrumentation (WMI-In) rule.

  • If a lot of historic data is stored in Citrix database, some sessions metrics might be missed.
    Workaround: Add the configuration key in the v4-brokeragent.config file.
    <max_session_count>500000</max_session_count>
    Note: 500000 is an example; you can choose a bigger value if required.