Thank you. Very well put. BUT, if what I'm reading is correct, with device cal's when your number is issued, you are done, no more connections are allowed until one is freed up. I own 70 device cals. I have less than 70 users logging in, but many of them log in from 2 or 3 different machines and we run out because of that. If I had purchased user licenses, and if I understand what I have read, even when/if my licenses were exceeded my users would not be denied access to the terminal server. It was an unfortunate choice for us. We intend to be compliant with our licenses ALL THE TIME, so we aren't just looking for a way to cheat MS. If I had purchased per user licenses I would not have a problem. I have fewer than 70 users accessing the TS servers I am absolutely sure.
On Tue, Oct 6, 2009 at 12:50 PM, Ben Scott <[email protected]> wrote: > On Tue, Oct 6, 2009 at 1:41 PM, Free, Bob <[email protected]> wrote: > > Still won't help. TS Licensing still has no notion of concurrency. > > To amplify what Bob is saying: > > Every client using your server must have a CAL. CALs are *not* > assigned to servers, they're assigned to clients. > > The client that gets the CAL assigned to it can be a warm body > ("user") or a piece of equipment ("device"). But one of those two > must have a CAL assigned it. > > If you have one Terminal Server, with 100 users (each with their own > PC), you need 100 CALs. Even if you only have *one* person logging on > at a time, you still need 100 CALs. > > http://www.microsoft.com/windowsserver2008/en/us/licensing-terminal.aspx > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
