Remote Desktop Session Host Licensing: RDS CALs, Per-User vs Per-Device, and 2026 Costs

Deploying RDS without a licensing plan is the single most common way small businesses end up non-compliant, and Microsoft’s own grace period is what hides the problem: a freshly installed Session Host accepts connections for 120 days before it starts refusing them. When the grace timer expires, users see a licensing error at logon and no amount of rebooting fixes it. Here is how the licensing model actually works and what it costs in 2026.

The Two Licence Layers You Actually Need

Nothing about RDS requires a Session Host licence by itself. Licensing applies to access, and it comes in two stacked layers.

• Windows Server CAL. Every user or device that authenticates to any Windows Server service needs one. This covers file shares, domain authentication, and printing, whether or not RDS is involved. Since Windows Server 2025, CALs are sold per user or per device and are version-tied but backward-compatible in practice.
• RDS CAL. Adds the right to open an interactive session on a Session Host. This is the licence people forget, and it is the one that produces the "licensing mode not configured" error at logon.

Only the Session Host role consumes RDS CALs. The Connection Broker, Gateway, and Web Access roles do not. If a server hosts only the Gateway, you need Server CALs, not RDS CALs, for the users passing through it.

Per-User vs Per-Device: The Decision That Sets Your Bill

Model	Licence attaches to	Best fit	Roaming behaviour
Per-User	The named user account	Shift workers sharing terminals, BYOD, remote staff	Follows the user to any device
Per-Device	The physical endpoint	Fixed desk fleets, kiosks, warehouse scanners	Any user on that device is covered

The rule of thumb: count users when people outnumber machines, count devices when machines outnumber people. A clinic with 60 staff sharing 15 workstations is far cheaper per-device. A call centre where every agent has a laptop is cheaper per-user. You cannot mix modes in one deployment without a legal exception, and switching later requires reissuing licences from the Microsoft Volume Licensing Service Center.

2026 Street Prices Per Seat

Licence	Typical list	Realistic reseller price	Term
RDS User CAL 2025	~$145	$110–130	Perpetual, one-time
RDS Device CAL 2025	~$145	$110–130	Perpetual, one-time
Windows Server Standard 2025 (16-core base)	~$1,180	$900–1,050	Perpetual
Additional core packs (2-core)	~$85	$65–75	Perpetual
RDS User CAL via CSP subscription	—	$5.50–7.00/user/month	Monthly, cancel anytime

The subscription route changes the math dramatically. Thirty users on perpetual licences is roughly $3,900 up front. The same headcount on CSP monthly runs about $200/month, which breaks even at around 20 months. If your headcount fluctuates seasonally, subscription wins outright; if you have stable staff and a five-year horizon, perpetual is cheaper.

Where Hosting Changes the Equation

Running RDS on a Windows VPS instance does not change the licensing requirements for the OS or the RDS CALs, but it changes the hardware economics completely. You are not buying the host, the redundant power, or the switches, and you are not paying for the idle capacity between shift changes. For deployments under roughly 25 concurrent sessions, the hosted model usually beats on-premise hardware plus licences on total cost within the first year.

A VPS also makes right-sizing easier, since you can move from 8 to 16 vCPU when session density grows instead of over-buying a physical server. Storage type matters more than raw CPU for interactive sessions: the Disk Cleanup and per-user profile overhead discussed in the Windows server optimisation guides applies directly to session hosts, where logon storms hit storage harder than any other workload.

Configuring the Licensing Role Without a Server

The Remote Desktop Licensing role can live on the Session Host itself for small deployments, though Microsoft recommends a separate server at scale. Point the Session Host at the licence server using Group Policy rather than local policy, so every host agrees on the setting:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core" /v LicensingMode /t REG_DWORD /d 4 /f

Value 4 means per-device, 2 means per-user. Then install the CALs from VLSC into the licence server console, and verify the count with Get-RDLicenseConfiguration in PowerShell. Track your 120-day grace timer explicitly: it starts at first session, and license issuance after that point is retroactive only within the grace window, not after it.

What Happens When Licences Run Out

Licensing enforcement is not graceful. When the licence server has no available CALs, the Session Host refuses new connections with a message that the remote session was disconnected because there were no Remote Desktop Licence Servers available. Existing sessions continue until users log off, which produces the confusing symptom of a server that works for everyone already inside and rejects everyone arriving. Check the licence console’s issued-versus-available count weekly and alert at 80% consumption rather than waiting for the refusal. Per-user licences are issued on first connect and remain tracked for 52 days before becoming reclaimable, so a churny user base can exhaust a pool far faster than headcount suggests.

Licensing Questions That Decide the Quote

• Do external contractors connect? Each external identity still consumes a licence, even for occasional access. Per-device is usually the cheaper pattern when contractors bring their own laptops but only a few machines exist in the office.
• Are sessions concurrent or staggered? CALs are users or devices, not concurrency, so three shifts of ten people need thirty licences, not ten.
• Will you grow past 25 sessions? Beyond that point a separate licence server and high-availability Session Hosts become worth their complexity, and pricing should include two hosts plus a broker.
• Is a Microsoft 365 subscription in play? It does not include RDS CALs. Bundled Windows E3 or E5 rights cover the Windows Server licence in Azure and some hosted scenarios, but RDS access remains separately licensable.
• Do you need User CALs for admin-only sessions? Administrators using remote desktop for management purposes on a server they administer are covered by the built-in administrative session allowance, which is two concurrent sessions, not a licence pool.

The Economics in One Line

Budget $115 per perpetual RDS CAL and $15–25 per user per month for the compute that hosts the session, then decide perpetual versus subscription based on how long your headcount stays stable. Do the licence inventory before you deploy, not after the grace period expires, because the remediation path involves a stalled helpdesk queue rather than a simple invoice.