How to organize a terminal server on Linux?

Question

linux

Greetings uv. admins.
The matter is as follows, there is a server mat. Supermicro X9SL-F processor Intel Xeon E5-2609 2.4 GHz, RAM 32Gb, 2 hard drives 2TB each (and there are 2 more 1TB each). workstations ~20. The gateway is placed on a separate PC, a ready-made solution from Ideco (dns / proxy / shaper / antivirus / IP authorization / filter) Ip addresses are static. It is possible to install a file server on a separate machine.
Employees don’t want to work with Linux systems (You see, they don’t like Libre office because it’s different! And there are no disks!) In their opinion, they have weak machines (medium conf. DualCore E5500 Ozu2Gb), they don’t listen to me, they say it’s not about Windows , which has been standing for five years, but in pc. Because it is problematic to ask for a new server from them, but if you save money, you can upgrade the server.
I would like to raise a terminal server based on Debian/Ubuntu (firebird or sql server and AIS "Delo" + Teamspeak chat server will still hang) and connect workstations in thick client mode. And the actual question is how to give them a Windows 10 guest operating system from the terminal to Linux, is this possible, and will the server pull it. Maybe someone will throw instructions for the basic configuration of the server and clients, or briefly describe how to set up clients, there are enough manuals for setting up the server in conjunction with a thin client, but not with a thick one. in principle, it is possible in thin client mode, but they do not know how to close tabs in the browser and documents, it is easier to open 20 tabs! Yes, and another problem is that 2 users have work with public procurement, i.e. need local USB ports to install keys, Soft for all Office, Browser.

Answer 1

You are confusing terminal access and virtual machines.
On Linux, you can only provide terminal access to Linux (ssh, VNC). ssh - only the console, VNC - slow, never used it for users, I think they will not be happy. Although on a local network, it may work fine.
On a hypervisor under Linux, you can raise any OS as a VM and distribute access to it. Raise the required number of Windows VMs, connect to them via RDP.
A server with a hypervisor should not be used for other purposes (SQL, Business, ...) - the performance of the VM and other services will decrease.
By the way: does Delo work on Linux? As far as I remember, there is only Windows, because. .Net/IIS/MSSQL.
Will you also lift it on a virtual machine?
It would be more convenient for you to set up a Windows Server as a terminal server and use RDP to connect clients. But Windows Server costs money and licenses for terminal connection are also not free.
If the server is powerful enough, and there are relatively few simultaneously working clients and they have "easy" tasks, then additional functionality can be added to the server.
If you buy an iron server, I recommend that you immediately include Windows Server and licenses for terminal connection in the kit. So it can be easier to smuggle the purchase of the necessary software - along with iron, which cannot be dispensed with.
At the expense of forwarding USB ports with encryption keys - there may be problems. Only the option with Windows Server + RDP + local key server USB port will guarantee performance. But often, for various reasons, it is not possible to use server ports. You must first test the configuration on which you stop.

Answer 2

If the organization is budgetary, let everyone line up. Jokes are jokes, or you can give them this entertaining reading:
How it all began - a question on a toaster with explanations , no "domains", "offices", "windows" ... As they did in one office where I worked with those who did not like LO: "We are ready to install Microsoft Office for you immediately after you purchase it and provide it to technical support license key"
Without hacking Windows (file substitution), it is impossible to get several connections to winX (and any client Windows) - for a budget organization, I think it is an essential point.
You can get the possibility of parallel RDP sessions by installing Windows Server and a terminal license server, but this is, firstly, very expensive, and secondly, see the points above.