Today there is a fairly limited circle of users who know what terminal servers are. Frankly, it would be worthwhile to study this issue, since from its solution it is possible to extract quite a large benefit in terms of increasing the computing power of its own computer terminal.
What are terminal servers?
First, let's see what the concept of terminal servers actually is. 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”.
Based on this, it is easy to understand that terminal servers are something like a single resource (central server) with user machines connected to it, which evaluates their capabilities in terms of computational ability and, in the case of a remote connection, uses them to perform tasks, set by the user, carrying out external control of all computer terminals.
How does this system work?
Actually, the scheme of work itself is quite simple. The fact is that terminal server users are limited only by the number of machines that are currently being accessed through the central hardware.
But a physically remote user does not work directly with machines on a local network or on the Internet. On the contrary, all tasks are redirected to the system part, and it doesn’t matter if the appropriate software for processing incoming information is installed on some local computer. Here, the price of the question is only hardware, or rather, the processor and RAM that can process the data stream, for example, when calculating floating point values. And this process, I must say, is quite laborious. For example, graphics processing in modern computer games is based on this.
But we were distracted. 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 time of an active connection with the corresponding statement of the problem.
Work restrictions
Unfortunately, even in Windows systems, a terminal server, when used, has both a number of advantages and a number of disadvantages. Not a single OS is known for this, known today.
But if we talk specifically about Windows-terminals, we can note the fact that, contrary to user prohibitions installed in the system itself, Windows, as they say, is always in touch. User reviews and system administrators say exactly that. When using the computing capabilities of the central processor or when loading on the RAM, he will not even know that his hardware is used for some extraneous tasks. The only way to get rid of this is to simply disconnect 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 someone else uses your resources, you can no less use the resources of another computer on the network. But not directly, but through a server that provides such capabilities.
Naturally, when performing complex computational tasks, this will be required. But, it seems, besides application developers or designers, hardly anyone will use such system capabilities.
Network Connections and Sharing
It goes without saying that when connecting to a local computer terminal, it is necessary to establish shared access to 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 the same intranet via direct cable connection or when accessing via Wi-Fi.
With the connection on the "LAN" everything is simple. The computer is visible on the network at the user level, and it can be used as a means for processing data. In the case of Wi-Fi, a computer or laptop can also be seen, and the execution of a specific task will be redirected to other machines on the network. In turn, depending on the level of complexity, they will be redirected to either hardware or software components. If someone does not understand, in the simplest version it looks like this: you run an executable task, and the solution is processed not by your computer (although it takes a direct part in this), but by neighboring (remote) terminals located on the same network with you.
Benefits
Of course, the fact that it is quite easy to use the computing capabilities of computer systems on a network with a higher configuration is, of course, a plus.
In addition, it is worth noting rather high stability in operation, easily customizable parameters (even without using Windows Server 2012 the terminal server does not work on server OSs like Windows XP or 7), an unlimited number of computers on the network, the simplest installation and administration procedures, as well as extremely low price of the server side of the system.
disadvantages
Some of the shortcomings should be attributed mainly to the fact that sometimes the system does not cope with tasks related, for example, with applications like AutoCAD.
In terms of setting and executing tasks, this heavy-weight program 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 you try, nothing good will come of it: the entire load will be concentrated on the local computer or laptop, and when distributing tasks the rest of the systems can simply “fly out” due to inadequate load on system resources.
Windows Server Terminal Server: Configuration Example in Windows XP
Now a few words about customization. Few people know that setting up a terminal server in the same "list" 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, and then run the BAT file (the accompanying library termsrv.dll is in the archive). If a warning message appears about replacing the configuration file, you can ignore it. Next, 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 item regarding the permission of remote access to this computer, and then in the standard "Control Panel" go to the administration section.
Here you will need to find the services section and first stop the terminal components. After that, look for the directory along the path C: \ Windows \ System32 \ dllcache, after which we copy the termsrv.bak file from the previously unpacked archive with TS Free there (you need to delete the same file from the System32 folder).
Now we go to the registry editor (regedit in the Run menu) and look for the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerLicensing Core branch, then create a new DWORD parameter with the value "EnableConcurrentSessions" = dword: 00000001 or, simply put, one. Now we call the Group Policy client (gpedit.msc) and find the terminal services section in the computer configuration (Administration / Templates), where in the restriction position of possible connections, specify the maximum possible number (for example, 99999). Next, change the “Enabled” parameter to “Allowed” with the specified value and reboot the system. Now it will be possible to work remotely on the local terminal using all its physical abilities.
General recommendations for use in "Enterprise: 1C"
The 1C terminal server is configured quite simply. At the same time, you do not need to have any extensive programming knowledge. Even system administrators, leaving their feedback and recommendations for improving the system, say that the setup is so simple that even a completely unprepared person can handle it.
All that is required is to install the required part of the software on the server, then repeat the procedure, but already on the client machines with the installation of the client rather than the server part, and then on the server set the number of users who have access rights (possibly limited) with reference to each specific to the 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 the fact that, perhaps, when installing sufficiently 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?