Pauline's community posts

Hello,

Thank you for your patience.

We've released an updated version 7.0.1.0 of Remote Utilities recently. However, I've just tried connecting my Agent to your self-hosted RU Server and your server seems to be offline or not reachable at the moment - the same Agent connects to our public servers with no issues.
Here's what can be done next:
1. Update your Viewer and RU Server to the latest version 7.0.1.0 (and version 3.0.1.0 for the RU Server respectively). The latest version is available for download here. You can also update your installation via the Self-Update feature.
2. Download the latest version of vanilla Agent or configure a new custom Agent package of the latest version.
3. Make sure that your RU Server is online and is accessible from the outside. In addition, please try checking the solutions provided in  this troubleshooting page.
4. Last but not least, please double check if you're able to connect to your Agent using our public servers instead of the self-hosted Server.

Please let me know if this worked for you.

Hello Mike,

Thank you for your message.

Yes, you are absolutely correct, Direct connection is always faster than the Internet-ID connection, so it's recommended to connect via Direct connection when possible. Perhaps, these pages might also provide some helpful information as well:
1. RU overview with a short video-guide.
2. Direct connection.
3. Internet-ID connection.

Please feel free to post another message if you have more questions.

Hello,

Thank you for the clarification.

We will additionally test this out using Windows 7 to see if we can reproduce the issue this time. Meanwhile, could you please provide us an event log file fr om one of the machines wh ere the issue have occurred? Here's how you can obtain Viewer's event logs. You can send the log files to support@remoteutilities.com.

Looking forward to your reply.

Hello Greg,

Thank you for your message.

Yes, of course, such settings should be updated automatically. We will test this out to see if we can reproduce the issue in our environment. I'll get back to you as soon as there are any updates on this or if we will need some additional information on the issue.

Thank you.

Hello Gaute,

I understand your situation and I'm very sorry for the inconvenience, but I simply forwarded the information I've received from our developers on this issue. In fact, I've tried reproducing your scenario as well, but it only works exactly as our developers stated - after I've connected to a remote machine via RDP, I also connected to the same machine via Full Control or via the View Only connection modes and when I switch to the Terminal session in my Full Control window, it simply kicks the other user out of the RDP session. I've tested this with both Windows 10 and Windows 7 just in case.

Sorry for the caused inconvenience once again.

Hello Douglas,

Thank you for your feedback.

As we've mentioned in the previous replies, unfortunately, we didn't update the update mechanism in time to accommodate for major version upgrade and we apologize for any caused inconvenience.
Please note that we do not force any of our users to update to the next major version - we understand that we should put a more clear warning next time for a major version update, however, even if you've already updated to the version 7, you can always easily roll back your installation by deleting the program in the Windows Settings menu - this will keep your settings and address books intact. After this, you can simply download the previous version 6.10.10.0 from our Older versions page and run the installer. In addition, please note that your license key for the previous versions of RU are not expired, it's only not compatible with versions starting version 7, so you can use your license key with the previous version of the program for as long as you wish. Sorry for any inconvenience.

Hope that helps.

Hello,

Thank you for your message.

Unfortunately, we couldn't reproduce the issue - I have just tried updating Viewer of version 6.10.10.0 to the latest version 7.0.1.0 via the Self-Update feature and it worked as expected, i.e. Viewer of the latest version was launched right after it finished updating and I'm able to run Viewer from its desktop icon or the respective icon in the Windows Start menu.
Perhaps, the issue might have been caused by some antivirus/firewall activity. Could you please, try the following and see if this helps to resolve the issue?
1. Fully exit the Viewer File -> Exit.
2. Locate the file config_4.xml in the C:\Users\[Your_username]\AppData\Roaming\Remote Utilities Files\ folder.
Please note that the AppData folder might be hidden by default in which case you need to enable "Hidden files and folders" in Windows Explorer settings.
3. Remove the file "config_4.xml" from the folder.
This will reset the Viewer settings/options. Your address books won't be affected by this action. However, you will need to register Viewer with your license key once again.

In addition, if you have any antivirus/firewall software running on the Viewer machine, please try adding your Viewer installation folder to the exception list as described here.

Please let me know if this helped to resolve the issue.

Hello Greg,

Thank you for your message.

I'm glad to hear you've found the solution! Please note that you can also re-assign any of the available hotkeys, including the F12 hotkey for the "Change view mode" command,  to your custom values - this can be done in the Viewer's Options -> Hotkeys tab.

Hope that helps.

Hello Daniel,

Thank you for the clarification.

We will test running Viewer for Linux on Pop! OS in our environment to see if we can reproduce the issue.

I'll keep you updated on this.

Hello Boris,

Thank you for your message.

We will test this out to see if we can reproduce the issue in our environment.

I'll get back to you with an update on this issue shortly.