I just checked MS Terminal server manager and it shows 35 sessions are active from students on the system used by the students. But, checking Terminal server licenses only shows 1 license (a single device cal) being required. Now, we have 50 licenses on the server, and over the last 4 years, only 6 have ever been used, one for each different device that has connected (4 other servers and 2 desktops via MS's TSclient). I agree that MS would probably take exception to the use of a Linux TS to tie in with their TS because it looks like it only pulls 1 license, but .. that is why I mentioned the device CAL issue. I still think that the way the licensing was intended was that each TS session requires a device cal for each device. This isn't unreasonable from MS's perspective where the remote devices are single user systems (their desktops) and thus each device corresponds to a user session, but ... if coming from a multi-user system, it appears they did not account for this scenario. I would probably still lose in court though :( Sincerely, Dave Hopkins <div>On 1/26/07, Petre Scheie <<a href="mailto:petre@maltzen.net">petre@maltzen.net</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> My recollection from previous discussions is that whatever is the most expensive way to do it, that's the way MS charges you, at least in regard to TS client licenses. Olivier's description fits that: you need a license for each client machine. The fact that multiple copies are running on one machine, the server, is irrelevant. Make sure the administration knows this, that ANY time you start to venture into the MS world, it will cost more money. Petre Olivier Mugnier wrote: > Knowing a bit of TSE technology on windows... you need one license for > each connection > I mean... 1 license <=> 1 thin client (the same or different during time) > > You can open a non-local session for each license you have.... > > Not knowing LSTP yet but I think that if you want RDP service on win, > you need as much license as you have thin client connected at same time > (1 client is already include in windows pro, 2 in server editions) > (RDP don't allow you to boot but linux have RDP client) > Not sure of the difference between RDP and TSE.... > > ----- Original Message ----- > *From:* David Hopkins <mailto:<a href="mailto:dahopkins429@gmail.com">dahopkins429@gmail.com</a>> > *To:* Support list for open source software in schools. > <mailto:<a href="mailto:k12osn@redhat.com"> k12osn@redhat.com</a>> > *Sent:* Thursday, January 25, 2007 11:32 PM > *Subject:* Re: [K12OSN] Terminal Services Licenses for rdesktop > > I think this was discussed before, but ... are TSCALs per device > that is connecting or per user? I thought there was a possibility > that if it was per device, then from the Windows Terminal Server's > perspective only one device is connecting (all connections originate > from the Linux terminal server), but with multiple sessions? > Anyhow, not sure I would want to test this logic in court. > > Otherwise, I second taking a shot at using wine to run the app first > before investing in the TSCALs. $138 Canadian? And I complained > about $42 US. > > Sincerely, > Dave Hopkins > > > > On 1/25/07, *Mel Wade* < <a href="mailto:mel@melwade.com">mel@melwade.com</a> <mailto:<a href="mailto:mel@melwade.com">mel@melwade.com</a>>> > wrote: > > Yes, if you are going to access a Windows Terminal Server. > > -- > Mel Wade > "The real problem is not whether machines think but whether men > do." - BF Skinner > <a href="http://www.melwade.com"> http://www.melwade.com</a> <<a href="http://www.melwade.com/">http://www.melwade.com/</a>> > _______________________________________________ > K12OSN mailing list > <a href="mailto:K12OSN@redhat.com"> K12OSN@redhat.com</a> <mailto:<a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a>> > <a href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a> > For more info see <<a href="http://www.k12os.org">http://www.k12os.org</a> <<a href="http://www.k12os.org/">http://www.k12os.org/</a>>> > > > ------------------------------------------------------------------------ > > _______________________________________________ > K12OSN mailing list > <a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/k12osn"> https://www.redhat.com/mailman/listinfo/k12osn</a> > For more info see <<a href="http://www.k12os.org">http://www.k12os.org</a>> > > > ------------------------------------------------------------------------ > > _______________________________________________ > K12OSN mailing list > <a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/k12osn"> https://www.redhat.com/mailman/listinfo/k12osn</a> > For more info see <<a href="http://www.k12os.org">http://www.k12os.org</a>> _______________________________________________ K12OSN mailing list <a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <<a href="http://www.k12os.org"> http://www.k12os.org</a>> </blockquote></div>