Install Session Recording servers from within the cloud

In addition to connecting existing Session Recording servers to the cloud, you can also install Session Recording servers directly from within the cloud.

This feature obliterates the need to download the Citrix Virtual Apps and Desktops installer or the SessionRecordingAdministrationx64.msi file. It also checks domain joining and certificate binding to prevent issues that might keep Session Recording servers from functioning after being connected.

This article walks you through the process of installing a Session Recording server from within the cloud and provides guidance for post-installation actions.

Installation steps

To install a Session Recording server from within the cloud, connect a machine to the Session Recording service and then install the Session Recording server on it from within the cloud. To do so:

  1. Prepare a machine.
  2. Allow outbound ports 443, 8088, and 9090–9094 on the machine.
  3. Download and install the Session Recording cloud client on the machine.

    1. Sign in to Citrix Cloud.
    2. In the upper left menu, select My Services > DaaS.
    3. From Manage, select Session Recording.
    4. Select Configuration > Server Management from the left navigation of the Session Recording service.
    5. Click Download on the Server connection guide page.

      The server connection guide page

      Tip:

      You can also access the Download and Generate command buttons by clicking Continue configuration on the Session Recording service welcome page:

      The service welcome page

    6. Install the cloud client on the machine. To do that, run a command as an administrator from the location of the cloud client .msi file that you downloaded earlier.

      You can enter a command manually or generate a command by clicking Generate command on the Server connection guide page.

      The Generate command button on the Server connection guide page

      Answer questions and provide information where necessary on the Generate command page. After that, click the Generate command button.

      The Generate command page

      Generated command

      If you modify the answers or provide different information after clicking the Generate command button, the generated command automatically updates accordingly. The Generate command button is available again after you sign out and sign back in to Citrix Cloud.

      To have a custom domain name work properly, use either of the following methods before installing the Session Recording cloud client:

      (Recommended) Method 1:

      1. On the machine, open Registry Editor.
      2. Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
      3. Right-click MSV1_0 and create a multi-string value.
      4. Set the value name to BackConnectionHostNames and the value data to include your custom domain name.

        Note:

        Type your custom domain name on a separate line. If the BackConnectionHostNames registry value exists as a REG_DWORD type, delete it and recreate a multi-string value.

      5. Exit Registry Editor.
      6. Restart the machine.

      Method 2:

      Note:

      This method lowers security thresholds because it disables the authentication loopback check.

      1. On the machine, open Registry Editor.
      2. Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
      3. Right-click Lsa and create a DWORD value.
      4. Set the value name to DisableLoopbackCheck and the value data to 1.
      5. Exit Registry Editor.
      6. Restart the machine.
  4. Verify that the status of the machine is Ready to install, and then click the installation icon.

    Ready to install

  5. Follow the wizard to install the Session Recording server component on the machine.

    Server installation wizard

    1. On the Overview page, complete the following steps:

      1. Run a check to verify the following prerequisites:
        • The machine is in a valid domain.
        • You have installed an SSL certificate and added a certificate binding on the machine.

        The prerequisite check is to prevent issues that might keep Session Recording servers from functioning after being connected.

      2. Create a site for the machine or add the machine to an existing non-empty site.

      3. Choose a server version to install.
      4. Specify an installation path and verify that the path is valid.
      5. Click Next to proceed to the Database and server page.
    2. On the Database and server page, specify the instance name and database name of the Session Recording database and the computer account of the machine. After filling the fields, click Test connection to test the connectivity to the Session Recording database.

      Tip:

      • If you allocated the machine to an existing non-empty site earlier, the Instance name and Database name fields are automatically filled.
      • You can also choose to use a cloud database. You can deploy the Session Recording database on Azure SQL Managed Instance, on SQL Server on Azure Virtual Machines (VMs), and on AWS RDS.

      Database and server configuration

      • Instance name: Type the name of your SQL Server in the Instance name text box. If you’re using a named instance, type computer-name\instance-name; otherwise, type computer-name only. If your SQL server listens on a custom port other than the default port 1433, set the custom listener port by appending a comma to the instance name. For example, type DXSBC-SRD-1,2433 in the Instance name text box, where 2433, following the comma, denotes the custom listener port.
      • Database name: Type a custom database name in the Database name text box or use the default database name sessionrecording that is preset in the text box. The machine must have the sysadmin role permission of the database. Otherwise, ask the database administrator to assign the permission.
      • Session Recording server computer account. Type the computer account of the machine.
    3. On the Administrator logging page, specify configurations for the administration logging feature and click Test connection to test the connectivity to the administrator logging database.

      Administrator logging configuration

      • Instance name: The SQL Server instance name of the administration logging database is automatically grabbed from the instance name that you typed on the Database and server page.
      • Database name: Type a custom database name for the administrator logging database or use the default database name sessionrecordinglogging that is preset in the text box. The administrator logging database name must be different from the Session Recording database name that is set in the Database name text box on the previous Database and server page.
      • Administrator logging: By default, the administration logging feature is enabled. You can disable it by clearing the check box.
      • Mandatory blocking: By default, mandatory blocking is enabled. The normal features might be blocked if logging fails. You can disable mandatory blocking by clearing the check box.
    4. On the Summary page, verify your settings and click Install.

      Server installation summary

    5. Check the installation progress by clicking the icon next to Installation in progress.

      Checking installation progress

      For example, the installation has progressed to the first step.

      Installation progressed to step 1

      After installation completes successfully, the machine becomes a Session Recording server that is connected to the Session Recording service. You can find the server under the site that you created or specified. Refresh the Server Management page to view all connected servers.

      Server installation succeeded

      If the installation fails, click the icon next to Installation failed and run diagnostics to identify possible issues. Fix the issues if any, restart the machine, and then restart the installation wizard.

      Server installation failed

Post-installation actions

After installing a Session Recording server from within the cloud, perform the following operations:

  • Connect the newly installed Session Recording server to the target Session Recording agent. Go to the target VDA or VDI machine and open Session Recording Agent Properties. Type the computer name of the machine where you installed the Session Recording server. Type the protocol and port information for the connection to the Session Recording server.
  • Configure server settings, policies, and playback permissions based on your needs.
  • Launch sessions to verify that sessions are recording.
  • View administrator logging data.
  • Go to the Session Recording management dashboard to gain insights into your deployment. For fresh installations, data is not immediately available on the dashboard.
Install Session Recording servers from within the cloud