Kasm Workspaces provides container-based workspaces and access to remote systems, among other capabilities. This can simplify access, but it does not automatically make a Windows business application run in a container. Its runtime environment, licensing and operational ownership still need to be defined.
The workspace runs in a container.
The application runs on a Windows system, for example.
Distinguish access from application execution
A Linux desktop or browser application can be delivered in a container. When connecting to a Windows system, that system remains the execution environment. Kasm supports different connection types. Available features depend on the workspace and its configuration.
What remains when a session ends?
During the pilot, save a test file in its intended location. First disconnect and reconnect. Then end the session fully and start a new one. Check the file and profile in both cases: reconnecting and creating a new session are different tests.
- Test uploads, downloads and clipboard operations with both permitted and blocked actions.
- Test printing, scanning, audio and video using the chosen connection type and real endpoints.
- Define storage location, permissions and recovery for data that must persist.
Include ongoing operations in the assessment
Images, hosts and connected systems need updates, monitoring and clear ownership. Appropriate Kasm licences and, where required, Microsoft or application licences are also needed. The pilot should show how your team maintains images, investigates faults and supports users.
Questions to resolve
- Do you need an isolated workspace or access to existing systems?
- Which data must persist beyond a session?
- Can your team operate the environment with its existing tools?