Single Server Installation

The simplest way to deploy Kasm Workspaces is to install all application services on a single server. End-user sessions will also be provisioned on this server. All interior docker communication occurs within the single server and there are no special configurations required.

Please read through the entire process before getting started.

For help please see Help and Support.

../_images/single_install2.png

Single Server Architecture

Ports and Protocols

In the Single Server configurations all services communicate via internal docker networks. Only access to the Web Application and port 3389 for RDP gateway access (if desired) needs to be exposed.

Source

Destination

Port

Notes

End User

Kasm Workspaces

443

Web Application

End User

Kasm RDP gateway

3389

RDP Thick Client Access

Installation Guide

Please review the System Requirements before beginning.

Tip

Kasm provides a Sizing and Deployment Guide to aid in determining hardware specifications for large scale deployments.

  • Download the latest version of Kasm Workspaces to /tmp

  • Extract the package and run the installation script.

Install Files
Installer

Contents

URL

SHA256

Installer Bundle

https://kasm-static-content.s3.amazonaws.com/kasm_release_1.16.1.98d6fa.tar.gz

096b27e3219b98a8e5faef2b36ccb58a0944a8f0e9b27933ce475335f745433a

Offline AMD Images

Contents

URL

SHA256

Services

https://kasm-static-content.s3.amazonaws.com/kasm_release_service_images_amd64_1.16.1.98d6fa.tar.gz

e8d87b47ba74fa63efc2f417848ebeda2eda3d75b65914c2e9823d173b068b94

Workspaces

https://kasm-static-content.s3.amazonaws.com/kasm_release_workspace_images_amd64_1.16.1.98d6fa.tar.gz

1b8575df087cf2db87da5bb2d23de341b41887313cd90134f353304072975248

Plugin

https://kasm-static-content.s3.amazonaws.com/kasm_release_plugin_images_amd64_1.16.1.98d6fa.tar.gz

673f29b8fef433e2919fe87e42fc6ccf71e9d5b6a4832bf2b382d635a58be793

Offline ARM Images

Contents

URL

SHA256

Services

https://kasm-static-content.s3.amazonaws.com/kasm_release_service_images_arm64_1.16.1.98d6fa.tar.gz

0d00edd30607d5ba95e277dfb098cf26216a80b71ea3e586ecbed90118c01e51

Workspaces

https://kasm-static-content.s3.amazonaws.com/kasm_release_workspace_images_arm64_1.16.1.98d6fa.tar.gz

20d4483066075aebc918b7a9e20ba0d344db651e556c6e45a1d35cbabcbe322b

Plugin

https://kasm-static-content.s3.amazonaws.com/kasm_release_plugin_images_arm64_1.16.1.98d6fa.tar.gz

a7425211836f71f4ea26713ea8488266a75fcccd5e1f269f8948ece77125d62b

cd /tmp
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_1.16.1.98d6fa.tar.gz
tar -xf kasm_release_1.16.1.98d6fa.tar.gz
sudo bash kasm_release/install.sh
  • Log into the Web Application running on port 443 at https://<WEBAPP_SERVER>

  • The Default usernames are admin@kasm.local and user@kasm.local. The passwords will be randomly generated and presented at the end of the install unless the --admin-password or/and --user-password are specified.

../_images/login5.webp

Default Login Window

Licensing the server during install?

Note

If you have an Activation Key it can be passed to the installation script and activation will be completed on your behalf as part of the install. Create a file for the Activation Key e.g. activation_key.txt and paste in the Activation Key you received in you confirmation email. When running the install.sh use the parameter -a or --activation-key-file so your command might look something like this sudo bash kasm_release/install.sh -a activation_key.txt. This will not work with an offline air-gapped install, as Kasm Workspaces must contact an activation server to complete licensing your installation. In a multi server install this option only applies to the database role.

Need to install Kasm on a different port?

Note

If you would like to run the Web Application on a different port pass the -L flag when calling the installer. e.g sudo bash kasm_release/install.sh -L 8443

Install Video Tutorial

This video walks through installing Kasm Workspaces on a single system.

Install troubleshooting

The install.sh script creates a log file as it runs, this file is removed upon completion of a successful installation. However, if something does go wrong the logfile will be available from the directory the install.sh script was executed from in the format kasm_install_${TIMESTAMP}.log. This file will be important for diagnosing the error that caused the installation to fail and will be requested when submitting a support ticket with Kasm Technologies.