Open Source

1
Open Source Thin Clients
The Lowest TCO workstations around!
Rich McCue June 2005 mccue_at_law.uvic.ca
2
Outline for This Session

• What is LTSP?
• Our Problems Possible Solutions
• Strengths Weaknesses of LTSP
• Server Install
• Client Install
• Kiosk Configuration
• Demonstration
• Discussion

3
What is LTSP?

• The Linux Terminal Server Project (LTSP) is a
  component of Linux that allows inexpensive thin
  client computers to be connected to a server,
  spreading the power of the server to many
  desktops.

4
Our Problems

• We needed more Public Workstations throughout our
  library.
• We had no budget for new workstations.
• We had a room full of Pentium 200's.

5
Screaming Fast Desktop-or- Usable Thin Client
6
Goals and Objectives

• Clean out the storage room!
• Reduce support costs decrease management
  headaches.
• Increase the number of available workstations for
  students.
• Fame, glory, tons of cash, stock options,
  adequate budgets, and all the other benefits of
  working in Education (yeah, right!).

Eric Harrison, link to quote
7
Possible Solutions...

• Traditional PC with Microsoft Windows
• Windows Terminal Service (Citrix)
• Traditional PC with Linux
• Thin client based on Linux

8
Solution 1 Traditional PC with Windows

• Too expensive to deploy. Each workstation would
  cost 1,200 US.
• Expensive to maintain. 50 workstations would
  require at least part-time systems admin.
• Virus and Spyware problems.
• Future software upgrades could mean hardware
  upgrades to ALL desktops.

9
Solution 2 Windows Terminal Service (Citrix)

• Based on Microsoft Windows (some might call that
  a strength -)
• Expensive Per-User licensing for software.
• Virus and Security issues.
• Much less expensive to maintain than full windows
  desktop or full linux desktop.

10
Solution 3 Traditional PC with Linux

• Lower initial cost than option 1 or 2.
• Too much hardware at each desktop for surfing web
  and email!
• Expensive to maintain upgrade hardware.

11
Solution 4 Thin Client based on Linux

• No moving parts.
• Loads the operating system from the server.
• No local storage. Means all data is stored (and
  backed up) on the server.
• Significantly lower cost to purchase (hardware).
• Less expensive to maintain.

12
Linux Terminal Server Project (Strengths)

• Centralized Management, Reliable, No Licensing
  Costs!
• Fast! Terminals run at the speed of the server.
• Inherent remote administration capabilities.
• Relatively secure (not many virus problems in any
  case).

13
Strengths continued

• Keep asking how much things cost... And say Wow!
  That's expensive! What does it offer that my no
  licence fee solution does not?

14
Weaknesses

• Legacy application support can be expensive
  and/or resource intensive (WINE WINdows
  Emulation).
• Floppy support is a bit different than students
  are used to.
• Managing mixed clients can be a pain.

15
Network Layout
16
Server Install Choices...

• K12 LTSP
• http//k12ltsp.org
• Currently based on Fedora Core 3
• Many built in features.
• Lots of programs.
• Admin Utilities built in.

• LTSP
• http//ltsp.org
• Use any linux distribution you want (almost).

17
Server Requirements

• Server for up to 5 Clients
• CPU One P4 or Athlon64
• RAM 512mb (50mb for each client)
• HD SATA (2 drives for faster performance)

18
K12-LTSP Install

• Looks like a regular RedHat install Until...

19
Some Quirks...

• Expects two network cards.
• DHCP server enabled by Default (a great way to
  cause network havoc).
• Automatically assumes you'll use 192.168.0.
• See the following URL's for install tips...
• http//k12ltsp.org/install.html
• http//k12ltsp.org/server.html

20
Configuring Clients

• You NEED access to your DHCP Server (or be on
  good terms with the sys Admin or set-up a
  separate VLAN for the LTSP, DHCP server).
• You need to put the MAC Address and IP address of
  the thin client in the dhcp.conf file (if you
  have an existing DHCP server that you use).
• Use either bootp or bootable floppy
• See http//www.Rom-O-Matic.net for boot floppy.
• You can also use the PXE boot protocol...

21
Kiosk configuration

• Add to the following File /etc/X11/xdm/kdmrc
• X-ws0040-Core
• AutoLoginEnabletrue
• AutoLoginUserws004
• Edit the following File /etc/sysconfig/desktop
• DISPLAYMANAGER"KDE"
• DESKTOP"KDE"
• Make sure you have a user called ws004 and the
  host name for a workstation is ws004.
• Reboot and you should be in business.
• You'll need to lockdown the ws004 user profile.
  KDE has great tools for this.

22
Demonstration

• Firefox Web browser
• OpenOffice (MS Office Compatible)
• Acrobat Viewer
• RealPlayer
• Flash Plugin
• Java Plugin
• Connect to Windows Terminal Server

My Test Bench
23
Conclusions

• The year we implemented the public access
  terminals, it was ranked as the most important
  improvement to student services that year!
• Use it where appropriate! (i.e. where legacy
  apps are not an issue).
• The cost savings will look good, and the
  performance is great.

24
Questions Discussion...

• Credits Thanks to the following
• http//ltsp.org/
• http//k12ltsp.org/
• http//www.ltsp.org/contrib/autologin_kdm.html
• http//k12linux.mesd.k12.or.us/intel/
• http//yhslug.tux.org/presentations/ltsp/
• http//www.ltsp.org/presentations/
• Case Studies
• City of Largo Florida - 400 Thin Clients
• LTSP for Libraries, a how-to

25
Any other questions?

• Feel free to contact me if you have any other
  questions...
• Rich McCue
• UVic Faculty of Law
• rmccue_at_law.uvic.ca
• Ph [phone]
• http//law.uvic.ca/rmccue/