Pauline's community posts

Hello Asaf,

Thank you for your message.

Unfortunately, for version 1.0.23 you would have to update your Remote Utilities manually.
As for the monitors issue - please try updating your Viewer to the latest version 1.0.24 and see if the issue persists when using the updated version.

Let us know if this helps.

Hi Anish,

This is to inform you that we just released an update for Mac/Linux. Please try updating your Viewer to the latest version 1.0.24 and see if this helps to resolve the issue.

Hope that helps.

Hello Anish,

Thank you for your message.

Could you please open the report provided next time you see the error message? You can copy the report and send it to us to support@remoteutilities.com.

Looking forward to your reply.

Hi Anish,

Thank you for your message.

Please make sure that the mobile device with the authenticator app and the Host PC both synchronize their time from an online source. Double check if the Windows Time Service w32tm is set up correctly on the Host machine as described in this guide.

Let us know if this helps.

Hi Kristian,

Thank you for your message.

Yes, you can absolutely blank a remote screen during a session via the Connection Properties menu and even set up a text that remote user would see on their screen in the meantime. For more information on how to do so, please visit this page.

Let us know if you have any questions.

Hi James,

Thank you for your message.

I’ve forwarded the issue to our development team to see if they’re able to provide any feedback on this.

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

Hello,

Thank you for your message.

What you are seeing is expected behavior based on how Remote Utilities is designed.

The Agent module is intended only for attended, on-demand support and runs under the user account that launches it. If that user logs out or switches to another Windows account (such as an administrator account), the session will terminate. This limitation cannot be avoided when using Agent.

For unattended access and the ability to remain connected while users log out or switch accounts, Host must be installed and running as a Windows service. When installed correctly with administrative privileges, Host operates system-wide and is not tied to a specific user session.

Regarding the connection mode, “Remote Registry” is simply one of the available session modes shown by the Viewer. Full Control can be started after connecting, but it cannot be set as the default connection mode.

In short, Agent is suitable only for temporary attended sessions. If you require persistent access or need to log in to different Windows accounts without losing the connection, the Host module is required.

Hope that helps.

Hi Andrzej,

Yes, Auto in the Connection Properties is the default order of the authentication methods Viewer will try to connect to a Host. If possible, please check what authentication methods are enabled in the Host Settings -> Authentication tab. You can also use the Remote Settings feature to do so.

Looking forward to your reply.

Hi Andrzej,

I’m glad to hear we were able to help and it works for you now!

I guess he has to leave his PC without any user on the log screen next time.

Could you please let us know what connection method and authentication method are used to log in to the remote Host? Are you using Host module or Agent?

Looking forward to your reply.

Hi Andrzej,

Thank you for your message.

Please try enabling the Use legacy capture mode option in the Host settings -> Other tab and see if this helps to resolve the issue. Make sure to restart your Host after enabling the feature to apply the changes.

Let us know if this helps.