Weird :) Well, indeed requiring only way to log in is strange. But I can guess that they do that to ensure their reviews are coming from real people (i.e. their staff visits the LinkedIn accounts and verifies it's authentic).
But thank you for your great review nonetheless. If you don't mind, we will put it on our home page, there is a dedicated review section.
Unfortunately, most connectivity problems arise on the Host side rather than on the Viewer side. If you cannot access a remote Host this means that the Host has issues connecting to our intermediary server. This might be caused by a number of reasons, such as antivirus software update that blocks the Host, the Host service hanging or not working properly or the Host installation being corrupted for some reason.
It's unlikely that you will be able to troubleshoot the issue while on the Viewer side. You'll need to get to the Host side anyway.
Speaking of potential customers - we recently registered our software on G2Crowd and Capterra. These services have become quite popular recently as they help people choose software and provide generic reviews. If you have time to write a short review (just a few lines would do) about Remote Utilities, we will much appreciate it. See the links to review form in my signature.
It speaks well of the Remote Utilities software and documentation (beautifully done) that there is so little activity in the forum of such a widely used product. (Potential customers: do yourself and your organization a big favor and get this software.)
Thank you for the kind words. Yes, we receive few support tickets and forum posts relative to our user base, but that has always been our primary strategy. We are planning to further improve and update our documentation and also provide some fresh video tutorials soon.
It would be useful to be able to modify the title of a forum posting after the post has been submitted.
This can be done by an administrator. So if you need to update the title, just send me a message through the forum (via PM) and I'll do that.
Under Host Setting > Security > Users and access control, I would change "User name" to "Remote utilities user name" to quickly distinguish it from the Windows user name.
That makes sense. Anyway, the Host settings window will be significantly revamped soon. When we'll be making this change, we'll keep in mind this suggestion.
4. Under point 5 of number 3 above regarding "Permissions for individual users can be overridden by global permissions set on the Modes tab."
I think this is incorrect. When a mode is disabled on the "User Access - RUT Security" window and enabled on the Security > Advanced > Modes tab, the statement states that the mode is enabled for the user when in fact it is disabled. The Modes tab setting (enabled) does NOT override the "User Access - RUT Security" setting (disabled).
It seems a connection mode is enabled for a particular user only if is enabled both on the Modes tab and on the user's "User Access - RUT Security" window.
Yes, for a connection mode to be allowed for a specific RU user it should also be allowed in global settings on the Mode tab. In other words, the Modes tab serves as a global "switch" to quickly block any undesirable permissions for all users.
Perhaps, we need to rephrase the documentation quote above then.
As a software user myself I know that even a small issue can be annoying when the related feature is used on a daily basis. So no problem with your letting us know your concerns. The more, the merrier :)
But if you'll allow me one more comment, can you simply enable changing connection modes by clicking a connection mode icon on the ribbon without affecting the current behavior?
This won't work, unfortunately. I.e. a click on a connection button on the ribbon should only do one action. But we'll consider if we can add an option to Viewer settings which would allow to switch from one behavior/system to the other.
(Don't forget to update your documentation that I cited earlier to reflect the change disabling the behavior we are discussing.)
Yes, some articles in the documentation still require updating. We will do our best to finish with that soon.