Hello Paul,

This is a really interesting issue indeed. Never encountered it before so we would need some Diagnostic Info from both of the machines to take a look. Please send them to us via Main Menu - Diagnostic and please mention this thread in the description. Thank you.

Hello Spires,

It seems that the Remote Assitant Service wasn't removed correctly, this usually might happen if there were not enough permissions for the installer to reach it. I would suggest trying to remove it manually via services.msc and re-installing the 2.3 running it from an elevated Admin account.

Hello,

Thank you for suggesting those features, I will discuss it with our R&D and some of them might get on the development roadmap.

Well this is exactly the case where one typo changes the whole point :) Sorry Joel I meant

and this shouldn't be really hard to upkeep.

Hello Alex,

Thank you again for noticing it, already discussing it with R&D.

Hello Alex,

This is definitely a bug, I have reported it to our R&D and it will be reviewed and added on the development roadmap. Thank you for noticing it, I have a possible workaround to try, let me know if you are interested and I will send it to you directly.

Hello Pavel,

Yeap, we were able to recreate the scenario with the Windows Updates, we will see how can we go with it further. Thank you for bringing it up.

Hello Joel,

Well I personally agree with you, however, there are some factors that also affect the ID generation and storage so far we are monitoring those processes and surely thinking about other cases where we can affect this.

Hello Alan,

Thank you for suggesting it, from my side I can promise you to bring up those suggestions on our next Dev meeting and maybe they will get onto the development roadmap.



Perhaps you are right, but there is a slight chance due to the fact that we use Amazon SES and this should be really hard to upkeep.

Hey there Daniel,

I replied to you in the e-mail, but for other our customers I should mention that the Menu is located in the Display Switch section. Thank you for bringing it up.

Hello Niklas,

I have looked up the case from our side and reproduced it also. This behavior is normal, previously we basically kicked you out of the session in case of using Unattended Access, now we just warn you that you will break up the session of the user that is currently logged in. If the application is running not as a service you can connect via PIN and join the current session. We understand that this is not obvious and we will re-work the mechanism and the text you are seeing. Thank you and let me know if you have any questions. Cheers!

Hello Tony,

Thank you for the informative follow-up, I will pass the info to our developers to take a look and use it in the development process.

One question Niklas, have you updated the remote part?

Hello Thomas,

Not yet, but this feature is already on our development roadmap and we are actively working on it.

Hello,

We have this feature on our development roadmap, however, no ETA yet. We will definitely announce it widely when it is ready.

Hello Pavel,

Were there any Windows updates before the ID changed? I think it might be related to this.

I have sent you the reply once again, it should arrive in a few minutes.

Hello Steve,

I cannot promise I will get you the class names, but I will show it to our developers definitely. Thank you for bringing it up and I will get back if I will be able to procure class names.

Hello Rich,

We are really sorry to hear about your situation, we have communicated with you via a ticket and I have sent you a follow-up that RA has nothing to do with that.

Hello,

In this case, I would suggest trying the Unattended Access feature, it looks like a UAC problem which interferes into the process of controllign the machine. I would suggest either running the host side of the RA from Admin or if you are using Unattended Access set the service execution to Admin one manually. Hope it helps, let us know how it goes after those settings.

Hello,

Well if everything goes well I presume you will be able to see it's BETA release until summer. But this is subject to discuss and change as the development process is really complex.

Hello,

First of all, I would suggest using the Unattended Access feature, which will get rid of those access issues and view-only mode and provide a much more secure way of working with the remote machine:

https://help.msp360.com/cloudberry-remote-assistant/using-remote-assistant/encryption-and-unattended-access

As for the taskbar, can you post a screenshot? Not really sure I understand how it looks, thank you.