What’s new in Kasm 1.14.0


  • Updated UI/UX throughout the application. Including launcher animation, launcher prompts and a redesign of the administrator user interface.

  • Webcam passthrough. User can control quality and frame rate.

  • Print to a local printer from within a session.

  • AWS S3-based user persistent profiles.

  • User mounting of cloud storage drives (Dropbox, Google Drive, NextCloud, OneDrive, and S3) into container-based sessions via Storage Mapping.

  • Language translations for 243 locales and timezone setting for all global timezones. Your language and timezone within your sessions will be based upon your local browser setting, but can also be overwritten at the user, group, and workspace levels.

  • Additionally the UI has been machine translated to over 90 languages.

  • Dynamic AutoScaling of Kasm agents and server VMs on VMWare vSphere.

  • Support for File Mapping on Windows systems.

  • Kasm managed Windows local accounts with SSO.

  • Admin definable PowerShell script hooks for Windows servers.

  • Sysbox Runtime support to all base images except for Fedora and Alpine.

  • Native IME for external server sessions with RDP, VNC and SSH connections.

  • High-DPI scaling option for users with high-resolution monitors.

  • Provision of compute resources fully on demand without the need to use standby compute or staged sessions. See Aggressive Scaling for more details.

  • AutoScaling configurations now support scheduling


  • Usability Enhancements

    • Added the ability to define which columns to show in a table, the default items to show is now 20 and search is more easily accessible. In addition, the total amount of rows is displayed, and pagination has been introduced. Multi-select has been introduced with the ability to delete multiple items at once.

    • Added ability to force delete Servers when there is a session running.

    • Added the ability to select the language used in the UI from the users profile.

  • Infrastructure Support Enhancements

    • Installer support for Debian 12.

    • Windows auto-logout on session termination.

    • Password resets support LDAP users that have not yet logged in.

    • Custom connection information on the request_kasm call of the developer API.

    • Support for longer container registry passwords to allow for using containers from Google Cloud Artifact Registry.

    • LDAP configurations can match usernames on multiple domain names or usernames without a domain in the username, such as user@domain.com.

    • AutoScaling pool option to recursively delete objects so Active Directory Computer objects with child objects can be deleted.

    • Allow templating of {image_id} (Workspace ID) variable in persistent profiles and Volume Mapping paths.

  • Kasm Image Enhancements


  • Web proxy not running in containers on RHEL 9 & Fedora 37 hosts.

  • Multi-server deployments were prevented from confirming database connectivity at install time on Oracle Linux 8 and similar distros.

  • Digital Ocean tags were handled by the UI which resulted in the tags being invalid.

  • Shared session termination. When a user stops sharing a session, all connected users will be forcefully removed and all future access will be blocked until sharing is enabled again.

  • Per-user license enforcement allowed the administrator to create one more user than licensed, which would then result in users not being able to create sessions.

  • Agents attempted to prune images twice when agent prune mode was set to Aggressive.

  • Installation logic for LibreOffice updated to allow it to be run in an Ubuntu based desktop environment.

  • Pasting of text containing non-Latin characters wwas prevented in Guac sessions.

  • Browser CORS issues on specific deployment architectures.

  • Force deleting servers that have existing kasm sessions.

  • Some installations would not complete due to netcat missing from the underlying host.

  • Admin_delete_pending kasms that are part of a server pool were not being cleaned up.

  • When the AutoScaling configuration contained an error it was possible to exhaust the database connection pool.

  • Azure network security groups were not being applied to virtual machines that are using local IP addresses during AutoScaling.

  • Azure network interfaces were not cleaned up when errors occurred in provisioning during AutoScaling.

  • Guac sessions incorrectly logging disconnection-related Websocket codes as errors.

  • AWS AutoScaling provider returning an incorrect count of the Kasm created VMs running in AWS.

  • MacOS modifier keys can sometimes get stuck in a down position.


Printing over RDP failing with Connection Proxy Role

The Connection Proxy Role configuration for the original Kasm workspace 1.14.0 release is missing a mount point.

If you are encountering issues with printing over RDP and installed a dedicated Connection Proxy role, run the following command on your Connection Proxy server to update the mounts:

/opt/kasm/current/bin/utils/yq_$(uname -m) \
  -e '.services.kasm_guac.volumes' \
export guac_container=$?
/opt/kasm/current/bin/utils/yq_$(uname -m) \
  -e '.services.kasm_guac.volumes[] | select(. == "/opt/kasm/1.14.0/tmp/guac:/tmp")' \
export has_volume=$?

if [ $guac_container -eq 0 ] && [ $has_volume -ne 0 ]
  sudo cp /opt/kasm/current/docker/docker-compose.yaml /opt/kasm/current/docker/docker-compose.yaml.bak$(date +%s)
  sudo /opt/kasm/current/bin/utils/yq_$(uname -m) \
    -i '.services.kasm_guac.volumes += "/opt/kasm/1.14.0/tmp/guac:/tmp"' \
  sudo /opt/kasm/current/bin/start
  echo "Applied Connection Proxy Hotfix"
  echo "Hotfix not needed"