Conrad Sallian's community posts

Hello Bretislav,

Thank you for your message.

Could you please clarify if you mean the background setting in the Agent configuration process?

BTW, the manual is going to be updated very soon.

In a sense, yes. By using the IP filter on the RU Server you narrow the list of remote IP addresses with which the server is allowed to communicate. But then again, the IP address of the Viewer or Host may be changing - for example, when the Viewer is installed on a laptop and the laptop travels with its owner often.

So it is only recommended to use the filter if you are sure that Viewers and Hosts fall into a certain IP range and will stay in that range.

Nate, in fact you can even distribute a Viewer with a synced address book that way. This is because the sync properties that you specify for an address book in the Address Book Manager are static/same (server and port) and because of the fact that the address book on the RU Server always takes precedence over a local one. So if the local one is outdated (e.g. the Viewer you distributed hadn't been open for a long time) it will simply download the latest address book from the server the next time the Viewer is run.

Hi Nate,

I see. There is a workaround though. Just follow these steps:

1. Download the portable Viewer

2. Unpack the downloaded archive to your local disc.

3. Run the rutview.exe in the folder and populate the address book with records - either manually or (if you already have an address book file created in a different Viewer) use the Tools -> Import Connections command. Close the Viewer.

4. Distribute your folder to whatever machines you want to run Viewer on and run the Viewer executable whenever you want to run the Viewer (you can create a shortcut on Desktop just like for any other file).

I'm assuming that you are using the General address book. In this case you don't have to touch the Address Book Manager at all (it's in the Tools tab).

However, if you want to create a separate address book alongside the general one, you'll need to add one more step. Namely, to add a relative link to your address book file in the address book manager. See this thread  https://www.remoteutilities.com/support/forums/forum1/437-problem-using-portable-viewer

Let me know if you have any questions. Thanks.

Hello Nate,

Thank you for your message.

No, you can configure the Host MSI only. For the newly installed Viewer, there are three ways to populate the address book with records:

1. Manually adding them using "Add computer" button.

2. Importing address book records using a corresponding button on the toolbar (Import Tools -> Import Connections).

3. "Plugging in" existing address book file via Address Book Manager (Tools -> Address Book Manager). The address book can reside on a local resource or a shared resource. Finally, you can connect to an automatically synced address book located on the RU Server.

This tutorial explains all the details about sharing address book: https://www.remoteutilities.com/support/docs/address-book/

Hope that helps.

Thanks for the input, Jeff! I will attach this information to the test case.

Hi Peter,

Thanks for pointing that out. We'll try to reproduce this issue and will think about how to fix it.

Hello Peter,

It's because of the absolute path. Please, do the following:

1. Open Address Book Manager, create a new address book and save the xml file to the folder or USB disc where your portable Viewer is located. The book should reside in the same folder with the rutview.exe.

2. Now select the newly created address book in the Address Book Manager and click Edit. In the path field remove the path and all slashes except only the file name itself.

3. Close the ABM. Now the path to your secondary address book is relative, and so it should open regardless of the disc letter.

Hope that helps.

Hello Tu,

Thank you for your message.

IP filtering for ID connection doesn't make sense because this connection is established through our servers. Anyone who knows the ID and password of the remote computer can connect to it.

Perhaps this year we'll also add a two-factor authentication.