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?
Could you please let me know what version of Remote Utilities do you use for Host, Viewer, and RU Server? In case if you use version 188.8.131.52 (version 184.108.40.206 for RU Server) or an older version, could you please try updating your Remote Utilities installation to the most recent version 6.12 Beta 4 (2.9 Beta 4 version for the RU Server) and see if RDP logon information is saved and synced correctly when using the latest version?
The latest 6.12 Beta 4 version (and 2.9 Beta 4 for RU Server) is available for download on this page. When updating please make sure to update both Host and Viewer (as well as RU Server) to the same version in order to avoid the version mismatch that might lead to performance issues or some features not working.
Please let me know if the issue persists when using the latest 6.12 Beta 4 version as well.
I have installed "RU-Server 220.127.116.11 (Beta 4)" and used the "RU-Viewer portable 18.104.22.168 (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've checked on the issue with our developers - this is expected behavior and, unfortunately, we do not plan to add RDP credentials synchronization with the RU Server's side (i.e. for the sync server) in our future updates for security reasons. Sorry for the inconvenience.
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).