There is currently a bug in profiles which won’t let you correctly disable access to the node:
User can connect to a remote node even if access to that host is disabled by profile rules
http://www.nomachine.com/TR05L04399
Once this bug is fixed the correct procedure will be to create user profile rules to forbid connections to specific Enterprise Desktops:
/usr/NX/bin/nxserver –ruleadd –class node –type <node:port> –value no –user <username>
where <node:port> is the name of the node as displayed by the nxserver –nodelist
Because of TR05L04399, a solution is to use the redirect capabilities instead of profile rules. You can use the following command to redirect connections from the cloud server to the enterprise desktop based on the users:
/usr/NX/bin/nxserver –useredit <username> –redirect <node:port>
where <node:port> is the name of the node as displayed by the ‘nxserver –nodelist ‘ command.
Redirection can be set also on-per client IP basis:
/usr/NX/bin/nxserver –hostadd <clientIP> –redirect <node:port>
Pre-requisite is that the user has a system account on the Cloud server host and on the Enterprise Desktop host. The username has to be the same. First of all add each Enterprise Desktop as a node of the Cloud server by running the following command from a console on the server host:
/usr/NX/bin/nxserver –nodeadd <IP of the Enterprise Desktop>
You can gather information on the node by running:
/usr/NX/bin/nxserver –nodelist
All the Enterprise Desktop you added will be seen by all users connected to the Cloud Server. Users will be able to choose which Windows desktop to join.