the QMU thin-client project
Fraser Muir
Director, IS and LRC
what is thin-client?A thin-client is a client computer in a client-server architecture network which depends
primarily on the central server for processing activities, and mainly focuses on conveying input and output between the user and the
remote server. In contrast, a thick or fat client does as much processing as possible and passes only data for communications and
storage to the server.
Definition courtesy of Wikipedia
perception vs realitythick-client thin-client
heavy footprint broad reach
time consuming to deploy network dependency
responsive poor user experience
highly productive complex and not well understood
rich user experience easy to deploy
well understood easy management
why would you choose to follow the thin-client path (from an IT perspective)?
the change process
from PC to TC
•change management•changing user perceptions of technology•re-skilling of IT staff
outcomes
All existing individual and IT lab computers are to be migrated and replaced with thin-client devices unless the work of the institution cannot be achieved by the use of this technology or by providing an alternative
within a shared space. No individual will have a personal computer on their desk.
This is an institutional imperative in line with project Re:Locate.
implementation schedule
project initiation november 2004
proof of concept june 2005
supplier award january 2006
student lab migration september 2006
old campus complete may 2007
campus relocation summer 2007
0
200
400
600
800
1000
1200
1400
Terminal count
Application count
PC count
benefits
remote working
funny; now tell me the specifics
blade servers• 40% less energy
than conventional servers
• HP BladeSystem 27% less energy than competitors
thin-clients• 17W per client max• 90% reduction on our
old PCs• CRT to LCD migration
conscious procurement decision end-2004
support
extended equipment
lifespan
thin-client: 5-6 years
disadvantagesand our solutions
non-compliant software
• computer aided design
• video and audio editing
• hardware dependent
all eggs in one basket
we had better make it a
super-strength basket
loss of local control
• tackled early as a separate project
• although staff were unable to install or change anything locally, support was improved and it was soon accepted (by most)
final thoughts
learn from our pain
• choose your targets• get institutional buy-in at all costs• choose some academic and support staff to
champion the technology• accentuate the benefits• accept that it will not meet everyone’s needs
so have a contingency• experience depends on the client hardware
“big picture”
print, copy and scan
smartcards
wireless & TC laptops
VoIP