Out of the box, Windows Server allows two simultaneous Remote Desktop sessions for administration. That’s often enough for one admin plus a colleague, but not for a team working on the server at the same time. Here’s how the limits work, how to manage sessions, and what’s needed for more users.

The default: two administrative sessions

Without the Remote Desktop Services (RDS) role, Windows Server provides “Remote Desktop for Administration”:

  • up to 2 concurrent active sessions (plus a console session);
  • intended for administration, not for users working in desktop apps;
  • no extra licences needed.

A third person trying to connect is asked to disconnect one of the existing users.

One session per user (or not)

By default, each user is limited to a single session: reconnecting puts you back into your existing desktop. Change it in Group Policy (gpedit.msc):

Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections → Restrict Remote Desktop Services users to a single Remote Desktop Services session

  • Enabled (default behaviour): reconnect to the same session. Recommended.
  • Disabled: the same user can open multiple sessions (still within the overall limit).

Session timeouts (free up slots)

Disconnected sessions keep using a slot and memory. Set limits in the same Group Policy area (Session Time Limits):

  • Set time limit for disconnected sessions: for example 1 hour. The session is logged off afterwards.
  • Set time limit for active but idle sessions: for example 2 hours.

Be careful on trading servers: a timeout logs the user off and closes their applications (including trading terminals). Use timeouts only where that’s acceptable, or run important apps as services.

See and manage sessions

quser                       # list sessions (or "query user")
logoff 3                    # log off session ID 3
qwinsta                     # sessions with states

Task Manager → Users tab shows the same, and lets you disconnect or sign out users.

More than two users: Remote Desktop Services

To let more people use the server at once (or to use it as a shared desktop for non-administrators), install the Remote Desktop Session Host role, and license it:

  1. Install the RDS roles (Session Host + Licensing) via Server Manager → “Remote Desktop Services installation” (Quick Start works for a single server).
  2. Configure the RD Licensing server, and install RDS CALs (per user or per device).
  3. Point the Session Host to the licensing server.

Without CALs, RDS works for a grace period (typically 120 days), then refuses connections. See RDS CAL licensing.

Sizing: each desktop user needs RAM and CPU (roughly 1–2 GB RAM per active user running office apps or a browser, more for heavier apps). See Windows Server performance tuning.

Alternatives to many simultaneous sessions

  • Separate Windows VPS per user, for example one trading VPS per trader. That gives better isolation and avoids CALs for shared desktops. See Windows VPS and forex VPS.
  • Run apps as services or scheduled tasks, so they don’t need someone logged in.
  • Web-based admin (Windows Admin Center) and PowerShell Remoting for admins, instead of full desktops. See PowerShell remoting.
  • RD Gateway for secure access through HTTPS, without exposing RDP directly. See Windows Server RD Gateway.

Avoid unlicensed “RDP wrapper” hacks

Tools that patch Windows to remove session limits violate Microsoft’s licence terms, can break with updates, and are a security risk. Use RDS with CALs, or separate servers.

Security for multi-user servers

Quick reference

Item Default / option
Concurrent admin sessions 2 (no CALs needed)
More users RD Session Host + RDS CALs
List sessions quser
Log off a session logoff <ID>
Free slots Disconnected/idle session time limits

Related: change the RDP port and RDP black screen fix.

  • RDP
  • Windows Server
  • Remote Desktop