In computer networking, a thin client (sometimes called a slim client or lean client) is a simple, low-performance computer that has been optimized for remote desktop connections to a server-based computing environment. In some cases, they are also referred to as network computers or, in their simplest form, zero clients. The server performs most of the workload, including launching software applications, processing computations, and handling data storage. This contrasts with a rich client or a traditional personal computer—the former is designed for a client–server model but retains significant local processing power, while the latter performs most of its functions locally. Thin clients typically operate as part of a larger computing infrastructure—often involving a server farm or cloud-based system—where many clients share centralized resources. The server-side infrastructure may use application virtualization, hosted shared desktop (HSD), or desktop virtualization (VDI). This model forms a centralized cloud computing environment hosted in one or more data centers. Key advantages of centralization include:
Hardware resource optimization – shared infrastructure pools computing resources for maximum utilization. Reduced software maintenance – operating system updates and software patching can be deployed from a centralized location. Improved security – centralized data is easier to protect, monitor, and firewall; physical device loss does not compromise stored data. Thin client hardware typically supports common peripherals, such as keyboards, mice, computer monitors, audio jacks, and open USB ports (e.g., for printers, flash drives, webcams). Some models include legacy serial ports or parallel ports to support specialized equipment such as receipt printers or time-clocks. Thin client software commonly includes:
a minimal graphical user interface (GUI), cloud access agents (e.g., RDP, ICA, PCoIP), a lightweight web browser, terminal emulators (in some cases), and essential local utilities.
Characteristics
Architecture In using cloud-based architecture, the server takes on the processing load of several client sessions, acting as a host for each endpoint device. The client software is narrowly purposed and lightweight; therefore, only the host server or server farm needs to be secured, rather than securing software installed on every endpoint device (although thin clients may still require basic security and strong authentication to prevent unauthorized access). One of the combined benefits of using cloud architecture with thin client desktops is that critical IT assets are centralized for better utilization of resources. Unused memory, bussing lanes, and processor cores within an individual user session, for example, can be leveraged for other active user sessions. The simplicity of thin client hardware and software results in a very low total cost of ownership, but some of these initial savings can be offset by the need for a more robust cloud infrastructure required on the server side. An alternative to traditional server deployment which spreads out infrastructure costs over time is a cloud-based subscription model known as desktop as a service, which allows IT organizations to outsource the cloud infrastructure to a third party.
Simplicity
Thin client computing is known to simplify the desktop endpoints by reducing the client-side software footprint. With a lightweight, read-only operating system (OS), client-side setup and administration is greatly reduced. Cloud access is the primary role of a thin client which eliminates the need for a large suite of local user applications, data storage, and utilities. This architecture shifts most of the software execution burden from the endpoint to the data center. User assets are centralized for greater visibility. Data recovery and desktop repurposing tasks are also centralized for faster service and greater scalability.
Hardware While the server must be robust enough to handle several client sessions at once, thin client hardware requirements are minimal compared to that of a traditional PC laptop or desktop. Most thin clients have low-energy processors, flash storage, memory, and no moving parts. This reduces the cost, power consumption (heat, noise and vibrations), making them affordable to own and easy to replace or deploy. Numerous thin clients also use Raspberry Pis. Since thin clients consist of fewer hardware components than a traditional desktop PC, they can operate in more hostile environments. And because they typically don't store critical data locally, risk of theft is minimized because there is little or no user data to be compromised.
Graphics Modern thin clients have come a long way to meet the demands of today's graphical computing needs. New generations of low energy chipset and central processing unit (CPU) combinations improve processing power and graphical capabilities. To minimize latency of high resolution video sent across the network, some host software stacks leverage multimedia redirection (MMR) techniques to offload video rendering to the desktop device. Video codecs are often embedded on the thin client to support these various multimedia formats. Other host software stacks makes use of User Datagram Protocol (UDP) in order to accelerate fast changing pixel updates required by modern video content. Thin clients typically support local software agents capable of accepting and decoding UDP. Some of the more graphically intense use cases remain a challenge for thin clients. These use cases might include applications like photo editors, 3D drawing programs, and animation tools. This can be addressed at the host server using dedicated GPU cards, allocation of vGPUs (virtual GPU), workstation cards, and hardware acceleration cards. These solutions allow IT administrators to provide power-user performance where it is needed to a relatively generic endpoint device such as a thin client.
… excerpt ends here. Continue reading the full article.
