Do NX accounts also require a system account?

Forum / NoMachine for Windows / Do NX accounts also require a system account?

  • This topic has 1 reply, 2 voices, and was last updated 4 years ago by kroy.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #30601
    m4387
    Participant

    I use Enterprise Desktop on Windows Server 2012.  The server is bound to Active Directory.  I have both AD and local accounts.  I connect using Enterprise Desktop Clients on Windows 10 and macOS.

    I want all users to view the same desktop of the logged-in local account.  This system controls a scientific instrument, and all remote users should see the same desktop.

    I’m confused by the user management documentation https://www.nomachine.com/DT02O00125#10.

    1. To use a NX account, do I first need to create a system account with the same name?
    2. Can I configure NoMachine to allow AD users to authenticate with their AD credentials, but then they view the currently logged-on user, which is a local account?
    3. If #2 is possible, how can I restrict which AD users can connect?

     

    #30661
    kroy
    Contributor

    To use a NX account, do I first need to create a system account with the same name?

    Yes, there should exist local or network account with the same name.

    Can I configure NoMachine to allow AD users to authenticate with their AD credentials, but then they view the currently logged-on user, which is a local account?

    Yes, enabling Users db and adding AD users will allow only them to login to Your host. If You doesnt enable Nx Password db, then NX will login them using their AD credentials. To enable users db, set following key in the server.cfg:

    EnableUserDB 1

    All added user which aren’t desktop owner, trusted or administrator – would require the approval of the desktop owner. The desktop owner also can allow or forbid the user to interact with the desktop.

Viewing 2 posts - 1 through 2 (of 2 total)

This topic was marked as solved, you can't post.