Pauline's community posts

Hello,

Thank you for your message.

Please make sure that you've selected Agent as the output package on Step 2 of the configuration process as the Show disclaimer at startup feature is only available for Agent and not for Host. For more information please also see this page.

Hope that helps.

Hello,

Thank you for your patience.

Yes, this should be possible - in fact, I've just tested this scenario out just to make sure. However, there are a few important details to note:
1. When installing Host remotely while connected to the remote machine via Agent, the Agent window will stay opened till one of the last steps of the installation process, then it will automatically get closed, so your current connection will be interrupted.
2. At the installation step when the connection interrupts, a remote machine gets a prompt requesting to set up an access password. Since you won't be connected at this point, we recommend that you prepare a One-Click installation package and install Host using it instead of vanilla installer.
3. When configuring a One-Click package please make sure to enable the Send Internet-ID to email feature and set up the SMTP server along with the following checkboxes:
- Automatically generate Host password
- When updating existing Hosts, overwrite their Internet-ID code with the generated code
These features will ensure that you receive an automated email with your Host's access credentials, so that when your connection via Agent is interrupted, but Host is installed and starts running, you can connect to it right away using the credentials.
4. Last but not least, in case if you had any previous Host installations on this remote machine, please make sure to remote the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities Host\. This will remove any traces of the previously existing installations' settings, so that the password is generated during the installation process.
5. Here's a guide on how to add the remote Host to your address book using the encrypted code you receive via email.

Hope that helps.

Hello John and Zach,

Thank you for your messages.

It appears that access to our servers at id.remoteutilities.com is being blocked by Malwarebytes. However, we've noticed that some of our users have already submitted this False Positive to them and the Malwarebytes team has responded that this will be fixed soon in their next database update. Please also see this post on the Malwarebytes forum.

Zach, please note that we've already responded to the ticket you've submitted. However, meanwhile please try adding the DNS name id.remoteutilities.com that points to our Internet-ID servers to an exception/allow list and see if this helps to resolve the issue.

Please let us know if you have more questions.

Hello Mitchell,

Thank you for the clarification.

So what does it mean if there are multiple events per month with: Remote Utilities - Host 69110 is started.

This entry simply means that the Host service was started - by default Hosts automatically starts along with the system. The "69110" number points to the Host version - in this case, it's version 6.10.10.0.
You can check if the log file contains any entries about remote sessions - if someone has connected to this remote machine and when. Such entries can be identified by their name, for example, Remote screen connection. Started.
In the Host log you can also find what Internet-iD code was used and what connection modes were used.

In case if someone got unauthorized access to this computer you should contact your nearest police department and let them know about the case so that they could investigate this further. We can provide our server logs (information that contains the originating IP address which is stored on our servers). However, please note that the  server logs can be only provided if there's a direct request from the police. Here is an excerpt from our Privacy Policy:

Government and law enforcement agencies

We may also share information to (i) satisfy any applicable law, regulation, legal process, or governmental request; (ii) enforce this Privacy Policy and our Terms of Service, including investigation of potential violations hereof; (iii) detect, prevent, or otherwise address fraud, security, or technical issues; (iv) respond to your requests; or (v) protect our rights, property or safety, our users and the public. This includes exchanging information with other companies and organizations for fraud protection and spam/malware prevention.

This is strictly within the law and international treaties and also conforms to our Privacy Policy. Please feel free to provide our contact information privacy@remoteutilities.com to the police - we will gladly provide our assistance to the investigation.

Please let us know if you have any questions.

Hello,

let's say i have a machine, that is used by an employee.
that employee is NOT allowed to have the administrator password for that machine.

As soon as we implement the feature that allows converting Agent to a Host installation, it will be possible to do directly within the remote session. Unfortunately, we cannot provide any specific ETA on this feature.

Meanwhile, you can restart Agent with elevated (admin) privileges by using the Restart Agent as... feature that allows you to control the UAC prompts on the remote machine when you perform actions that require administrative access (for example, installing software). In case if you want to install Host you can also configure a custom MSI installation package or a One-Click installer and enable the Send Internet-ID to email feature that sends an email with the Host's access credentials to a specified email address upon the installation.
Alternatively, if you want to install Host on a domain or across your Windows network, you can also push-install Host using GPO or use the Remote Install Tool.

Hope that helps.

Hello,

Thank you for your message.

--> user01
Error #67
Unable to connect a network drive.
The network name cannot be found

This error usually means that the admin$ (admin share) isn't found or unavailable on the remote PC. Admin$ is required to be available whenever you need to push-install Remote Utilities (or any Windows software) onto a remote machine. For more information please refer to this guide.

it seems to be running but take a look at this snippet.

Please note that you should also have a rfusclient.exe running on the Host machine in addition to the rutserv.exe process as these processes must be running in order for Host or Agent to work properly. For more information please also see this page.
If the rfusclient.exe is not running or you cannot locate a corresponding file in the Host installation folder, then the issue might be occurring doe to some file in the Host installation folder being somehow damaged or corrupted (perhaps, by some firewall or software activity). Please try fully uninstalling Host as described here and please make sure to clean up the previous installation traces, then restart remote PC and install Host from scratch. After installing please make sure to add the Host installation folder C:\Program Files (x86)\Remote Utilities - Host\* to the exception list as described here.

In addition, please make sure that the Host service is running on the remote machine as it's required in order for the Host to work properly. You can identify the service as Remote Utilities - Host. Here's a related guide on the Host service that might also provide some useful information.

Hope that helps.

Hello,

Thank you for your message.

Unfortunately, running Host and Agent at the same time is not currently supported by Remote Utilities. However, I'll forward your request to our development department for a review to see if it's possible to implement this at some point in the future. Sorry if this makes our software less useful for you.

i found this post, but not sure what it means?

The feature mentioned in the referred post is already in our wishlist and, once implemented, it will allow users to convert a running Agent to Host, i.e. the Host will be installed automatically with all Agent's settings imported to the new Host installation.

Hope that helps.

Hello,

Thank you for your message.

This issue might have occurred due to some kind of False Positive which might block/restrict Remote Utilities or block access to our servers. Most of the times the end user is not notified of this type of security software (or ISP) activity, so it seems like there were no changes that might have caused the issue.

Could you please let us know if you have an antivirus or firewall installed on your remote Host machines or somewhere on the perimeter? If yes, then please make sure to add Remote Utilities installation folders to the exception lists as described here.
In addition please make sure that the outbound TCP ports 5655 and 443 are not blocked or used by another software since these ports are required to be opened (or at least one of them) in order for the Internet-ID connection to work properly. For more information on ports used by RU please see this page.
Last but not least please make sure that the DNS name id.remoteutilities.com which points to our servers is not blocked anywhere on your network or at the ISP level.
Please also try referring to this troubleshooting guide that might provide some helpful information.

Hope that helps.

Hello Michael,

Thank you for your message.

Please note that our Free License does not restrict you to a specific workstation - the only limitation for the free license users is that they can only add up to 10 remote connection to their address book.  For more information on the Free License please refer to this page.

In this case, if your Viewer is not minimized to the taskbar, then the issue might be occurring due to some files in the Viewer installation folder being somehow corrupted (perhaps, by some firewall/antivirus software activity). Please try the following:
1. Fully uninstall Viewer on the machine where you get the "Error: Another user is using this copy of R-viewer" error message as described in this tutorial and make sure to clean up the previous installation traces.
2. Re-install Viewer.
3. Make sure to add the Viewer's installation folder C:\Program Files (x86)\Remote Utilities - Viewer\* to the exception list as described here.
4. Run Viewer and see if the issue persists.

Hope that helps.

Hello Martin,

Thank you for the clarification.

We do not plan to stop supporting the 9-digit Internet-ID codes as we do our best to maintain as much backward compatibility as possible. However, we do recommend upgrading the 9-digit codes to the 12-digit ones to improve the overall stability of the connection.
Since you’ve mentioned that you have other Hosts with the 9-digit Internet-ID codes of version 6.10.10.0, then it does seem to be an issue caused by the Host’s outdated version. In this case, simply updating Hosts might help to resolve the issue without actually generating new codes.
However, if you would like to replace the older Internet-ID codes anyway, you can do so with the help of Remote Install Tool which allows you to update the Host remotely along with updating its settings. You simply need to configure a custom MSI installation package to use with the Remote Install Tool.
I’m order to generate new Internet-ID codes please make sure to enable the Generate a new internet-ID code and When updating existing Hosts, overwrite their Internet-ID code with the generated code checkbox - these options will ensure that new Internet-ID code is generated upon the installation. You can also enable the Send Internet-ID to email feature which will automatically send an email with access credentials to a specified email address.
Here’s a related guide with detailed description for each feature in case it might provide some helpful information as well.

Hope that helps.