The Spin on Thin: Thin Clients in Academic Libraries

1
The Spin on ThinThin Clients in Academic
Libraries

• Presented at LITA 2006
• by
• Helene GoldElectronic Services LibrarianEckerd
  College, St. Petersburg, FL

2
A little background

• 15 millionNew Library!
• Library and ITS department to share new building
• ITS uses new library for thin client testing
  grounds
• ITS decided, implemented, managed

3
The Big Picture

• Server(s) performs all functions
• Windows, UNIX, or Linux based
• All software runs from the server(s)
• Clients (dumb terminals) connected to server
• Clients unique thin terminals or PCs

4
The Small Picture Thin Clients

• No hard, floppy, cd-rom drive
• Users login to save data to server account
• Can run in kiosk mode
• Can run Windows desktop, SunOS or Linux interface
  (GNOME)
• Supports USB storage devices

5
SUN Thin Client Terminal
6
SUN Thin Client Terminal Side View
7
How and Where Libraries

• Designated OPAC
• General Public Computing (Internet, Word
  Processing, etc.)
• Labs
• Open staff work areas

8
How and Where Around Campus

• Recreational and dining areas
• Visitor areas
• Lobbies
• Dorm Lounges

9
How and Where Beyond Libraries

• Cube farms (data entry, call centers, etc.)
• Warehouses
• Franchise locations
• Public Schools
• Hospitals
• Law Firms

10
TRENDS

• By 2008, 50 of corporate workstations will be
  thin
• Citrix 95 of PC applications can run through
  Citrix platform (75 of market share).
• Wireless and remote access thin computing
• Colleges and Universities LAB USE

11
Appropriate for library computing?

• Cons
• No CD-ROM drive
• No Floppy drive
• Limited / No support for external devices (bar
  code readers)

12
AND

• Software usability issues
• High bandwidth needed
• Comprehensive User Training
• SPOF (Single Point of Failure)
• High initial costs

13
AND

• Limited CONTROL (ITS expert programming skills,
  time, money)
• Limited EVIDENCE (few libraries using thin
  clients)

14
Cons from Survey

• Software incompatibility
• No CD-ROM or floppy drive
• Network too slow
• Freeze up too often (MS Office-related)
• Students dont know how to use them

15
Appropriate for library computing?

• Pros
• Space, cost, and energy savings
• Centralized upgrades
• Longevity

16
AND

• Security (data and viruses)
• Not targets for theft
• No chat, games, downloads

17
Pros from Survey

• Centralized Upgrades
• Easy to operate / maintain
• Cost Savings
• Security
• 62.5 report high / average satisfaction

18
From the Trenches day to day

• User Interface
• Microsoft Office
• Smart Cards
• Printing

19
User Interface

• ITS decision to use GNOME (UNIX/Sun)
• Unfamiliar / unintuitive aspects
• Other libraries use Win OS interface
• Outreach / Education

20
Microsoft Office

• Runs on separate Linux Server
• Uses SSH tunnel display
• Uses LDAP servers
• Majority of our user complaints are with MS
  Office software performance

21
Word and USB storage The Steps

• User creates document in Word
• User saves document to default My Documents
  folder (Crossover server)
• User inserts USB storage device and waits for USB
  icon to appear on screen. User opens USB folder
• User opens Documents folder, opens My Documents
  sub-folder
• Drags file from My Documents to USB folder.
• User never returns to thin client for word
  processing

22
Smart Cards

• Uniquely Sun MicroSystems Technology
• Hot Desking

23
Smart Cards

• Costs (4 per card)
• User education

24
Smart Cards Student Confusion
25
Smart Cards Student Confusion
26
Printing

• Removed Solaris Printer Server and installed
• CUPS (UNIX standard) stand-alone
• Web interface
• Thin clients do not support USB printers

27
The Server

• Server memory- 250MB kiosk, 500MB session
• We run 30 clients on 8GB
• Performance affected by network traffic, software
  demands- when server is slow, all clients are
  affected.
• Linux No Kiosk Mode

28
SERVER ARCHITECTURE
OS and Software 2 CPUs and 4GB RAM Medusa
OS and Software 2 CPUs and 4GB RAM Hydra
INTERNET
Crossover Server 1 CPU2 GB RAM Gorgon
29
SERVER ARCHITECTURE
OS and Software 2 CPUs and 4GB RAM Medusa
OS and Software 2 CPUs and 4GB RAM Hydra
INTERNET
LDAP Authentication Smart Card Login
Crossover Server 1 CPU2 GB RAM Gorgon
30
SERVER ARCHITECTURE
OS and Software 2 CPUs and 4GB RAM Medusa
OS and Software 2 CPUs and 4GB RAM Hydra
INTERNET
ACASUN FILE SERVER logged-in users only
LDAP Authentication Smart Card Login
Crossover Server 1 CPU2 GB RAM Gorgon
31
SERVER ARCHITECTURE
32
So

• Decide who will implement and manage thin clients
• Decide user needs and software compatibility
• Decide cost savings and ROI

33
Does your library

• Have its own staff with Unix programming
  expertise?
• Have a really, really good relationship with ITS
  / CS?
• Spend too much time upgrading, fixing, and
  managing PCs?
• Welcome change?

34
If you answered yes to all of these

• Thin client computing can work for you

35
Does your library

• Need public computing with CD-ROM and floppy
  drives?
• Need public computing with computational /
  graphical heavy software?
• Have few/no technologically savvy staff or poor
  ITS support?
• Seem just fine and happy with what youve got?
  (thank you very much for asking!!)

36
Then Thin Clients

• Might not be right for your library

37
Survey Comments

• Like most new things, there was hesitation in
  the beginningbut now, most students seem to have
  adapted very well.
• Despite the cost savings, the number of problems
  for staff, students, and IT outweighs any
  advantage

38
The Spin on ThinThin Clients in Academic
Libraries

• Presented at LITA 2006
• by
• Helene GoldElectronic Services LibrarianEckerd
  College, St. Petersburg, FL