Install Bot Agent and register device
- Updated: 2024/05/10
Install Bot Agent and register device
Install Bot Agent on your local device and connect it to Control Room. In order to run bots on that local device, ensure that you add it to the list of enabled host devices.
- Install the Bot Agent, java.exe will be replaced by NodeManager.exe.
- Run a bot, javaw.exe will be replaced by BotLauncher.exe.
- Configure a trigger, the trigger will be activated with TriggerListener.exe instead of javaw.exe.
- Run a bot with Automation Co-Pilot (integrations), javaw.exe will be replaced with ChildSessionLauncher.exe.
Prerequisites
- To install the Bot Agent, the Windows installer policy must be enabled for your local device.
- The read, write, and execute permissions must be enabled for the Bot Agent folders on your local device.
- Ensure that the local device system date and time are in sync with the current date and time so that the device registration is successful.
- Ensure that the following conditions are met:
- The available storage (free disk space) meets the minimum hardware
requirements.
For more information, see Bot Agent device requirements.
- You have write permission to the global cache directory where the bot files are downloaded by default.
- You have the required permission to other folders if the bot logic is trying to write or update data on the local device
- The available storage (free disk space) meets the minimum hardware
requirements.
The Bot Agent version available for download is the latest and compatible with the Control Room version that is used.
- You can now install the Bot Agent on a device with an
existing Enterprise 11 client. However,
ensure that the Automation 360 and Bot Agent versions that you are using are v.25 or
later.
- A Bot Creator can log in and access both Automation 360 and Enterprise 11 client to create bots.
- Attended Bot Runners can run bots from both Automation 360 and Enterprise 11 Control Room instances.
- Unattended Bot Runners can deploy bots by using the run and schedule permission on the same device.
- You cannot run bots from Enterprise 11 and Automation 360 at the same time.
- You cannot install a Bot Agent on a device with an existing Enterprise 10 client.
- When the Bot Agent is installed on a device where Enterprise 11 client is also installed and then you uninstall the client, you might face login issues with the device. Therefore, you must uninstall and re-install the Bot Agent on the device.
- Full access for System user and Administrator group.
- Read, Execute, and List access for Authenticated users.
Procedure
Troubleshooting:
- If you face any issues registering your device, see Automation 360: Error while registering device - An unexpected problem occurred (A-People login required).
- If the Bot Agent service is paused and does not start after installation, see Automation 360 Error: Device is disconnected or needs upgrade (A-People login required).
- If you are using Google Chrome browser version 94 or
later and if you face issues registering your device in a Control Room
On-Premises, we recommend that you configure the Control Room for HTTPS instead of HTTP. Alternatively, use
Microsoft Internet Explorer or Mozilla Firefox to
register your device.
If you face any issues adding a new device, see Unable to Add New Device (A-people login required).
- We recommend that you do not remove the Google Chrome
extension. If you remove the extension, existing Google Chrome policy
will restrict you from adding the extension (online or offline) even after you
reinstall the Bot Agent. However, if you have removed the
extension, use the following instruction to add it:
- Go to the Google Chrome extension store to add the extension online. See Automation 360 extension for Chrome.
- Drag the ChromeExtension.crx file (C:\Program Files\Automation Anywhere\Bot Agent\AABrowserAgent) to the Google Chrome extension tab ( ).
- Similarity, ensure that you do not remove the Microsoft Edge extension as the existing Microsoft Edge policy will restrict you from adding the extension (online or offline) even after you reinstall the Bot Agent. For Microsoft Edge extension store, see Microsoft Edge extension for Automation 360
Watch the following video on how to install the Bot Agent in Automation 360:
Next steps
If your device is set with a proxy, see the tasks that apply to your proxy settings, Connect Bot Agent to a device with a proxy.