Application Launcher and Session Recording Requirements

Application Launcher Platform Requirements

A Windows Server operating system is required for any installation of the application launcher. The solution is fully supported on a physical server or a virtual machine, regardless of the virtual host platform. All service pack levels and editions of the supported operating systems are supported, except where specifically noted. Bomgar recommends using the most current version of Windows Server.

Supported Windows versions:

  • Windows Server 2016
  • Windows Server 2012 R2

Application Launcher Hardware and Software Requirements

  • Web Service installed and configured with a valid and trusted SSL certificate
  • Microsoft .NET Framework 4.5.2+
  • Microsoft Remote Desktop Services (RDS) with proper licensing
  • RAM and CPU appropriate for the number of users and applications using application launcher

IMPORTANT!

High availability should be employed whenever possible. All components of Privileged Identity support a high availability configuration.

Session Recording Platform Requirements

A Windows Server operating system is required for any installation of the session recording component. The solution is fully supported on a physical server or a virtual machine, regardless of the virtual host platform. All service pack levels and editions are of supported operating systems are supported, except where specifically noted. Bomgar recommends using the most current version of Windows Server.

Supported Windows versions:

  • Windows Server 2016
  • Windows Server 2012 R2

Session Recording Hardware and Software Requirements

  • Microsoft .NET Framework 4.5.2+
  • Microsoft .NET Framework 3.5 SP1
  • Multi-core CPUs
  • 2 GB+ RAM

Minimum Requirements for Bastion Hosts

Application Launching Minimum

The following requirements are for launching applications on a bastion host.

Note: The bastion host can function as the video transcoder and media server; however, this will impact the performance of the host during video transcoding.

  • Bastion host: RDS host
    • 2 GB RAM
    • 2+ CPU cores;
    • .NET Framework 4.5.2+

For more information about RDS sizing, please see the Microsoft Help Center.

  • Session Recorder / Media Server
    • 2 GB RAM
    • 2+ CPU cores
    • NET Framework 4.5.2+
    • IIS
    • Microsoft Media Services (included in download)

Note: The amount of free disk space required depends on the number of recordings being stored.

Recommended Hardware for Deploying Application Launcher with Session Recording

If you wish to deploy application launcher with session recording, Bomgar recommends the following hardware:

  • Bastion host: RDS host
    • 6 GB+ RAM
    • 4+ CPU cores (not including hyper-threading)
    • .NET Framework 4.5.2+ 
    • Multiple RDS hosts configured as an RDS farm
  • Session Recorder / Media Server
    • 4 GB+ RAM
    • 4+ CPU cores (not including hyper-threading)
    • .NET Framework 4.5.2+
    • Microsoft Media Services (included in download)
    • Storage for recorded videos (can be on a distributed file system (DFS) share)

Example

Application Launching Recommended

In the diagram shown, an Active Directory-based Distributed File System (DFS) is depicted as the storage for raw and converted session recording files. DFS is not a requirement, but it is recommended in order to add online redundancy for the storage of the recorded sessions.

In this scenario, the bastion host records raw sessions and copies them to the DFS share. The media server transcodes the files from the DFS share, writes the converted files back to the DFS share, and deletes the original raw files.

If a DFS share is not used, the bastion host moves the raw files to the media server, performs video transcoding services, and stores the files locally.

In either case, the media server provides access to the recorded sessions via IIS and Microsoft Media Services.