Conrad Sallian's community posts

Hello Keith,

Another question - did you change your cursor settings in Windows (on the Host computer) from Windows defaults to something else?

Hello Keith,

Thank you for your message. Could you tell us the name of the application on the remote Host where the input field is located?

Hello Steven,

Thank you for the information. We will test it out and see if we can reproduce the issue and possibly add the necessary fixes to the mobile client.

Hi Corey,

Unfortunately, we couldn't reproduce the issue. The iOS app works as normal and the keyboard is showing.

Could you please check with the AppStore that you have the latest Remote Utilities version installed.

Hi Frank,

Perhaps, the computer where you are installing the Viewer has issues with msiexec, that's why although the update file is downloaded properly the installation itself cannot finish.

I recommend that you completely uninstall the Viewer, then download the Viewer installer and manually run the installation.

Hope that helps.

Hello Frank,

Thank you for your message.

Is your report referring to installing Viewer or Host?

Hello Steven,

This is what we are currently working on . It may take a few months before the release can be made. Sorry for the delay.

Hi Trent,

That's great to hear. You are welcome!

Don't hesitate to post another message if you need assistance.

Hello Keith,

We are going to release the fix tomorrow, but if you like, you can already test it out. Please, send a message to support@remote-utilities.com and I'll send you a new Viewer exe. You will just need to replace the existing Viewer exe (rutview.exe) in the Viewer installation folder. Hosts are not affected by this bug.

Hello Anne,

You are right, it's a different problem. This problem is caused by our migration to another (more modern) key input mechanism.

However, it seems that we should also keep the option to switch to older (previously used) key input/transfer mechanism just for such occasions.  Some older applications as in this case may experience problems with accepting key input the new way.

So in the upcoming hotfix we'll add an option to switch to legacy key input so you will be able to enable that option in Viewer connection properties for that specific machine.

Sorry for any inconvenience.