VMware vRealize Operations for Published Applications Release Notes

Updated on: 05 DEC 2016

VMware vRealize Operations for Published Applications Release Notes | 06 SEP 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

VMware vRealize™ Operations for Published Applications™ extends the functionality of VMware vRealize™ Operations Manager™ to monitor and manage Citrix XenApp 6.5 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.


Features in This Release

vRealize Operations for Published Applications 6.1.1 includes the following new features.

  • As of 05 DEC 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.
  • TLS 1.1 and TLS 1.2 support - The vRealize Operations for Published Applications 6.1.1 supports TLS 1.1/TLS 1.2 for enhanced security. By default, TLS 1.1/TLS 1.2 is enabled and TLS 1.0 is disabled.

Limitations

vRealize Operations for Published Applications has the following limitations.

  • You cannot select the Choose a unit option in Application User Statistics.
  • Creating more than one vRealize Operations for Published Applications adapter instance per cluster node or remote collector is not supported.
  • VMware vRealize Operations for Published Applications 6.1.1 does not support high availability (HA). If a Published Applications adapter instance is moved to a different cluster node, the broker and desktop agents can no longer communicate with the vRealize Operations for Published Applications adapter and the VMware vRealize Operations for Published Applications 6.1.1 solution stops functioning. See http://kb.vmware.com/kb/2119460 for additional details and solutions.
  • When the broker agent is down the Collection Status remains as Collecting for the following objects.
    • XA Farm
    • XenApp Clients (logical tier)
    • XenApp Infrastructure (logical tier)
    • XA Web Interface
    • XenApp License Server
    • XenApp Store Front
    • XenApp Receiver

Installation Notes

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

  • vRealize Operations for Published Applications 6.1.1 is compatible with the following vCenter Server, vRealize Operations Manager, and Citrix XenApp versions:
    • VMware vCenter Server 5.5 or 6.0
    • VMware vRealize Operations Manager 6.0.2
    • Citrix XenApp 6.5 for Windows Server 2008 R2
  • You download the vRealize Operations for Published Applications installation files from the VMware download page.
  • You install the vRealize Operations for Published Applications adapter on a vRealize Operations Manager 6.0.2 cluster node or remote collector.
  • You install the vRealize Operations for Published Applications broker agent on a Windows machine. You install a broker agent for each farm in your environment.
  • You install the vRealize Operations for Published Applications desktop agent on all Citrix Delivery Controllers and Session Host servers.

Resolved Issues

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

  • The vRealize Operations for Published Applications Broker Agent that released with VMware vRealize Operations for Published Applications 6.1.1 in September 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

  • If an end user is logged in to an application session before you install vRealize Operations for Published Applications, some data does not appear in the XA Application Usage dashboard.
    If an end user is logged in to an application session before you install vRealize Operations for Published Applications, the data for that application session does not appear in the Application User Statistics widget in the XA Application Usage dashboard. Some of the session metrics are not displayed for these sessions in the XA Session Detail dashboard.

    Workaround: The end user must log out of the application session and then log in to the application session.

  • Exceptions in the desktop agent log files might appear after you install the desktop agent.
    After you install the desktop agent, the desktop agent might display exceptions in the agent log files until the Group Policy (GPO) successfully refreshes and obtains the message server URL and adapter certificate.

    Workaround: There is no workaround for this issue.

  • The daily usage count data might be cleared.
    When you restart the vRealize Operations for Published Applications adapter, the daily usage count data is cleared.

    Workaround: There is no workaround for this issue.

  • Desktop agent log files might contain messages for missing performance counters.
    The desktop agent log files might contain messages for missing performance counters as Failed to subscribe provider of source 'perfmon' to metric xxxxxxx|xxxxxxxxxx.

    Workaround: Run the lodctr /r command to recreate some of these performance counters.

  • vRealize Operations for Published Applications cannot identify which executable image is associated with which image.
    When two applications that reference the same executable image are assigned to the same user, and the user launches two instances of the executable image by using both applications, vRealize Operations for Published Applications cannot identify which executable image is associated with which application. Data from the first application might be sent to the first application.

    Workaround: There is no workaround for this issue.

  • You are prompted to restart your machine.
    When you repair the broker agent, the installer prompts you to restart your machine.

    Workaround: You do not have to restart your machine. Click No and start the broker agent service manually.

  • When you test the connection between the broker agent and the adapter before pairing the broker agent with the adapter, the procedure fails.
    In the broker agent utility, if you click Test before pairing with the adapter, the pairing procedure fails.

    Workaround: Close the broker agent utility, open it again, and click Pair before you click Test.

  • Data is displayed in the Farm Indicator Metrics widget, but the No Data tag appears.
    Data is displayed in the Farm Indicator Metrics widget, but the No Data tag appears.

    Workaround: Verify that the time is synced between the XenApp server and vRealize Operations Manager.

  • After you delete an object form the Citrix AppCenter, the object still appears in vRealize Operations Manager but no data is collected.
    When you delete an object from the Citrix AppCenter, for example a farm or workgroup, the object still appears in vRealize Operations Manager but no data or metrics are collected for the object. Object relationships are removed from the vRealize Operations Manager.

    Workaround: There is no workaround for this issue.

  • A session appears in the XA Session Details dashboard after you log off of that session.
    After you log off of a session from the Citrix receiver, that session still appears in the XA Session Details dashboard and no data is collected.

    Workaround: Log in to vRealize Operations Manager and select Administration > Environment Overview, and select the object that you want to delete.

  • If an end user is logged in to an application session before you install vRealize Operations for Published Applications, some data does not appear in the XA Session Detail dashboard.
    If an end user is logged in to an application session before you install the vRealize Operations for Published applications desktop agent, values for Launch Time, Logon Duration, Profile Load Duration, and Session Duration for the session do not appear in the XA Session Detail dashboard.

    Workaround: The end user must log out of the application session and then log in to the application session.

  • The String Value column is empty when you export data to a CSV file.
    When you export the data from the Application User Statistics widget to a CSV file, the String Value column might be empty.

    Workaround: To populate the String Value column:

    1. In vRealize Operations Manager, click Administration, and select the VMware Published Application solution.
    2. Select the adapter instance on which the issue is occurring.
    3. Click Stop collecting, and wait several minutes.
    4. Click Start collecting and wait approximately ten minutes for the vRealize Operations for Published Applications objects to start collecting data.
    5. Export the data from the Application User Statistics widget to a CSV file.

  • The first instance of a unique user's data is not captured and displayed in vRealize Operations Manager.
    The first instance of a unique user's data, for example user data for an XA Application object, that is collected by vRealize Operations for Published Applications is not captured and displayed in vRealize Operations Manager.

    Workaround: There is no workaround for this issue.

  • The Memory Page Faults Per Second metric in the Application Instance Metrics widget on the XA Application dashboard displays as No Data.
    The Memory Page Faults Per Second metric in the Application Instance Metrics widget on the XA Application dashboard displays as No Data.

    Workaround: To populate the Memory Page Faults Per Second metric:

    1. Select Content -> Manage Metric Config.
    2. Expand the ReskndMetric folder, and select the common_object.xml file.
    3. Click the pencil icon to edit the common_object.xml file.
    4. Change the app_io|page_faults_per_second parameter to app_memory|page_faults_per_second, and click Save.