[THIN] Re: Tracking 2003 CAL's
- From: "Landin, Mark" <Mark.Landin@xxxxxxxxxxxxxxxx>
- To: "thin@xxxxxxxxxxxxx" <thin@xxxxxxxxxxxxx>
- Date: Mon, 29 Jun 2009 14:56:29 -0500
TS Per-User CAL's are currenly done on the "honor system". In 2003, TS Per-User
CAL usage is not tracked. In 2008, TS Per-User CAL usage is tracked, but not
enforced (i.e., at least you can tell when you are breaking your license
agreement!)
There's no real easy way to tell what is going on. Your TSCAL license serve, or
alternatively, your Microsoft EA agreement, ought to tell you how many TS CAL's
you own. If you control access to the TS server, or the applications that are
hosted on them, via something like AD group membership, you can count the
number of folks in those groups and compare that to the TS CAL count. That's
about as scientific as it can get with 2003. If you don't control access to
your TS systems, then theoretically all of your users are potential users of TS
and thus should be covered by a TS CAL, and HR can thus tell you how many you
should own.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Gary Scanga
Sent: Monday, June 29, 2009 2:15 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Tracking 2003 CAL's
Thanks again Carl.
To be clear, ensuring that I own enough TSCAL's for every named user is for
satisfying compliance requirements and not technical requirements. This is
where the ability to track utilization would be helpful since it'd provide real
data to decision makers as well as ensure that we originally sized our TSCAL's
accurately.
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Carl Stalhood
Sent: Monday, June 29, 2009 1:09 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Tracking 2003 CAL's
User CALs are not enforced.
Device CALs are enforced.
Make sure all of your Terminal Servers are configured with Per User TS
Licensing and there won't be a problem (run tscc.msc). However, you still have
to ensure that you own a TSCAL for every named user that connects to Terminal
Server.
On Mon, Jun 29, 2009 at 1:03 PM, Gary Scanga
<Gary.Scanga@xxxxxxxxxxxxxxx<mailto:Gary.Scanga@xxxxxxxxxxxxxxx>> wrote:
Thanks Carl. Yes, I was asking about Per-user CAL utilization. Bummer there's
no simple way to track these in 2003.
I'm continuing to look into managing the utilization of these CAL's because I
suspect that we're running near capacity and want to know when the limit's been
reached. However, based on this
definition<http://en.wikipedia.org/wiki/Client_Access_License#CAL_Enforcement>
it appears that my 2003 terminal server farm may allow additional connections
beyond the number of CAL's installed. So, if I have 500 CAL's configured on my
2003 terminal server license server, connection number 501 would technically be
allowed. And perhaps that's a reason why tracking their utilization isn't so
important as it won't negatively impact the business.
Can else anyone confirm this?
I simply want to avoid the opposite being true and connection number 500 is
rejected due to a CAL limitation.
Thanks!
From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx>
[mailto:thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx>] On Behalf
Of Carl Stalhood
Sent: Wednesday, June 17, 2009 9:27 AM
To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx>
Subject: [THIN] Re: Tracking 2003 CAL's
You mean User CALs? User CALs are tracked in 2008 but not in 2003.
On Tue, Jun 16, 2009 at 11:24 PM, Gary Scanga
<Gary.Scanga@xxxxxxxxxxxxxxx<mailto:Gary.Scanga@xxxxxxxxxxxxxxx>> wrote:
Does anyone have a decent way of tracking the issuance or utilization of TS
CAL's in 2003?
Thanks in advance!
________________________________
This message and any attachments may be a confidential attorney-client
communication or otherwise be privileged and confidential. If you are not the
intended recipient, any review, distribution or copying of this transmittal is
prohibited. If you have received this transmittal in error, please reply by
e-mail and delete this message and all attachments
Other related posts:
