What RDSH does

Install the Remote Desktop Session Host role on Windows Server and the machine becomes a multi-user application server: each connecting user gets an isolated session with their own desktop, profile, and running programs, all sharing the server's OS kernel, CPU, and RAM. To users it feels like their own Windows machine; to you it's one server to patch, back up, and monitor instead of twenty.

RDSH is one piece of the broader Remote Desktop Services (RDS) family — alongside the RD Connection Broker (routes users to the right host), RD Web Access (a browser portal), RD Gateway (secure external access), and RD Licensing (tracks CALs). A single server can host several of these roles for small deployments; larger ones split them across machines.

Session-based vs VDI

RDSH provides session-based desktops: everyone shares one Windows Server OS. The alternative, VDI (Virtual Desktop Infrastructure), gives each user a full virtual machine with their own OS instance. Session-based wins on density and cost — far more users per host, one OS to maintain, simpler licensing. VDI wins on isolation and customization — users needing admin rights, unusual drivers, or conflicting app versions get their own VM.

Rule of thumb: if users run a standard set of business apps, RDSH is the efficient choice. If they need personal admin rights or kernel-level software, you're in VDI territory. Most small-to-mid remote-work deployments are session-based.

Session-based (RDSH) One shared Windows Server OS User Asession User Bsession User Csession VDI Full VMper user Full VMper user RDSH: many sessions, one OS. VDI: one VM per user, full isolation.
Fig. 1 — Session-based desktops share one OS across users; VDI gives each user a complete virtual machine.

When to use it

RDSH shines for task workers and office staff: call centers, data entry, accounting teams, and branch offices where everyone uses the same applications. It's also the engine behind many hosted "RDP server" products — when a provider sells multi-user RDP, there's usually an RDSH (or a set of them behind a broker) underneath. If instead you need one powerful desktop per person with full admin rights, a dedicated server or VPS per user is simpler; compare in our RDP plan tiers (Shared $6/mo, Virtual $28/mo, Dedicated $165/mo).

Setup essentials

  1. Install the role: Server Manager → Add Roles and Features → Remote Desktop Services → select RD Session Host (plus Connection Broker for multi-server farms).
  2. Create a session collection: in Server Manager → Remote Desktop Services → Collections, publish either full desktops or individual RemoteApp programs.
  3. Publish applications: add the .exe paths users need; they appear as seamless windows on the client, feeling like local apps.
  4. Configure user profiles: use UPD (User Profile Disks) or roaming profiles so settings follow users across hosts in a farm.
  5. Set session limits: idle timeouts, disconnected-session cleanup, and single-session-per-user — so abandoned sessions don't eat RAM all weekend.
  6. Open access: point users at the broker or use an RD Gateway for external access; distribute a preconfigured .rdp file.

Licensing

The licensing tripwire: Windows Server allows two concurrent administrative sessions without extra licensing, but the moment regular users connect for work, you need RDS CALs (Client Access Licenses) — per-user or per-device — plus an RD Licensing server to track them. There's a 120-day grace period from first RDSH use; after it expires, unlicensed servers refuse connections. Buy CALs through proper channels, install the RD Licensing role, and point your session hosts at it. Skipping this is the most common "it worked for months then broke" story in RDS.

ScenarioRDSH fitNotes
20 office staff, same appsExcellentOne image, high density, simple patching
Call center shiftsExcellentSession limits reclaim seats between shifts
Developers needing adminPoorUse VDI or individual VMs instead
Single power userOverkillA dedicated server is simpler
Seasonal burst workforceGoodScale hosts up/down; mind CAL counts
RemoteApp single programExcellentUsers get just the app, no full desktop

Sizing and performance

Density planning is workload-specific, but the discipline is universal: measure, don't guess. As a starting example only, light office workloads often run 15–25 sessions per host on healthy specs — but your apps, not a blog post, decide. Pilot with real users, watch CPU, RAM, and disk queue in Performance Monitor during peak hours, and scale out (add hosts behind the broker) before users feel it. The two silent killers: disk I/O (twenty profiles hitting one spindle) and one hungry app (a single user's runaway process starves nineteen others — use fair-share CPU policies).

Connection Broker Session Host 1 n sessions Session Host 2 n sessions Session Host 3 n sessions The broker spreads users across hosts; add hosts to scale, not bigger single servers.
Fig. 2 — Scaling RDSH: the Connection Broker distributes sessions across hosts — scale out with more hosts.

Managing sessions day to day

Daily RDSH life runs through Server Manager → Remote Desktop Services → Collections (or the classic qwinsta/rwinsta and Task Manager's Users tab): see who's connected, message users before maintenance, log off stuck sessions, and shadow a session for support (with user consent). Keep a maintenance window — patching a session host kicks everyone off, so schedule it, warn users, and drain the host via the broker first. Document the runbook; 2 a.m. you will thank daytime you.

Application quirks on shared session hosts

The server side of RDSH is straightforward; the applications are where shared session hosts get interesting. Common gotchas:

  • Install in install mode. Before installing software on a session host, run change user /install; when done, change user /execute. This tells Windows to store per-user settings correctly instead of baking the installing admin's settings in as everyone's defaults. Installing like it's a single-user PC is the classic RDSH rookie mistake.
  • Single-instance apps. Some programs assume one user per machine and misbehave — or refuse to launch — when twenty users run them at once. Check the vendor's documentation for multi-user or RDS support before promising users the app will work.
  • Hardcoded paths. Apps that write to fixed locations instead of the user profile cause cross-user interference: one user's temp files become another user's errors. User Profile Disks contain the damage but don't fix the app — test with two simultaneous users, not one.
  • Profile bloat. Every session writes to its profile, and without quotas or folder redirection, logons slow to a crawl over months. Monitor profile sizes; it's the quietest performance killer on session hosts.
  • Redirection surprises. Printer, drive, and time-zone redirection behave differently per client and per policy. Set expectations with Group Policy deliberately instead of discovering the defaults through support tickets.

The meta-rule: pilot with real concurrent users, never with one admin testing alone. Most session-host quirks only appear at user number two and beyond.

Ready for your own RDP server?

Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan.

Shared Servers$6/mo
Dedicated Server$165/mo
Get Started

3-day money-back guarantee · Full admin RDP · Dedicated IP · 24/7 support

remote desktop session host: FAQ

It's a Windows Server role (RDSH) that hosts multiple simultaneous user desktop sessions on one server. Each user gets an isolated session with their own desktop and apps, while everyone shares the server's OS, CPU, and RAM — one machine to manage instead of many.

RDSH is session-based: many users share one Windows Server OS, which is efficient and cheap per user. VDI gives each user a full virtual machine with its own OS, which offers more isolation and admin rights per user but costs more in resources and licensing.

Yes, for regular users. Windows Server includes two concurrent admin sessions, but user workloads require RDS CALs (per-user or per-device) and an RD Licensing server. There's a 120-day grace period, after which unlicensed hosts refuse connections.

It depends entirely on the workload and hardware — light office apps allow far more sessions than heavy applications. Pilot with real users, monitor CPU, RAM, and disk I/O at peak hours, and scale out with additional hosts behind a Connection Broker before performance degrades.

RemoteApp is an RDSH feature that publishes individual applications instead of full desktops. Users click an icon and the app opens in a seamless window that feels local, while it actually runs on the session host — ideal when people need one or two programs, not a whole desktop.

Yes — put an RD Gateway in front of it. External users connect over HTTPS (port 443) to the gateway, which authenticates them and proxies to the internal session hosts, so no RDP port is exposed directly to the internet.