Known issues
-
Upgrading the Session Recording server fails when “Require SSL” is enabled in IIS for the SessionRecordingBroker application and only TLS 1.2 is enabled for the server-side protocol on the SR server.
To work around this issue, complete the following steps:
- Temporarily Disable SSL: On the Session Recording server, open IIS Manager. For the SessionRecordingBroker application, go to SSL Settings and uncheck “Require SSL”.
- Run Upgrade: Execute the upgrade installer for the Session Recording server.
- Re-enable SSL: After the upgrade completes, go back to the SSL Settings in IIS and re-check “Require SSL” for the SessionRecordingBroker application.
-
If you are using Citrix Web App Firewall (WAF) signatures to mitigate in part the CVE-2021-44228 vulnerability, Session Recording might not work as expected. To resolve the issue, exclude the IP addresses of your Session Recording servers from the mitigate_cve_2021_44228 policy on the NetScaler side. [CVADHELP-24365]
-
A domain user with local administrator privileges on the machine where the Session Recording Policy Console is installed can add both local users and domain users to which the action of a policy rule applies. However, a local user with local administrator privileges can add only local users but not domain users. [SRT-5769]
-
The web player might not work properly if you upgrade it from Version 2009 or earlier. To work around the issue, clear your browser cache. [SRT-5624]
-
Rules of Session Recording custom policies might be lost after you update Session Recording from the version included in the XenApp and XenDesktop 7.6 LTSR to the latest version. As a workaround, before updating Session Recording to the latest version, update the software to the version included in the latest CU of the XenApp and XenDesktop 7.15 LTSR and then update it to the latest release. [SRT-4546]
-
When Machine Creation Services™ (MCS) or Provisioning Services (PVS) creates multiple VDAs with the configured master image and Microsoft Message Queuing (MSMQ) installed, those VDAs can have the same
QMIdunder certain conditions. This case might cause various issues, for example:- Sessions might not be recorded even if the recording agreement is accepted.
- The Session Recording Server might not be able to receive session logoff signals and therefore, sessions might always be in a live state.
For information about a workaround, see Install, upgrade, and uninstall. [#528678]