VMware vRealize Operations for Published Applications Release Notes

|

Updated 21 SEP 2017

VMware vRealize Operations for Published Applications 6.5 | 21 SEP 2017

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

VMware vRealizeTM Operations for Published ApplicationsTM extends the functionality of VMware vRealizeTM Operations ManagerTM to monitor and manage Citrix XenDesktop/XenApp 7.13, 7.14, and 7.15 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

vRealize Operations for Published Applications focuses on the following features.

  • Nvidia vGPU Monitoring -- VMware vRealize Operations for Published Aplications supports monitoring the usage of Nvidia vGPU on ESXi hosts. To use this feature, you must have the Nvidia vGPU adapter installed, then import the integrated dashboards for vGPU monitoring. With this feature, you can check the usage of vGPU for each session and the usage and health of each vGPU in your environment.
  • New Process Alerts -- vRealize Operations for Published Applications enables you to monitor processes by triggering an alert and offering a recommendation for any process abnormalily in your VM.

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:

  • VMware vCenter Server 6.0 and later
  • VMware vRealize Operations Manager 6.4, 6.5, 6.6, 6.6.1.
  • Citrix XenDesktop and XenApp 7.13, 7.14 and 7.15

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

  • Download the vRealize Operations for Published Applications 6.5 installation files from the VMware download page.
  • Install the vRealize Operations for Published Applications Adapter on a vRealize Operations Manager 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.

  • Upgrading from vRealize Operations for Published Applications 6.1.0 to 6.5 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 this release.  

  • vRealize Operations for Published Applications 6.4 failed to monitor Storefront server when it is configured with a NetScaler load balancer. This issue is fixed in this release.
  • Sessions are no longer missing in a workload.
  • Some users are not listed in reports.
  • Data no longer missing when using XenDesktop Standard/Enterprise license.
  • Adapter installation is improved so it can be installed faster.

Known Issues

  • Database-related alerts may not be visible.

    A database-related alert may not be visible if the site database is down. When a site database is down, the PowerShell becomes very slow and can take up to several minutes to get a result. As the broker agent has a task thread to monitor the system health, it can take a long time to finish all queries.  

    None.

  • 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".

    None.

  • The Broker Agent cannot communicate with Citrix PVS Servers if a firewall is enabled on them.

    • Apply the following rules to the firewalls of all PVS servers:
      • Enable Ping using the File and Printer Sharing (Echo Request -ICMPv4-In) rule.
      • Enable Remote WMI 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.

    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.

    None.

  • When you upgrade from vRealize Operations for Published Applications 6.2 to vRealize Operations for Published Applications 6.4, 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.

    Go to Administration > 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.

    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.

    None.

  • Even after the deletion of site environment, the stale entries are retained on the dashboards.

    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.5, the collection state of the adapter instance shows failed.

    Either restart the collector service. Run service vmware-vcops --full-restart. Or, restart the vRealize Operations Manager appliance.