Need a specific scenario covered (RDS on Domain Controller, licensing for RemoteApp, or Azure hybrid)? Let me know.
If you are using RDS, you generally need both . You need a Windows Server CAL to legally access the server OS, and an RDS CAL to legally use the graphical interface features.
Many companies forget this honeymoon ends. Once those 120 days are up, the doors lock instantly. Users will suddenly see an error saying no license server is available, and productivity stops. Real-World "Moral of the Story" remote desktop services licensing
You cannot mix Per User and Per Device in the same environment for the same user.
| Scenario | Required Licenses | | :--- | :--- | | | None (Included in Server OS) | | 5 users sharing 1 PC (Shift work) | 1 Windows Server CAL + 1 RDS Per Device CAL | | 1 user with laptop, iPad, and Phone | 1 Windows Server CAL + 1 RDS Per User CAL | | 50 users accessing an RDS Farm | 50 Windows Server CALs + 50 RDS CALs (User or Device) | Need a specific scenario covered (RDS on Domain
Think of like managing access to a high-security office building. You can't just let everyone in; you need a system to track who—or what—is allowed through the door. The "Office Building" Analogy
RDS Licensing is a mandatory compliance step. While the 120-day grace period allows you to set up your infrastructure, failing to configure the RD Licensing Server and install the correct number of CALs will result in downtime. Remember the mantra: You need a Windows Server CAL to legally
If your RD Licensing Server goes down, your RDS Hosts will usually continue to function for a short time, but eventually, they cannot validate connections.
For small deployments (<10 users), consider Windows 365 or Azure Virtual Desktop —they include licensing.
Here is how the process actually functions in practice:
A Windows Server role that stores and issues CALs (Client Access Licenses). You can run it on a domain controller, a member server, or even the same server as your RDS host.