pproved by: NoMachine Enterprise Products, Cloud Server Installation and Configuration Guide Page 1 of 18
pproved by: Table of Contents 1. NoMachine Cloud Server 3 1.1. Resources on the Web 3 1.2. Prerequisites 4 2. Installing on Windows 4 2.1. Installing the Cloud Server 4 2.2. Updating the Cloud Server 7 2.3. Uninstalling the Cloud Server 7 3. Installing on Mac OS X 7 3.1. Installing the Cloud Server 7 3.2. Updating the Cloud Server 9 3.3. Uninstalling the Cloud Server 10 4. Installing on Linux 10 4.1. Managing the RPM Package 10 4.2. Managing the DEB Package 11 4.3. Managing the TR.GZ Package 11 5. Initiating a Web Connection via Cloud Server 12 6. Managing the Cloud Server 13 7. Connecting Multiple Servers by Cloud Server 13 Page 2 of 18
pproved by: 1. NoMachine Cloud Server Welcome to the NoMachine Cloud Server Installation Guide version 4 or higher. This document is intended to provide you with step-by-step instructions on how to install the Cloud Server package (it was named 'Portal Server' in version 4.0) and it's updated to fit version 4.2.27 and later. This package includes a small pache-based web server, the NoMachine HTTP server (nxhtd), pre-configured to work out-of-the box to let you get access to the server on which it is installed, or other Enterprise and Cloud Servers. 1.1. Resources on the Web The NoMachine Web site, www.nomachine.com, provides you with a variety of online resources in conjunction with the software and its usage: The NoMachine Packages The latest version of NoMachine is available at: www.nomachine.com/download. The Knowledge Base The Knowledge Base, https://www.nomachine.com/support, makes available both technical documents especially for administrators and end-user oriented guides, as well as articles on specific topics and How-Tos. Leave Feedback bout This Guide Our goal is provide comprehensive and clear documentation for all the NoMachine products. If you would like to send us your comments and suggestions, you can use the Web contact tool available at https://www.nomachine.com/contact-request, by selecting the Web Quality Feedback as your option. 1.2.Prerequisite Operating System Windows 32-bit/64-bit XP/Vista/7/8/8.1 Mac OS X Intel 64-bit 10.5/10.6/10.7/10.8/10.9/10.10 Linux 32-bit and 64-bit Red Hat Enterprise 4/5/6/7 SLES 10/11 SLED 10.x/11.x Open SUSE 10.x /11.x/12.x/13.x Mandriva 2009/2010/2011 Fedora 10/11/12/13/14/15/16/17/18/19/20 Page 3 of 18
pproved by: Debian GNU Linux 4.0 Etch/5.0 Lenny/ 6.0 Squeeze/ 7.0 Wheezy Ubuntu 8.04 Hardy Heron/8.10 Intrepid Ibex/Ubuntu 9.04 Jaunty Jackalope/ 9.10 Karmic Koala/10.4 Lucid Lynx/10.10 Maverick/11.04 Natty/11.10 Oneiric/ 12.04 Precise Pangolin/12.10 Quantal Quetzal/13.04 Raring Ringtail/ 13.10 Saucy Salamander/14.04 Trusty Tahr Hardware requirements Intel Core2 Duo or MD thlon Dual-Core or equivalent 1 GB RM Network connection (either a LN, or Internet link: broadband, cable, DSL, etc...) Size required on disk: Windows 107.5 MB Linux 81 MB Mac 83 MB 2. Installing on Windows 2.1. Installing the Cloud Server Download the package from the NoMachine web site and install it by double-clicking on the icon of the executable: a setup wizard will take you through the installation. ccept to reboot the machine, this is mandatory for completing the installation. Page 4 of 18
pproved by: Page 5 of 18
pproved by: 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 Then reboot the machine: > SHUTDOWN -r -t 10 -c " your comments here" Page 6 of 18
pproved by: 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" Note for Windows XP: the NoMachine server will not start until the machine is rebooted. 2.2. Updating the Cloud Server Starting from version 4.0.365, you can update your installation from the NoMachine repositories instead of downloading and installing the new package.just run the NoMachine GUI and access the Preferences -> Updates panel and click on 'Check now'. lternatively, you may download the lastest available package from the NoMachine web site and click on the executable file to launch Setup. s for the installation, Setup will guide you through all steps necessary for updating your installation. 2.3. Uninstalling the Cloud Server You can uninstall NoMachine Cloud Server from the Windows Control Panel and the dd or Remove Programs in Windows XP or Program and Features in Windows Vista, 7 or 8. Find the NoMachine program in the list of installed programs and choose to uninstall it. On Windows 8, you can use the Search box from the Charms bar on the right side of the screen: type Control Panel to open it. Then access the Programs - 'Uninstall a program' panel. On Windows 7, Vista and XP, click on the Start button and click to open the Control panel from the Start menu. Then access panel 'Programs and Features' or 'dd or Remove Programs', depending on your Windows version. Reboot is requested to complete the uninstalling process. Tip To uninstall from a CMD console, move to C:/ProgramData/NoMachine/var/uninstall/ (if you are on Vista/7/8) or to C:/Documents and Settings/ll Users/NoMachine/var/uninstall/ (if you are on XP). Then run: > unins000.exe /silent Page 7 of 18
pproved by: or: > unins000.exe /verysilent Uninstalling is completed when your command prompt is back. Then, your computer will restart automatically. 3. Installing on Mac OS X 3.1. Installing the Cloud Server Download the DMG package from the NoMachine web site. Double-click on the disk Image to open it and see the package icon. Then double-click on the package icon to install the program: the installer will take you through the installation. Page 8 of 18
pproved by: Page 9 of 18
pproved by: Tip To install from the command line, run: $ NXMOUNTDIR=$(echo `hdiutil mount nomachine-cloud-server_version.dmg tail -1 awk '{$1=$2=""; print $0}'` xargs -0 echo) $ sudo installer -pkg "${NXMOUNTDIR}/NoMachine.pkg" -target / 3.2. Updating the Cloud Server Starting from version 4.0.365, you can update your installation from our repositories instead of downloading and installing the new package. Just run the NoMachine GUI and access the Preferences -> Updates panel and click on 'Check now'. Page 10 of 18
pproved by: lternatively, you may download the lastest available package from the NoMachine web site and click on the dmg file to mount the disk image and launch the Installer. s for the installation, Installer will guide you through all steps necessary for updating your installation. 3.3. Uninstalling the Cloud Server To uninstall the Cloud Server drag and drop NoMachine from pplications 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 /pplications/nomachine.app 4. Installing on Linux 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. Starting from version 4.0.365, you can update your installation from our repositories instead of downloading and installing the new package. Just run the NoMachine GUI and access the Preferences -> Updates panel and click on 'Check now'. Up to version 4.4.6, all packages were qualified by the same name 'nomachine'. Next versions use different package names to distinguish among client, node and server types (FR09L02829). 4.1. Managing the RPM Package If you want to install to default location, namely /usr/nx Installing # rpm -ivh <pkgname>_<pkgversion>_<arch>.rpm Updating # rpm -Uvh <pkgname>_<pkgversion>_<arch>.rpm Uninstalling # rpm -e nomachine-cloud-server For versions up to 4.4.6 use: Page 11 of 18
pproved by: # rpm -e nomachine Tip To find out which NoMachine package you have installed, run the following command: # rpm -qa grep nomachine You will get the full name of the NoMachine package already installed, for example: nomachine-cloud-server-4.4.10-1.x86_64 If you want to install to a non-default location, for example /opt/nx Installing # rpm -ivh <pkgname>_<pkgversion>_<arch>.rpm --prefix /opt Updating # rpm -Uvh <pkgname>_<pkgversion>_<arch>.rpm --prefix /opt Uninstalling # rpm -e nomachine-cloud-server or for versions up to 4.4.6: # rpm -e nomachine 4.2. Managing the DEB Package If you want to install to default location, namely /usr/nx Installing $ sudo dpkg -i <pkgname>_<pkgversion>_<arch>.deb Updating $ sudo dpkg -i <pkgname>_<pkgversion>_<arch>.deb Uninstalling $ sudo dpkg -r nomachine-cloud-server For versions up to 4.4.6 use: Page 12 of 18
pproved by: $ sudo dpkg -r nomachine Tip To find out which NoMachine package you have installed, run the following command: $ dpkg -l grep nomachine You will get the full name of the NoMachine package already installed, for example: nomachine-cloud-server 4.4.10-1 If you want to install to a non-default location, for example /opt/nx: Installing $ sudo NX_INSTLL_PREFIX=/opt dpkg -i <pkgname>_<pkgversion>_<arch>.deb Updating $ sudo NX_INSTLL_PREFIX=/opt dpkg -i <pkgname>_<pkgversion>_<arch>.deb Uninstalling $ sudo dpkg -r nomachine-cloud-server or for versions up to 4.4.6: $ sudo dpkg -r nomachine 4.3. Managing the TR.GZ Package If you want to install to the default location /usr/nx ensure that package is placed there. Installing $ cd /usr $ sudo tar xvzf <pkgname>_<pkgversion>_<arch>.tar.gz $ sudo /usr/nx/nxserver --install Updating $ cd /usr $ sudo tar xvzf <pkgname>_<pkgversion>_<arch>.tar.gz $ sudo /usr/nx/nxserver --update Page 13 of 18
pproved by: Uninstalling $ sudo /usr/nx/scripts/setup/nxserver --uninstall in case, remove the installation dir: $ sudo rm -rf /usr/nx If you want to install to a non-default location, for example /opt/nx: Installing $ sudo NX_INSTLL_PREFIX=/opt /usr/nx/nxserver --install Updating $ sudo NX_INSTLL_PREFIX=/opt /usr/nx/nxserver --update Uninstalling $ sudo /opt/nx/scripts/setup/nxserver --uninstall in case, remove the installation dir: $ sudo rm -rf /opt/nx 5. Initiating a Web Connection via Cloud Server Once installation has completed with success, Cloud Server is ready to go. Point your browser to http://servername:4080 where servername is either the name or IP address of the host you want to reach. E.g., if you have the installation on a host named myserver.com, the URL will look like this: https://myserver.com:4080. Then provide your username and password and connect. 6. Managing the Cloud Server You can start and stop the NoMachine HTTP server (nxhtd) from the NoMachine GUI -> Preferences -> Server status -> Server Preferences -> Services panel. lways from the NoMachine GUI you can also change the listen port for the web server (by default 4080 and 4443 for secure connections). 7. Connecting Multiple Servers by Cloud Server By default the Cloud Server connects to the server installed local to the web player application, but it can be configured to give access to multiple servers on different hosts. To do that, you have to follow Page 14 of 18
pproved by: instructions below. Step 1 First of all, it's necessary to change some configurations in the cloud.cfg file that is: /usr/nx/etc/cloud.cfg on Linux C:\Program Files\NoMachine\etc\cloud.cfg on Windows /pplications/nomachine.app/contents/frameworks/etc/cloud.cfg on Mac OS X. The 'SectionSession' directive in the cloud.cfg file allows to define to which server users will connect to. SectionSession "Connection to localhost" ServerHost localhost ConnectionMethod NX ConnectionPort 4000 ServerPath /etc/nx/nxserver EndSection Name set in the "Connection to localhost" field is the connection name that will appear to users when there are multiple servers available. ServerHost is IP or hostname of the server machine. ConnectionMethod and Port indicates protocol and port that web player will use to connect to the server. Supported protocols are: NX SSH with system login SSH with nomachine login (i.e. authenticating by using NoMachine DS keys and user 'nx'). Set 'ConnectionMethod NX' to use the NX protocol (this is the default). Set 'ConnectionMethod system' to use SSH protocol and system login Set 'ConnectionMethod nomachine' to use SSH protocol and NoMachine DS keys. Note NoMachine uses by default port 22 for SSH protocol on Linux and Mac, and port 4022 on Page 15 of 18
pproved by: Windows. Default port for NX protocol is 4000. ServerPath indicates path to launch the server program and in general doesn't need changing, unless you installed the server in a non-default path. To allow users to connect to multiple servers by a unique Cloud Server, add a new 'SectionSession' for each of them and specify a different name in the "Connection to localhost" field to recognize different servers. For example: SectionSession "Connection to server " ServerHost localhost ConnectionMethod NX ConnectionPort 4000 ServerPath /etc/nx/nxserver EndSection SectionSession "Connection to server B" ServerHost 192.168.1.12 ConnectionMethod system ConnectionPort 22 ServerPath /etc/nx/nxserver EndSection Step 2 - Update the list of allowed hosts Depending if web player is configured to allow connections via NX or SSH protocol, you need to follow procedure a) or b). a) ConnectionMethod is set to 'NX' in the cloud.cfg configuration file To connect via web player and NX protocol to another server than localhost, you need to update list of allowed hosts in the client.crt file. This file is placed in the home of the nxhtd user at: /var/nx/nxhtd/.nx/config/ on Linux %PROGRMDT%\NoMachine\nxhtd\.nx\config\ on Windows Vista, 7 and 8 /Library/pplication\ Support/NoMachine/var/nxhtd/.nx/config/ on Mac OS X Page 16 of 18
pproved by: 1) Create a backup of the original file, client.crt. 2) Copy in place the nxd certificate from the server host machine to the web player host. For example on Linux, if the server is 192.168.1.12, copy from 192.168.1.12 its nxd certificate to your Cloud Server host installed let's say on testdrive: # scp root@testdrive.nomachine.com:/usr/nx/etc/keys/host/nx_host_rsa_key.crt 3) Then add a line to the client.crt file to specify the host and then the certificate. In this way the certificate will be assigned to the specified host: # echo "Host:<hostname or ip>" >> client.crt # cat nx_host_rsa_key.crt >> client.crt so for example, if you have set 'ServerHost 192.168.1.12' in cloud.cfg, you have to issue the following commands: # echo "Host:192.168.1.12" >> client.crt # cat nx_host_rsa_key.crt >> client.crt Then the client.crt file will look like: Host:192.168.1.12 -----BEGIN CERTIFICTE----[...] -----END CERTIFICTE----- 4) and set correct permissions and ownership: # chmod 600 client.crt # chown nxhtd:nxhtd client.crt 5) You can then delete the nx_host_rsa_key.crt file copied from testdrive: # rm nx_host_rsa_key.crt IMPORTNT: This procedure must be repeated for each server host you want to connect by Cloud Server and NX Page 17 of 18
pproved by: protocol. b) ConnectionMethod is set to 'SYSTEM' or 'NOMCHINE' in the cloud.cfg configuration file When the ConnectionMethod key it's set in the cloud.cfg file to 'SYSTEM' or 'NOMCHINE', web connections will use SSH + system login or SSH + NoMachine login respectively. To connect via web and SSH protocol to another server than localhost, you have to update the list of allowed hosts in the known_hosts file. This file is placed in the home of the nxhtd user at: /var/nx/nxhtd/.ssh/ on Linux %PROGRMDT%\NoMachine\nxhtd\.ssh on Windows Vista, 7 and 8 /Library/pplication\ Support/NoMachine/var/nxhtd/.ssh on Mac OS X 1) Rename the original known_hosts file: # mv known_hosts known_hosts.ori 2) Then execute the ssh-keyscan tool for building and verifying ssh_known_hosts files. For example, if the Cloud Server is installed on testdrive and you want to let it connect to another NoMachine server on let's say 192.168.1.12, execute on testdrive: # ssh-keyscan -p 22 -t rsa,dsa 192.168.1.12 >> known_hosts where 22 is the default port for SSH connections unless the SSH server (SSHD) has been configured for listening on a different port. Page 18 of 18 Powered by TCPDF (www.tcpdf.org)