VMware vRealize Operations for Published Applications 6.4 Release Notes

|

Updated on: 08 DEC 2016

VMware vRealize Operations for Published Applications 6.4 | 08 DEC 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

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, 7.8, 7.9, and 7.11 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.

  • Application Crash Alerts - VMware vRealize Operations for Published Applications now enables you to monitor events when an application launched inside a session crashes.  The crash alert summary is shown on the alerts page.  Click the link for the alert to see details of the crash, including cause and recommended action.
  • App Volumes Support - VMware vRealize Operations for Published Applications now includes optional App Volumes monitoring. With this feature, you can see which App Stacks are attached to sessions and users and view their attach times. Additionally, by viewing objects related to sessions and users, you can see associated stacks and discern, for example, which App Volumes Manager controls a stack, or which AD is associated with it.
Additionally, a new XD-XA App Volumes Environment item on the Environment Overview lets you view summary information and metrics for App Volumes servers and App Stacks. 

App Volumes releases 2.10 and 2.11 are supported in this release. 
  •  Root Cause Analysis - VMware vRealize Operations for Published Applications now includes a Root Cause Analysis Dashboard.  Reachable from the XD-XA Help Desk and XD-XA User dashboards, it provides metrics for objects associated with sessions, and uses colors (green, yellow, and red) to indicate metrics that may require troubleshooting.  Additionally, clicking on a metric displays it in a chart view that shows the given metric over time, enabling further analysis. 
  • XenDesktop 7.11 Support - VMware vRealize Operations for Published Applications now supports monitoring of XenDesktop 7.11 environments, including RDS catalogs, with Windows Server 2016, in addition to supporting Citrix XenDesktop and XenApp 7.6, 7.7, 7.8, and 7.9. 
  • New Widgets - VMware vRealize Operations for Published Applications includes the following new widgets:
    • Desktop Applications:  Available on the XD-XA VDI Desktops Dashboard, this widget displays a list of all the configured applications hosted by a VDI desktop.
    • Desktop Application Users:  Available on the XD-XA VDI Desktops Dashboard, this widget displays a history of user logon information for a selected application, indicating who uses the application, and when the application is used.
      Desktop Applications Launched by User:  Available on the XD-XA Session Details Dashboard, this widget displays when and which application hosted by a VDI desktop was launched by the selected user in a selected time period.
      VM Host:  Available on the XD-XA Help Desk Dashboard, this widget displays the ESXi host of the related VM that is hosting a session.
    • Host Metrics:  Available on the XD-XA Help Desk Dashboard, this widget displays metrics of a selected host.
    • How to Use the Help Desk Dashboard and How to Use the XD-XA User Experience widgets.
  • New Reports - VMware vRealize Operations for Published Applications includes the following new reports for 6.4:
    • XD-XA Application Instance Usage Report:  includes information about CPU and memory usage of an application instance.
    • XD-XA Desktop Application Instance Usage Report:  includes information about CPU and memory usage of a desktop application instance.
    • XD-XA Desktop Application Usage Report:  includes information about desktop application usage. 

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, 6.3, and 6.4.
    • Citrix XenDesktop and XenApp 7.6, 7.7, 7.8, 7.9, and 7.11.

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

  • Download the vRealize Operations for Published Applications 6.4 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.

  • Upgrade from vRealize Operations for Published Applications 6.1.0 to 6.4 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.4. 

  • Functionality - In vRealize Operations for Published Applications 6.3, in-guest metrics would sometimes disappear after a browser refresh.  This has been fixed in 6.4. 
  • Performance - All string metrics have been changed to properties to avoid a thread block issue in the Analytic Module of vRealize Operations Manager.
  • Performance - Fixed an issue with high CPU usage with the Desktop Agent, which was caused by frequently invoking the WMI query API.
  • Performance - Fixed a Desktop Agent memory leak issue.
  • Security - Dual sign is now used for all binary and installation packages
  • Stability - Enhancements have been made to RMI connections.
  • Upgrade – You no longer need to update a vRealize Operations Manager firewall rule after upgrading vRealize Operation Manager to 6.4 or above.  
  • Usability - The V4H config file has been migrated from older versions to 6.4. 

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. 
    Workaround:  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".
    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.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.
    Workaround: 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.
    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.4, 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.