Starting from v9, the upgrade procedure doesn't update the current keys in server.cfg, node.cfg and web.cfg files when they are renamed. NoMachine applications will be still able to rely on the old key name to preserve compatibility.

New keys are added by the upgrade procedure.

Default configuration files for v9 are added to the installation with post .sample, e.g. server.cfg.sample. Administrators can compare the .sample file with their current .cfg file to notice differences.

Changes to configuration files in v9:

1) The value 'classic' for the AcceptedWebMethods key in server.cfg is renamed into 'mjpeg'.
2) Key 'EnableNetworkBroadcast 1' in server.cfg is now  'EnableLocalNetworkBroadcast 1' (default is the same)
3) Key 'EnableDirectXSupport key 1' in node.cfg is now 'EnableHardwareAcceleration 1' (default is the same)
4) The PhysicalDesktopAcceptUsers and VirtualDesktopAcceptUsers keys is added to server.cfg.
5) The 'EnableNodeAuthentication 1' key is added to server.cfg.
6) The 'EnableCommunicationHub' key is added to server.cfg.
7) The 'ShowNotificationInfo' key is added to node.cfg

By means of PhysicalDesktopAcceptUsers and VirtualDesktopAcceptUsers keys in server.cfg, administrators can define which type of users (included guests) are allowed to authorize incoming connection requests, by default only the desktop owner can do it.

In v9, we have introduced a feature requiring users to confirm their right to access the node host by entering a password when connecting (usually this password is automatically provided by the player when the authentication os password-based). Disabling the EnableNodeAuthentication key in node.cfg reverts to the v8 behavior, where no password is required for connecting to the remote node. In case of problems to authenticate on the remote node, for troubleshooting, disable that key (EnableNodeAuthentication 0) and try to connect again.

The 'EnableCommunicationHub' key defines if the Cloud Server is the only communication hub for the NoMachine traffic, included NoMachine Network traffic. This corresponds to option 'Tunnel all the NoMachine network traffic through the server' in the UI -> Settings -> Server -> ports panel.