If you already have a free license installed in your portable 6.10.10 version, then: Close all Viewers. Copy the config_4.xml from your portable 6.10.10 folder in "C:\Users\[Your_username]\AppData\Roaming\Remote Utilities Files\" folder
Hi Marco, I guess a corruption of the config_4.xml file. This file holds the license key. A newly generated free license is not compatible with version 6.x.
If you still have the old 6.x version license key, you can use it. If not, try the following: Exit the Viewer. Make a backup of your "C:\Users\[Your_username]\AppData\Roaming\Remote Utilities Files\" folder, including subfolders. In that folder, under "backups" folder, you will find a xxx-xx-xx_config_4.zip file. Extract the config_4.xml file and copy it in "C:\Users\[Your_username]\AppData\Roaming\Remote Utilities Files\" folder (overwiting the current config_4.xml file)
Thank you very much Polina for checking it. It's a pity because that makes the synchronized address book useless for us. A solution could be an encrypted address book (RU-Server protected with a password), just as already implemented in the RU-Viewer, thus saving a lot of development work. By the way, the RDP credentials are not secure (base64) in a RU-Viewer address book that is not encrypted (RU-Viewer not protected with a password).
I have installed "RU-Server 188.8.131.52 (Beta 4)" and used the "RU-Viewer portable 184.108.40.206 (Beta 4)", but the result is the same.
The RDP logon information does not seem to be saved at the RU-Server side, but only at the RU-Viewer side locally (on the local copy of the remote/synchronized address book). So if another user (or the same user from another installation of RU-Viewer e.g. other computer) logs in and adds the remote address book, then he/she does not get the correct RDP logon information.
I have set up an address book on a self-hosted RU Server. On RU Viewer, I added the synchronized address book of the RU Server. On RU Viewer again, I exported a large local address book and imported it into the synchronized address book.
Unfortunately, I came into an unpleasant surprise: the RDP logon information of every imported connection, on the synchronized address book, is replaced with the default RDP logon information for new connections of the RU Viewer. Therefore, it seems that the RDP logon information of the connections is not saved in the RU Server address book. Is this a normal behavior and is there a possibility to save RDP logon information on the RU Server centralized address book?