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?
We decided to remove this feature from the Viewer to reduce complexity a bit.
Instead, we are going provide a choice in the RU Server installation wizard whether you want to install both Admin Console and Service, or just one of these. This way you'll be able to install the Admin Console on your Viewer PC without installing the actual service/server.
Could you please do the following. I'm assuming that you have installed the latest beta version:
1. Fully exit the Viewer.
2. Access the %APP DATA% folder, "Remote Utilities Files" and cut the file config_4.xml . This is Viewer configuration file, it doesn't contain any personally identifiable or sensitive information. Please, send the file over to us (you can send it to firstname.lastname@example.org).
3. Start the Viewer and try again.
4. If you can, please provide information about what Windows updates were installed. You can get this information in Windows Update settings.