RDS Client Access Licensing

Posted on 2016-08-21
Last Modified: 2016-08-21
Under a Windows Server 2008 R2 setup, I was under the impression that the "per user" CALs simply limited the number of simultaneous users connected to the server (via RDS) at any one point in time.  I recently read somewhere that the "per user" CALs actually are specific to individual users so that, if I had 50 CALs, only 50 "specific" users could connect via RDS vs. my original assumption that 1000 users, for example, could connect but only 50 at a time.  Can someone help clear this up for me?  I've been promoting the idea of remote access to a major client for a number of years and now, all of a sudden, they are really interested in the idea and I'm having second thoughts and feeling a little overwhelmed.  I have a second question regarding RDS.  I have it set up on my own network and it works well except when the end-user attempts to "dump" one of my larger reports to an Excel file on their local system.  This process takes forever (if it even completes) and I'd like to find out if anyone can suggest a solution to make this process any faster?  More RAM, faster bandwidth, etc.?
Question by:Jim Klocksin
  • 2
  • 2

Accepted Solution

Scott Silva earned 500 total points
ID: 41764398
RDS Cal's don't work that way... Although per seat or per machine cals do get permanent assignments, per user cals don't get limited or locked...

But it also means that there is no limiting done by the server, and if user 51 tries to connect, it succeeds and then you are out of licensing compliance... I think there are third party products that will fix this, but I don't think windows does it on its own.

Author Closing Comment

by:Jim Klocksin
ID: 41764404
This is essentially how I always thought it worked, except for the part where the 51st user would still get connected.  Since the reality is that we will most likely be purchasing at least 100 CALs for RDS, I'm currently not too concerned about going over the limit.
LVL 56

Expert Comment

by:Cliff Galiher
ID: 41764649
2012 and newer have enforced per user as well. 2008 and older were honor system. But condoning illegal behavior because you can get away with it is never good.

Author Comment

by:Jim Klocksin
ID: 41764657
What I meant when I said I wasn't too concerned is that I don't believe we will even remotely come close to 100 concurrent users, probably not even 50, but I don't want to take any chances, the account is too important to me.  Point is, I would buy 200 if needed rather than go over my allotted licenses.  When you say that "2012 and newer have enforced per user" what exactly do you mean?  If you're saying that, in my original example, the 51st user would get rejected, but my basic premise on the meaning of the licensing paradigm is correct, I'm good with that.  If, on the other hand, you're implying that the "per user" license is actually associating a CAL with a login ID, then I have a problem!
LVL 56

Expert Comment

by:Cliff Galiher
ID: 41764668
No it isn't correct. RDS isn't, and never was, concurrent. But in 2012, your users will not be allowed to sign in if hey can' get a CAL.

Featured Post

Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

Join & Write a Comment

I had a question today where the user wanted to know how to delete an SSL Certificate, so I thought that I would quickly add this How to! Article for your reference. WHY WOULD YOU WANT TO DELETE A CERTIFICATE? 1. If an incorrect certificate was …
Remote Desktop Shadowing often has a lot of benefits. When helping end users determine problems, it is much easier to see what is going on, what is being slecected and what is being clicked on. While the industry has many products to help with this,…
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now