Pauline's community posts

Hello,

This is to inform you that we've managed to reproduce some issues that you've reported in your initial post. We will implement fixes for the reproduced issues in our next update. The updated version of Remote Utilities will be released approximately by the end of next week. Sorry for the inconvenience.

Please let us know if you have more questions.

Hello,

Thank you for your message.

Unfortunately, this is expected behavior of Agent as it's a module intended to be used for spontaneous, attended-only remote sessions.

For the described scenario you can use Host instead as it allows unattended reboot and can start automatically at the remote machine's startup, as well as allows you to control UAC prompts remotely. In case if you don't want to use Host for security reasons, please note that there's a number of settings for enhancing Host's security, including 2-factor authentication and the Ask user permission feature that prompts the remote user to accept or reject an incoming connection.

Hope that helps.

Hello,

Thank you for the clarification.

Please try switching Current user to System or vice versa in the Access menu of the File Transfer connection mode and see if this works for you.

Hope that helps.

Hello Alan,

Thank you for the update.

Please feel free to send us the archived files to support@remoteutilities.com for examination.

Hope that helps.

Hello Pedro,

Thank you for your message.

I've just tested the RU Server's version 3 executable file and it launches the installation process as expected. Could you please let us know if you have any antivirus software running on the machine where the issue occurs?
In addition, please try using this Microsoft Tool that helps to automatically repair issues that might be preventing you from installing/updating, or removing programs.

Hope that helps.

Hello Arnaud and Boris,

Thank you for your messages.

As Boris has correctly mentioned, this is rather expected behavior - Direct connection can be only established if your Host and Viewer are located in the same LAN/VPN.
In this case, we recommend that you access your remote Host machine via the Internet-ID connection - please also note that Remote Utilities has a built-in mechanism that detects direct route between Host and Viewer and, if available, uses it automatically.

Hope that helps.

Hello Michael,

Thank you for your message.

As David has correctly noted, we've previously released a few beta versions for the public test. Since the major version 7 of Remote Utilities was released we haven't been reported any critical issues that might have rendered Remote Utilities completely unusable. There was a minor issue in version 7.0.0.0 that only caused somewhat frequent disconnects, but we've fixed this issue in just a few days and released an updated version 7.0.0.1 with the implemented fix.
In case if you encountered some issues after updating Remote Utilities, please feel free to refer to this blog post that provides more details on the new features/improvements. We also encourage our users to check our Knowledge Base as it provides solutions for the most common issues that our users might encounter.
In case if you still experience the issue, please feel free to elaborate on it a bit more, so that we're able to assist you in resolving it. We're always happy to help.

David, thank you for your input on this.

Please feel free to let us know if you have more questions or need our further assistance.

Hello Kerry,

Of course, we're always happy to help!

Please feel free to let us know if the issue persists or if you have other questions.

Hello Marco,

Yes, sometimes the Host installation might be interrupted, for example by some firewall/antivirus software activity.

Please feel free to let us know if there are any updates on the issue.

Hello Alan,

Thank you for the provided upd ate.

We need to run "start Host" each time the computer restarts. In the settings for host, it is se t to automatic and is se t to automatic in "services".

This seems like the issue might have been caused by the Host installation files or the Host service being somehow damaged/corrupter (most probably by the firewall software activity).
Please note that the Host service must be running on a remote machine in order for the Host to work properly and the service should start automatically by default unless you changed manually.

Before we can proceed to further troubleshooting, please try referring to this KB page to see any of the listed solutions help to resolve the issue.
Namely, please additionally double-check the following:
1. When uninstalling Host please make sure to also remove the folder C:\Program Files\Remote Utilities - Host\ and restart your PC before re-installing Host.
2. Please make sure to add the Host's installation folder to your antivirus software exception list as described here.
3. If your remote Host machine is running on Windows 8 or Windows 10, please make sure to disable the Turn on fast startup feature as described in the article linked above.

Please let me know if any of the solutions worked for you or if the issue still persists.