Terminal servers: definition, basics, and advantages

Computers have become an integral part of daily life for businesses, and many companies now have their own, indispensable IT departments. Their most important tasks are not just installing software programs and creating e-mail accounts, but also ensuring that all devices are optimally integrated into the company network. For example, employees should be able to access the central file server, check the corporate e-mail account, or use company software from both a company PC and their mobile device. Users should also have as many options as possible in terms of operating systems (Windows, Linux, macOS, etc.). Although requirements may vary from company to company, terminal servers have proven to be a powerful tool in an IT department’s kit.

There are three necessary building blocks needed to create a terminal server:

1. Server hardware that supports a multi-user system
2. Network protocol for remote access
3. Client application for the terminal server

Like any server, a terminal server also needs the necessary hardware to fulfill its function properly. It is therefore important to ensure that sufficient computing power is available to host the individual applications and the server’s operating system. Processing performance is the most important element, and using multi-core processors is recommended. Work memory and disk space are equally important, with the requirements being heavily dependent on the resource intensity of managed applications. An additional factor is the number of terminal server clients that simultaneously access the offered terminal services.

The second protocol then lays the foundation for communication between terminal server and client. It establishes policies for data exchange to allow users to remotely access the terminal services. While the initial protocols, like the previously mentioned X11, only had to regulate establishing the connection, newer proxies like the Citrix Protocol ICA (Independent Computing Architecture) or the proprietary Microsoft Protocol Remote Desktop Protocol (RDP) also allow compression specifications, encryption, and the caching of transmitted data and information.

Finally, each device must install client software that allows users to connect to the terminal server over the remote protocol and use the applications provided. The software and hardware architecture is also often enhanced by a licensing server that manages the access licenses.

If software is made available through a terminal server, both the server and every accessing client must have the necessary licenses to use it. This plays an important role especially with proprietary programs, because they often require a license for the server itself and for each client. In this scenario, the licensing server will act as a central administrative entity for the various licenses that Microsoft require, such as Client Access Licenses (CAL) for example. There are two licensing models:

• Device license: When equipped with a device license, the device can be used by multiple users to access the terminal service. This model is ideal for situations where multiple users share a work PC, like a hotel reception.
• User license: If users need to access terminal server services from more than one device, users’ licenses are the best option. This means that just a single license is required even if a user accesses remote services from a work computer, as well as from a smartphone on the go, or a PC at home.  

After the initial connection is established, the licensing server forwards the desired licenses to the client. Each time they access it, they adjust it to determine that the device or user in question already has a valid license. Administrators should always be aware of how licensing works on the proprietary terminal server to optimise costs.

The previously mentioned license costs are one of the most important costs when it comes to running a terminal server. The amount depends on how many users are connected to the remote environment and use it simultaneously. Furthermore, which applications should be centralised plays a key role in whether proprietary products like a Windows operating system, or open source software like Linux distributions and LibreOffice, are more likely to be used. Next to the costs of the terminal services provided, the following expenses apply to terminal server operators:

• Hardware: As previously mentioned, there must be enough computing power to run the server. When it comes to a local hardware solution, redundancy must be ensured to be able to replace defective components as quickly as possible. 
  
  
• Maintenance and operation: The chosen hardware solution not only results in purchase but also maintenance costs. In addition, expenses for cabling, electricity etc. should be included in the budget.
  
  
• Application maintenance: The individual applications that are available to terminal server users must also be maintained regularly. Therefore, it is necessary to ensure that you update, make adjustments, or install new terminal services if necessary. 
  
  
• Backup and protection: Both the terminal services themselves as well as the individual databases should be secured in the best possible way. Protection software and backup solutions are therefore a must to be optimally prepared for technical problems (e.g. power outages) and unauthorised access.  
• Rights management: Funds should be set aside for the development of a comprehensive access concept (authentication, authorisation, etc.) to benefit in the long term from a well-considered and regulated rights allocation.

A terminal server is very beneficial to businesses as a central application management unit for a number of reasons. For example, administrators benefit from the considerable workload associated with network architecture being eased: all application software just needs to be installed once (on the server), which saves a lot of time and effort. This preference is also noticeable when the respective applications need to be maintained and updated. It is only necessary to install the terminal server client software on all devices that should allow remote access to the services provided. In addition, a central dashboard makes it easy to monitor the infrastructure of the network and all relevant user activities.

As previously mentioned, costs can be saved thanks to the specific terminal server licensing models. But the remote concept is also very cost-effective for other reasons: Since most of the processing and storage of data is done on the central server, expensive hardware does not have to be purchased for individual workstations. In certain scenarios, even a return to the original terminal server concept with clients without their own hard disk space is conceivable. In this instance, we are also talking about so-called thin clients (“slim clients”). These slimmed-down desktop setups also have the advantage of being very energy efficient and have a longer lifespan than ordinary workstations.

The great advantages of a terminal server include the ability to access the services provided (including personal data) with almost no restrictions. Users have the freedom to select their terminal and operating system. The chosen system only needs to support the respective terminal server client software and the protocol needed for communication. Remote access requires no physical connection between server and the client, so resources can be used from anywhere.

Centrally hosting and managing applications also has the advantage of providing less access to external users. Since the data does not leave the server environment, a comprehensive security plan can be created with little effort. If a client experiences an unforeseen incident (power failure, virus attack, hack, etc.), the program and user data stored on the terminal server is never compromised. Meanwhile, backup solutions and protection programs ensure its security.

The advantages listed make terminal servers a worthwhile investment for numerous companies. The prerequisite is, however, that the application requirements of different clients are not too different. Namely, if the terminals place too broad a range of demands on hardware and software, a client terminal server network tends to be impractical. In this case, the benefit of unified installation and maintenance cannot be realised, while dependency on central management still exists. However, this shows one of the few concrete disadvantages of the model: Terminal service users are automatically limited in their options (administration, etc.) and cannot use individual applications in the event of a server failure.

A second disadvantage is that a terminal server does not always support all standard software. If the applications that need to be centrally hosted are not compatible with the server, the remote model does not make much sense for a business. Similarly, the licensing models associated with the server and its services can similarly become exclusion criteria if they are not cost-effective for the specific requirements.