Oh, yeah, I just wanted to say that they are different all the time and ask what version you could get identical keys with. We never faced any issues like this.

That's right, and that's what I'm trying to show, they are always different, for every machine and every time you regenerate them. Please let me know if I'm missing something from the question.

Thanks for the feedback! We'll take this into account.

As far as I understand, your biggest concern is about the keys not changing

Here are the two keys and I'm not sure if they are equal:

"PFJTQUtleVZhbHVlPjxNb2R1bHVzPnpWVDlRUVgwcFVYdlBSbUNVUy9teGVGQjRQNy9tWlM4a3RzN2ZHNGNtamkwRSttUmU2a051N2M4THpCTGZtRlEyS1h3ZmkwV1g2MkkwNm5aV0NnN3hNQnI1TzNUKzExUGY0WHZ4YzZpdjAweFVaeXVlUmxycUlmOHhLaUdNbDArdENacFczSHBRd2RFUkRTQloxNXY3ZGdsZ0EweXRWZTRraXpMZ0VOUVBZNmt4czNwVjh5NXV5Y1VZZ2IwM2lGaEpFTGFGaSs2RkFKVDJGcHNnWEk1TlJjTXJtSG9uM1ZHTm15SjNFazZMd0w5ZkhaWUpzZTc0OFJicFh6b2dhQkEwWndZc2lyUkVzTWprT3VqbDJiZHlQdHVmTjI1NlRoc25LRWF3QUpKUWEwa0VVTHRRQkFhSmE0ODFnK2NVNnd6TUpXRm45VnRBOG1DMlZpOGVubEJUUT09PC9Nb2R1bHVzPjxFeHBvbmVudD5BUUFCPC9FeHBvbmVudD48L1JTQUtleVZhbHVlPg=="

"PFJTQUtleVZhbHVlPjxNb2R1bHVzPnB3eTdDQ3NYRTFGaC8yMkw0ajBtVEFoK0JXNkpxSHQ1WncwOStVRWJVaThOczZXQnZnVFdadWFiSzF6cFNYQ09md0ZOZk44eWlRclZSeUZVclZneDhuVlF3S1o0OFYyWENHMlNzaG1ndWw2dGJ5L3A5MlZwME80SUNlalNxQ2FvbzVOMXBmUHNld3JzWkJXanhzRnN2NkFBbVBITG01eTNhV01LSksyZDVFcmdIMUtTdkFxWldiSDZLNHNDbEpFTyt0SVNrRWs3YVVCWXNkSVZ0SVgwSzl2bk00ckxiVWRTeGRCL2pGS3FaV3B2TzN6blFUN3Z6Yk5pZnhPNU5qby9KaFpDU3dCem9GL3hrR2hscEU3ZWNBRUt2bFpYZnNTR251U0ZRRndjUzZIRVU1eGdhWDMzUGx5OG5xNDUweFY0TE5mNzlZcllpb1dtZXI5TkppT3lvUT09PC9Nb2R1bHVzPjxFeHBvbmVudD5BUUFCPC9FeHBvbmVudD48L1JTQUtleVZhbHVlPg=="

Please let me know what version do you use?

Thanks for your suggestion, we'll definitely consider this.

At the moment it works so, that we're reading all of your requests (that's me usually) and counting them in our bugtracker, that's how we prioritize them and understant that they are "important".

We'll take your suggestion into account and discuss internally, thanks for your initiative.

BTW, the biggest upcoming features are listed on the product page

, ,

This is the most complicated activation method actually, it was created for some very strict networks, who only want to whitelist a very short list of things.

By design, there's no manual activation, the activation code is included with the name of the installation package and is executed automatically. However, we still show the activation code on the download page after you pressed "Download". Also, we have "I don't have activation code" button, which will also be way easier, as mentioned. Could you tell me why do you prefer this method?

Thanks for the feedback!

You can unpin it (very left icon on the toolbar)
You can restart it and in case unattended access is configured you'll be able to connect again, but we'll introduce some automatic solution for sure
On the roadmap, we'll add this soon
On the roadmap as well.

Thanks a lot once again!

.

Remote Assistant starts as a service actually, (you may see CloudBerry Remote Assitant Service in services.msc) however Service Control Manager might be killing it in case your Network Service starts too slowly, we have improved this with the latest update (<a href="http://1.7.0.138" target="_blank" rel="nofollow">1.7.0.138</a>), could you upgrade and check if it's better now for you?

All of the machines are saved in the history, see screenshot below, but we'll definitely improve the list in the future.

File transfer in Remote Assistant can only be "pro-active" which means that you would need to "send" the files from one PC to another instead of trying to download them.

Please let me know if you have any remaining questions.

No problem, thanks for the feedback.

The easiest way to do that would be to edit the display name on the host. Please go to Menu-->Options-->General, change the display name and establish one more connection. After that, the display name will be changed on the client as well.

We got a video showing the utmost part of the functionality, though, please check it out and let me know if you got any remaining questions: https://www.youtube.com/watch?v=rmhOS8bP0Yw

Perfect, thanks for the feedback!

Please try unpinning it (the very left icon), then it should fade away and only appear if you hold the mouse on it's place.

Check the following video out: https://youtu.be/rmhOS8bP0Yw?t=251

Please let me know if it's not too helpful.

Could you explain what happens when you try to in more details?

Great, thanks for the feedback!

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

Please let us know if this doesn't help.

Perfect, glad it worked for you!