<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Shawn:</FONT></DIV>
<DIV><FONT face=Arial size=2>This sounds correct. We are using MS terminal
Services in addition we have a Cal for Citrix for each desktop. One grey area is
the licensing for the MS apps if you meter the usage and they are open licenses.
In other words they were not purchased installed on a particular PC. One help we
have found is the MS Fresh Start program that allows a free Desktop license (W98
or W2k) for schools that are using donated PC,s. Saves $50.00 per station.
Because of this program we did not switch to using Linux and Citrix on the
desktop, which works very well by the way.</FONT></DIV>
<DIV><FONT face=Arial size=2>MIke</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>Few salesmen understand the licensing for terminal sessions. Here's
the <BR>skinny as far as I know. (someone correct me if I'm
wrong)<BR><BR>For the "Microsoft way" to connect to a terminal server, using
their <BR>software, you are required to have:<BR>(1) Server OS license.
then for the clients,<BR><BR>(1) OS license for the terminal (running win98 or
winCE something like that)<BR>(1) CAL for accessing the server<BR>(1) TCAL for
accesing the server as a terminal (and requesting a session)<BR>(1) license for
each app installed on the server. ie, I have to have 75 <BR>Office 2003
licenses on the machine, whether or not more than 1 person <BR>will actually
*use* it -- I still have to have the license for all <BR>possible
connectees.<BR><BR>The way LTSP saves a little money is that there is no need
for that <BR>first license, ie the "Win98 or WinCE" on the terminal.
That's how LTSP <BR>is the cheapest way to implement Microsoft
Terminals.<BR><BR>I hope that is clear. PLEASE realize that even if your
salesman says <BR>you only need a TCAL -- they are wrong. You need a CAL
and a TCAL for <BR>each device or user. (That's another twist, you can
assign the licences <BR>to specific units, or to specific users -- or a
combination. For most <BR>folks like us, it's easiest to just get the
license for each thin client.)<BR><BR>I'm still waiting for my servers to arrive
-- but the notion of the <BR>rdesktop -s flag is exciting, as it could just
"embed" a windows app <BR>into a standard linux desktop. I like that idea.
:)<BR></DIV></BODY></HTML>