![]() Preferably, install the Cloud Server on an AD client and not on the Domain Controller. It's preferable that the Cloud Server and the Enterprise Desktop are in the same AD domain or connected to the same LDAP directory. This account can be a local system account, or a LDAP or an AD account.Ģ) Install NoMachine Cloud Server, CS1 on MachineA. The user must have a valid account with the same username on the Cloud Server host (MachineA in the next examples) and on the node (MachineB) where he/she will connect. Supported Authentication Methods and known limitationsġ) Setup and configure the authentication subsystem by referring to the documentation of your Operating System. Propagating profile rules to the nodes New!Ĥ. Assigning the first available Enterprise Desktop to the user New!ģ.8. Set-up the HA failover cluster (optional)ģ.7. ![]() Limit access to a group of nodes (optional)ģ.6. Limit access to one or more nodes (optional)ģ.5. Dispatch the connection to a specific node (optional)ģ.4. Deeper insight: traffic forwarding and user authenticationģ.3. How to setup a NoMachine Cloud Server multi-server environmentģ.2. Use Case 1: Cloud Server in a LAN or VPNĢ.2. Preliminary operations for all supported operating systemsĢ.1. ![]() The nodes in these guidelines will be Enterprise Desktops. The users’ desktops/servers/workstations will be referred to as 'nodes'. The single point of access will be via Cloud Server. It is intended for system administrators who need to provide a single point of access to computers in the corporate network, including academic and research institutions which want to offer hosted desktops to their students and staff.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |