Primary Computing Models
- Non-administered Desktop: Here users have their own desktop system. Users/System Administrators conduct each principles individually together with premise and upgradation of software and Os.
- Administered Desktop: Using this model the principles Administrators can install and conduct applications on users' desktops remotely from a centralized remote location.
- Thin client/Server-based: In this model, processing takes place on one or more centralized servers. Users can way these applications locally and remotely, using a accepted browser, wireless device, desktop device, or thin client device.
Basic Categories of Thin Clients
1. Basic
2. Robust
3. Flexible
4. Mobile
5. Legacy
Basic Thin Clients
- Provides server-based computing
- Can run remote protocols of Microsoft/Citrix/etc on a centrally managed server to remotely display the user's desktop which is running on the server.
Robust Thin Clients
- Provides all the functionalities of the basic thin client along with a browsing terminal, which give way to the web or web-applications.
Flexible Thin Clients
- Provides all the functionalities of the basic thin client and robust client along with the quality to run applications locally.
Basic Forms of Thin Clients:
1. Standalone
2. Wireless
Out of these two, Standalone machines dominate. There are also new more mighty types of thin clients that offer some onboard memory and faster processing. Wireless allows personel machines to be mobile within the predefined workspace.
Advantages of Thin Clients
1. Total cost of proprietary (Tco)
2. Efficient and easy administration
3. Easy application deployments
4. Security
5. Efficient utilization of server resources
6. Thin client Lifecycle is longer (7-10 years)
Disadvantages of Thin Clients
The major disadvantage is that the thin client setup is not for heavy processing applications; only light-weight applications can be run on thin clients. For example, clubs that use high-performance applications like Cad, Cam, multimedia applications, etc, will do better with a full Pc-based system.
Thin Client Network
The network server that uses thin client devices should be robust, modular, with heavy processing power, and itsybitsy fault tolerance. In expanding to thin client devices that can sit on the desktop, server-based computing requires four elements:
1. An operating principles
2. Efficient network protocol
3. Client supervision software
4. Centralized application
Thin Client Network Protocols
The most generally used protocols are Ica (Citrix), Rdp (Microsoft), and X (Linux/Unix). Microsoft's protocol Rdp allows use of Win Terminals.
Thin Client Booting
There are two-ways straight through which a thin client can connect to the server. They are:
1. Thin clients may boot whether directly from the server and then connect to it or
2. Boot up from locally installed mini-disk and then connect to the server.
After connecting to the server, log in screen of the operating principles running on the server is displayed to the user.
Applications Deployable on Thin Client Server
Light-weight application which does not wish much processing power can be deployed on thin clients. Heavy processing applications like Maya, 3D Max, etc, can not be deployed on thin clients. You cannot deploy any application at thin client's end because there is no storehouse device/ Cpu at the client's end. Anyone you want to deploy, you can do that only on the server.
Thin Clients & Remote Offices
Internet connection, a router, and a hub related to the main data town enables remote offices to way the same network services, databases, and applications as they do at the corporate headquarters. Because thin clients do not need expensive network equipment, configuration, and support, their remote offices can be setup within hours.
Security
If all documents and files of all users are stored on the same server and on the same storehouse device, can one user way or read the files of other user -- No
- To way others' folders, the principles Administrator should give users extra permission; otherwise it is not inherent to way them.
- To way each others folders the server should have an Ntfs file storehouse system; with the accepted Fat32 it is not possible.
Thin clients vs. Particular server
The estimate of thin clients that a Particular server can hold depends on
- The server hardware configuration
- The programs/applications that are installed on that Particular server.
Using Load balancing technology with added servers prevents any Particular server from reaching significant levels.
Benefits of Using Thin Clients
1. Flexibility
2. Functionality
3. Performance
4. Customizability
Thin client technology was patronized and implemented by small-to-mid sized clubs during dotcom burst to sacrifice their It costs.
Thin Clients
