Terminal servers: description, characteristics, settings

Today there is a fairly limited number of users who know what terminal servers are. Quite frankly, it would be worthwhile to ask ourselves this question, since from its solution it is possible to derive a sufficiently large benefit in terms of increasing the computing power of your own computer terminal.

What are "terminal servers"?

First, let's see what really constitutes the concept of terminal servers. This designation is derived from the English phrase "terminal servers". In the interpretation, we are interested in the first word. It is translated not only as "terminal", in fact it is "temporary".

Proceeding from this, it is easy to understand that terminal servers are something like a single resource (central server) with connected user machines that assess their capabilities in terms of computing power and, in the case of remote connection, use them to perform tasks, Delivered by the user, performing external control of all computer terminals.

How does this system work?

Actually, the scheme itself is quite simple. The matter is that users of the terminal server are limited only by the number of machines to which the central hardware is currently accessing.

But after all physically remote user directly with machines in a local network or on the Internet does not work. On the contrary, all tasks are redirected to the system part, and it is not important whether the appropriate software for processing incoming information is installed on any local computer. Here the price of the question is only "hardware", more precisely, the processor and RAM, which can process the data stream, for example, in the calculation of floating point values. And this process, I must say, is quite laborious. For example, the processing of graphics in modern computer games is based on this.

But we digress. Returning to the topic: "What are terminal servers", one more important fact can be noted: since the connection is temporary, the resources of computer terminals are used only at the moment of active connection with the corresponding statement of the task.

Restrictions in work

Unfortunately, even on Windows systems, the terminal server has a number of advantages as well as a number of shortcomings when it is used. This is not insured by any "operating system", known to date.

But if we talk specifically about Windows-terminals, we can note the fact that, contrary to the user's restrictions installed in the system itself, Windows, as they say, is always in touch. Feedback from users and system administrators say exactly that. If you use the computational capabilities of the CPU or when you load RAM, it will not even know that its hardware is being used for some other tasks. The only way to get rid of this is the usual disconnection from the network.

But it is worth considering that terminal servers in their work are similar to the same peer-to-peer networks. In other words, if your resources are used by someone else, no less, and you can use the resources of another computer on the network. But only not directly, namely through a server that provides such capabilities.

Naturally, when performing complex computing tasks, this will be required. But, I think, besides the developers of application software or designers, such possibilities of the system are unlikely to be used by anyone.

Network Connections and Sharing

It goes without saying that when connecting to a local computer terminal, you need to share its components. No no! This is not related to the so-called "sharing" of folders and files. It is enough that the computer or laptop is connected to one intranet through a direct cable connection or when accessing via Wi-Fi.

With the connection to "local" everything is simple. The computer is visible in the network at the user level, and it can be used as a means for data processing. In the case of Wi-Fi, a computer or laptop can also be seen, and performing a specific task will be forwarded to other machines on the network. In turn, depending on the level of complexity, they will be redirected either to "iron" or to software components. If someone does not understand, in the simplest version it looks like this: you start the executable task, and the solution is processed not by your computer (although it takes it directly), but by neighboring (remote) terminals that are with you on the same network.

Benefits

Of course, the fact that you can easily use the computing capabilities of computer systems in a network with a higher configuration is naturally a plus.

In addition, it is worth noting the high stability in operation, easily configurable parameters (even without using Windows Server 2012, the terminal server works also on non-server OSs such as Windows XP or 7), unlimited number of computers on the network, simple installation and administration procedures, and Extremely low price of the server part of the system.

disadvantages

Some of the shortcomings can be attributed mainly to the fact that sometimes the system does not cope with tasks related, for example, with applications like AutoCAD.

This heavy-weight program in terms of setting and executing tasks must correspond not only to the local computer on which it is running, but also to network terminals. If they do not meet the minimum requirements of the software package, no matter how hard you try, nothing good will come of it: the entire load will be concentrated on the local computer or laptop, and when distributing tasks other systems can simply "boost" due to inadequate load on system resources.

Windows Server Terminal Server: example of configuration in Windows XP

Now a few words about the setting. Few people know that setting up a terminal server in the same "Ippishka" is quite simple.

First, you can simply replace the source file that is responsible for connecting via RDP. On the other hand, this is not always convenient, and you can use the option that assumes the launch of the TS Free utility. You need to unzip the archive, then run the BAT-file (the termsrv.dll companion library is in the archive). If you receive a warning about changing the configuration file, you can ignore it. Then we reboot the system in safe mode and use the properties of the computer, where we select the parameters of the remote session. In this tab, you need to pay attention to the point concerning allowing remote access to this computer, and then go to the administration section in the standard "Control Panel".

Here you will need to find the services section and start stopping the terminal components. After that, we look for the directory on the path C: \ Windows \ System32 \ dllcache, then copy the termsrv.bak file from the unpacked archive with TS Free (from the System32 folder the same file should be deleted).

Now we go to the Registry Editor (regedit in the "Run" menu) and look for the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerLicensing Core branch, and then create a new DWORD parameter with the value "EnableConcurrentSessions" = dword: 00000001 or, simply speaking, one. Now we call the Group Policy client (gpedit.msc) and find the Terminal Services section in the computer configuration (Administration / Templates), where the maximum possible number is assigned in the restriction of possible connections (for example, 99999). Next, change the parameter "Enabled" to "Enabled" with the specified value and overload the system. Now on the local terminal it will be possible to work remotely, using all its physical abilities.

General recommendations for use in "Enterprise: 1C"

Terminal server "1C" is configured quite simply. At the same time, you do not need to have any extensive knowledge of programming. Even the sysadmins, leaving their feedback and recommendations for improving the system, say that the setting is so simple that even an absolutely unprepared person will cope with it.

You only need to install the required part of the software on the server, then repeat the procedure, but on the client machines with the installation of the client, not the server part, after which the server should specify the number of users with access rights (possibly limited), bound to each specific Terminal. After that, the program will be launched from the central server, and the user will only have to enter the login and password set by the network administrator.

Conclusion

As you can see, setting up a terminal server requires some skills, and an ordinary user is unlikely to encounter this. Nevertheless, sometimes such knowledge can be useful in terms of what, perhaps, when installing enough specific applications the power of one computer may not be enough. So why not use a tool that is already supported by almost all operating systems?