What Is a Terminal Server? (And How to Set One Up in 2026)

"Terminal server" is the name that refuses to die: Microsoft renamed the technology Remote Desktop Services (RDS) back in 2009, but admins, vendors and job tickets still call it a terminal server — and the concept is more relevant than ever. Here's what it is, when it's the right architecture, and how to stand one up on a current Windows Server.

What a terminal server actually does

A terminal server is a Windows Server that hosts sessions: many users log in simultaneously, each getting their own desktop and applications, all executing on the server's hardware. The user's device — an old laptop, a thin client, a tablet — just sends keystrokes and receives screen updates. One well-specced server can comfortably carry dozens of knowledge workers.

Why businesses still build them

  • Centralisation: apps and data live in one place — one server to patch, back up and secure, instead of fifty PCs.
  • Legacy line-of-business apps: that Access database or industry app that must run "in the office" becomes available from anywhere.
  • Cheap endpoints: aging hardware stays useful for years as terminals.
  • Remote work without data sprawl: data never leaves the server; the session is just a window into it.

Terminal server vs VDI

VDI gives each user a whole personal virtual machine; a terminal server shares one Windows instance between users. VDI wins on isolation and app compatibility for demanding users; the terminal server wins — usually decisively for SMBs — on hardware density, licensing simplicity and cost per user.

Building one: the short version

  1. Install Windows Server (2022 or 2025) — see our ISO download & licensing guide.
  2. Add the Remote Desktop Services roles via Server Manager's RDS deployment wizard: Session Host (where sessions run), Connection Broker, and RD Licensing.
  3. Install your RDS CALs — one per user or device beyond the two admin sessions. This is the step that catches people out 120 days later when the grace period lapses; our RDS CAL guide covers User vs Device CALs and installation.
  4. Install applications in install mode (change user /install) so they register correctly for multi-user use.
  5. Publish full desktops or individual RemoteApps, and secure the deployment (an RD Gateway rather than raw port 3389 to the internet).

Sizing rule of thumb

Plan roughly 2–4 GB RAM and a fraction of a modern core per office-productivity user, more for heavier apps — a single 16-core, 64 GB server handles a 20–30 user office with headroom.

What it costs to license

Three parts: a Windows Server Standard license, Windows Server CALs, and RDS CALs for each user or device. At Nerdused all three are lifetime licenses delivered by email within minutes — a complete Server + 50 CAL bundle covers a typical deployment in one purchase, with a 30-day guarantee.

Zurück zum Blog