![]() for which we don't build native packages. a Unix-like host running an unsupported O.S. Another NoMachine Cloud Server which in turns rules its own nodes (multi-level infrastructure). A NoMachine Enterprise Terminal Server which in turn manages a multi-node environment made of NoMachine Terminal Server Nodes. Any of the standalone NoMachine servers like Enterprise Desktop, Workstation, Small Business Server and Terminal Server. Then add your node(s) to the Cloud Server. NoMachine Cloud Server is fully operative once installation is completed. Only specific users are allowed to connect to the physical desktop of the Cloud Server, mainly for maintenance or administrative operations on this host.īuilding your centralized NoMachine architecture The Cloud Server is not intended for providing access to desktops on his host machine. It can create a scalable infrastructure with multi-level nodes.Īvailable for Linux, Mac and Windows, the Cloud Server provides access to its nodes, (previously called 'child servers') via a browser (thanks to its built-in web server) or via NoMachine client. NoMachine Cloud Server works as a single point of access to multiple subsystems globally distributed and running NoMachine server installations or Unix-like operating systems for which we don't build a native package ('Foreign X Servers'). Welcome to the NoMachine Cloud Server - Installation and Configuration Guide v. Guest Users (Automatic Generation of System Accounts)ĩ.1. Special Users with Permisssion to connect to the Cloud Server Physical DesktopĨ.4. Managing Users on the Cloud Server HostĨ.3. Handling with Discovering of this Server on LANĨ.1. Stopping and Starting Network Servicesħ.4. ![]() Stopping and Starting Cloud Server and Servicesħ.3. Web Optimizations: Using WebRTC (Real-Time Web Communication)ħ.2. Using an Alternative Apache Web Serverĥ.4. Preventing Users from Storing their CredentialsĬonfigurations and Optimizations for Web Sessionsĥ.3. Connecting by Browsers Via Cloud Server Web ToolsĤ.3. Initiating a NoMachine Connection (end-user's side)Ĥ.1. Setting-up a Failover Cluster with a Second Cloud Server for High Availability (optional)ģ.11. Propagating Profile Rules from the Cloud Server to the Nodes (optional)ģ.10. Assigning Users to the First Available Enterprise Desktopģ.9. Assigning Users to a Group of Nodes (optional)ģ.8. Assigning Users to a Specific Node (optional)ģ.7. Adding 'Foreign X Servers' to the Cloud Serverģ.6. Using the 'token' Forwarding Method for Client Connections by SSH (Advanced)ģ.5. ![]() Advanced Configurations for Multiple Levels of NoMachine Serversģ.4. Creating Multiple Levels of NoMachine Serversģ.3. Adding NoMachine Servers as Nodes of the Cloud Serverģ.2. Use the Cloud Server to Provide a Single Point of Access to Remote Computersģ.1. Activating the License (for Customers)īuilding a Scalable Multi-tier Infrastructure with Centralized Access to Remote Hostsģ. NoMachine Cloud Server Installation and Configuration GuideĢ.8.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |