Read and Review Automation Anywhere Documentation

Automation 360

Close Contents


Open Contents

Perform bulk installation of Bot Agent on devices

  • Updated: 2022/09/16
    • Automation 360 v.x
    • Explore
    • RPA Workspace

Perform bulk installation of Bot Agent on devices

Edit the Bot Agent MSI file to bulk install (or silently install) the Bot Agent on permanent and temporary devices such as on-premises machines, virtual machines (VM), and non-persistent virtual desktop infrastructure (VDI), for example Citrix, in the Control Room.


To perform this task, you must be a Control Room administrator and have the required rights and permissions.

Ensure the following requirements are completed:
  • Bot Agent setup and MSI files are downloaded from the Control Room and the parameters required to install devices are available in the Bot Agent MSI file.

    If you are not able to access the MSI files, contact support on

  • Windows 10 Software Development Kit including Orca and Control Room are installed on your device.

    You can install Orca from C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\Orca-x86_en-us.msi.

Sample file: You can find a sample file at the end of the page for your reference.


  1. Use the latest AutomationAnywhereBotAgent.msi file from the following locations:
    • Download the file from the Control Room (Administrator > Settings > Bot agent bulk install).

      The download option is available for On-Premises and Cloud deployments.

    • Select the file from the <application filepath>\crui\asset folder. For example C:\Program Files\Automation Anywhere\crui\asset

      This option is available only for On-Premises deployments.

  2. Edit the AutomationAnywhereBotAgent.msi file using the Orca tool.
  3. Click the Property option.
  4. Enter appropriate values for the following parameters:
    Parameter Description
    AA_CRTOKEN Enter the registration key that is used to install the Bot Agent on multiple devices at a time in bulk.

    The registration key is provided by the Control Room admin.

    See Generate registration key to install Bot Agent in bulk.

    AA_CRURL Enter the Control Room instance to which the Bot Agent will to be connected.
    Note: Ensure you do not add a backslash (/) at the end of the Control Room URL. For example,
    AA_DEVICE_TYPE Enter one of the following values for the device type:
    Note: Enter the values in uppercase letters when you install the Bot Agent.
    AA_LIFESPAN Enter one of the following values for a non-persistent or persistent device:
    Note: Enter the values in uppercase letters when you install the Bot Agent.
    AA_CONCURRENT_SESSIONS Enter the concurrent sessions allowed, from 1 through 99. The default value is 1.
    AA_INSTALL_ONLY Choose whether you want to install the Bot Agent without registering with the Control Room.
    • Enter True to only install and not register the Bot Agent.
    • Enter False to install and register the Bot Agent.
    AA_DEVICE_POOL_NAME Enter a value to accept the device pool name and add the device to the device pool. The default value is 0.
  5. Save the changes.
  6. Copy the AutomationAnywhereBotAgent.msi file to the VM instance (golden image) on which you want to install the Bot Agent.
  7. Run the AutomationAnywhereBotAgent.msi file.
  8. Validate that the Bot Agent is installed on the VM instance and Bot Agent service is not running in the Task Manager Services tab.
    Note: An file will be generated at C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere.

To deploy the Bot Agent on temporary or non-persistent devices, you must configure the SysPrep settings and create machine images on the VM instance.

  1. Shut down the VM instance without SysPrep after you enable temporary or non-persistent computer name settings for the VM.
    For an example of how to use SysPrep on AWS EC2 instance, see Use Sysprep to create and install custom reusable Windows AMIs.
  2. Create machine images on the VM instance as required.
    For an example of how to create Amazon Machine Images (AMI) from an AWS EC2 instance, see Create an AMI from an Amazon EC2 Instance.
If a Bot Agent is registered in the VM instance by mistake, perform these steps to restore the machine image:
  1. Uninstall the Bot Agent from the Windows Control Panel of the VM instance.
  2. Delete all files from C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere.
  3. Enter True for the AA_INSTALL_ONLY parameter in the AutomationAnywhereBotAgent.msi file that you previously used to install the Bot Agent.

Sample file


Next steps

Validate that the devices are added on the Control Room Devices page.