[K12OSN] Windows Terminal Services
David Hopkins
dahopkins429 at gmail.com
Tue Jul 17 00:29:45 UTC 2007
Shoot, I mean Terrel, sorry Terrel.
On 7/16/07, David Hopkins <dahopkins429 at gmail.com> wrote:
>
> Julius has it correct I fear. You need to carry as many tscals as
> simultaneous connections.
>
> On 7/16/07, Kemp, Levi < lnkemp at bolivar.k12.mo.us> wrote:
> >
> > Dave,
> > So for example I have one LTSP lab and one Legacy app I'm
> > wanting to use. If I have 30 users logged in and wanting to open that one
> > app off of a terminal server through the LTSP server I only need one device
> > cal? Or do I need 30 user cals as well since 30 users will be accessing the
> > terminal server. If it is only the device cal how do I set that up? My LTSP
> > server is authenticating to the AD so each user is logged on using their AD
> > account, is that an issue?
> >
> > Levi Kemp
> >
> >
> >
> > ________________________________
> >
> > From: k12osn-bounces at redhat.com [mailto:k12osn-bounces at redhat.com
> > ] On Behalf Of David Hopkins
> > Sent: Wednesday, July 11, 2007 10:42 AM
> > To: Support list for open source software in schools.
> > Subject: Re: [K12OSN] Windows Terminal Services
> >
> >
> > Julius,
> >
> > If you notice, I said I carry enough device cals to cover my
> > thin clients. However, I have device cals, not user cals, and the MS
> > agreement is per device that is connecting. Technically, I have exactly 3
> > devices which are connecting, the 3 LTSP boxes, and as picky as MS is in
> > enforcing whatever rules favor them, I find it ironic that I could get by
> > with just 3 device cals.
> >
> > Now, that said, MS has also tried to force businesses to only
> > use User cals so that when a user leaves, the cal goes with them. At a
> > school, this would be silly since students leave every year. Anyhow, not
> > trying to start an argument on this. Just found it interesting.
> >
> > Sincerely,
> > Dave Hopkins
> >
> >
> >
> > On 7/11/07, Julius Szelagiewicz <julius at turtle.com> wrote:
> >
> >
> >
> > On Wed, 11 Jul 2007, David Hopkins wrote:
> >
> > > I don't agree with this way of viewing it. Rdesktop is
> > running from LTSP
> > > server. And, if you go to the Terminal Services
> > Licensing Manager on the
> > > Windows TS, you'll see exactly 1 connection showing
> > up, not matter how many
> > > thin clients are connected. I have 3 LTSP servers,
> > and the most I have ever
> > > had is 3 licenses being used, even with 150 thin
> > clients in use. I think MS
> > > didn't think of this loophole.
> > >
> > they most certainly did - the licensing is per user, no
> > matter how the
> > server sees it. if you use their software, you should
> > pay for it, no
> > matter the value you get out of it.
> > julius
> >
> >
> >
> >
> >
> >
> >
> > > On 7/10/07, Krsnendu dasa <krsnendu108 at gmail.com>
> > wrote:
> > > >
> > > > If you run the screen script, isn't rdesktop running
> > as a local
> > > > application on the terminal? If so it would have a
> > different ip
> > > > address. i.e. another device
> > > >
> > > > Of course if you run it through the server it would
> > have the same ip
> > > > address, but as Rob mentions below they have
> > probably set it up that
> > > > you can't access more than once from one ip address.
> > > >
> > > > On 11/07/07, Rob Owens < rowens at ptd.net> wrote:
> > > > > Personally I think that if MS's technical measures
> > don't prevent the
> > > > > "one device loophole", then it is ok to do. Like
> > you said, I'm sure MS
> > > > > would want you to pay more, but the fact seems to
> > be that they
> > > > > overlooked this--and that's their problem.
> > > > >
> > > > > -Rob
> > > > >
> > > > > On Tue, Jul 10, 2007 at 11:41:27AM -0400, David
> > Hopkins wrote:
> > > > > > A question I asked about the licence, but is
> > dicey is that the device
> > > > cals
> > > > > > cover 'per device'. From the windows side,
> > every terminal session
> > > > coming in
> > > > > > via rdesktop from you LTSP server looks like it
> > is all coming from 1
> > > > device,
> > > > > > so technically it probably meets the license
> > requirements though I am
> > > > sure
> > > > > > MS wants to you pay for every client device and
> > not for the terminal
> > > > server
> > > > > > itself. I carry enough TSCALS/CALS to cover my
> > thin clients, but I
> > > > guess
> > > > > > some brave soul could argue the technical
> > aspects with MS if they
> > > > wanted.
> > > > > > Seems MS pulls the same tricks when it is in
> > their favor.
> > > > > >
> > > > > > Sincerely,
> > > > > > Dave Hopkins
> > > > > >
> > > > > >
> > > > > > On 7/9/07, "Terrell Prudé Jr." <microman at cmosnetworks.com>
> > wrote:
> > > > > > >
> > > > > > >
> > > > > > >Roger Morris wrote:
> > > > > > >
> > > > > > >John Lucas wrote:
> > > > > > >
> > > > > > > On Monday 09 July 2007 09:28, Timothy Legge
> > wrote:
> > > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > >What is the deal with terminal Services
> > again? I believe I need the
> > > > > > >following:
> > > > > > >
> > > > > > >1) Windows Server
> > > > > > >2) Device/Client Cals for Windows
> > > > > > >3) Device/Client Cals for Terminal Services.
> > > > > > >
> > > > > > >I will be connecting via rdesktop, I assume
> > that is okay as long as
> > > > > > >the above is properly licensed.
> > > > > > >
> > > > > > >Anything else required?
> > > > > > >
> > > > > > > Only to configure Terminals Services for
> > "Application mode",
> > > > > > > otherwise the
> > > > > > >default is "Administrative mode" which only
> > allows 2 simultaneous
> > > > users.
> > > > > > >
> > > > > > > to elaborate a little. in 'admin' mode,
> > no CAL is required,
> > > > right?
> > > > > > >
> > > > > > >
> > > > > > >Correct. You get two CAL's with admin mode
> > automatically...but only
> > > > two.
> > > > > > >Furthermore, if you've got a userID logged in
> > at the console, then
> > > > that
> > > > > > >counts as a session. Thus, Windows XP will
> > give you only one
> > > > terminal
> > > > > > >server session. Dunno how that applies to
> > Windows Server; might be
> > > > > > >similar.
> > > > > > >
> > > > > > >--TP
> > > > > > >
> > > > > > >_______________________________________________
> >
> > > > > > >K12OSN mailing list
> > > > > > >K12OSN at redhat.com
> > > > > > > https://www.redhat.com/mailman/listinfo/k12osn
> > > > > > >For more info see <http://www.k12os.org>
> > > > > > >
> > > > >
> > > > > > _______________________________________________
> > > > > > K12OSN mailing list
> > > > > > K12OSN at redhat.com
> > > > > > https://www.redhat.com/mailman/listinfo/k12osn <https://www.redhat.com/mailman/listinfo/k12osn
> > >
> > > > > > For more info see <http://www.k12os.org>
> > > > >
> > > > > _______________________________________________
> > > > > K12OSN mailing list
> > > > > K12OSN at redhat.com
> > > > > https://www.redhat.com/mailman/listinfo/k12osn
> > > > > For more info see < http://www.k12os.org>
> > > > >
> > > >
> > > > _______________________________________________
> > > > K12OSN mailing list
> > > > K12OSN at redhat.com
> > > > https://www.redhat.com/mailman/listinfo/k12osn
> > > > For more info see <http://www.k12os.org <http://www.k12os.org>
> > >
> > > >
> > >
> >
> >
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN at redhat.com
> > https://www.redhat.com/mailman/listinfo/k12osn
> > For more info see < http://www.k12os.org>
> >
> >
> >
> >
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN at redhat.com
> > https://www.redhat.com/mailman/listinfo/k12osn
> > For more info see <http://www.k12os.org>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/k12osn/attachments/20070716/0f09a903/attachment.htm>
More information about the K12OSN
mailing list