{"id":11936,"date":"2026-07-31T11:38:51","date_gmt":"2026-07-31T16:08:51","guid":{"rendered":"https:\/\/www.apps4rent.com\/blog\/?p=11936"},"modified":"2026-07-31T11:38:57","modified_gmt":"2026-07-31T16:08:57","slug":"rds-cals-explained","status":"publish","type":"post","link":"https:\/\/www.apps4rent.com\/blog\/rds-cals-explained\/","title":{"rendered":"RDS CALs Explained: What They Cost and How Hosting Changes the Math"},"content":{"rendered":"

An RDS CAL, or Remote Desktop Services Client Access License, is a separate license required for every user or device that connects to a Windows Server Remote Desktop Session Host, in addition to the Windows Server CAL those same users already need.<\/strong> Most small businesses discover this the hard way, usually during a Microsoft licensing review, after assuming their Windows Server CALs already covered remote access. They do not. This guide explains what RDS CALs actually cost, how to choose between per-user and per-device licensing, where the audit risk actually comes from, and how hosted environments handle this cost differently than buying the licenses yourself.<\/p>\n

What Is an RDS CAL, Exactly?<\/h2>\n

A Windows Server CAL gives a user or device the right to connect to a Windows Server and use its basic services, file sharing, print services, and general network access. It does not include the right to run a full desktop session or remote application through Remote Desktop Services. That is a separate right, licensed separately, and it applies whether the connection happens through a standard RDP session, RemoteApp, or a virtual desktop infrastructure deployment built on Windows Server.<\/p>\n

This catches people off guard because the terminology sounds like it should overlap. It does not. If ten employees connect to a Windows Server machine to run a shared accounting application through Remote Desktop, that server needs ten Windows Server CALs and ten RDS CALs. Two separate license types, two separate costs, for the same ten people.<\/p>\n

The RDS CAL requirement applies to the Remote Desktop Session Host role specifically. A few related RDS roles do not add their own licensing cost on top: the Remote Desktop Connection Broker that routes users to the correct session host, the Remote Desktop Gateway that provides secure external access, and Remote Desktop Web Access, the browser-based portal for launching RemoteApp sessions. These all ride on the licensing already covering the session host itself. The cost concentrates specifically at the point where a user actually lands on a desktop or application session.<\/p>\n

One narrow exception is worth knowing. Windows Server Essentials edition, built for small businesses with basic computing needs, allows up to 25 users and 50 devices to access certain Windows services without CALs. It does not extend to full Remote Desktop Session Host deployments in the way most growing businesses eventually need, but it explains why some very small setups never hit this licensing requirement at all while others hit it on day one.<\/p>\n

Per User CAL vs. Per Device CAL: Which One Do You Actually Need?<\/h2>\n

Both CAL types cost the same per license. The decision is not about price, it is about which one requires fewer licenses for your actual usage pattern.<\/p>\n

A Per User CAL is assigned to a specific named person and allows that person to connect from any device, a work laptop, a home computer, a phone, without needing a separate license for each one. A Per Device CAL is assigned to a specific machine and allows any number of different users to connect from that machine, without each of them needing their own license.<\/p>\n\n\n\n\n\n\n\n\n\n
Deployment Pattern<\/strong><\/th>\nCheaper Model<\/strong><\/th>\nWhy<\/strong><\/th>\n<\/tr>\n<\/thead>\n
Office staff with a laptop, home PC, and phone<\/strong><\/td>\nPer User<\/td>\nOne license covers all their devices<\/td>\n<\/tr>\n
Call center running three shifts on the same workstations<\/strong><\/td>\nPer Device<\/td>\nOne license per workstation covers every shift worker<\/td>\n<\/tr>\n
Hospital nurse stations with rotating staff<\/strong><\/td>\nPer Device<\/td>\nFewer devices than staff means fewer licenses needed<\/td>\n<\/tr>\n
Remote or hybrid employees using multiple personal devices<\/strong><\/td>\nPer User<\/td>\nDevice count per person is unpredictable and often high<\/td>\n<\/tr>\n
Seasonal or contract staff with high turnover<\/strong><\/td>\nPer Device<\/td>\nLicenses stay with the machine, not the rotating person<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The simplest way to decide is to count both ways for your actual environment. If your device count is lower than your user count, Per Device wins. If your user count is lower than the number of devices those users collectively touch, Per User wins. Mixed environments are common, and Microsoft licensing allows a mix of both CAL types on the same server, so a business does not have to force every user or device into a single model.<\/p>\n

What RDS CALs Actually Cost in 2026<\/h2>\n

Pricing varies by Windows Server version, licensing program, and reseller, but a realistic range for a standalone RDS CAL purchased outright is roughly $150 to $220 per license, on top of the Windows Server CAL each of those same users or devices also needs. Volume packs bring the per-unit price down somewhat, a five-pack typically prices lower per CAL than five individual purchases, but the underlying per-seat cost still scales directly with headcount.<\/p>\n

This is where the total cost tends to surprise people who budgeted only for the Windows Server CAL. A 20-person deployment does not need 20 licenses, it needs 40: 20 Windows Server CALs and 20 RDS CALs, purchased separately, often from different line items in a quote that makes the doubling easy to miss.<\/p>\n

One detail worth checking before buying anything: Microsoft 365 E3 and E5 subscriptions already include the Windows Server, RDS, SharePoint, Exchange, and System Center CAL rights as part of the per-user subscription price. A business that has already moved its workforce to E3 or E5 licensing should not be purchasing standalone RDS CALs for those same users. This gets missed more often than it should, because the standalone CAL often sits on a completely separate line of an IT budget or vendor agreement from the Microsoft 365 subscription, and nobody reconciles the two against each other.<\/p>\n

The Audit Risk Nobody Talks About<\/h2>\n

RDS CAL non-compliance is one of the most common findings in Microsoft Software Asset Management audits, and the mechanics of why are not well understood outside of licensing specialists.<\/p>\n