Product documentation
Session Recording
Current Release 2407 2402 LTSR 2311 2308 2305 2303 2212 2210 2209 2207 2206 2204 2203 LTSR 2201 2112 2110 2109 2107 2106 2104 2103 1912 LTSR 7.15 Service
View PDF

Get started

March 1, 2022
Contributed by: 
L

Session Recording consists of five components:

  • Session Recording agent. A component installed on each VDA for multi-session OS or single-session OS to enable recording. It is responsible for recording session data.
  • Session Recording server. A server that hosts:
    • The Broker. An IIS 6.0+ hosted Web application that serves the following purposes:
      • Handling search queries and file download requests from the Session Recording player and web player.
      • Handling policy administration requests from the Session Recording policy console.
      • Evaluating recording policies for each Citrix Virtual Apps and Desktops session.
    • The Storage Manager. A Windows service that manages the recorded session files received from each Session Recording-enabled computer running Citrix Virtual Apps and Desktops.
    • Administrator Logging. An optional subcomponent installed with the Session Recording server to log the administration activities. All the logging data is stored in a separate SQL Server database named CitrixSessionRecordingLogging by default. You can customize the database name.
  • Session Recording player. A user interface that users access from a workstation to play recorded session files.
  • Session Recording database. A component that manages the SQL Server database for storing recorded session data. When this component is installed, it creates a database named CitrixSessionRecording by default. You can customize the database name.
  • Session Recording policy console. A console used to create policies to specify which sessions are recorded.

In the deployment example illustrated here, all the Session Recording components reside behind a security firewall. The Session Recording agent is installed on a VDA for multi-session OS or single-session OS. A second server hosts the Session Recording policy console, a third server acts as the Session Recording server, and a fourth server hosts the Session Recording database. The Session Recording player is installed on a workstation. A client device outside the firewall communicates with the VDA where the Session Recording agent is installed. Inside the firewall, the Session Recording agent, policy console, player, and database all communicate with the Session Recording server.

Session Recording components

Get started
March 1, 2022
Contributed by: 
L
March 1, 2022
Contributed by: 
L

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.