Follow Us.
Become a Fan! 
All Thin Clients rely on a small local Operating System (or O/S) to display a program's output, get input from the user, and handle any local communication requirements. This O/S can either be embedded in the Thin Client when it is manufactured, or it can be download from the server when the Thin Client is powered up. Booting a Thin Client from a server eliminates the need for local storage, which actually has two major benefits - it reduces the hardware cost of the Thin Client and simplifies client management. Currently only two companies have a network boot Thin Client offering - ACP and Wyse Technologies.
Thin Clients that store the Operating System locally (inside the Thin Client) also require local software to allow for configuration of the client. This typically involves starting up the Thin Client, setting the IP address (or pointing it to a DHCP server), and setting local parameters such as screen resolution etc. This is a process that must be repeated for each client installed. While not a laborious task for a single unit it becomes daunting when there are dozens of clients and exceedingly expensive when there are thousands of clients distributed across a large geographic area. By comparison, setting up a network boot Thin Client is simply a matter of plugging it in and turning it on.
Having a local O/S stored on the client also brings up the issue of client firmware updates. Over time, the local O/S will grow obsolete and need to be updated. Today most manufacturers allow you to 'flash' the O/S with updates, a process that is fraught with danger. If something goes wrong (and it often does) during the flash process the Thin Client will be rendered useless. The O/S becomes "scrambled eggs" and the unit will need to be serviced by the manufacturer. By contrast, the network boot provides a fresh copy of the O/S each time the user powers-up up their machine. If there is an update to the O/S it is simply loaded on the server and the next time the user logs on the Thin Client will get the latest Operating System. This means that Network Boot Thin Clients don't grow obsolete as fast as local boot units - pull a 2 year old unit off the shelf and when it boots it will have the same O/S as all the currently running Thin Clients.
With a local O/S like Windows CE, there can be subtle differences between the CE versions that are actually installed. And because of the way that each build of CE is selected as a subset of all of CE's components, different manufacturers will choose different CE components depending on their particular hardware. While many companies strive to only install the same model and version of hardware, it is almost impossible to achieve a homogeneous collection of products, and consequently slightly different versions of CE will exist on the same network. This makes it difficult to assure that upgraded applications will react the same way at each client. Fully testing the different versions of CE for application compatibility would require testing at each physical location. By contrast, a Network Boot Thin Client provides a uniform operating system to all clients that can be rigorously tested prior to initiating an application upgrade.
Using a Network Boot Thin Client also provides for more predictable operating costs. The cost of upgrading the WinCE O/S on all installed Thin Clients is difficult to measure, as several steps are required. First there is the cost of the Microsoft CE software upgrade, then the cost of additional testing, and finally the cost of deployment. And, more than likely, you'll have the cost of fixing some of the Thin Clients if there is a problem along the way. There are less points of failure in the Network Boot Model, and compatibility will be less of an issue because there won't be a dozen different versions of the WinCE O/S installed in the Thin Client hardware. A Network Boot Thin client doesn't require going through the flash process because a fresh copy of the O/S gets loaded every time the machine boots. And testing will take less time because all clients will be running the exact same O/S.
Many Thin Clients with local CE function as a small computer (very much a PDA) even when not connected to the Thin Client network. This makes it a useful item, and one that people might be inclined to steal. A local O/S also invites the introduction of viruses, as the unit can be brought up and 'tinkered with' anywhere, and viruses can be introduced into the client's O/S. For a Network Boot Thin Client, the operating system is stored on the server, which is typically kept in a secure location. This means that when a network boot Thin Client is removed from the Thin Client network there is no chance that it can even be booted.
When compared to standard PCs, Thin Clients are much less prone to failure because of the lack of moving parts. But if a unit is destroyed or damaged in some way, a network boot Thin Client can be replaced very simply by even the most computer illiterate user. Simply plug it in and turn it on, and the Thin Client will automatically configure itself. On the other hand a CE Thin Client will need to be told its username/password and the IP address of the terminal server (do you know your IP address?).
Interestingly enough, the entire process of loading the O/S at boot time takes only about 6 seconds over standard 10MB/sec Ethernet, which is considerably less time than it takes to even read the same size file out of a local Disk On Chip. This is because of the difficulties associated with current DOC technology, combined with the limited speed of processors that are typically found in Thin Clients.
The Network Boot Thin Client requires much less manpower to deploy and support. Using Thin Client auto-configuration for installation and the centralized management tools (which can be operated from a remote site) provides cost savings when you purchase, deploy and manage your computer infrastructure.
For more information on ACP Industrial Thin Client computers, please visit our web site at http://www.thinmanager.com
To sign up for the E-mail newsletter go here: ACP newsletter signup
For an archive of past newsletter articles go to: ACP Newsletter Archive
Copyright © Automation Control Products, Inc. All rights reserved.
