| Primary Computing Models | | | | 3. Client management software |
| - Non-administered Desktop: Here users have their | | | | 4. Centralized application |
| own desktop system. Users/System Administrators | | | | Thin Client Network Protocols |
| manage each system individually including installation | | | | The most commonly used protocols are ICA (Citrix), |
| and upgradation of software and OS. | | | | RDP (Microsoft), and X (Linux/Unix). Microsoft's |
| - Administered Desktop: Using this model the System | | | | protocol RDP allows use of Win Terminals. |
| Administrators can install and manage applications on | | | | Thin Client Booting |
| users' desktops remotely from a centralized remote | | | | There are two-ways through which a thin client can |
| location. | | | | connect to the server. They are: |
| - Thin client/Server-based: In this model, processing | | | | 1. Thin clients may boot either directly from the |
| takes place on one or more centralized servers. | | | | server and then connect to it or |
| Users can access these applications locally and | | | | 2. Boot up from locally installed mini-disk and then |
| remotely, using a standard browser, wireless device, | | | | connect to the server. |
| desktop device, or thin client device. | | | | After connecting to the server, log in screen of the |
| Basic Categories of Thin Clients | | | | operating system running on the server is displayed |
| 1. Basic | | | | to the user. |
| 2. Robust | | | | Applications Deployable on Thin Client Server |
| 3. Flexible | | | | Light-weight application which does not require much |
| 4. Mobile | | | | processing power can be deployed on thin clients. |
| 5. Legacy | | | | Heavy processing applications like Maya, 3D Max, etc, |
| Basic Thin Clients | | | | can not be deployed on thin clients. You cannot |
| - Provides server-based computing | | | | deploy any application at thin client's end because |
| - Can run remote protocols of Microsoft/Citrix/etc on | | | | there is no storage device/ CPU at the client's end. |
| a centrally managed server to remotely display the | | | | Whatever you want to deploy, you can do that only |
| user's desktop which is running on the server. | | | | on the server. |
| Robust Thin Clients | | | | Thin Clients & Remote Offices |
| - Provides all the functionalities of the basic thin client | | | | Internet connection, a router, and a hub connected |
| along with a browsing terminal, which give access to | | | | to the main data center enables remote offices to |
| the web or web-applications. | | | | access the same network services, databases, and |
| Flexible Thin Clients | | | | applications as they do at the corporate |
| - Provides all the functionalities of the basic thin client | | | | headquarters. Because thin clients do not need |
| and robust client along with the ability to run | | | | expensive network equipment, configuration, and |
| applications locally. | | | | support, their remote offices can be setup within |
| Basic Forms of Thin Clients: | | | | hours. |
| 1. Standalone | | | | Security |
| 2. Wireless | | | | If all documents and files of all users are stored on |
| Out of these two, Standalone machines dominate. | | | | the same server and on the same storage device, |
| There are also new more powerful types of thin | | | | can one user access or read the files of another user |
| clients that offer some onboard memory and faster | | | | -- No |
| processing. Wireless allows individual machines to be | | | | - To access others' folders, the System |
| mobile within the predefined workspace. | | | | Administrator should give users special permission; |
| Advantages of Thin Clients | | | | otherwise it is not possible to access them. |
| 1. Total cost of ownership (TCO) | | | | - To access each others folders the server should |
| 2. Efficient and easy administration | | | | have an NTFS file storage system; with the standard |
| 3. Easy application deployments | | | | FAT32 it is not possible. |
| 4. Security | | | | Thin clients vs. Single server |
| 5. Efficient utilization of server resources | | | | The number of thin clients that a single server can |
| 6. Thin client Lifecycle is longer (7-10 years) | | | | hold depends on |
| Disadvantages of Thin Clients | | | | - The server hardware configuration |
| The major disadvantage is that the thin client setup | | | | - The programs/applications that are installed on that |
| is not for heavy processing applications; only | | | | particular server. |
| light-weight applications can be run on thin clients. For | | | | Using Load balancing technology with additional |
| example, companies that use high-performance | | | | servers prevents any single server from reaching |
| applications like CAD, CAM, multimedia applications, | | | | critical levels. |
| etc, will do better with a full PC-based system. | | | | Benefits of Using Thin Clients |
| Thin Client Network | | | | 1. Flexibility |
| The network server that uses thin client devices | | | | 2. Functionality |
| should be robust, modular, with heavy processing | | | | 3. Performance |
| power, and little fault tolerance. In addition to thin | | | | 4. Customizability |
| client devices that can sit on the desktop, | | | | Thin client technology was patronized and |
| server-based computing requires four elements: | | | | implemented by small-to-mid sized companies during |
| 1. An operating system | | | | dotcom burst to reduce their IT costs. |
| 2. Efficient network protocol | | | | |