Conrad Sallian's community posts

Hello Keith,

Thank you for your message. Could you please send the Host logs to support@remoteutilities.com.

Hi Jorge,

In the previous version that you have (6.x.x.x) the logs folder is located in: C:\Program Files(x86)\Remote Utilities - Host\Logs.

Only examining the logs can tell why you cannot connect using the Internet-ID.

Hello Jorge,

Our servers are up and running and according to monitoring data there were no downtimes. Could you ask the remote user to look into the Host log. You can be located in: C:\ProgramData\Remote Utilities\Logs

Matthew Cooper wrote:

@Conrad, could you advise what the host log entry would look like if the software restarts itself? I can then do a thorough search and see if it has taken place.

Hi Matthew,

There will be a line:

Remote Utilities - Host [version] is started. GMT[time_zone]

Hi Martin,

Thank you for the kind words. Yes, Host for Mac/Linux will also be availalbe.

Hello,

Beta 17 for Mac and Linux has been released. An issue that would (in some circumstances) cause authentication errors has been fixed.

Craig Golucki wrote:

Please use my contact information on my account to continue this conversation further. I sent an email to your privacy@remoteutilites.com as well.

Hello Craig,

We haven't received anything to privacy@remoteutilities.com so far. Could you please resend your email?

Also, with regards to your previous posts within this thread, and specifically the post where you voluntarily share logs and (possibly) other information that in some jurisdictions may be considered as personally identifiable . We would like to repeat our disclaimer here as is stated by our privacy policy:

Personal Data Shared on Forums

We value the privacy and security of our users' personal data. In compliance with the General Data Protection Regulation (GDPR), particularly referring to recital 85, we acknowledge that a breach of personal data can lead to serious consequences such as loss of control over personal data, discrimination, identity theft, financial loss, and other privacy violations.

However, it is important for users of our forum to understand that any personal data they voluntarily share within the forum posts, comments, or discussions is publicly accessible. While we take reasonable measures to protect the privacy and security of information processed through our services, we cannot control or be responsible for the protection of information that users choose to share publicly.

This section of the privacy policy is intended to inform you of the risks associated with the sharing of personal data in our forum and to clarify our position and responsibilities. By using our forum, you acknowledge and agree to these terms.

User Responsibility

   Voluntary Disclosure: If you choose to disclose personal or sensitive information within our forum, please be aware that this information becomes public. We strongly advise against sharing any details that could compromise your privacy or security.
   No Liability for User-Shared Data: Please be advised that in the event of any breach or unauthorized access to the personal data that you have voluntarily shared in the forum, we shall not be held responsible. The responsibility for the security of such information rests with the individual who has chosen to share it.

Mike G wrote:

Ahh, it's clear now. Thanks for your continued help Conrad!

You are welcome! Have a great weekend ahead.

When does this message pop up with the pro licence, at custom MSI install? with host simple update or remote install? or every time we connect to a client host? I don't mind the message, I just need to warn customers if they are going to see it.

Also does this affect the Agent as well?

Hello Mike,

I'll be using the terminology from this page:

If the requirements for temporary alert  are met, Host will show the alert to the remost user. If the connection is established from a Viewer registered with a Pro license, the alert has a timeout and a button.

Now the alert will go away forever for this given Host if either of the requirements are met:

- The remote user clicked on the button
- 10 minutes have elapsed.

It should be noted that if the remote PC has been restarted before the time on the button rans out, the next time it will be all over again. Technically speaking, the flag is set only if the alert is 'handled' explicitly (i.e. via a timeout or by clicking  the button).

Once this happens, the alert is never shown again on the same computer unless you wipe the Host settings, that is.

Hope that helps.

Hello,

We've released a minor update (beta 16) to the beta version for macOS / Linux , both Viewer and Host were updated. This update fixes the issue with character duplication when sending keystrokes from Viewer on macOS/Linux to Agent on macOS.

If you are updating to beta 16 make sure that you update both Viewer and Agent. Download pages:

macOS
Linux