This article applies to a Cloud Server setup + Enterprise Desktop nodes on Windows and an Active Domain user with administrative privileges on the Enterprise Desktop host.

In this context the domain user cannot connect via Cloud Server with the remote Server admin UI to the node. It's necessary that the domain user connects before by the Server admin UI directly to the Enterprise Desktop node. In this way NoMachine can create and cache the security context for that domain user, who will be then allowed to connect also through the Cloud Server with the remote Server admin UI. In practice, it's not possible to create a NoMachine process for a domain user, unless he/she connected already by NoMachine. If the Enterprise Desktop is restarted, it will be necessary to connect directly again to create a new security context.

Alternative ways:

1) add or edit the node with the 'Require further authentication on this node' option enabled in the UI (Settings -> Server -> Nodes).
2) or enable Kerberos authentication with ticket forwarding
3) or use a local account with administrative rights on the Enterprise Desktop host.
4) It should work also if the domain account is logged physically to the Enterprise Desktop host.