Introduction
Many small businesses are on a tight budget and scrambling to find ways to reduce costs. With IT often at the head of the line of budget cuts, what can the smart small business do to reduce IT overhead while keeping vital IT services available? One answer is using thin clients.
Using thin client architecture can do all of the following:
- Reduces your overall IT TCO
- Reduces your energy consumption by 30-50% (or more)
- Reduces equipment investment costs
- Reduces end-user training costs
- Reduces IT support costs
- Reduces network bandwidth usage
- Reduces data loss by centralizing storage
- Reduce data theft opportunities
- Reduces viruses and malware
- Eliminates the need for remote office servers
- Eliminates rogue software installations
- Increases network reliability
- Increases network performance
- Increases network scalability
- Simplifies network management
- Centralizing storage makes for easy backup and archiving
- Increases network security
- Increases network availability using fault tolerance and load balancing
- Increased hardware lifespan (7-10 years for a TC compared to 3-4 years for a PC)
- Adds desktop standardization
- Adds software license management controls
This whitepaper will look at how thin client architectures can be a perfect fit in today’s small business environment.
Thin Clients Defined
A thin client is essentially a stripped down computer in a client-server network which depends on centralized servers for processing and data storage activities. Often, the only software that is on the thin client is a thin OS like Windows CE or just a web browser used for generating the user interface. A remote desktop application is used for accessing the server across the network. The majority of the processing and storage functions are no longer on the client. The servers will be doing almost all of the heavy lifting.
Thin client technology originally started out as text based “dumb terminals.” From there the evolution of the client server architecture advanced to “graphical terminals,” then the popular X-Terminals of the 1990′s. Soon after that, Microsoft and Citrix came out with WinFrame which used Microsoft Windows NT v3.51 to allow multiple users to run applications from the same server. Later, Microsoft released a special version of NT 4.0, the Terminal Server Edition, or TSE.
Client server architecture never quite caught on though. Much of the hesitation to adopt the technology was related to falling cost of PC hardware and the markets greater familiarity with tried and true PCs. Still the technology continues to advance and mature.
There are three main components to thin client architecture:
1) A multi-user server Operating System which allows many users to log onto and work concurrently using applications accessible in protected sessions or “sandboxes.”
2) A thin client which may or may not have an onboard thin OS is used to connect to the server over the network. Some thin clients may only have a flash-memory based web browser installed. A thin client may not have any software installed and these are called “zero clients.”
3) A network protocol such as ICA or RDP creates the communication efficiency of thin clients by compressing the data and only using the minimum network resources needed. For the most part only keystrokes and screen refreshes pass over the network drastically reducing the amount of bandwidth necessary.