To consider (if you enable the session persistence) this setting must be applied on server.cfg on both NX Terminal Servers: EnablePersistentSession all Here is the main guide to setup the cluster from the NX Team. In this scenario, because we had enabled the session persistence we were able to recover our previous session with all the applications opened. It will take sometime to do it (less than a minute or the time you setup in the cluster options) and a new session will be established against our Secondary Server. When you shutdown, reboot or for some reason your primary server (where your clients are connected in first place) dies, the NX Client will automatically reconnect to the secondary server. A computer/laptop/RaspberryPi that acts as client.A remote desktop (were the client will be connected and will start a graphical interface).Those nodes are balanced automatically by the NX Terminal Servers (default is round robin).Several Nodes were the session of the clients will be created.The NX Clients will be connected to the T.S, in this model you aren’t able to connect to the nodes directly (there are other ways of configuring NoMachine to allow this but not in cluster mode.).Two terminal servers acting as a cluster (One Primary and one Secondary).NoMachine Terminal Server (cluster and multinode environment)īasically your remote desktop client will be «NX CLIENT» that can be installed in both, Linux or Windows. In this document I leave the configuration of the product, administration commands and knowledge I’ve acquired in order to make it work. A month ago I was required to setup NoMachine (the paid version of FreeNX) also known as «!M or NX».
There are some products as x2go and FreeNX (which isn’t longer available) that were designed to provide Remote Desktops to users.
0 kommentar(er)
