How does Awingu’s session recording work, and can I auto-enable it?

Awingu provides the possibility to record streamed application sessions. This is applicable for all RDP sessions that run through the Awingu HTML5 gateway. This is not possible for applications that run through the Awingu reverse proxy or SaaS apps that are configured in SSO authentication.

Awingu admins can create a rule for auto-recording of sessions:

• • • either session based: a specific streamed application is auto-recorded
    • either user based: all sessions that are opened by the specific user are recorded

The recordings are stored on an external storage environment as configured by the Awingu admin. Recordings are are available in an .rdpv format (representative data). They can be played within the Awingu workspace via the “recorded session player”.

The file size of the file depends on a number of criteria:

• • • Screen resolution (e.g. full HD)
    • Screen refresh rate (i.e. is there a lot of changes going on in the application)
    • RemoteApp (typically smaller) vs. Remote Desktop (typically more)

To give some guidance in the required storage, our tests show an spread between of 0,5Mb/hour and 10Mb/hour. This assumes sessions longer than 5 minutes.

Sessions that get recorded will show a message before start. As such, the end-user is warned and aware of the recording. Users that don’t “accept” the recording are not able to start and enter the application.

If you’re in doubt about how to set up session recording within Awingu, allow our COO Steven Dewinter to explain it to you: