Pauline's community posts

Hello,

Thank you for your message.

Unfortunately, this issue is beyond the scope of our technical support. I'm sorry about that.
Please, refer to the Microsoft technical support for all questions related to the TEMP variables.

Let me know if you have other questions.

Hello Ivan,

Thank you for the clarification.

Do you think that this issue affects many users or is it something related to my environment (say OS version)?

It's unlikely that the issue is related to the environment, as we managed to reproduce it on a Windows version.

I am surprised that no one has reported this so far, because with the default cursor settings it is a pain to work with terminals or dark text editors.

I understand. However, while we do have this fix on our wishlist, there are lots of complications and the priority of it is much lower. I'm sorry, but it's unlikely that we will be able to release the fix for this issue any time soon, as we have more pressing priorities to implement.

I'm sorry if this made the program less useful for you.

Hello Martin,

Thank you for your message.

This depends on the Operating System of your device. If the device comes with the Windows 10 Home with the S mode turned on, unfortunately, you won't be able to run RU.
However, if you have upgraded from Windows in S mode to the Windows 10 Home, then Remote Utilities should be running as usual.

Hope that helps.

Hello Andrew,

Thank you for your message.

If you want to migrate to a new phone or if your phone is lost/stolen/destroyed, you can restore your access to the Host by simply deploying a new custom installer with updated 2FA settings.

Hope that helps.

Hello Ivan,

Thank you for your patience.

Unfortunately, it's unlikely that we will be able to implement a fix for the issue any time soon.

I am sorry for the inconvenience.

Hello Erica,

Thank you for the details.

Of course, let us know how the test went. Also, feel free to post another message if you have more questions.

Looking forward to your reply.

Hello Gabriel,

Thank you for your feedback.

We plan to fix this issue in the medium term as we plan to implement an updated process of fetching AD records in the near future.

I am sorry for the inconvenience.

Hello Brett,

Thank you for reporting this.

We will try to reproduce the issue and see what can be done to fix it. Meanwhile, we could use more screenshots or even a short video. You can send them to support@remoteutilities.com or attach the files to your ticket in case you don't want to share them on the forum.

Looking forward to your reply.

Hello Peter,

Thank you for your message.

Please consider using Windows Security as the authorization method for User2. This authorization method allows you to use Windows accounts to authorize on a remote Host. This way, User2 will only be able to log on under his own Windows account and won't have any access to User1's account.
For more information please refer to this Documentation article: https://www.remoteutilities.com/support/docs/security/#Windows_security

Hope that helps.

Hello Ivan,

Thank you for reporting this.

We managed to reproduce the issue and will forward it to our developers to see what can be done to fix it.

I'll keep you updated.