Community

Polina Krasnoborceva wrote:

Hello Max,

Thank you for the provided details.

Could you please let us know if you have tried adjusting the touchpad settings or updating the mouse software on the Viewer's side?
Unfortunately, we cannot reproduce the issue which means that it only manifests itself in certain circumstances.

This is on a desktop PC to other Desktop PC's, no touchpad controls. Mouse is a Logitech M705. I'll let you know if I can reproduce on other PC's.

So then this pop up happens some time later

Could you please clarify if you mean the First connection warning  window? If this is the case, then we are considering the revamp of the First connection warning window along with some other features. However, unfortunately, we cannot provide any specific ETA on this yet.

Yes, that one. I will stop using this feature.

I'm checking the host version (because its not shown in the Viewer, for example)

Actually, it's also possible to check the Host version in the Viewer if you switch to the Details view style:

   
Yes, that is my preferred view I use all the time but a lot of the hosts have blank boxes or out of date. I'm in the process of migrating to a new computer and have my new and old PC side by side. They are using same synchronized address books. Some don't show the same versions for the same hosts. Some don't show any version for some hosts in one viewer and not the other. It's not a reliable place to confirm actual versions. Right now, my new PC has yellow exclamation marks next to 5/7 cloud address books and the old PC, also running viewer 6.12.1, has no yellow exclamation marks on any of the address books.

Install RUT using a silent installer made against 6.10.3. When I went to add the code in 6.12.1, it said I needed to use the same Viewer version as what was used to generate it! Jeepers, that is another strike against the silent installer feature. If I had installed the silent installer, got home and then got this message without an opportunity to manually se t a new password so I could manually add to the Viewer, I probably would just give up on RUT right then and there and move to another solution. Try and only break backwards compatibility on major versions, not on minor versions, I beg you!

I apologize for the inconvenience. We try to maintain as much backward compatibility as possible with each update because we understand that our customers might not be able to update remote Hosts all at once. Besides, we even advise updating remote Hosts in small increments and first test the update procedure on a small sample. There is backward compatibility, however, it's always better to upgrade both Viewer and Host and avoid relying on it.

As for the issue itself - could you please clarify if the issue occurred on another Viewer machine instead of the one where the installation package was configured? If this is the case, you simply need to copy the  keys.dat  file which is an  encryption key  to the Viewer machine where you want to use the  Add using code  feature. This file is located in the  C:\Users\user_name\AppData\Roaming\Remote Utilities Files\  folder on the computer where you originally configured the installation package.
Please try copying this file and pasting it to the same  C:\Users\user_name\AppData\Roaming\Remote Utilities Files\  folder on the Viewer PC where you want to use the  Add using code  feature.
Here's a related  KB article .

Looking forward to your reply.

Now that you mention this, I somewhat recall this limitation when making the silent installer - it's just been so long ago that I last generated it that I forgot. I knew to migrate relay server settings, but on the Viewer side I was only thinking of synchronized address books and that didn't need to be backed up/restored when migrating Viewer PC's.  And now that I know that was the issue, the message pretty much says that, and I just didn't clue in. doh. Only thing to add to that help page, was that after I pasted over the keys.dat file, I had to close and reopen the Viewer to get the Add Code box to appear again. It was appearing before I pasted the keys.dat file but wouldn't appear again until I restarted the Viewer. Then I could add the code.

Gentlemen,

There must be an option to discard same screen shots in screen recorder.

I have seen this option in [censored].

You must add this option to save disk space and to limit log file size with respect to time.

It is very strange not to have this option.

Thanking you.
ruabc

I did just try to upgrade from Host version 6.10.10 to 6.12 beta 2. Everything went far in that I can still connect fine and remote control works, but for some reason the image quality went way down: It seems that the screen from a 6.12 host is only sent in 256 colors rather than whatever is set in the connection properties (65536 by default on my setup, but as far as I can tell, that setting has no effect now). It seems that the fault lies with the Host (installable) rather than the viewer, because the 6.12 viewer displays fine when connected to 6.10.10, but once I upgrade the host to 6.12, I only get 256 colors.

Screenshots sent. Note that before I installed beta, both directions looked the same, after discounting different screen sizes, of course.

If I disable screen blanking, the colors are back to normal. Can the feature be fixed so that it supports blanking while keeping the colors?