locked
Per User CAL Questions RRS feed

  • Question

  • We're looking to bring up a 2008 R2 box running RDS.  We would be using Per User CALs.

    We're having some discussions on what our business policy will be so far as who has access, but I'm trying to understand the initial CAL purchase.

    We obviously intend to be fully legal but don't want to purchase more CALs up front than we have to.

    My understanding from here http://technet.microsoft.com/en-us/library/cc753650.aspx is that CALs are not enforced and basically work on trust so if we initially buy, say 10 CALs, but underestimated and 12 people try to logon they will be able to but obviously we need to go and buy 2 more CALs?

    So Joe comes along and logs onto our RD box.  A User CAL is assigned to him.  He uses the RD box for a few months and then leaves the company.  52 to 89 days after the date that he last used the RD box, his User CAL is released back into the pool.

    Have I missed anything here?  With the likes of Contractors is there any way to manually release a User CAL as they can leave at short notice.

    Thanks,

    Paul

    Saturday, October 29, 2011 7:19 PM

Answers

  • Hi Paul,

    Per User RDS CALs expire after 60 days from last renewal so will automatically be removed from the usage report.  They also will be removed from the report immediately if you delete the user account.  For example, a Contractor logs on to your RDSH server, then if you delete the account the RDS CAL will not show up as being used.

    In RD Licensing Manager (licmgr.exe) you first create a Per User usage report, export it as a csv file, then open it in Notepad, Excel, etc.  In the usage report you can see what users have been assigned an RDS CAL, when it expires, totals, etc.

    Keep in mind that all of the above is simply a mechanism to help you comply with the license agreement.  You should own a Per User RDS CAL for each person that connects to the RDSH server, and each CAL should be permanently assigned to that user.  Under the agreement you may permanently reassign a CAL to another user if needed (say the employee leaves the company) as well as temporarily assign a CAL to a temporary worker while a user is absent.  This gives you a large amount of flexibility.

    What is perhaps subject to interpretation is the definition of permanently assign, permanently reassign, etc.  For example, say a company had 100 employees that regularly used their RDSH server, however, only 10 used it each day on a rotating basis.  If every day they "permanently reassigned" the Per User RDS CALs to 10 different people I think an auditor would judge this as noncompliant in my opinion.

    -TP

    • Proposed as answer by TP []MVP Saturday, February 11, 2012 11:01 PM
    • Marked as answer by TP []MVP Tuesday, February 14, 2012 8:12 AM
    Saturday, October 29, 2011 7:50 PM

All replies

  • Hi Paul,

    Per User RDS CALs expire after 60 days from last renewal so will automatically be removed from the usage report.  They also will be removed from the report immediately if you delete the user account.  For example, a Contractor logs on to your RDSH server, then if you delete the account the RDS CAL will not show up as being used.

    In RD Licensing Manager (licmgr.exe) you first create a Per User usage report, export it as a csv file, then open it in Notepad, Excel, etc.  In the usage report you can see what users have been assigned an RDS CAL, when it expires, totals, etc.

    Keep in mind that all of the above is simply a mechanism to help you comply with the license agreement.  You should own a Per User RDS CAL for each person that connects to the RDSH server, and each CAL should be permanently assigned to that user.  Under the agreement you may permanently reassign a CAL to another user if needed (say the employee leaves the company) as well as temporarily assign a CAL to a temporary worker while a user is absent.  This gives you a large amount of flexibility.

    What is perhaps subject to interpretation is the definition of permanently assign, permanently reassign, etc.  For example, say a company had 100 employees that regularly used their RDSH server, however, only 10 used it each day on a rotating basis.  If every day they "permanently reassigned" the Per User RDS CALs to 10 different people I think an auditor would judge this as noncompliant in my opinion.

    -TP

    • Proposed as answer by TP []MVP Saturday, February 11, 2012 11:01 PM
    • Marked as answer by TP []MVP Tuesday, February 14, 2012 8:12 AM
    Saturday, October 29, 2011 7:50 PM
  • Thanks TP.  Useful to know that deleting a user immediately frees up a CAL, I wasn't aware of that.

    Ignoring the definition of "permanently reassign", how do you technically reassign a CAL, or is it purely an "on paper" exercise because so much of the per user stuff seems to be done on trust?

    Thanks,

    Paul

    Sunday, October 30, 2011 3:05 PM
  • Hi Paul,

    There is no built-in option for reassigning Per User RDS CALs.  You could manually edit the user account object attributes, but I do not think that it is necessary.

    So it is a compliance/on paper exercise.

    -TP

    Saturday, February 11, 2012 11:07 PM
  • This may not technically belong on this thread, so apologies in advance if it is not. I have an RDS License Server that has both Per Device and Per User. The Per User CALs being new and we want to switch from Per Device to Per User. I've manually changed one of my servers to use Per User, but on the license server, I do not see a Per User CAL being used. I want to avoid having issues obviously and wanted to know if there was something special I needed to do in order for the Per User CALs to start being used, or if I can simply just deactivate our Per Device CALs and the Per User will start being used once I change all of my servers to start using Per User. Thanks in advance for any assistance.
    Thursday, October 25, 2012 5:18 PM