
”How much does it cost?” is one that we hear often, and that is… pretty complex matter, to say the least. When we talk with partners and customers, we are frequently confronted with questions about Microsoft RDS & VDI licensing. Yes, even in this 2000+ words post, we will (need to) cut some corners. Just to be sure: by no means will this be a complete reference. For example, a Windows Server 2016 RDS license server can host licenses from all previous versions of RDS, while a Windows Server 2012 R2 RDS license server can only host licenses up to Windows Server 2012 R2.In this blog post, we’ll try to put some structure in RDS and VDI licensing and explain some of the main concepts and options. The following table shows the CALs that are compatible on RD Session Hosts and RD Virtualization Hosts.Īny RDS license server can host licenses from all previous versions of Remote Desktop Services and the current version of Remote Desktop Services. You can't use older CALs to access newer Windows Server versions, but you can use newer CALs to access older Windows Server versions. Note about CAL versions The CAL used by users or devices must correspond to the version of Windows Server that the user or device is connecting to. The following table outlines the differences between the two types of CALs:ĬALs are physically assigned to each device.ĬALs are assigned to a user in Active Directory.ĬALs are tracked and enforced by the license server.ĬALs are tracked but not enforced by the license server.ĬALs can be tracked regardless of Active Directory membership.ĬALs cannot be tracked within a workgroup.ĬALs can be over-allocated (in breach of the Remote Desktop licensing agreement). Use the following information to learn about how client access licensing works in Remote Desktop Services and to deploy and manage your licenses: If an appropriate RDS CAL is available from a license server, the RDS CAL is issued to the client, and the client is able to connect to the RD Session Host server and from there to the desktop or apps, they're trying to use. The RD Session Host server then requests an RDS CAL from the Remote Desktop license server.

When a user or a device connects to an RD Session Host server, the RD Session Host server determines if an RDS CAL is needed. An RDS licensing server is needed to install, issue, and track RDS CALs. A client access license (CAL) is needed for each user and device that connects to a Remote Desktop Session (RDS) host.
