-
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 2308
This release includes the following new features and addresses several issues that help improve overall performance and stability.
Audio recording for non-optimized HDX audio (preview)
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.
Fast seeking through ICA screen recording
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.
Lossy video codec renamed to lossy screen recording
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 for dynamic screen recording when configuring an event response policy. When certain events during an event-only recording trigger dynamic screen recording, lossy screen recording works.
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
Support for installing the Session Recording database on Google Cloud SQL Server
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.
Ability to close unresponsive or dormant live recordings
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.
More parameters are available for ICLDB ARCHIVE, ICLDB REMOVE, and ICLDB DORMANT commands
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.
Share
Share
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.