SOSI 2.1.1: You Decide Whether Recordings Take Up Space

September 11, 2026
SOSI 2.1.1: You Decide Whether Recordings Take Up Space

SOSI 2.1.1 is primarily a maintenance release, but two of its changes affect day-to-day use directly: how recordings consume storage, and a gap in a security setting.

MP4 conversion is no longer automatic

Until now, SOSI converted every session recording to MP4 as soon as the session ended. The upside was that any recording could be downloaded at once; the cost was a second copy of every session — and in practice, the vast majority of recordings are never downloaded at all.

2.1.1 adds a site-wide switch, on by default. Turn it off and MP4 files are no longer generated automatically, slowing the growth of your recording storage considerably.

The MP4 automatic conversion card in system settings
A new card in system settings: one switch decides whether an MP4 is produced for every session.

Playback is entirely unaffected. In-browser playback has always read the original recording, so every session can still be opened, scrubbed through, and reviewed alongside its keystroke log.

When a particular recording does need to leave the system, an administrator clicks "Convert to MP4" in the connection list and is notified once it is ready. In other words, MP4 moves from "always prepared in advance" to "produced on demand".

The connection info bar can be moved

The floating bar at the top of the remote desktop screen — device name, connection time, username — used to be fixed in place. On target systems that have their own toolbar along the top edge, the two got in each other's way.

It can now be set to the top, bottom, left or right in system settings.

The connection info bar position card in system settings
The info bar position can be adjusted to suit the target system's own layout.

Please review: new accounts were not covered by mandatory 2FA

This is the fix that most deserves your attention.

When site-wide mandatory two-factor authentication is enabled, SOSI brings every account that exists at that moment into scope. But accounts created afterwards were never asked to set up 2FA — they effectively bypassed the requirement, while the administration screens gave no indication that anything was wrong.

2.1.1 fixes this: new accounts now inherit the current site-wide setting.

If mandatory 2FA is enabled in your environment, we recommend reviewing the accounts created after you switched it on to confirm they are all covered.

Other fixes

  • BrowserApp credential auto-fill did not work: BrowserApp devices failed to fill in the username and password on the target site, forcing users to type them manually. Fixed.
  • Administrators were signed in automatically to devices that disallow it: with "LDAP automatic sign-in" turned off on a device, administrators were still signed in automatically. The device setting is now respected.
  • BrowserApp can open new tabs and windows: the session was previously locked to a single window, blocking "open in new tab" links. URL restrictions are unchanged — addresses outside the allowlist are still blocked.
  • Device permissions must be cleared before promoting to administrator: this prevents a stale, unmaintained permission set from being reused if the account is later demoted.
  • Reloading after changing pages returned to page one: list pagination now updates the address bar.
  • Recording playback page was broken on mobile widths: the layout now stacks vertically and fills the width on phones.
  • Up to five minutes without connectivity after a restart: recovery now takes about ten seconds.

For the full list of changes, see the SOSI 2.1.1 release notes. If you have any questions, please get in touch.

Ready to Upgrade Your Remote Access Management?

Book a free Demo and let our consultants show you how SOSI solves your management challenges