workspaces-issues icon indicating copy to clipboard operation
workspaces-issues copied to clipboard
verified publisher icon kasmtech

[Bug] - No option to set RDP sessions to single monitor only when using Native Client

Open jtruland opened this issue 5 months ago • 0 comments

Existing Resources

  • [X ] Please search the existing issues for related problems
  • [X ] Consult the product documentation : Docs
  • [X ] Consult the FAQ : FAQ
  • [X ] Consult the Troubleshooting Guide : Guide
  • [X ] Reviewed existing training videos: Youtube

Describe the bug RDP Connections can support multiple monitor connections. There is an option within the native Windows RDP client to allow or disable multiple monitor support. Kasm doesn't seem to have a way to specify that the native client should restrict itself to a single client monitor.

To Reproduce Steps to reproduce the behavior:

  1. Create RDP server using Windows 11
  2. Allow for native client connection to remote desktop
  3. Launch the workspace using native client option
  4. Native windows RDP client launches in Full Screen mode using all available local monitors.

Expected behavior There should be a Kasm configuration option to allow setting multi-monitor support On or Off. Optionally, Windows RDP client also allows for specific control over how many/which local monitors to use.

Screenshots If applicable, add screenshots to help explain your problem.

Workspaces Version Version 1.17

Workspaces Installation Method Single Server

Client Browser (please complete the following information):

  • OS: Windows 11 23H2
  • Chrome browser 137.0.7151.104
  • Version

Workspace Server Information (please provide the output of the following commands):

  • uname -a Linux kasm 6.8.12-11-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-11 (2025-05-22T09:39Z) x86_64 GNU/Linux
  • cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
  • sudo docker info Client: Docker Engine - Community Version: 28.2.2 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.24.0 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.5.0 Path: /usr/local/lib/docker/cli-plugins/docker-compose

Server: Containers: 11 Running: 11 Paused: 0 Stopped: 0 Images: 25 Server Version: 28.2.2 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: true Logging Driver: json-file Cgroup Driver: systemd Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan kasmweb/sidecar:1.2 macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog CDI spec directories: /etc/cdi /var/run/cdi Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da runc version: v1.2.5-0-g59923ef init version: de40ad0 Security Options: seccomp Profile: builtin cgroupns Kernel Version: 6.8.12-11-pve Operating System: Debian GNU/Linux 12 (bookworm) OSType: linux Architecture: x86_64 CPUs: 6 Total Memory: 28.09GiB Name: kasm ID: ff314fe7-de43-42bd-bdf3-3d746bbde5c8 Docker Root Dir: /var/lib/docker Debug Mode: false Experimental: false Insecure Registries: ::1/128 127.0.0.0/8 Live Restore Enabled: false

  • sudo docker ps | grep kasm ed84e86f58f4 kasmweb/chrome:1.17.0-rolling-weekly "/dockerstartup/kasm…" 2 hours ago Up 2 hours 4901/tcp, 5901/tcp, 6901/tcp jonbitz.dev_37db9288 354696dd7676 kasmweb/proxy:1.17.0 "/docker-entrypoint.…" 14 hours ago Up 14 hours 80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp kasm_proxy 8dea0a9883e5 kasmweb/share:1.17.0 "python3 /src/api_se…" 14 hours ago Up 14 hours (healthy) 8182/tcp kasm_share 280751b8c989 kasmweb/agent:1.17.0 "python3 /src/Provis…" 14 hours ago Up 14 hours (healthy) 4444/tcp kasm_agent ae9eb8813ecb kasmweb/rdp-https-gateway:1.17.0 "/opt/rdpgw/rdpgw" 14 hours ago Up 14 hours (healthy) kasm_rdp_https_gateway b2394362ed63 redis:5-alpine "docker-entrypoint.s…" 14 hours ago Up 14 hours 6379/tcp kasm_redis dd460040b8fb kasmweb/manager:1.17.0 "python3 /src/api_se…" 14 hours ago Up 14 hours (healthy) 8181/tcp kasm_manager 7a3eb2cafb77 kasmweb/rdp-gateway:1.17.0 "/start.sh" 14 hours ago Up 14 hours (healthy) 0.0.0.0:3389->3389/tcp, [::]:3389->3389/tcp kasm_rdp_gateway f982ad496d13 kasmweb/kasm-guac:1.17.0 "/dockerentrypoint.sh" 14 hours ago Up 14 hours (healthy) kasm_guac eff5472a98e2 kasmweb/api:1.17.0 "/bin/sh -c /usr/bin…" 14 hours ago Up 14 hours (healthy) 8080/tcp kasm_api 7d0f16b4b5b6 kasmweb/postgres:1.17.0 "docker-entrypoint.s…" 15 hours ago Up 14 hours (healthy) 5432/tcp kasm_db

Additional context The protion of the rdp file output, below, successfully limits the client to a single monitor if the noted parameter is manually edited to have a 0 value.

connection type:i:6 networkautodetect:i:1 bandwidthautodetect:i:1 screen mode id:i:2 use multimon:i:1 ##THERE SHOULD BE A CONFIGURATION OPTION TO SET THIS PARAMETER## singlemoninwindowedmode:i:1 keyboardhook:i:2 disable full window drag:i:1 disable menu anims:i:1 bitmapcachepersistenable:i:1 session bpp:i:32 dynamic resolution:i:1 autoreconnection enabled:i:1 videoplaybackmode:i:1 allow desktop composition:i:1 disable themes:i:0 disable cursor setting:i:0 allow font smoothing:i:1

gatewaycredentialssource:i:5 gatewayusagemethod:i:1 gatewayprofileusagemethod:i:1 gatewaybrokeringtype:i:0

drivestoredirect:s:* redirectsmartcards:i:0 audiocapturemode:i:1 redirectclipboard:i:1 redirectprinters:i:1 redirectwebauthn:i:0

jtruland avatar Jun 20 '25 17:06 jtruland