Pauline's community posts

Hello Rob,

Unfortunately, the full silent install is only possible when using the One-click package option that allows not to ask for the confirmation before the installation by enabling the Do not ask for confirmation before installation checkbox on Step 3 -> Other tab of the configuration process.
Silent installation is also possible via using the /silentinstall command line parameter (for more information please see this page).

Please let us know if you have more questions.

Hello Rob,

Thank you for your message.

You can mass update the Hosts via the Remote Install Tool as described in this tutorial for Advanced update method that allows you to update or change the existing Host settings.

In order to specify another server for the Hosts you want to update, you only need to create a custom MSI installation package using the MSI Configurator tool:
1. On Step 3 - Advanced options of the configuration process enable the Set or update Internet-ID connection settings checkbox.
2. Select one of the following radio-buttons depending on the intermediary server you want to use:
Use default (public) Internet-ID server — to use our company's servers for Internet-ID connection
Specify custom Internet-ID server — to specify your custom self-hosted RU Server
3. Enable the following checkbox: When updating existing Hosts, overwrite their Internet-ID server address with the specified address. This will allow the installer to replace the current Internet-ID server address of the existing Host installation with your selected Internet-ID settings.
For example, Step 3 - Advanced options window should look like this:


Finally, please select this custom MSI package in the Remote Install Tool window.

Hope that helps.

Hello Max,

Thanks for the provided details.

So, not reproduced. I'll see if I have any more hosts I can try.

Of course, please let us know if the issue reoccurs again.

Yes, that works. It was unchecked by default. After enabling it, I was able to connect and type into the password field to login.

I'm glad to hear this worked for you!
As for the mouse pointer focus problem - I've forwarded the issue to our developers and asked for their input on this. I'll get back to you soon with their reply.

Note, the connection isn't slow, just the time to establish it in the first place is slow, in my opinion. I think its the authorization being set to "auto". By default, they are se t to auto. When I connected to 3 hosts, I could see it do the first of 5 attempts, fail and succeed on the next attempt. This all takes like 12-13 seconds or more.

Thank you for the clarification. Auto is just the recommended setting for the Authorization method when it's set to Auto, the Viewer tries authorization methods in the following order:
1. Custom Server Security (CSS)
2. Windows Security
3. Remote Utilities Security
4. Single password
However, I will additionally check with my coworkers if the Authorization method being set to Auto can affect the time that it takes to establish a connection or if there's something else that might be affecting it.

I figured out why I thought I upgraded a bunch of hosts but wasn't reporting 6.12.1. It actually failed and I just didn't realize. I'd suggest making the failure more noticeable, like red text instead of the same blue.

Of course, I will forward this to our development department to see if we can improve the installation log in our future updates. Thank you for the suggestion!

I'll get back to you soon with updates on the issues above.

Hello Roger,

Thank you for your message.

This warning prompt is usually caused by starting a connection via Microsoft's RDC using a .rdp file that was not digitally signed by a trusted publisher.
Could you please clarify if you use the RDP connection mode or is it the RDP-over-ID?
In addition, could you please also double check if it's still possible to connect to any of these remote Host machines using the Full Control and View connection mode?
Also, please let us know if the remote Hosts were installed using a default vanilla installation file downloaded from our website or if it was installed using a custom installation package, configured via the MSI Configurator tool? In the latter case, could you please confirm if the installation package was built using the Online or Legacy option?

Looking forward to your reply.

Hello Derek,

I'm glad to hear we were able to help!

Please let us know if you need any further assistance.

Hello Max,

I'm glad to hear we were able to help!

Why can't the Viewer monitor the status of the upgrade and so it knows when an upgrade is successful and therefore can immediately know the version, or the host does a callback with the version info? I complained about this in the past and thought there was a plan to improve on that in the future...

Of course, there are definitely some improvements planned for the update process, namely, the process of the Host version's number fetching after the update and the upgrade status as well. We have already partially implemented some of them back in April, however, we still have this improvement in our roadmap and will do our best to implement it as soon as possible. Sorry for the inconvenience.
Could you please also confirm if the Hosts were successfully updated but the Viewer was showing the wrong version?

But the biggest issue I'm having is not being able to mouse click anything and then when I reconnect, only getting a black screen.

Could you please let me know if you have the Use legacy capture mode feature enabled in the Settings for Host -> Other tab? If not, could you please try enabling it and see if it helps to resolve the black screen issue?
In addition, please also double-check if you have the Monitor driver installed on the Host's side. If it's installed, please try uninstalling the driver as it's only needed for the blank screen feature. You can check if the Monitor driver is installed in the Settings for Host -> Driver tab.
Here's also a related KB article that might be helpful.

It's regularly MUCH, MUCH higher with RUT than any other remote access program.

Please try referring to this KB article regarding the troubleshooting of the slow remote connection speed. If you have already tried the solutions listed there but none of them helped to resolve the issue, then you might send us the Host log files for the examination. The Host logs can be found in the C:\Program Files (x86)\Remote Utilities - Host\Logs\ folder. In addition, you might send us the Viewer log file as well, it might help to diagnose if there are any connection problems on the Viewer side.
Please send the log files to support@remoteutilities.com and do not post them on the forum.

Looking forward to your reply.

Hello Derek,

Thank you for the clarification.

Could you please confirm if I'm right in assuming that you're setting the FPS value in the Color and CPU window that you invoke on the toolbar in the Full Control window?


If this is the case, please try setting the FPS value in the Connection properties window that is invoked in the main Viewer window (i.e. from the address book). The FPS value is greyed out if the CPU usage is set to any other value than FPS. Please try setting the CPU usage value as FPS and then changing the FPS value itself. In this case, the FPS value is saved for this remote Host.


Please let me know if this worked.

Hello Nijel,

Thank you for your input on the issue.

Hopefully, it will be helpful for future users who might encounter the issue with the AdwCleaner.

Please let us know if you have more questions. We're happy to assist.

Hello Derek,

Thank you for your message.

Unfortunately, we could not reproduce the issue. Could you please clarify if you have the FPS value set to 1 in the Connection properties for a specific remote Host machine or in the Default connection properties?
In addition, please let me know what version of Remote Utilities do you use?

Looking forward to your reply.

Hello Max,

Thank you for your feedback.

It would be better if the viewer could update hosts to 6.12 instead of 6.10.10. You're going to get less beta testing if you need to manually update it out of band on the host directly instead of remotely.

Actually, it is possible to update Hosts remotely via Viewer. In order to do this, please consider using the Advanced update method via the Remote Install Tool as described in this tutorial. You only need to download the latest Host .msi package, i.e. in this case, the 6.12.1.0 (Beta 1) version and then sel ect it within the Remote Install Tool window:

when I click into a Viewer session, the initial mouse click is several inches to the left of where I click, and its super frustrating when you go to click into a window and your click takes effect somewhere else on the screen, taking the main window out of focus.

Could you please let me know what options are selected for the cursor in the Connection properties -> the Cursor tab?

I just did a host upgrade over RDP from 6.10.10 to 6.12.1. It was in the process of installing, I walked away and when I came back, the final screen saying the installation was finished was 90% off the screen and needed to be dragged back to the center of the screen.

Could you please also let me know if it's possible to check if the issue re-occurs when updating another remote Host via RDP or Remote Install Tool as described above? I've just tried updating Host both ways and, unfortunately, couldn't reproduce the issue - the installation window did not move fr om its initial place.

Looking forward to your reply.