More information about Portable Viewer is available here. Also, we highly recommend that anyone using the portable Viewer enables address book encryption as a means of protection against unauthorized access to remote computers in case the USB stick is lost or stolen. This is especially important if the "save password" option is used on remote connections in the address book.
However, in the event that my private server goes offline, I'd like it to be possible that the connection falls back to the public server. It doesn't matter if the Internet ID has to be different for each server (which I'm guessing will be necessary).
Unfortunately, there is no fallback server functionality in RU. The reason is that the effort and complexity of implementing such feature (the more complex a feature the more likely it may fail) far exceeds potential gains. RU server is supposed to be used under direct command of the user/customer. If the server doesn't respond the user can simply restart the server - whether it's the machine itself or the RU Server service and it'll be back up and running in a couple of minutes.
For the same reasons, I'd like to be able to do the same using the Agent host as well. Also, I like to have the Agent and the preinstalled host available on a remote terminal (again as a backup), but it appears that the Agent won't launch if the Host service is already running.
Host and Agent are mutually exclusive. In the future we'll add the ability to "convert" one to the other, though. But this is not a solution to this problem. If you want to be 100% sure that you have a back up remote connection method, you should use another remote software. Unlike some of our competitors we never claim that our program is necessarily "the best" or "the fastest" and that there may not be a possibility of something going wrong. So you can use Remote Utilities as your primary tool and yet have another tool as secondary backup tool for emergency.
For example, antivirus software may all of the sudden decide that our Host is dangerous and start blocking it. We know that this is not true and we are very quick to report this to the a/v vendor. Yet, it may take some time for them to remove the detection (and for your a/v endpoint software to update their database). Fortunately, false positives of this sort are very rare nowadays.
I guess one work around for the Agent tool specifically would be to us the MSI configurator to build multiple Agent packages - one with the public server preset, another with my private server?
It is possible. In this case each running Agent instance will overwrite the registry settings of its predecessor on the computer where it is run (see more about Agent settings here here ). I recommend that you experiment with different configurations.