What’s new in 2308
You can now enable audio recording for non-optimized HDX audio when configuring session recording policies. The audio that is handled on the VDA and delivered to/from the client where the Citrix Workspace app is installed is referred to as non-optimized HDX audio. Unlike non-optimized HDX audio, optimized HDX audio has its processing offloaded to the client, as seen in the Browser Content Redirection (BCR) and Optimization for Microsoft Teams scenarios.
For information about enabling audio recording, see Configure session recording policies.
You can now enable fast seeking through ICA screen recording by configuring how often an I-Frame is generated. This feature significantly improves the playback seeking experience. For more information, see Enable fast seeking.
The lossy video codec feature has been renamed lossy screen recording, and its toggle switch is moved from the Session Recording Agent Properties to the Session Recording policy console.
You can now enable lossy screen recording in any of the following ways:
- Activate a system-defined session recording policy that has lossy screen recording enabled.
- Create and activate a custom session recording policy, and make sure to select Enable lossy screen recording when creating the custom policy.
- Select Enable lossy screen recording when configuring an event response policy. When a monitored event is detected later, lossy screen recording is triggered.
After you enable lossy screen recording, you can adjust compression options through the Lossy Screen tab of Session Recording Agent Properties.
For more information, see the following articles:
- Configure session recording policies
- Configure event response policies
- Enable or disable lossy screen recording
You can now install the Session Recording database on Google Cloud SQL Server, either by running a command or by running the SessionRecordingAdministrationx64.msi package. You can find the SessionRecordingAdministrationx64.msi package on the Citrix Virtual Apps and Desktops ISO under \x64\Session Recording. For more information, see Install the Session Recording Database on cloud SQL database services.
Previously, a live recording was considered unresponsive or dormant if no new data was written to the recording file for 48 hours. Unresponsive live recordings could not be closed. Starting with this release, you can configure this time threshold on the Storage tab of Session Recording Server Properties to close unresponsive or dormant live recordings automatically when the threshold is exceeded. You can also manually close unresponsive or dormant live recordings by using the ICLDB DORMANT command. For more information, see Manage recordings.
You can now append the FILEID parameter when using the ICLDB ARCHIVE, ICLDB REMOVE, and ICLDB DORMANT commands to manipulate a specific session recording file. You can also append the CLOSEFILES parameter when using the ICLDB DORMANT command to manually close unresponsive or dormant live recordings. For more information, see Manage recordings.
What’s new in earlier releases
For new features included in the releases that shipped after the 1912 LTSR through the 2305 CR, see What’s new history.