[K12OSN] one more time

[Sharon Betts]

"Support list for opensource software in schools." <k12osn at redhat.com> on
Wednesday, February 23, 2005 at 11:36 AM +0000 wrote:
>Please elaborate on what you're trying to do.  It's not clear to me what 
>you want to accomplish.  If all your clients boot from their local 
>drives, what's the point of the terminal server?  Actually, the real 
>question is the other way around: since you can have the clients boot 
>from an LTSP server, why even bother having a locally-installed OS on 
>the clients?  Or are these Windows boxes that need to remain so, but you 
>want to use a boot-floppy for those times when you want them to be 
>thin-clients?
I have IGEL clients (linux flash bootable) and legacy windows 2000
machines.  They presently all boot and then authenticate through my
Windows server, access my WIndows terminal server for Star Office and many
other apps. and use the file server for their folders.

 I want to implement a Linux terminal server to serve GIMP, some TUX
stuff, Scribus, Kino, etc.   The users need to be able to access the apps
on the windows terminal server as well  and print to network printers and
save/load from their folders (on the Windows file server).  These are
elementary students and teachers -- things must be pretty seamless for
success.  This is my pilot school -- I have 4 others presently running
purely WIndows networks (except for one standalone LTSP project with thin
clients).

Best scenario --At each school, my windows authentication and file servers
remain, and I add both WIndows and a LInux terminal servers and get away
from all those locally installed apps.  Obviously adding Windows terminal
servers is no problem, its the linux....
Sharon
>
>I think the simplest approach would be to start by building a two-NIC 
>LTSP server, with one NIC connected to a switch that only has terminal 
>clients attached to it, and the other NIC connected to your existing 
>network.  This is the default configuration for LTSP.  This way, the 
>DHCP server on the LTSP server only provides IPs to the clients, not 
>other workstations, and it doesn't bother the rest of your existing 
>network.
>
>Are you trying to provide additional workstations for users but have 
>them all have access to the existing Windows resources?
>
>Petre
>
>
>
>Sharon Betts wrote:
>> I tried to ask this previously, but wasn't clear, I guess.
>> Is there anyway to incorporate LTSP into an existing Windows 2000 / 2003
>> network?  I have a Windows network with  DHCP, authentication/file and
>> terminal servers running.  I would like to add an LTSP to the network --
>> but HOW?   The clients need to access every resource -- they are all
>local
>> bootable clients (no true thin clients booting from the server).  
>> 
>>>From all we have read, LTSP doesn't play nice in this situation.  At
>this
>> time, I cannot begin to change the entire network for LDAP.  Just not
>> feasible with the number of workstations and users.
>> 
>> Sharon 
>> MSAD#71 Director of Educational Technology
>> sbetts at msad71.net          http://www.msad71.net     207-985-1100
>> "To err is human - and to blame it on a computer is even more so."    
>> Robert Orben
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> 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>



Sharon 
MSAD#71 Director of Educational Technology
sbetts at msad71.net          http://www.msad71.net     207-985-1100
"To err is human - and to blame it on a computer is even more so."    
Robert Orben