

I am also assuming that this a medical practice though the same analysis might be appropriate in other type such as engineering consultancy.I assume that your Internet speed is a type and should be 1.6Mbits/s up and 0.8 down (that is one less zero).Robert, just a few points, some of clarification: He can switch back and forth between his windows and linux environment.

In case he needs to run a windows program, he starts the virtual machine and runs the windows program in the Windows XP guest. How can this be solved in a thin client/terminal server environment?Ī user in the external practice works on his thin client with his linux programs. five thin clients should be able to run their windows software simultaneously). seven simultaneous thin client connections on the terminal server, of which max. The users there need access to the windows programs as well, so they will need access to some kind of virtual machine (there will be max.
Nomachine as terminal server how to#
The problem is how to solve the virtualization issue on the thin clients in the external practice.
Nomachine as terminal server install#
Since we have a quite slow internet connection on both locations (16000 down / 800 up) we will install a terminal server (LTSP with freeNX or NoMachine NX) in the main practice and Linux thin clients in the external practice. Now, the external practice should be connected to the network of the main practice. So, if needed, we start a virtual machine on the fat clients with windows XP as guest, so we can use these programs. Our main software is linux-based, just a few specialised programs run on windows only. All clients there are fat clients with linux as OS. The main practice runs an homogeneous linux network with a central practice server which acts as file/db/print/authentification server. We need to connect an external practice to our main practice. This is my first post here, so please bear with me!
