Thanks for the suggestion, we definitely got this on the roadmap and will implement it in future, we had a couple of obstacles and got a couple more at the moment, overall, I believe we'll get this done this year.
In case both the instances are on 1.7, this message means that we couldn't connect to our servers. Please check that you got your firewall open for ports 80 and 443 and ra.cloudberrylab.com
At the moment we don't have the option to regenerate it in GUI, but you can do this manually. Please navigate to C:\ProgramData\CloudBerryLab\CloudBerry Remote Assistant\RaSettings.xml and find the following string:
<Id>999999999</Id>
Then delete the whole string, save the file, relaunch the app and here's your brand new ID.
Thanks for the details. 1.7 and 1.6 are not compatible as long as we changed the network architecture a lot to make multi-regional authentication possible as stated in the FAQ. Please make sure all of them are on 1.7 and let me know if this doesn't help.
At the moment we close the session in case it was not active before our connection and leave it open in case it was. We will consider making this optional for future releases, but the current one seems to be the most secure and reasonable, that's why we designed it this way. Could you share your use case, please?
Could you provide us with some more details on the second machines specs like what is the OS, is it physical or virtual, does it have the keyboard connected?
It seems like there's nothing valuable in there and it's all about the current architecture. We're working on the release at the moment and we believe it will resolve your issue.
Please let me know how it goes when we release it.