Ideally the bot agent needs to be installed by an user who have admin privileges, this will provide the bot agent the administrative privileges to make changes to a service.
Also ensure the bot agent service is running on “local system”
Article to refer: https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/control-room/devices/cloud-add-local-device.html#:~:text=All%20users%20of%20the%20device%20can%20use%20this%20Bot%20Agent.%20However%2C%20users%20installing%20the%20Bot%20Agent%20must%20have%20administrator%20privileges.
Ideally the bot agent needs to be installed by an user who have admin privileges, this will provide the bot agent the administrative privileges to make changes to a service.
Also ensure the bot agent service is running on “local system”
Article to refer: https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/control-room/devices/cloud-add-local-device.html#:~:text=All%20users%20of%20the%20device%20can%20use%20this%20Bot%20Agent.%20However%2C%20users%20installing%20the%20Bot%20Agent%20must%20have%20administrator%20privileges.
@Jose Marin : your bot id should have full read and write access for the botagent installation directory, you do no not need complete admin access for whole VDI / runner machine.
Thks to all of you for your ideas/solutions…, Have tested the bot with an user with the permissions as admin and worked as expected, now we ae worwing in checking the pemissions to give the minimun required in order to have it running…
Again, Thks for pointing / giving me to the solution.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.