RDS Per Device CALs : RDS CALs are physically assigned to each device. After that we need to choose either of below Licencing model and need to Purchase it from the Microsoft store or from a vendor.
#User cal vs device cal license#
There is a default licensing applied on installation and activation with a grace period of 180 Days during which no purchased RDS CAL license needed. The RDS CALs is installed as a server Manager Role. If we enable RDS CALs, each user and device that connects to a Remote Desktop Session host needs a client access license (CAL). If we need more than two users simultaneously log into the server we need to have Remote Desktop Licensing (RD Licensing), formerly Terminal Services Licensing (TS Licensing), which manages the Remote Desktop Services client access licenses (RDS CALs) for users to connect to a Remote Desktop Session Host (RD Session Host) server.
#User cal vs device cal windows#
Applies Toīy default only two concurrent active rdp sessions are allowed on a windows server editions like 2012,2016 or 2019. There is no noticeable changes in the Steps we follow for any of these Windows Server Editions. The steps are almost identical on each windows server editions. We can also use same steps if we have windows 2016 or 2012. Maybe I'm wrong but if you're licensing server is trying to hand out per-user CALs (because it detects that's what you need based on the type of login) then you need per-user CALs installed.In this blog post we will discuss on Installing and Configuring a Remote Desktop License Server (RDS CALs) on Windows server 2019. After all this.does it matter? To me, I think it does. This makes sense to me based on the logic provided in the article I mentioned above, further bolstering the fact that they need per-user and not per-device CALs. It never touches the per-device CALs that are installed. When the new environment is tested, the licensing server creates this alternate per-user (what I would call "temporary") license to provide the user. They have their Citrix licensing but now they have per-device RDS CALs. Maybe a user here and there will go login from a different device but they overwhelmingly all use the same device on a daily basis.Ī new environment is being stood up which is based on XenApp with Server 2016. A typical day for a user is that they walk up to their thin client or workstation, login, do their work, log off. They don't have multiple users sharing devices. By definition, they don't meet the "per-device" scenario. Somewhere along the way their licensing renewal switched to per-device. They have per user installed in their current 2012 environment. Anyway, per-device CALs were purchased and installed and I think they need per-user. It walks you through the different license types and how licenses get checked out etc. I've researched around and the most logical and well written article I could find about licensing is here. Here's the situation.I'm pretty sure the wrong type of RDS CALs were purchased for a client of ours.