Hi @MJ 8116 ,

Could you please confirm whether you have individually running the Control Room in each machines or are you trying to add all 14 machines to a single CR?

If the answer is second one, Community edition will not support more than 1 device to be connected with the CR.

Hi @MJ 8116 

If you are trying to configure each machine with a individual Community CR login it will work, not other way around.

If the above point is valid, uninstall the existing bot agent and try installing as a admin and then try connecting to the device.

Adding to the above, checkout below links for setting up Bot Agent and Community CR limitations,

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/release-notes/cloud-A2019-faq.html

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/control-room/log-on-to-control-room/cloud-register-community-user.html

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/deployment-planning/cloud-community-capacity.html

Hi @Padmakumar ,
We are trying to setup each device individually for each user, when you say adding all 15 machines to a single CR does it mean our company has a specified number of CR?.

The users actually tried to configure using their personal computer but got the same error, so I guess it’s not the CR issue.
Each user has their own community access and has their own computer that they can use.

Thanks

Thanks @MJ 8116 for the clarification, think your team is going in a right way.

Can you ask the team to install bot agent as a admin and try connecting to the CR? Hope they are providing user credentials as per below steps,

1. Open cmd
2. Type whoami
3. Copy the domain\username as a username

@ChanduMohammad This is exactly what we were doing but using our community access not the trainee access. Do multiple logins can cause this issue?

This has been done just a few minutes ago and we always get the same error. We tried it on multiple computers and laptop.

Multiple logins using one single account in the same machine will not cause any issue

This is strange, hey can you try once again using below steps,

• Uninstall Bot Agent
• Delete files in C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere
• Download and install Bot Agent again
• Complete the Device registration instructions shown on the screen

How about multiple logins in different machines? But I did try not to do it simultaneously.

Alright will try this and I’ll let you know, Thanks.

Might be @MJ 8116 

In the above comment will delete existing AA folder so we can do a clean installation

Welcome

@MJ 8116 restart VDI and try to connect again.. it may be the SSL cert issue… if thats the case you have to execute SSL cert update 

Thanks @rbkadiyam will try this tomorrow.

Hey @rbkadiyam they are using Community CR, still should we check on SSL?

Hi team, 
Thank you for your support, we opted to use our training environment in A360 instead of using the community edition.
Cheers!

Welcome @MJ 8116