-
What's new
-
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
What’s new
What’s new in 2411
This release includes the following new features and addresses issues to improve the user experience:
Important note about upgrading to version 2411:
To prevent session recording failures due to incomplete upgrades of Session Recording agents, follow these steps when upgrading to 2411:
- Upgrade each Session Recording server to version 2411.
Enable remote access using .NET Remoting with the following command:
<Session Recording server installation path>\Bin\SsRecUtils.exe -EnableBrokerRemoting <!--NeedCopy-->- Upgrade each Session Recording agent to version 2411.
After all Session Recording agents are upgraded, disable remote access using .NET Remoting with the following command:
<Session Recording server installation path>\Bin\SsRecUtils.exe -DisableBrokerRemoting <!--NeedCopy-->
Group Service Managed Account (gMSA) support for Session Recording
Session Recording now supports Group Service Managed Account (gMSA) to simplify service principal name (SPN) management for services running on multiple servers. This feature enhances security and simplifies the management of service accounts. For more information, see the best practice article: Configure Group Service Managed Accounts (gMSA) support for Session Recording.
Support for Microsoft Entra ID authentication
In addition to SQL Server authentication, Session Recording now supports Entra ID authentication for cloud-based SQL databases including Azure SQL Database and Azure SQL Managed Instance. To enable Entra ID authentication, include the AADPASSWORD parameter and set it to 1 when installing the Session Recording database through the command line. For more information, see Install, upgrade, and uninstall.
Support for installing databases on separate Instances
You can now install the Session Recording database and Session Recording admin logging database on separate instances. To enable this feature, complete the following steps before installing the databases:
- Go to the machine where the Session Recording server is installed.
- Open the Registry Editor.
- Modify the registry:
- Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SmartAuditor\Server. - Add the
SmAudDatabaseLoggingStateDWORD (32-bit) value and set the value data to1. - Add the
SmAudDatabaseLoggingInstancevalue. Set the value data to the instance name where you want to install the Session Recording admin logging database.
- Navigate to
Later when you install the databases through either a GUI or command line, the admin logging database is installed on the separate instance specified by the SmAudDatabaseLoggingInstance registry value. For more information about Session Recording installation, see Install, upgrade, and uninstall.
Capturing printing activities in recorded sessions is now generally available
You can capture printing activities that occur during recorded sessions and tag them as events in recordings for later search and playback. The feature is now generally available and has been enhanced to capture the full paths of printed files. For more information, see Configure event detection policies.
Enhanced diagnostic logging
More types of diagnostic logs, beyond message queue quota exceedance, can now be detected on the Virtual Delivery Agents (VDAs) and sent to the Session Recording server. Previously, diagnostic logs were visible in the Windows Event Viewer, but they are now visible in the Session Recording web player. For more information, see View diagnostic logging.
What’s new in earlier releases
For new features included in the releases that shipped after the 1912 Long Term Service Releases (LTSR) through the 2407 Current Releases (CR), see What’s new history.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.