Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Thin client
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==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=== [[Image:Gigabyte TA7.JPG|thumb|upright|TA7 thin client by [[Gigabyte Technology|Gigabyte]]]] 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 Pi]]s.<ref name="Eric Brown">{{cite web |last1=Brown |first1=Eric |title=Thin Client Market Embraces Raspberry Pi |url=https://www.linux.com/news/thin-client-market-embraces-raspberry-pi/ |website=Linux.com |date=26 May 2017 |access-date=25 July 2022}}</ref> Since thin clients consist of fewer hardware components than a traditional desktop PC, they can operate in more [[IP code|hostile environment]]s. 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 [[VGPU|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. ===Limitations=== To achieve such simplicity, thin clients sometimes lag behind desktop PCs in terms of extensibility. For example, if a local software utility or set of device drivers are needed in order to support a locally attached peripheral device (e.g. printer, scanner, [[biometric security device]]), the thin client operating system may lack the resources needed to fully integrate the required dependencies (although dependencies can sometimes be added if they can be identified). Modern thin clients address this limitation via port mapping or USB redirection software. However, these methods cannot address all scenarios. Therefore, it is good practice to perform validation tests of locally attached peripherals in advance to ensure compatibility. Further, in large distributed desktop environments, printers are often networked, negating the need for device drivers on every desktop. While running local productivity applications goes beyond the normal scope of a thin client, it is sometimes needed in rare use cases. License restrictions that apply to thin clients can sometimes prevent them from supporting these applications. Local storage constraints may also limit the space required to install large applications or application suites. It is also important to acknowledge that network bandwidth and performance is more critical in any type of cloud-based computing model. IT organizations must ensure that their network can accommodate the number of users that they need to serve. If demand for bandwidth exceeds network limits, it could result in a major loss of end user productivity. A similar risk exists inside the data center. Servers must be sized correctly in order to deliver adequate performance to end users. In a cloud-based computing model, the servers can also represent a single point of failure risk. If a server fails, end users lose access to all of the resources supported by that server. This risk can be mitigated by building redundancies, fail-over processes, backups, and [[Load balancing (computing)|load balancing]] utilities into the system. Redundancy provides reliable host availability but it can add cost to smaller user populations that lack scale. ===Providers=== Popular providers of thin clients include Chip PC Technologies, [[Dell]] (acquired [[Wyse]] Technology in 2012), [[Hewlett-Packard|HP]], [[ClearCube]], [[IGEL Technology]], [[LG]], [[NComputing]], Stratodesk, [[Samsung Electronics]], ThinClient Direct, and ZeeTim.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)