NoMachine Support

Your questions answered

Knowledge Base

Searching in: Documents
Filter the search results
Version:
Last update:
Searching in: Documents
ID: DT10R00170
Version: NoMachine 7
Added on: 2020-11-13
Last update: 2020-12-17
NoMachine Enterprise Client - Installation and Configuration Guide
Table of Contents
Introduction
1. NoMachine Enterprise Client Installation and Configuration Guide
1.1. About This Guide
How to set-up the Enterprise Client
2. Install the Enterprise Client
2.1. Prerequisites
2.2. Windows Installations (install, update, uninstall)
2.3. Mac Installations (install, update, uninstall)
2.4. Linux Installations (install, update, uninstall)
2.5. RPM Packages
2.6. DEB Packages
2.7. TAR.GZ Packages
Custom Settings
3. Personalizing Appearance and Behavior
3.1. The Settings UI
Connect to the Remote Computer
4. Initiating a Connection
4.1. Creating New Connections
4.2. Connecting and Run Physical or Virtual Desktop and Custom Sessions
4.3. Displaying the Remote Session on Your Computer
4.4. Closing Physical and Virtual Desktop and Custom Sessions
Facilities Inside the Session
5. NoMachine Menus and Others
5.1. The NoMachine Menu Panel
5.2. The NoMachine Monitor Menu
5.3. Blanking of the Physical Screen and Auto Lock Upon Disconnecting
5.4. Disabling Screen Sharing
5.5. Multi-Monitor Support
Enterprise Client's Administration (Advanced)
6. The Enterprise Client for NoMachine Administrators
6.1. Pre-configuring the Client to End-Users
6.2. Federating Servers Under a Cloud Server via UI
6.3. Adding Terminal Server Nodes to the Enterprise Terminal Server via UI


Introduction
1. NoMachine Enterprise Client Installation and Configuration Guide

Welcome to the NoMachine Enterprise Client - Installation and Configuration Guide v. 7.


What is NoMachine Enterprise Client for?
NoMachine Enterprise Client is a software designed to let you connect to a remote computer where any of the NoMachine server products, included NoMachine free, is installed. For example let's say there is an Enterprise Desktop running on the remote computer, you can connect from the Enterprise Client on your machine to the remote physical desktop:

You can also use your browser to connect to the remote computer: this works with any server product, except NoMachine free.

Client packages are available for Windows, Mac, Linux and also for Android and iOS mobile devices, included smartphones.



A Graphical Interface
The client is equipped with a native graphical User Interface (UI) providing a number of functionalities that we can group into the following:

1) Creation of a new connection.

2) Displaying of the remote desktop.

3) Easy access to recent connections (Machines) and computers in the same network if any.

4) Preferences to personalize aspect and behavior of the client (Player settings)



TIP
All NoMachine server types (included NoMachine free) provide the client UI and can work as a client to connect to a remote machine hosting a NoMachine server. In case of servers, it's possible to switch between 'player' and 'server' settings to access the corresponding UIs for managing their configurations.


1.1. About This Guide

This guide is organized in different sections which deal with client's installation, configuration and administration (advanced).

Online Resources
Visit the NoMachine Support Area to access a variety of online resources included the NoMachine Forums, tutorials and FAQs: https://www.nomachine.com/support

Find a list of all documents and tutorials: https://www.nomachine.com/all-documents

Use the Knowledge Base search engine to access articles, FAQs and self-help information: https://www.nomachine.com/knowledge-base


Leave Feedback About This Guide
Our goal is to provide comprehensive and clear documentation for all NoMachine products. If you would like to send us your comments and suggestions, you can use the contact tool available at https://www.nomachine.com/contact-request, selecting Web Quality Feedback as your option.

2. Install the Enterprise Client
2.1. Prerequisites

Supported Operating Systems
Windows 32-bit/64-bit XP/Vista/7/8/8.1/10

Windows Server 2008/2012/2016/2019

Mac OS X Intel 64-bit 10.7 to 10.15

Linux 32-bit and 64-bit

RHEL 4 to RHEL 8
SLED 10 to SLED 15
SLES 10 to SLES 15
openSUSE 10.x to openSUSE 15.x
Mandriva 2009 to Mandriva 2011
Fedora 10 to Fedora 32
Debian 4.0 to Debian 10
Ubuntu 8.04 to Ubuntu 20.04

Raspberry Pi 2/3/4 ARMv6/ARMv7/ARMv8

iOS 8.0 or later

Android 4.1 or later

Hardware requirements
Intel Core2 Duo or AMD Athlon Dual-Core or equivalent
1 GB RAM
Network connection (either a LAN, or Internet link: broadband, cable, DSL, etc...)
Size required on disk:
Windows 85 MB
Linux 80 MB
Mac 80 MB
ARMv6 70 MB
ARMv7 60 MB
ARMv8 78 MB

Compatibility Between Client/Server Versions
Compatibility between client/server v. 7 and v. 6 and v. 5 is fully preserved.



2.2. Windows Installations (install, update, uninstall)

INSTALL
Download the NoMachine Enterprise Client EXE package from the NoMachine web site and double click on the package icon: the Setup wizard will take you through the installation.

TIP
To install the package in silent or very silent mode from a CMD console, run respectively:
>nomachine-packageName_packageVersion.exe /silent
or:
>nomachine-packageName_packageVersion.exe /verysilent
To specify a non-default installation directory, use:
>nomachine-packageName_packageVersion.exe /SILENT /DIR="X:Target_directory"
or:
>nomachine-packageName_packageVersion.exe /VERYSILENT /DIR="X:Target_directory"
To skip the installation of USB modules, use the following.
Note that next updates via command line will still require to specify the usbinstall=0 option to skip the installation of USB modules. If you don't specify it, the USB module will be installed.
>nomachine-packageName_packageVersion.exe /usbinstall="0" /silent "
or:
>nomachine-packageName_packageVersion.exe /usbinstall="0" /verysilent"

 

UPDATE
There are two ways to update your current installation:

I Automatic updates

You can update your installation from our repositories. Just run the NoMachine UI from your Programs Menu and access the Settings -> Updates panel. Then click on the 'Check now' button.

NoMachine Enterprise Client has the automatic check for updates enabled: it will check by default our repositories every two days to verify if updates are available. In this case, the server will prompt a dialog informing that a new version is available but it will never automatically update the current installation.

Checking for updates can be disabled from that dialog by selecting the 'Don't ask again for this version' option or in the Updates panel by unchecking the 'Automatically check for updates' option.

Detailed instructions for configuring the Automatic Updates are available in a separate document in the Configuration section at: https://www.nomachine.com/all-documents .

II Update with NoMachine packages

Alternatively, download the latest available package from the NoMachine web site and click on the executable file to launch Setup. As for the installation, Setup will guide you through all steps necessary for updating your installation.

 

UNINSTALL
On Windows 10 and 8: open the Start menu and look for the NoMachine Enterprise Client application. Right mouse click on it and choose 'Uninstall'.

You can also use the Search box from the Charms bar on the right side of the screen and type 'Control Panel' to open it. Then access the Programs - Uninstall a program panel.

On Windows 7 and Vista: click on the Start button and click to open the Control panel from the Start menu. Then access panel 'Programs and Features' and choose to uninstall NoMachine Enterprise Client.

On Windows XP: Click on the Start button and click to open the Control panel from the Start menu. Then access panel 'Add or Remove Programs' and choose to uninstall NoMachine Enterprise Client.

TIP
To uninstall from a CMD console, move to C:/ProgramData/NoMachine/var/uninstall/ (if you are on Vista/7/8/10) or to C:/Documents and Settings/All Users/NoMachine/var/uninstall/ (if you are on XP). Then run:
> unins000.exe /silent
or:
> unins000.exe /verysilent
Uninstalling is completed when your command prompt is back.

 

2.3. Mac Installations (install, update, uninstall)

INSTALL
Download the NoMachine Enterprise Client DMG package from the NoMachine web site and double click on the package icon to mount the disk image. Next double-click on the package to install it; the Installer will take you through the installation.

TIP
To install from the command line, run:
$ NXMOUNTDIR=$(echo `hdiutil mount nomachine-packageName_packageVersion.dmg | tail -1 | awk '{$1=$2=""; print $0}'` | xargs -0 echo)
$ sudo installer -pkg "${NXMOUNTDIR}/NoMachine.pkg" -target /

 

UPDATE
There are two ways to update your current installation:

I Automatic updates

You can update your installation from our repositories. Just run the NoMachine UI from your Programs Menu and access the 'Settings' -> 'Updates' panel. Then click on the 'Check now' button.

NoMachine Enterprise Client has the automatic check for updates enabled: it will check by default our repositories every two days to verify if updates are available. In this case, the server will prompt a dialog informing that a new version is available but it will never automatically update the current installation.

Checking for updates can be disabled from that dialog by selecting the 'Don't ask again for this version' option or in the Updates panel by unchecking the 'Automatically check for updates' option.

Detailed instructions for configuring the Automatic Updates are available in a separate document in the Configuration section at: https://www.nomachine.com/all-documents .

II Update with NoMachine packages

Alternatively, download the latest available package from the NoMachine web site and click on the executable file to launch Setup. As for the installation, Setup will guide you through all steps necessary for updating your installation.

 

UNINSTALL
To uninstall the Enterprise Client, drag and drop NoMachine from Applications to trash or select 'Move to trash' from the mouse button menu. This will uninstall all the NoMachine software.

TIP
To uninstall from command line, it's enough you remove the NoMachine application directory:
$ sudo rm -rf /Applications/NoMachine.app

 

2.4. Linux Installations (install, update, uninstall)

Installing for the first time
You can install, update and uninstall using the graphical package manager of your Linux distribution or from command line by running commands from an xterm or similar with the sudo utility, or as root user if you don't have sudo installed. Instructions below refer to installation by command line.

There are two ways to update your current installation:

I Automatic updates

You can update your installation from our repositories. Just run the NoMachine UI from your Programs Menu and access the 'Settings' panel, go to the 'Updates' UI and click on the 'Check now' button.

NoMachine Enterprise Client has the automatic check for updates enabled: it will check by default our repositories every two days to verify if updates are available. In this case, it will prompt a dialog informing that a new version is available but it will never automatically update the current installation.

Checking for updates can be disabled from that dialog by selecting the 'Don't ask again for this version' option or in the Updates panel by unchecking the 'Automatically check for updates' option.

Detailed instructions for configuring the Automatic Updates are available in a separate document in the Configuration section at: https://www.nomachine.com/all-documents .

II Update with NoMachine packages

Alternatively, download the latest available package from the NoMachine web site and click on the executable file to launch Setup. As for the installation, Setup will guide you through all steps necessary for updating your installation.

2.5. RPM Packages

If you want to install to default location, namely /usr/NX/:

INSTALL

# rpm -ivh <pkgName>_<pkgVersion>_<arch>.rpm
To find out which NoMachine package you have installed (you will get the full name of the package), run:
# rpm -qa | grep nomachine

 

UPDATE

# rpm -Uvh <pkgName>_<pkgVersion>_<arch>.rpm

 

UNINSTALL

# rpm -e nomachine-enterprise-client

 

TIP
For non-default locations, for example /opt/NX:

INSTALL

# rpm -ivh <pkgName>_<pkgVersion>_<arch>.rpm --prefix /opt

UPDATE

# rpm -Uvh <pkgName>_<pkgVersion>_<arch>.rpm --prefix /opt

UNINSTALL

# rpm -e nomachine-enterprise-client

 

2.6. DEB Packages

If you want to install to default location, namely /usr/NX/:

INSTALL

$ sudo dpkg -i <pkgName>_<pkgVersion>_<arch>.deb
To find out which NoMachine package you have installed (you will get the full name of the package), run:
$ dpkg -l | grep nomachine

 

UPDATE

$ sudo dpkg -i <pkgName>_<pkgVersion>_<arch>.deb

 

UNINSTALL

$ sudo dpkg -r nomachine-enterprise-client

 

TIP
For non-default locations, for example /opt/NX:

INSTALL

$ sudo NX_INSTALL_PREFIX=/opt dpkg -i <pkgName>_<pkgVersion>_<arch>.deb

UPDATE

$ sudo NX_INSTALL_PREFIX=/opt dpkg -i <pkgName>_<pkgVersion>_<arch>.deb

UNINSTALL

$ sudo dpkg -r nomachine-enterprise-client

 

2.7. TAR.GZ Packages

If you want to install to default location, namely /usr/NX/, ensure that package is placed there.

INSTALL

$ cd /usr
$ sudo tar xvzf <pkgName>_<pkgVersion>_<arch>.tar.gz
$ sudo /usr/NX/nxclient --install

 

UPDATE

$ cd /usr
$ sudo tar xvzf <pkgName>_<pkgVersion>_<arch>.tar.gz
$ sudo /usr/NX/nxclient --update

 

UNINSTALL

$ sudo /usr/NX/scripts/setup/nxclient --uninstall
$ sudo rm -rf /usr/NX

 

TIP
For non-default locations, for example /opt/NX:

INSTALL

$ sudo NX_INSTALL_PREFIX=/opt /usr/NX/nxclient --install

UPDATE

$ sudo NX_INSTALL_PREFIX=/opt /usr/NX/nxclient --update

UNINSTALL

$ sudo /opt/NX/scripts/setup/nxclient --uninstall
$ sudo rm -rf /opt/NX

 

3. Personalizing Appearance and Behavior

 

3.1. The Settings UI

Launch the NoMachine Enterprise Client program, then click on the 'Settings' button in the UI to access Player settings:

You will see that the Player settings panel is made of two sections, in the left area there's the menu where you can select which panel to open in the right area for changing configurations:

I Set preferences for input devices and keyboard shortcuts (Input).
II Customize UI appearance and language (Appearance).
III Set preferences for transferring files from/to remote (Transfers).
IV Save or not log files and screenshots, disable network browsing(Security).
V Modify store directories for NoMachine files, included connection files and recordings (Folders).
VI Find out the version of your client and manage the automatic updates (Updates).

Fig. 1 - The 'Player settings' panels to configure your client

 

4. Initiating a Connection

 

4.1. Creating New Connections

Pre-requisite are that any of the NoMachine server products is installed on the remote computer, that you know the IP of that computer and that you have a system account there.

To connect the first time to the remote computer, or to create a new connection, click on 'Add':

Fig. 2 - Click on Add and provide information to start a new connection

Provide the relevant information: a name for the connection, the IP address and port number of the computer you want to connect to.
If you are connecting in a local network, provide the internal IP of the remote host, the default port is suitable for almost cases, unless the administrator has changed it on the server.

If you connect over the internet, use the public (or external) IP of the remote host and the assigned external port. These data can be retrieved on the remote host by opening the NoMachine UI on the remote host:

Fig. 3 - Open the NoMachine application on the remote computer to know its IP address.

When connecting to a NoMachine (free) server, only the NX protocol is available. When connecting to a commercial server, you can choose to use the SSH protocol or the HTTP protocol. In this last case, the session will be launched in your browser.

For a more advanced configuration, click on item 'Configuration' in the menu on the left. It permits to define any of the authentication methods available for the given protocol (NX, SSH or HTTP). The authentication method must be already configured and properly working on the remote computer, test it by other means than NoMachine. Note that password-based authentication is the method used by default by NoMachine.

Once the connection is created, it will be listed in the first opening panel of the client, 'Machines':

Fig. 4 - The new connection is displayed in the client UI ('Machines')

To connect to the remote computer, double-click on the connection icon.

Right-click on the icon, instead, opens a context menu where you can choose to:
- Start connection.
- Edit connection (to modify its settings).
- Rename connection.
- Remove connection (from the 'Machines' list and permanently delete it).
- Access connection info

Connection settings can be edited at any moment: click on the connection icon in the UI ('Machines') to open the context menu and select 'Edit connection'. In the 'Edit connection panel' you can choose what to do from the menu on the left area:
- Modify connection name, IP of remote computer, port and protocol (Address)
- Modify the authentication method (Configuration)
- Access connection info (Info)

Fig. 5 - Change settings of an existing connection.

TIP
Connection files are .nxs files, not intended to be edited manually.
They are stored in the directory defined by 'Connections and recordings' in the Settings -> Folders panel in the UI.
They are by default located in:
/Users/USERNAME/Documents/NoMachine on macOS
%USERPROFILE%\Documents\NoMachine on Windows
/home/USERNAME/Documents/NoMachine on Linux

 

4.2. Connecting to the Remote Host and Choosing Session Types

Pre-requisite are that any of the NoMachine server products is installed on the remote computer and that you have a system account there.

You will have to use its credentials to log-in to the remote host when requested. Insert them in the 'Username' and 'Password' fields when shown in the client GUI, password cannot be empty.

TIP
Save log-in credentials to not be prompted again to insert them the next time you connect again. If doing that it's not possible, it means that your administrator has configured the server to prevent users from storing credentials.

A particular log-in case is 'Login using a guest account': the server will automatically generate a system account (guest user) for you and you don't need to know your access credentials. This is available only when the NoMachine server supports this feature and the administrator has configured the server to provide it.

Once logged-in, if you connect to a NoMachine (free) server or to the Enterprise Desktop, you will be immediately connected to the physical desktop of the remote machine. When you are connected to the physical desktop, it's like if you are sitting in front of the remote computer.

TIPS
I If the remote desktop is owned by another user, he/she will have to authorize your connection. This is the default behaviour, which can be changed by configuring the server.
II If the login screen is active, you will be able to enter with any of the system accounts enabled for that.
III If the remote screen is locked, you will have to unlock it by providing the password of the logged user.

If you are connecting to any of the NoMachine terminal servers on Linux instead, besides connecting to the physical desktop, you will be also able to choose between creating a virtual desktop or a custom session. A custom session allows to run a single application in a floating window instead than running the whole desktop. Click on 'Create a new desktop or custom session' and choose among the available options:

Fig. 6 - Choose to create a new virtual desktop or a new custom session (single application)

 

TIP
Save your choice by selecting 'Save this settings in the connection file' wherever this flag is available, it's at the bottom left of the client window . The session type you decided to start will be re-used the next time you run this connection and you will skip steps to select it.

A virtual desktop is an individual instance of the remote desktop: it's your personal desktop.

Many users can have each one his/her own virtual desktop on the same remote host as you. That's why when you connect you can see also their sessions listed in the client GUI. Click on the 'My desktop'/'All desktops' button to switch view list and show only your own virtual desktops or also those of other users. This last view mode is useful if you need to connect to the desktop of someone else to make collaborative work (session collaboration or desktop sharing). Virtual desktops can be shared in interactive or view-only mode.

When you close the virtual session or application (i.e. you disconnect but don't terminate it), you will find it listed once you log-in the next time. Instead of choosing 'Create a new desktop' you can click on any of your virtual desktops to reconnect it.

A custom session permits to run a single Linux application instead than the full desktop. To do that, provide command to launch it with the 'Run the command in a floating window' option enabled:

Fig. 7 - Specify path to the application you want to run in the 'Run the following command' field.

The Application area permits to define which remote application will be run:

Run the console will launch a system terminal.

Run the default X client script on the server will execute the X client script set on the remote host.

Run the following command permits to specify the application to be launched. If such application is not in the path on the remote host, it's necessary to provide the full path in the UI field.

For example if 'firefox' is in the path, it's enough to write in the command field: firefox. If it's not in the path, it's necessary to specify the full path such as: /usr/bin/firefox. If the application supports options, they can be specified in the command as well. E.g. to open a URL in a new tab: /usr/bin/firefox -new-window http://www.nomachine.com/

In the Options area you can define if the application has to be run as single application or embedded in the NoMachine client window by selecting respectively: Run the command in a floating window or Run the command in a virtual desktop.

4.3. Displaying the Remote Session

Once the session is started, you will be welcomed by a series of tutorial panels to explain which are the NoMachine tools at your disposal to manage the session. They show, in the following order:

1.How to open the NoMachine menu panel inside the session (click on the page peel at the top right or ctrl+alt+0); how to change screen resolution (icon buttons at the bottom of the window)

2.What each buttons in the menu panel stays for.

3.Which are the available display resolutions view modes.

After completing all the introductory steps, you are in!

By default you have access to the remote desktop (either physical or virtual) in interactive mode, and you can use applications, access files and directories exactly as if you are sit in front of the remote computer.

TIP
Select 'Don't show this message again' at the bottom left of the client window to skip tutorials the next time you run this session.

 

4.4. Closing the Session

Let's distinguish between when you are connected to the (i) physical desktop of the remote machine and when you are running (ii) a virtual desktop or a custom session.

Closing physical desktop sessions
You can close the connection to the remote physical desktop by clicking on the X in the upper right corner of the client window or open the NoMachine menu (ctrl+alt+0), enter the 'Connection' panel and click on 'Disconnect'.

The default shortcut to close it is: Ctrl+Alt+T.

You can reconnect to the physical desktop at any time, by launching your connection again.

Closing virtual desktops and custom sessions

To close a virtual desktop and be able to reconnect it later, simply close the client window by clicking on the X button in the upper right corner. Otherwise, open the NoMachine menu (ctrl+alt+0), enter the 'Connection' panel and click on 'Disconnect'. You will be able to reconnect your session later, even from a different computer (we call it 'session migration'). If you left an application running inside the session (e.g. a graphics program rendering images), you will find it still running once reconnected.

If you need instead to terminate the virtual desktop, simply log-out from the system.

To disconnect a custom session, close the client window showing the NoMachine menu (not the window of the custom application!)

For teminating it, close the application window.

TIP
If you use a program to elaborate data, disconnect the NoMachine virtual session and let the program continue its operations.
5. NoMachine Menus and Others

This chapter provides an overview of which are tools at your disposal to configure the session behavior and use the available NoMachine services. More specific guides dealing with some functionalities in detail are available in the 'Tutorials' section here: https://www.nomachine.com/all-documents

 

5.1. The NoMachine Menu Panel

To open the NoMachine menu panel inside the session, enter the key combination Ctrl+Alt+0 or move your cursor to the page-peel in the top right-hand corner of the window:

Fig. 8 - Click on the page peel in the top right corner to open the NoMachine menu panel.

The menu panel is like a console providing some facilities you can use while running the session, for example use it to:
- Emulate the middle mouse button if your mouse has three buttons or a clickable scroll wheel (Input)
- Define shortcuts for quickly terminate the session, toggle to fullscreen, minimize the client window and more (Input).
- Connect disks, printers, USB devices and more from local to remote and vice-versa (Devices)
- Tune at runtime display settings like quality of images and screen resolution (Display)
- Mute audio and microphone or tune volume (Audio and Mic in)
- Record a video of the session or of your local desktop and play it (Recoding)
- Retrieve statistics of the data traffic generated by the NoMachine session (Connection).

It looks like:

Fig. 9 - The NoMachine menu panel inside the session.

 

5.2. The NoMachine Monitor Menu

A NoMachine Monitor is present on your computer (where the NoMachine Enterprise Client is installed) and on the remote computer (where any of the available server types is installed). Let's distingusih the two cases.

The Monitor menu for the client
To open the Monitor menu, right mouse click on the !M icon the system tray of your computer:

Fig. 10 - Open your client's Monitor menu by clicking on the !M icon in the system tray of your computer.

The Monitor menu for the server
To open the Monitor menu, right mouse click on the !M icon the system tray of the remote desktop:

Fig. 11 - Open the NoMachine server Monitor menu it by clicking on the !M icon in the remote system tray

This menu gives quick access to some facilities like:
- Accepting connections (this allows you to enable/disable the sharing of your desktop).
- Show the recording bar (to register a video of your remote desktop).
- Send a file from the client and Download a file from the server and others.

Other options like 'Show the server status' are deserved to the server administration and give access to NoMachine Server preferences. Changing settings in this panel requires to have administrative privileges on the server host.

 

5.3. Blanking of the Physical Screen and Auto Lock Upon Disconnecting

Blanking the remote screen and auto lock are server side options that apply when users connect to the physical desktop of the remote host.

They can be both enabled/disabled via the Server Preferences UI in the Security panel, but you need to be an administrator on the server to change these settings.

For more details on server side configurations, refer to the NoMachine Server UI guide in the 'Configuration' section at https://www.nomachine.com/all-documents

5.4. Disabling Screen Sharing

Disabling screen sharing, i.e. disabling access to your local desktop via NoMachine applies only to the physical desktop, either if you are sit in front of the desktop or you are connected from remote.

Open the NoMachine Monitor menu (click on the !M icon in the system tray) of the remote desktop and click on Accept connections to switch on/off access to your desktop.

TIP
When accepting connections it disabled, it lasts until you change it again. It persists also when you are physically logged-out or closed the NoMachine connection. Be very careful when disabling accepting connections from remote, since it will be no longer possible to reconnect to the desktop via NoMachine once the current session is closed.

 

5.5. Multi-Monitor Support

NoMachine has full multimonitor support for multiple monitors connected on end-user's side as well as for those connected to the remote server computer.

Multiple monitors connected to your computer
If you have more than one monitor connected to your computer you can display the NoMachine session window on a single monitor (you can resize the window or send it at fullscreen) or spawn at fullscreen the session windows on all monitors.

To adapt the session window or access the Display settings for tuning quality and resolution, use the small icons (quick access display icons) in the footbar of the NoMachine menu panel. Move the mouse over each icon to display its label.

TIP
Move the cursor over the quick icon in the footbar to show its label and see what it does.

 

Multiple monitors connected to the remote computer
When the remote computer has multiple monitors, you can switch through those monitors by using shortcuts:
Ctrl+Alt+I to identify the monitor.
Ctrl + Alt + MonitorID to change the current monitor.
Ctrl + Alt + A to view all monitors.

Default shortcuts can be personalized in Player Settings -> Input panel by clicking the 'Shortcuts' button.

It's possible to switch monitor also from the NoMachine menu by using the quick access display icons in the footer of the menu.

Select the monitor you wish or view all the monitors in one window.

 

6. The Enterprise Client for NoMachine Administrators

You can find at: https://www.nomachine.com/all-documents a detailed guide to preconfigure client sessions (section 'Configuration') and Tutorials dealing specifically with the administrations of multi-host environments via UI (section 'Tutorials').

 

6.1. Pre-configuring the Client to End-Users

Client configuration file (player.cfg) and connection files (*.nxs) are not intended to be edited manually, they are created automatically by the client according to options set via the UI.

In some cases, however, administrators may need to facilitate their users and avoid that they have to define specific settings by themseleves. Administrators can tune settings in player.cfg and pre-configure the connection file according to their needs. Such files can then be distributed to users.

6.2. Federating Servers Under a Cloud Server via UI

The client UI permits to set-up and manage a multi-host infrastructure, with the possibility to add, edit and remove hosts at any moment.

To do that, log-in to the Cloud Server as 'root' if the host is Mac or Linux, or as 'administrator' if the host is Windows. Then click on 'New server' button to federate a server:

Fig. 12 - Add a child server to the Cloud Server

As an alternative, you can use a NoMachine administrator account to log-in to the Cloud Server. A NoMachine administrator has special rights only to create NoMachine multi-host environments via UI. Being a NoMachine administrator doesn't alter current system privileges for that user. To make a user becoming a NoMachine administrator, do the following on the CS host.

On Linux and macOS open a terminal and execute:

sudo /etc/NX/nxserver --useredit USERNAME --administrator yes

On Windows open a CMD console as Windows administrator and execute:

cd C:\Program files (x86)\NoMachine\bin\
nxserver --useredit USERNAME --administrator yes

For a step by step guide to federate servers under a Cloud Server via UI, please refer to the 'Tutorials' section at: https://www.nomachine.com/all-documents

For more details about how to configure a Cloud Server multi-server setup, please refer to the Cloud Server guide available in the 'Installation' section at: https://www.nomachine.com//all-documents

 

6.3. Adding Terminal Server Nodes to the Enterprise Terminal Server via GUI

NoMachine Enterprise Terminal Server (ETS) permits to setup a single-tier multinode environment made of Terminal Server Nodes (TSN). Also in this case NoMachine administrators can add the nodes via UI. Connect to the Enterprise Terminal Server as 'root' on Mac and Linux or as 'administrator' on Windows or as NoMachine administrator. Then click on the 'New node' button to add the Terminal Server Node:

Fig. 13 - Add a Terminal Server Node to the Enterprise Terminal Server

For more details about how to configure a multi-node setup, please refer to the Enterprise Terminal Server guide available in the 'Installation' section at: https://www.nomachine.com/all-documents

 

For a step by step guide to add nodes to the Enterprise Terminal Server via UI, please refer to the 'Tutorials' section at: https://www.nomachine.com/all-documents