VMware vRealize Operations for Published Applications 6.3 Release Notes

|

VMware vRealize Operations for Published Applications 6.3 | 16 JUN 2016

Last Document Update: 18 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.3

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 XenDesktop/XenApp 7.6, 7.7, and 7.8 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.

  • As of 18 NOV 2016, there is a new vRealize Operations for Published Applications Broker Agent available that addresses an issue caused by an expired digital signature. See Resolved Issues for more information.
  • Support for Citrix XenDesktop and XenApp 7.6, 7.7, and 7.8.
  • Help Desk dashboard enables help desk administrators to quickly troubleshoot a user session from a single dashboard.
  • Improve scalability performance by automatically clearing unused objects.

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 later
    • VMware vRealize Operations Manager 6.0.3, 6.1, 6.2, 6.2.1, and 6.3.
    • Citrix XenDesktop and XenApp 7.6, 7.7 and 7.8.

    For the most current information about supported versions, see the VMware Product Interoperability Matrixes.

  • Download the vRealize Operations for Published Applications 6.3 installation files from the VMware download page.
  • Install the vRealize Operations for Published Applications Adapter on a vRealize Operations Manager 6.2.1 cluster node or remote collector.
  • Install the vRealize Operations for Published Applications Broker agent on the Active Delivery Controller.
  • 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 must 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.3 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.
  • Multizone is supported collection of zone information is not supported.
  • When the primary controller (broker) fails, administrators must manually configure and enable the broker agent at the back-up contoller (broker).

Resolved Issues

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

  • The vRealize Operations for Published Applications Broker Agent that released with VMware vRealize Operations for Published Applications 6.3 in June 2016 uses an 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.
  • Performance - Fixed Broker Agent/Desktop Agent memory leak issue.
  • Performance - Broker Agent filters the historic objects.
  • Stability - RMI connection enhancement.
  • Performance - Added machine-session map to reduce the use of xpath.
  • Performance - Reduce the use of vRealize Operations Manager API
  • Performance - Fix GPO refresh issue.
  • Stability - Added smaller granularity TTL for unused object.

 

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.

  • Launch Application Metric under User Resource kind shows the application ID instead of the name.
    Workaround: None.

  • When you upgrade from vRealize Operations for Published Applications 6.2 to vRealize Operations for Published Applications 6.3, there will be two vRealize Operations for Published Applications solutions in vRealize Operations Manager namely vRealize Operations for Published Applications 6.2 and vRealize Operations for Published Applications XD-XA.
    Workaround: Go to Adminstration > Licensing. Delete the vRealize Operations for Published Applications 6.2 solution in the License Key tab. Apply the license key to the new solution. Create a new adapter instance and pair with the broker agent again.

  • Sometimes, Application Instance count is not updated in the XD-XA Server Applications dashboard.
    Workaround: Restart the desktop agent service on the RDSH host, log off all the sessions, and log in again.

  • XD-Site resource kind shows old licensing name (6.2) as a parent in topology relationship. This does not impact any functionality.
    Workaround: None.

  • Even after the deletion of site environment, the stale entries are retained on the dashboards.
    Workaround: Run service vmware-vcops --full-restart to restart the service. Login to vRealize Operations Manager. Go to Administrator > Inventory Explorer, and select the objects and delete manually.

  • When you upgrade adapter from 6.2 or 6.2.1 to 6.3, the collection state of the adapter instance shows failed.
    Workaround: Either restart the collector service. Run service vmware-vcops --full-restart. Or, restart the vRealize Operations Manager appliance.