Hi ,

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 ! So the fix works for you?

Thanks for the suggestion, we'll consider this for the next minor release

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.

Could you try reinstalling 1.7.0.80 and checking in Programs and Features again?

Do you got any errors when trying to?

Hey ,

thanks for reporting, we fixed this behavior. Please download the latest 1.7.0.80 and give it a try.

Sorry for the inconvenience with the previous release.

Hi ,

It seems like the issue is caused by one of the latest Windows updates: https://lonelycoding.com/system-directoryservices-accountmanagement-principalcontext-broken-after-windows-10-update/

Could you please check that solution and let us know if it helps? Thanks in advance.

It's released now, could you give it a try?

Good evening everybody,

1.7 is released now! Please feel free to give it a try and let us know how it goes.

Hey ,

The issue should be about the .NET incompatibility, we require .NET 4.5.1, please check that you got it installed or reinstall it (https://www.microsoft.com/en-us/download/details.aspx?id=40779)

Please let me know if it doesn't help

Thanks, I got them, I'll consult with the devs and get back to you shortly

Could you send us the logs from both the machines (Menu-->Diagnostic) referencing this e-mail thread?

Thanks in advance.

Hi ,

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?

Hi ,

Could you tell me, do you use local or Microsoft account to log in to this machine?

Hey ,

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?

Thanks in advance.

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.

Hey ,

Thanks for the feedback, we still got some time before the release, because our QA is testing it at the moment, but we believe it will be released pretty soon.

We'll need to reproduce the issue, I'll get back to you soon.

Could you check what is set here on the destination machine?