Generate an autoregistration.properties file and configure the various parameters before using it along with the default AutomationAnywhereBotAgent.msi file for bulk installation of Bot Agent.

Copy the AutomationAnywhereBotAgent.msi file to the VM instance (golden image) on which you want to install the Bot Agent.
Note: Ensure that you do not restart the VM instance (golden image).

Procedure

  1. After you have generated the AutomationAnywhereBotAgent.msi file, run it.
  2. Validate that the Bot Agent is installed on the VM instance.
    Also review the Services tab in the Task Manager to ensure that the Bot Agent service is not running.
    Note: An autoregistration.properties file will be generated at the following default location:
    C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere\autoregister

    Sample autoregistration.properties file

    url=http://ec2-myexampleCR.com
url2=URL2
url3=URL3
url4=URL4
token=eyJhbGciOiJSUzUxMiJ9.eyJjbGllbnRUeXBlIjoiQk9UX0FHRU5UX0FVVE9fUkVHSVNUUkFUSU9OIiwidGVuYW50VXVpZCI6ImI4ZjVmNDE0LWMzZDMtNGRhNy04NDljLWMxOGUwOGNiM2Q5ZCIsImlhdCI6MTY1NTg3NTgyMiwiZXhwIjoxOTcxMjM1ODIyLCJpc3MiOiJBdXRvbWF0aW9uQW55d2hlcmUiLCJuYW5vVGltZSI6NzMxMDYzMzkwNzQ5NX0.BA2bPiIECl9PE34BC1mj2iePLuTlSd8y8Fe1LtIkOKYrD8mR-KVOnMeupDQF4IQ3oZbjpyk73vrLI2k0UeTVpvKuURbZhz8bPIBYer4zlzRjEB-9nOID8MtNRcpzlXgkQ27GEN2pOn4Xs_k198rPJEYHcTwaHRbQ8Mv5UF0eGd8_Q9sLgZB6jt1BhnzMNS3qwZBl1aG1xbOc7orlfyBfTGSvAxnlsRa3_fF7QeFKiw7EdfJDGsIVmIZ58-IMzer-R8sxMnr7hSfi_aYDx8emyoH2XtFAQAYuXiw6vOXWa1o-TYDtPknIJsga6aAiFJ9-w6ndJAov0JvTClmeyLQgBA
token2=t2
token3=t3
token4=t4
device_type=MULTIPLE_USERS
concurrent_sessions=4
lifespan=TEMPORARY
delay_registration_until_login=true
  3. Edit the autoregistration.properties.
    Various parameters are displayed. Review the following table to understand what each parameter is used for:
    Parameter Description
    url Enter the Control Room URLs for connecting the Bot Agent.
    Note: Ensure that you do not add a backslash (/) at the end of the Control Room URL. For example, mycr.mydomain.com/.
    You can configure up to 20 Control Room URLs and their corresponding registration keys. Ensure that:
    1. You provide the correct registration key for the corresponding Control Room.

      There must be a one-to-one match between URL and TOKEN. For example: The registration key set in AA_TOKEN is generated for the Control Room where the URL is set in AA_URL. Similarly, AA_TOKEN2 through AA_TOKEN20 must match AA_URL2 to AA_URL20.

    2. Do not skip a URL and TOKEN pair midway.

      The values must be filled consecutively in the MSI properties. For example, to configure three Control Room URLs, the following MSI properties must be populated in the specified order:

      AA_URL, AA_URL2, AA_URL3 followed by AA_TOKEN, AA_TOKEN2 and AA_TOKEN3.

    token Enter the corresponding registration key for each chosen Control Room.
    For information on generating or using an existing registration key, see Generate Control Room registration key
    Note: You can configure up to 20 Control Room URLs. Ensure that:
    1. You provide the correct registration key for the corresponding Control Room.

      There must be a one-to-one match between URL and TOKEN. For example: The registration key set in AA_TOKEN is generated for the Control Room where the URL is set in AA_URL. Similarly, AA_TOKEN2 through AA_TOKEN20 must match AA_URL2 to AA_URL20.

    2. Do not skip a URL and TOKEN pair midway.

      The values must be filled consecutively in the MSI properties. For example, to configure three Control Room URLs, the following MSI properties must be populated in the specified order:

      AA_URL, AA_URL2, AA_URL3 followed by AA_TOKEN, AA_TOKEN2 and AA_TOKEN3.

    delay_registration_until_login Enter True to delay the Bot Agent registration to a Control Room until a user logs in to that Control Room.

    If a user logs in to any of the Control Rooms, configured using the AA_URL property, from the device where the Bot Agent is installed, the Bot Agent on that device will be automatically register with that associated Control Room. If the logged-in Control Room URL is not configured, then Bot Agent is not registered with that Control Room.
    device_type Enter one of the following values for the device type:
    • SINGLE_USER
    • MULTIPLE_USERS

    For more information, see Configure device registration.

    Note: Ensure that you enter the property value in uppercase.
    lifespan Enter one of the following values for a temporary or persistent device:
    • TEMPORARY
    • PERSISTENT

    For more information, see Configure device registration.

    Note: Ensure that you enter the values in uppercase.
    concurrent_sessions Enter the concurrent sessions allowed, from 2 through 999. The default value is 2.
    Note: The CONCURRENT_SESSIONS parameter is only applicable for multiple user devices (DEVICE_TYPE = MULTIPLE_USERS)

Troubleshooting

If 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.