There are multiple ways to share the same address book, they are described in this section. So long as you are already using the Server, then the best way to sync the book will be through the server. I highly recommend then that you start using the 6.5 beta version (downloadable here), because in this beta the entire sync mechanism and security model has been changed and vastly improved as compared with the current stable version and previous versions.
Don't hesitate to ask me if you have other questions.
Unfortunately, it is how it works on Windows 7. The new monitor driver that we implemented in the recent beta version and that fixes many issues with "blank remote screen" feature only works starting Windows 8/10.
So I shut down Webroot, started the service and it's been connected now for more than an hour! Although I do have to report a few minutes ago the icon for the host is no longer in my taskbar, though the service is still running and I can connect/logon. I do have rutserv.exe, rfusclient.exe, ripcserver.dll, and rwln.dll all on the Allow list in Webroot. I restarted Webroot and within a couple minutes the service crashed.
So we found the reason. I'm afraid the only remedy here would be to contact Webroot and report this problem. We do our best to keep the number of false positives low, but as you can see there is always something that slips through the cracks. A/V companies usually pay little attention to their fellow software developer requests, but they will listen to you - their customer.
Once I used Windows control panel to remove the host, and when I reinstalled the beta it already had the old internet-ID and custom host
For complete uninstall you also need to delete the Host settings in the registry. The registry key you need to delete is HKEY_LOCAL_MACHINE/Software/Usoris.
I think we need Host logs from at least a couple of beta Host PCs that had issues connecting. The beta version has an extended/more informative Host log so that I think it will shed the light on this issue. You can find the Host logs in C:\Program Files\Remote Utilities - Host\Logs\
And another question - do you have Webroot installed on all those Host PCs?
Can I not run both the viewer and host at the same time on the same PC?
Of course, you can. They won't affect each other - each module only performs its own role.
This PC is different from my RU server, but when I'm running the Viewer my host is not connected and if I restart the host it'll stay connected for maybe 5 minutes then drop. When I say drop I cannot see it connected to the RU server in idle connections plus the dot next to whatever the blue thing is in the icon is no longer there. It still shows running still in the taskbar. I left for the weekend and could not connect to this host and I was using the viewer before I left. Something doesn't seem right, not with it dropping every 5 minutes and never reconnecting.
I'm afraid it could be a "post hoc" assumption/mistake. It's very unlikely that Viewer can affect the Host's ability to connect.
And FYI, Webroot is blocking/quarantining the rutserver.exe files now. I was trying to manually install the beta host on a few PC's running the older version and I had a heck of a time getting it to install (had to run multiple times, even when I figured out I needed to disable webroot while I installed). And it seems all those PC's I installed the beta host onto this weekend had connected for 5 minutes but now do not show connected to my server.
Webroot told us a week or so ago that they fixed the issue. Please, make sure that you have your Webroot signature bases updated to the most recent version. If you still have issues, please let us know we will contact them again. Just like many of our users and customers we can't help but wonder why antivirus software companies are incapable of adding a certain specific file (signed and checked) into their white list once and for all :)
I see this in regarding the host service crash in my event log (stayed connected only 1 minute)...
I will forward this to our developers and request their input on the matter. We need to figure out why the beta Host crashes on your system. It is a windows 10 machine with the latest updates installed including Anniversary, correct? Also, did you try to completely uninstall and re-install the beta Host?