Fixed Servers

Kasm supports managing user session and user access to fixed Windows servers. These backend servers can be virtual machines running on-premise, the cloud, or physical servers. The above video walks through the process of adding fixed Windows servers to your Workspaces deployment.

Server Pools

Server pools is an optional concept for fixed servers. Administrators have the option to group fixed servers into a Server Pool. This allows you to then provide users access to a pool of servers, rather than individual servers. When you create a Workspace that targets a pool, users are automatically load balanced to the pool of servers. Kasm knows how many concurrent user sessions each server is configured to allow and tracks which users are using a session on each server. Kasm allows for users to have multiple sessions open to different servers, if your configuration allows for that. To create a Pool, go to Infrastructure, Pools, and click the Add button in the Pools list. Provide a name, select Server in the Type drop down, and click Save. From the edit pool page, you can add and remove servers from the pool.

Servers

A server in Kasm is an individual system that Kasm brokers a user connection to. A Workspace can point to an individual server or a pool of servers. To create a server, go to Infrastructure, Servers, and click Add in the Server list.

  1. Provide a name and IP address or hostname for the server.

  2. Select RDP from the connection type drop down.

  3. Configure the port to use for the RDP connection, the default RDP port is 3389.

  4. There are multiple options for authentication to Windows servers, the example screenshot below just uses a static username and password.

  5. Enter the maximum number of concurrent sessions the Windows server will handle. For static credentials, only a single concurrent session can be allowed. In order for more than 1 simultaneous sessions to be allowed, you need to configure SSO for authentication to Windows from Kasm and you need to use a Windows operating system that supports multiple concurrent RDP sessions.

  6. Select the deployment zone, by default there is only one zone called default.

  7. Click Save

../../_images/create_server.webp

Create Server

Workspace

A Workspace is how you provide end-users with access to resources, such as a server. In the Workspaces is where you define the user facing name, description, categories, and thumbnail image. To create a Workspace, go to Workspaces -> Workspaces in the Admin dashboard and click Add Workspace in the Workspaces list.

  1. Select Server from the Type drop down. Select Pool if configuring a pool of servers.

  2. Provide a short user friendly name for the Workspace.

  3. Provide a description of the Workspaces.

  4. Provide a thumbnail URL that will be displayed to the user.

  5. Check the Enabled checkbox.

  6. Select the target server/pool from the dropdown.

  7. In the RDP Client Options dropdown, select one of:

    • Web native client to access the Windows instance using Kasm’s in browser access method.

    • RDP local client to access the Windows instance using the client endpoint’s RDP think client software authenticated through the Kasm RDP gateway.

  8. Optionally provide a category(s), users will be able to search for the Workspaces using the categories.

  9. Click Save

../../_images/server_workspace.webp

Create Workspace for Server

Groups

By default, new Workspaces are added automatically to the All Users group. Therefore, all users will have access to any newly defined Workspace. This default behavior can be changed in the Server Settings under Images, Add Images to Default Group checkbox. In more secure environments you will want to uncheck that setting, remove all Workspaces from the All Users group, and then add Workspaces to individual groups as needed.