Enhance Remote Utilities capabilities with RU Server installed on your premises.
RU Server is self-hosted server software that you can deploy in your organization. The same RU server installation may act as a relay server, sync server, or authorization server, or perform all three roles at once.
NoteSynchronization and authorization roles are only available with the self-hosted server. These features are not available with our public server infrastructure.
The Internet ID technology implemented in Remote Utilities uses a relay (routing) server to help establish a remote connection over the Internet. Our company provides such relay server infrastructure as a default setting for the Internet ID connection type:
However, you can switch from using our servers to using your own RU Server. In this case, you'll need to deploy the server on your premises and configure both sides of a remote connection — the Viewer and the Host — to connect through your server:
In order to save time when deploying Hosts on multiple remote PCs, you can build a custom Host installer and embed your RU Server address (or DNS name) in the settings. Use the MSI Configurator tool built into the Viewer to create a custom Host installer.
Technicians working on a team can synchronize their address books. This means that changes made to the address book by one technician will immediately be seen by the others.
The sync setup process starts on the server. The server administrator creates users, groups and an address book to sync so he can assign users and/or groups access rights to the whole address book, or its specific folders and connections:
Technicians must sign in on the server in their Viewer app. This will ensure they can load and sync the address book:
The specific folders and connections a technician can view and edit depend on what permissions were set for that technician's account on the server:
All Hosts that communicate with the RU Server can automatically be added/imported into your address book. You can assign a specific folder in your address book to be your "inbox" where to put all new connections:
You can then move connections from the inbox folder to other folders in the address book. So long as you do not delete them from your address book, duplication won't occur. That is, the same Host won't be added twice if it already exists somewhere in your address book.
The self-hosted server can act as a central hub for storing user accounts and access permissions data for all your Hosts. When this role is enabled, technicians can connect to remote Hosts in one click without entering access credentials.
To achieve that, the technicians must be signed in on the server in their Viewer app:
Also, the custom server security authorization method must be enabled on the Host side and access permissions must be set:
Important!If you have multiple Hosts to manage you do not have to set permissions individually for each Host. Use the MSI Configurator to set all the necessary permissions and settings prior to mass-deployment.
Administrators benefit from this server role, because it allows them to centrally manage Host permissions without updating settings on each and every Host. For example, if a technician leaves the company the administrator can quickly disable their access using the server interface:
The custom server security authorization method can be used side-by-side with either Remote Utilities security or WinNT security. This means that the same Host can be simultaneously accessed using different authorization methods.