Remote Desktop Services 2019 · licensing decision diagram, not a product screenshot
RDS User or Device CALs are additional to the underlying Windows Server access rights. Match the CAL version to the session host: an older RDS CAL cannot license access to a newer host. Check licensing-server compatibility and the deployment mode separately.
Record the exact edition, version, quantity, agreement and support date. Obtain written confirmation of delivery, refund and support terms; a perpetual licence is not a lifetime support guarantee.
On this page
Editions covered
3
Edition matrix with feature differences and the right audience.
In-depth sections
5
Channels, activation, audit, modern management & more.
FAQs answered
6
Common questions buyers and IT admins ask before purchase.
Words of reference
0.7k
Edition and deployment guidance; verify current rights against official sources.
Edition matrix
Pick the right edition
Each edition targets a specific scale and feature set. Match the workload, not the price tag.
Edition 1
RDS User CAL 2019
Per-named-user in AD. User can connect from any device. Best when users are mobile.
Edition 2
RDS Device CAL 2019
Per-device. Best for shared workstations like training rooms and kiosks.
Edition 3
Base Windows Server 2019 CAL
Separate and additional to RDS CAL. Required for every user or device touching the server.
Side-by-side
Edition comparison
Compare the stated edition details. An omitted capability is not evidence that a feature is unavailable; verify the exact release in Microsoft's documentation.
Capability
RDS User CAL 2019
RDS Device CAL 2019
Base Windows Server 2019 CAL
Edition and licensing notes
Per-named-user in AD. User can connect from any device. Best when users are mobile.
Per-device. Best for shared workstations like training rooms and kiosks.
Separate and additional to RDS CAL. Required for every user or device touching the server.
Deep dive
Remote Desktop Services 2019 — what to actually know
Remote Desktop Services on Windows Server 2019 is the long-running RDS release that preceded RDS 2025. It ships as a set of roles (Session Host, Connection Broker, Web Access, Gateway, Licensing) and is licensed via per-user or per-device RDS Client Access Licences layered on top of the base Windows Server 2019 CAL. Mainstream support on Windows Server 2019 ended in January 2024; extended support runs through 9 January 2029 with security-only updates. Many organisations still run RDS 2019 in production today; the migration question is RDS 2025 (on-prem continuation), Azure Virtual Desktop (cloud-hosted session host), Windows 365 (per-user cloud PC), or a third-party VDI broker on top of Server 2025.
01
The five RDS roles
A production RDS deployment is built from five roles. Session Host runs the user sessions and the published apps. Connection Broker load-balances incoming sessions across multiple Session Hosts and handles session reconnection when a user returns to an existing disconnected session. Web Access publishes the RemoteApp and Desktop Connection portal. Gateway provides the SSL-tunnelled entry point from the public internet so that the RDP protocol does not need to be exposed directly. Licensing tracks CAL allocation and issues per-user or per-device CALs to clients. The Connection Broker and Licensing roles can be highly available; Session Host scales horizontally by adding hosts.
02
Per-user vs per-device RDS CALs
RDS CALs come in two flavours. Per-user CALs are assigned to named users in Active Directory and follow the user across any device they use to connect — the right choice when users connect from multiple devices (laptop, phone, home PC). Per-device CALs are issued to the specific device that connects — the right choice for shared workstations like training rooms, kiosks, or shop-floor terminals where many users sit at the same device through the day. Mixing both modes is allowed; the Licensing service hands out the right CAL type based on the connection. Per-user CALs are technically a 'temporary issued' licence that should reconcile against Active Directory, but in practice many estates do not perform that reconciliation and so over-deploy per-user CALs — a common audit finding.
03
Base Windows Server CAL on top of RDS CAL
Critically, every RDS user or device also needs a base Windows Server 2019 CAL. The RDS CAL grants access to the RDS-specific session-hosting feature; the base CAL grants access to Windows Server itself. Missing base CALs underneath valid RDS CALs is the second most common RDS audit finding, after under-licensed per-device deployments. For Microsoft 365 estates, the base Server CAL needs to be procured separately from the M365 user subscription — M365 does not include Windows Server CALs.
04
Support timeline and the migration question
Windows Server 2019 (and therefore RDS 2019) is in extended support through 9 January 2029. Security-only updates continue, but no new features and no protocol enhancements ship. RDS on Windows Server 2025 is the supported on-prem continuation; in-place upgrade from 2019 to 2025 is supported, and existing RDS CALs hold downgrade rights covering older session hosts but cannot be used against newer session hosts without an upgrade. For estates that want to leave on-prem RDS entirely, Azure Virtual Desktop (multi-session Windows 11 Enterprise hosted in Azure) is the cloud destination, with per-user licensing bundled into Microsoft 365 E3/E5 and pay-as-you-go compute. Windows 365 (per-user Cloud PCs) is the simpler alternative for shops that want a one-Cloud-PC-per-user model without managing session hosts at all.
05
Architecture pitfalls and audit findings
The most common architectural mistake is running Session Host on the same Windows Server instance as the domain controller or the SQL database — Microsoft has been explicit for years that Session Host must run on a dedicated VM. The most common licensing mistake is operating in the 120-day grace period that the RDS Licensing service grants before requiring an installed CAL pack; once that window closes, sessions stop connecting and the licensing team has a fire to fight. Audit findings cluster around missing base Server CALs, under-counted per-device CALs (shared workstations counted as one device when several physical devices share the same hostname through KMS reissue), and per-user CALs deployed against more named users than purchased.
By channel
Where to buy this product
Confirm that the exact SKU is available in the proposed channel and region. A channel name does not establish entitlement or guarantee a lower price.
Evidence to request
Exact product, edition, version and licence quantity.
Order, invoice and applicable agreement or subscription record.
Ownership in your organisation's account, where applicable.
Written reassignment, renewal and support conditions.
OEM is supplied only pre-installed by hardware manufacturers, never sold as a standalone licence.
Retail / FPPIndividuals & small teams
Boxed or ESD keys, transferable, registered to a Microsoft account.
Monthly / annual seats, managed through partner or admin center.
OEM is not a buying channel for end users. OEM keys are supplied pre-installed by hardware manufacturers and are not sold standalone — choose Retail, Volume or CSP instead.
Support timeline
Lifecycle phases to plan against
Server licensing is per-core with strict minimums, and almost every workload also needs Client Access Licences. Get the core math wrong and you either fail an audit or buy twice the licences you actually need.
Phase 1
Exact product
Identify
Record the release, edition and servicing channel of Remote Desktop Services 2019; family names alone do not establish support dates.
Phase 2
Official lifecycle
Verify
Look up the exact product in Microsoft's lifecycle directory. Fixed and Modern Lifecycle policies differ; not every release has extended support.
Phase 3
Deployment
Plan
Confirm supported operating systems, application dependencies and upgrade rights before deployment.
Phase 4
End of support
Migrate
A perpetual licence can remain valid after support ends, but it does not guarantee security updates. Check any ESU programme separately.
Purchase preparation
What to include in a Remote Desktop Services 2019 quote request
CAL mode
User or Device CAL and all users or devices needing access.
Versions
Session Host version, existing RDS CAL version and licensing server.
Underlying rights
Existing Windows Server access rights; RDS CALs are additional.
Deployment
Session hosts, licensing mode and planned upgrades.
These are planning inputs, not a licence calculation. Confirm the final quantity and use rights against the exact version and agreement.
Compare like-for-like quotations
Match product, edition, version, quantity and perpetual or subscription terms.
Confirm total cost, renewal conditions and the evidence of ownership supplied.
Obtain written delivery, refund and support conditions before payment.
The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.
DO
Count every physical core on every populated socket, apply the 8-per-processor / 16-per-server minimum, and round up to the nearest 2-pack.
DON'T
Assume hyperthreaded logical cores reduce the licence count — they never do.
DO
Buy User CALs when users access from multiple devices, Device CALs when shared devices have many users (call centres, shop floors).
DON'T
Mix CAL types within the same agreement without a clear split — auditors will pick the worst case for you.
DO
Compare Datacenter with stacking fully licensed Standard coverage using the actual core count, peak VM placement and written prices; there is no universal VM break-even.
DON'T
License only the active node of a failover cluster — every node that could host the VM needs cores licensed unless SA mobility applies.
DO
Activate Azure Hybrid Benefit on SA-covered cores to halve Azure VM cost or stack with reservations.
DON'T
Forget that AHB requires Software Assurance or a subscription — perpetual-only licences without SA are not eligible.
Typical deployments
How buyers actually use Remote Desktop Services 2019
Illustrative planning scenarios, not customer case studies. Check the exact product rights and deployment requirements.
Scenario 1
Single-host file & print
One Standard server licensed for all physical cores, plus Device or User CALs for everyone who reads a share or prints a job. Essentials only if you genuinely stay under 25 users and never need a second box.
Scenario 2
Hyper-V cluster (3 nodes)
Datacenter on every node, sized to the largest host's core count. Cluster-aware updating, Storage Spaces Direct optional, and live migration without licence movement headaches.
Scenario 3
RDS farm
Per-user or per-device RDS CALs in addition to the Windows Server CAL. License the broker and session hosts identically; do not forget the redundancy node.
Cost optimisation
Where the savings actually live
Compare entitlement, deployment and renewal costs; savings depend on your workload and written quotation.
💰
Datacenter for dense virtualisation
Compare full-host Standard licence stacking with Datacenter using the actual quotation and required edition features. Guest count alone cannot establish which option costs less.
📊
Azure Hybrid Benefit
Reuse on-prem core licences with active SA on Azure VMs for up to 180 days of dual-use during migration, then keep the discount on the Azure side indefinitely while SA is current.
🎯
Right-size CALs
Count users and devices with direct or indirect access, not only authenticated sessions. External Connector eligibility relates to qualifying external users, not automatically to service accounts or IoT devices.
Counterfeit & risk
Red flags when buying second-hand
These warning signs require further verification; activation alone cannot establish licence ownership.
⚠ 01
Standalone OEM key sold below market
OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is not an eligible standalone purchase; request documented rights through an appropriate channel.
⚠ 02
Lifetime key with no invoice or Microsoft 365 admin center volume licensing record
Request applicable order and agreement records, such as Microsoft Store purchases, CSP subscription records or volume licensing details in the Microsoft 365 admin center. Activation alone is not proof of entitlement.
⚠ 03
Key works once, then 'not genuine' after the next cumulative update
Activation failures can have several causes, including key eligibility, activation counts, connectivity and hardware changes. Check the error through official Microsoft guidance; it does not by itself prove counterfeiting.
⚠ 04
Seller refuses to put the entitlement in your tenant
For tenant-based subscriptions, confirm your organisation controls the tenant and can read its subscription records. Retail and on-premises entitlements use different records; not every licence is assigned through a tenant.
Acronyms
Licensing terms used on this page
Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.
CSP
Cloud Solution Provider — Microsoft's primary indirect channel for subscriptions and cloud services.
Microsoft 365 admin center volume licensing
Volume licensing administration — agreements, keys and downloads are now managed in the Microsoft 365 admin center.
MAK
Multiple Activation Key — a Volume Licensing key with a finite activation count, used for isolated machines.
KMS
Key Management Service — an on-premises activation host that activates clients on a 180-day re-check cycle.
EA
Enterprise Agreement — Microsoft's largest commitment-based volume contract, typically a 3-year term with annual true-ups.
SA
Software Assurance — the upgrade-and-benefits add-on to Volume Licensing; required for new version rights and several mobility scenarios.
Per-user for mobile staff. Per-device for shared workstations. Mixing both modes is allowed and licensing chooses the right CAL per connection.
Do we still need base Server CALs underneath RDS CALs?+
Yes. RDS CALs cover the session-hosting feature; base Server CALs cover Windows Server itself. Both are required and both are checked in audits.
Is RDS 2019 still supported?+
Through 9 January 2029 under extended support with security updates only.
Should we move to RDS 2025 or Azure Virtual Desktop?+
RDS 2025 for organisations committed to on-prem session hosting. AVD or Windows 365 for organisations comfortable with cloud-hosted session hosts and a per-user subscription model.
Where can I legitimately buy a license?+
Through Microsoft's Retail channel, an authorised Cloud Solution Provider (CSP), or a Volume Licensing partner (MPSA, Enterprise Agreement, Open Value, Server & Cloud Enrollment). OEM keys are distributed only pre-installed by hardware manufacturers and stay bound to that device for life — they are not sold to end users as standalone products. Anyone offering a 'cheap OEM key' as a standalone download is, by definition, operating outside Microsoft's distribution terms.
What gets checked in a Microsoft licensing audit?+
Auditors map every installed copy to a proof of purchase (VLSC record, CSP invoice, sealed Retail FPP), verify edition alignment (features used must match the licensed edition), and confirm CAL counts cover the maximum number of authenticated users or devices during the audit window. Small variances usually resolve with a true-up; large gaps escalate to Software Asset Management engagements and back-billing at list price.