Source: https://www.nomachine.com/DT03O00129
Timestamp: 2019-04-26 08:47:33+00:00

Document:
This document provides an overview of new products and their features introduced with NoMachine v. 6.
Due to differences between version 6 and previous versions 5, the automatic updates via GUI from the NoMachine repositories have been disabled. Automatic updates are available only for NoMachine free and NoMachine Enterprise Client.
To upgrade from v. 4 (or v. 3.5.0) to v. 6 it's necessary to have previously upgraded to v.5.
To upgrade from v. 5 to v. 6, it is necessary to use the appropriate package downloaded from the Customer Area or provided by our Sales or Support Team. In some cases it's also necessary to replace license v. 5 with a v. 6 license.
To connect to NoMachine Cloud Server v. 6 it's necessary to use a NoMachine client v. 6.
The other NoMachine servers of version 6 accept connections from clients v. 5 and 4, but it's recommended to upgrade your client installations to benefit from all the new features sported by v. 6.
(*) The 'NoMachine login' authentication method in version 6 is no longer available.
To upgrade NoMachine installations, customers should use packages downloaded from their Customer Area at: https://www.nomachine.com/support#login or provided by the Sales Team.
II making a new installation.
To be compliant with MPEGLA royalty fees, downloads are limited to two for each license. The counter is reset every new release.
Please read carefully all the steps below before proceeding with the upgrade and do not hesitate to contact our Sales or Support Teams for any advice.
Support for web sessions is extended to all server types (except NoMachine free).
Starting from v. 6, Cloud Server assumes a different role with the purpose of federating multiple NoMachine servers or foreign servers (Unix-like hosts running unsupported OS) and providing a single point of access to these hosts.
The new Cloud Server is not intended to be used for creating user sessions on its host but to work as a 'gateway'.
Cloud Server CS Linux, Windows, Mac Single point of access to NoMachine multi-server subsystems and foreign hosts. Can be federated under a CS.
(*) Connections to physical desktop of this host are permitted to system administrators, NoMachine administrators and 'trusted' users and are mainly intended for administrative or remote assistance purposes.
(**) The Terminal Server Node doesn't accept direct connections to its host and must be used in conjunction with Enterprise Terminal Server. Enterprise Terminal Server does not accept connection requests to other NoMachine servers, only Terminal Server Nodes.
This table shows how server types and functionalities present in v. 5 are mapped to v. 6.
Customers are invited to check before downloading and installing that the package available in the customer area corresponds to their scenario. In some specific cases it will be necessary to contact the Sales Team to get the appropriate package v.6 and license.
used with ED Linux CS Download package from your Customer Area.
Mac CS Download the package from your Customer Area.
used with virtual desktops on its host or with Linux terminal server nodes Linux ETS Download the package from your Customer Area.
used as standalone servers Linux WS or TS Download WS or TS package from your Customer Area.
Upgrading the installed software requires the termination of all running sessions. In case of virtual desktops and custom sessions (available on Linux only), these sessions cannot be recovered later.
This is necessary for installing the new libraries and binaries. Processes already loaded in the system memory lock down the corresponding binaries, libraries that cannot be otherwise replaced.
The upgrade procedure implies a shutdown of the server and all services. They are automatically restarted once the upgrade procedure is completed.
All operations must be executed with administrative privileges: root or 'sudo' user on Linux and Mac, and as administrator on Windows.
I Send a broadcast message to all connected users to inform them about ongoing operations.
II If there are two servers in failover cluster mode: shutdown NoMachine server on the primary server and on the secondary server.
Note that in case of a multi-node environment, stopping the remote nodes before proceeding with the upgrade is not required.
Large environments often adopt specific configurations that are different from the default ones. The upgrade procedure automatically preserves the original configuration: it creates a backup of the original configuration files (server.cfg.backup and node.cfg.backup in 'etc' under the NoMachine installation directory) and carries their settings over to the new configuration files.
- Removing obsolete keys no longer used in the new version.
- Adding new configuration keys.
- Renaming existing configuration keys to fit new specifications.
In the case of upgrade from Cloud Server installations to v. 6, it's important to notice that the cloud.cfg and cloud.inc files will be no longer used. A backup of these files will be created and their settings moved respectively into server.cfg and htd.cfg.
This means, for example, that the upgrade will preserve all profile rules set and all nodes of the multinode environment, if any.
The following procedures apply to NoMachine installations v. 5.
Administrative rights are required for upgrading server-side installations.
Instructions for Linux are based on the command line, but it's also possible to execute them using the system's graphical package manager, as explained for Mac and Windows.
sudo /etc/NX/nxserver --broadcast "Your message here"
Step 1- Send a broadcast message to all connected users to inform them about the maintenance operations.
On the NoMachine server host, click on the !M icon in the system tray and then on 'Show the server status'. Open the 'Connected users' panel and right click on users to 'Send message'.
nxserver --broadcast "Your message here"
Step 2- Shutdown the NoMachine server.
On the NoMachine server host, click on the !M icon in the system tray and then on 'Show the server status'. Click on the 'Shutdown the server' button.
double-click on the icon of the executable file and follow the wizard to proceed with the installation.
On the NoMachine server host, click on the !M icon in the system tray and then on 'Show the server status'. In the server GUI access the Server preferences -> Updates panel. You can verify the version and license of your current installation.
I The package type to be used for upgrading the main server (CS or ES v. 5) is: Enterprise Terminal Server, ETS.
If the server was a CS, contact the Sales Team if you don't have yet an ETS license (server.lic and node.lic) and get it before proceeding.
II The package type to be used for upgrading the remote nodes is: Terminal Server Node , TSN.
Contact the Sales Team if you don't have yet a TSN license.
If you have two servers in failover cluster, shutdown also the secondary server.
Step 3- Upgrade each remote node.
Download the TSN package from your Customer Area and upgrade each node installation.
- replace the node.lic file.
- rename or remove the server.lic file (TSN requires only one license file, node.lic).
Step 4- Finally upgrade the main server installation.
Download the ETS package from your Customer Area and upgrade the server installation.
If the license v. 5 is for CS, replace the server.lic and node.lic files with ETS license files.
Step 5- If you have two servers in failover cluster, proceed to upgrade the second server and replace the licenses if necessary.
I The package type to be used for upgrading the main server (CS or ES v. 5) is: Cloud Server, CS.
If the server is ES, contact the Sales Team if you don't have yet a CS license v. 6 (server.lic and node.lic) and get it before proceeding.
II CS v. 6 is not intended for running sessions on its host, it works as a gateway to its child servers.
III Due to structural differences between the multi-host environment v. 5 and v. 6, it will be necessary to re-add all the remote host to the main server.
IV The package type to be used for upgrading the remote nodes is the same of the previous installation v. 5.
Download the proper package from your Customer Area and upgrade each node installation.
Replacing the license files (server.lic and node.lic) is not necessary.
Step 4- Upgrade the main server installation.
Download the CS package from your Customer Area and upgrade the server installation.
If the license v. 5 is for ES, replace the server.lic and node.lic files with CS license files.
This section deals with specific cases which require that you contact the Sales Team. Customers will receive the proper package suitable for their environment and the new license v. 6 necessary for the software.
I Upgrade the remote node(s) with the TSN package. Then replace the license v. 5 if the node was WS or TS: (i) rename or remove the old server.lic and (ii)replace node.lic with the new node.lic file for TSN.
Cloud Server version 5 is set-up in a multi-node environment with ED on the remote nodes. Besides upgrading nodes and server host, it will be necessary to add the ED server(s) to CS v.6. That's because Cloud Server v. 6 implements the new concept of multi-tier server architecture and works as single point of access to server subsystems. The multi-node environment v. 5 will therefore become a multi-server environment v.6.
I Upgrade the remote node(s) with ED v.6. Replacing licenses on the nodes is not necessary.
II Upgrade CS v. 5 to CS v.6. Replacing the license is not necessary.
III Add each ED host to CS by means of 'nxserver --serveradd HOST' command or via client v. 6 GUI.
II Upgrade ES to ETS. Replacing the ES license is not necessary since it's automatically mapped to ETS.
Enterprise Server v. 5 on Windows, Linux or Mac is set-up in a multi-node environment with ED as remote nodes. Besides upgrading nodes and server host, it will be necessary to add the ED server(s) to CS v.6. That's because Cloud Server v. 6 implements the new concept of multi-tier server architecture and works as single point of access to servers' subsystems. The multi-node environment v. 5 will therefore become a multi-server environment v.6.
I Upgrade the remote node(s) with ED v.6. Replacing license on the nodes(s) is not necessary.
For any other scenario not contemplated in this document, please contact the Sales Team or the Support Team.

References: v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v.