Terminal Office: Linux vs Windows - holy war: Part I
Preamble: There are typical office, for 15 local users + 5 remote, the range of tasks is simple: 1C + Office + Internet + Mail + Print. The task is to make a sustainable and inexpensive (because the crisis in the yard) solution.
Actually, there are only 2 solutions: Terminal server on Windows || Terminal server on Linux. Standalone PC we do not consider, because This is not a solution, but a hemorrhoid.
We will immediately determine the hardware for the terminal server: CPU 2 Quad Xeon 5405, 6Gb RAM, RAID 1 SATA 1 Tb (I know that is bad, but I don’t have money for SAS, the more so that the database is a separate server). Why such iron is a task to parallel well, the more nuclei, the better. In memory of 20 users * 200-250 MB (1C and the office love it) + system. Agreeing that Windows / Linux setup / support costs the same
')
With a terminal server under Windows - everything is clear, there are no options (do not offer citrix, see the preamble). The only question is the cost, because we need a lot of memory, then standart edition x32 does not fit, we will have to take 64 bits. At cost, it turns out about:
* 26.000 rub. for Windows Server R2 Standart x64 2003 with 5 CAL licenses
* 17.000 rub. for 15 client licenses (CAL, good thing will not be called feces)
* 70.000 rub. for 20 licenses for a terminal server (TS User CAL)
TOTAL: only for the OS and the ability to access a bare server, without any software - 113.000 rubles., Much more than the cost of the server itself.
The cost of Linux = the cost of the disc on which it is written, but the client part of 1C does not work under Linux, you must install WINE @ Etersoft Network for 5600 rubles.
TOTAL: OS and software to run business applications 5600 rubles.
A few words about WINE @ Etersoft ... This is not a Windows emulator, but provides WinAPI for applications. I used to think it was a “crooked share”, but the guys showed enviable progress and it really works, that is, it allows you to run a number of applications. Checked on yourself.
But the choice of terminal technologies under * NIX is wider than under Windows, you have to choose:
* X Window System - a classic of the genre. For those who are not familiar with terminology: X Server is where the picture is drawn, i.e. the client, and the X Client is where the application runs, i.e. server. For a home PC, both the server and the client work on the same machine, but nothing prevents them from working on different machines as was originally incorporated into the concept of the X Window System. The advantages of this solution: the minimum settings of the server and the client, everything is already in almost any distribution. Cons: does not save the user session in the event of dying client machine / connection failure; likes a wide band, it’s not comfortable to work via the Internet - only in the local network.
* X Window + Nomad. In OpenSuSE 11.1, a delicious Nomad chip appeared, which is a proxy for X11, and allows you to save sessions and drive remotely heavy applications, such as compiz desktop effects. Moreover, Nomad allows you to connect to the X-itself with a standard Windows rdp client.
* VNC - both the server and the client can work both on Linux and on Windows, is good for remote control, as a replacement for RAdmin, but the screen drawing is rather slow, and this will annoy users. But not exacting to the strip.
* NX Nomachine is a strongly modified X-protocol that, on the one hand, allows you to work on thin lines, and on the other hand, it allows you to save the session on the server. Very similar to X + Nomad. In this case, the client is authorized on the server via ssh. To work you need a special client. The open and free version of the server is called FreeNX.
* XRDP - open version of RDP for Linux, client, or rdesktop or standard Windows client. Uses server side VNC as a backend.
And all of the above is free!
About setting up the actual terminal server under Linux and clients for it, in the second part.
ps transferred to Linux for all
ws okhabrakatil
Actually, there are only 2 solutions: Terminal server on Windows || Terminal server on Linux. Standalone PC we do not consider, because This is not a solution, but a hemorrhoid.
We will immediately determine the hardware for the terminal server: CPU 2 Quad Xeon 5405, 6Gb RAM, RAID 1 SATA 1 Tb (I know that is bad, but I don’t have money for SAS, the more so that the database is a separate server). Why such iron is a task to parallel well, the more nuclei, the better. In memory of 20 users * 200-250 MB (1C and the office love it) + system. Agreeing that Windows / Linux setup / support costs the same
')
With a terminal server under Windows - everything is clear, there are no options (do not offer citrix, see the preamble). The only question is the cost, because we need a lot of memory, then standart edition x32 does not fit, we will have to take 64 bits. At cost, it turns out about:
* 26.000 rub. for Windows Server R2 Standart x64 2003 with 5 CAL licenses
* 17.000 rub. for 15 client licenses (CAL, good thing will not be called feces)
* 70.000 rub. for 20 licenses for a terminal server (TS User CAL)
TOTAL: only for the OS and the ability to access a bare server, without any software - 113.000 rubles., Much more than the cost of the server itself.
The cost of Linux = the cost of the disc on which it is written, but the client part of 1C does not work under Linux, you must install WINE @ Etersoft Network for 5600 rubles.
TOTAL: OS and software to run business applications 5600 rubles.
A few words about WINE @ Etersoft ... This is not a Windows emulator, but provides WinAPI for applications. I used to think it was a “crooked share”, but the guys showed enviable progress and it really works, that is, it allows you to run a number of applications. Checked on yourself.
But the choice of terminal technologies under * NIX is wider than under Windows, you have to choose:
* X Window System - a classic of the genre. For those who are not familiar with terminology: X Server is where the picture is drawn, i.e. the client, and the X Client is where the application runs, i.e. server. For a home PC, both the server and the client work on the same machine, but nothing prevents them from working on different machines as was originally incorporated into the concept of the X Window System. The advantages of this solution: the minimum settings of the server and the client, everything is already in almost any distribution. Cons: does not save the user session in the event of dying client machine / connection failure; likes a wide band, it’s not comfortable to work via the Internet - only in the local network.
* X Window + Nomad. In OpenSuSE 11.1, a delicious Nomad chip appeared, which is a proxy for X11, and allows you to save sessions and drive remotely heavy applications, such as compiz desktop effects. Moreover, Nomad allows you to connect to the X-itself with a standard Windows rdp client.
* VNC - both the server and the client can work both on Linux and on Windows, is good for remote control, as a replacement for RAdmin, but the screen drawing is rather slow, and this will annoy users. But not exacting to the strip.
* NX Nomachine is a strongly modified X-protocol that, on the one hand, allows you to work on thin lines, and on the other hand, it allows you to save the session on the server. Very similar to X + Nomad. In this case, the client is authorized on the server via ssh. To work you need a special client. The open and free version of the server is called FreeNX.
* XRDP - open version of RDP for Linux, client, or rdesktop or standard Windows client. Uses server side VNC as a backend.
And all of the above is free!
About setting up the actual terminal server under Linux and clients for it, in the second part.
ps transferred to Linux for all
ws okhabrakatil
Source: https://habr.com/ru/post/47999/
All Articles