Terminal window of the Remote Utilities Viewer
Remote Utilities 7.9: Terminal mode on every platform, files through the clipboard. Learn more →

Community


RU Server – Address book permissions for individual connections

Links used in this discussion
Support level: Free or trial
Hello Remote Utilities Support and Community,

We are currently evaluating Remote Utilities as a replacement for  [censored] in our company.

Our environment consists of approximately 160 Windows computers and servers, around 20 Viewer users, and a self-hosted RU Server (version 3.5.6.0). Viewer and Host are running version 7.9.0.0.

We would like to implement the following access control model:

- IT administrators should be able to see and access all computers. -> works
- Regular users should only see and access specific computers assigned to them.
- Computers should remain organized in folders by department or function.

For example, a user may need access to only one specific computer within a folder containing multiple computers.
In our case, I want the user ru-test to see and access only SOFTWARE_11 in the Viewer, while all other computers in the same and all other folders should remain hidden (see attached screenshot).
How should I configure the address book permissions to achieve this?
Attached Files
RU Server – Address book permissions for individual connections
Hello Peter,

Thanks for the detailed description and the screenshot.

You can set permissions on a single connection, so SOFTWARE_11 can stay in the Software folder. By default a connection inherits its permissions from its folder and address book, much like files on Windows, so they are greyed out and can't be changed. To give ru-test access to SOFTWARE_11 only:
  • In the Address book manager, edit SOFTWARE_11 and click the Security button on the General tab.
  • Click Disable inheritance and choose "Convert inherited permissions into explicit permissions on this object". Your administrators keep their access, and the checkboxes become editable.
  • Click Add, select ru-test and tick the permissions they need, for example Read. Click OK, then the green checkmark to apply the changes.
The attached screenshots show the dialog before and after the conversion. Don't give ru-test permissions on the folders or the other connections, so the rest of the address book stays hidden from them. Once inheritance is disabled, permission changes made on the folder no longer reach SOFTWARE_11, so make those on the connection itself. Setting permissions on address books and folders works the same way, as shown in this guide.

Keep in mind that this only controls what ru-test sees. Whether they can connect is decided on the Host itself, in Host Settings → Authentication → Custom Server Security → Users and access control. Add ru-test there on SOFTWARE_11, and don't add them on the other computers. Restart the Host after the change, because it doesn't re-read the list live. This page covers it.

With 20 users and 160 computers, it's worth granting both kinds of permissions to groups rather than to individual users. Then giving someone access, or taking it away, is a change of group membership on the server, and you don't have to touch the Hosts again.

Hope that helps.
Attached Files
RU Server – Address book permissions for individual connections RU Server – Address book permissions for individual connections RU Server – Address book permissions for individual connections

* Website time zone: America/New_York (UTC -5)