Known Issues

The Citrix Analytics service has the following known issues:

  • Gateway Action is not working with User, after the user-correlation is enabled. This issue occurs when aaaUsername field is incorrect. [CAS-40978]

  • For existing users, Citrix Analytics displays user names with repeated or different domain names in the events sent by the Citrix Virtual Apps and Desktops data source. This issue occurs in cloud brokered published virtual apps and desktops sessions with Citrix Workspace. [CAS-33767]

  • For some newly onboarded Citrix Virtual Apps and Desktops users, the Log Off User policy-based action fails to take effect when the First time access from new device risk indicator is triggered. [CAS-35310]

  • For Citrix Endpoint Management users, the policy-based or manually applied actions on the user accounts fail to take effect. [CAS-33934]

  • Citrix Analytics displays unidentifiable application names that are sent by the Citrix Virtual Apps and Desktops data source. This issue occurs only in events reported by the Citrix Workspace app for Mac platform.

    [CAS-29583]

  • Few versions of Citrix Workspace app and Citrix Receiver do not send specific events to Citrix Analytics. Therefore, Citrix Analytics cannot provide insights and generate risk indicators for these events. [CAS-16151]

    The following table lists the events and its transmission states:

    • Yes- The event is transmitted from the client to Citrix Analytics.
    • No- The event is not transmitted from the client to Citrix Analytics.
    • NA- The event is not applicable for the client version.
    Event Workspace app for Windows 1808 or later Workspace app for Mac prior to version 1910 Workspace app for Mac 1910 or later Workspace app for Linux 2006 or later Workspace app for Android 1809 or later Workspace app for iOS 1811 or later Workspace app for Chrome 1809 or later Workspace app for HTML5 1809 or later Receiver for Windows 4.11 Receiver for Windows 4.12 Receiver for Mac 12.9.1
    Account Logon Yes No Yes Yes Yes Yes No No Yes Yes No
    Session Logon Yes No Yes Yes Yes Yes Yes Yes Yes Yes No
    Session Launch Yes No Yes Yes Yes Yes Yes Yes Yes Yes No
    Session End Yes No Yes Yes Yes Yes Yes Yes Yes Yes No
    App Start Yes No Yes Yes No Yes Yes Yes Yes Yes No
    App End Yes No Yes Yes No Yes Yes Yes Yes Yes No
    File Download Yes Yes Yes Yes No No Yes Yes Yes Yes Yes
    Printing No Yes Yes Yes No No Yes Yes Yes Yes Yes
    SaaS App Launch Yes Yes Yes No No No No No NA NA NA
    SaaS App End Yes Yes Yes No No No No No NA NA NA
    SaaS App URL Navigation Yes Yes Yes No No No No No NA NA NA
    SaaS App Clipboard Access Yes Yes Yes No No No No No NA NA NA
    SaaS App File Download Yes Yes Yes No No No No No NA NA NA
    SaaS App File Print Yes Yes Yes No No No No No NA NA NA

    Based on the event transmission state, you might encounter the following issues:

    • When users connect to their Citrix environment using the clients, they might not get discovered in Citrix Analytics until they perform an action that has a supported event. For example, consider two user events - App Start and SaaS App Launch. If a user is using Citrix Workspace app for iOS 1811 or later, the App Start event is discovered, whereas the SaaS App Launch event is not discovered by Citrix Analytics. For information on discovered users, see Discovered users.

    • Events marked as No on the table do not appear on the self-service search page. For information on how to use the self-service page, see About self-service search.

    • Risk indicators cannot be reliably triggered when the users use one of the clients- Citrix Workspace apps for Mac, Citrix Workspace app for Chrome 1809, Citrix Workspace app for HTML5 1809, or Citrix Receiver for Mac. For information on the risk indicators for Virtual Apps and Desktops, see Citrix Virtual Apps and Desktops risk indicators.

    • The Self-service search for Virtual Apps and Desktops page displays multiple app start and app end events when virtual apps are launched only once. This issue occurs on Citrix Workspace app for Linux client versions. [CAS-36236]

    • Citrix Workspace app for Linux fails to send printing events to Citrix Analytics when apps and desktops are enumerated through a web browser and launched from ICA on the native client. [CAS-36238]

    To get maximum benefits of Analytics, Citrix recommends the following:

    • Windows user: Connect to your Citrix environment using Citrix Workspace app for Windows 1808 or later.

    • Mac user: Connect to your Citrix environment using Citrix Workspace app for Mac 1910 or later.

    Note

    Citrix Receiver for Windows 4.11 reached End of Life (EOL) in August 2019 and Citrix Receiver for Windows 4.12 reached End of Life (EOL) in December 2019.

    For more information on the lifecycle strategy of Citrix Workspace app and Citrix Receiver on all platforms, see Lifecycle Milestones for Citrix Workspace app & Citrix Receiver.

  • If you specify a policy-based action for the Unusual Application (SaaS) risk indicator, the action is not applied automatically when the risk indicator is triggered.

    Workaround: Apply action manually for the risk indicator on the user’s risk timeline. [CAS-14667]

  • Citrix Workspace app for iOS fails to transmit data to Citrix Analytics when apps and desktops are launched from a web browser. However, Android client versions 20.3.0 or later, Windows client versions 2006.1 or later, Mac client versions 2006 or later, and Linux client versions 2006 or later support this transmission.

    Workaround: Launch applications through the native Citrix Workspace app on the Mac, Linux, iOS, Android, or the Windows user interface. For more information on the supported versions, see the issue CAS-16151 with the updated table.

  • In the user’s profile page, if you apply an action manually without selecting the appropriate risk indicator in the Risk Timeline, the following error is displayed: “Unable to apply [product] actions.”

    Workaround: To apply an action, first select the risk indicator in the Risk Timeline. Then, select an action for the same product the risk indicator originated from.

    Note

    Currently, you can apply manual actions only to the product from which the risk indicator originated. For more information, see Policies and actions.

Known Issues