Devices

The device is a machine through which a user connects to the Control Room to create or run bots. Manage devices that are registered to the Control Room through the Devices page located in the Manage tab.

Tasks performed from the Devices page

As a Control Room user with Bot Runner, Bot Creator, and Device pools privileges, use the Devices page to perform the following actions:

View a list of devices registered and connected to the current instance of the Control Room.
Create and view a list of device pools available from the current instance of the Control Room.
Run bots immediately on selected Bot Runners.
If the device is already registered by another user other than the Bot Creator and the Bot Creator does not have the Register device permission or the associated device assigned to it, when you run a bot from the bot editor window, the deployment fails with an insufficient permission error message.
Schedule bots to run on selected Bot Runners.
Run bots on selected device pools.

Notes:

Only an admin user has access to view all the devices in the Control Room. A non-admin user does not have access to view Bot Creators.
Only one Bot Creator can be logged in to a device to run bots at any one time. For a new user as a Bot Creator on the same device, the first Bot Creator has to be removed.

Devices

The Devices page lists all configured devices and the current state for each device listed. Devices are identified by IP and hostname. A device can be in one of the following states:

Connected: Device is logged in to the Control Room.
Note: Wait for 35 seconds for a device to show as connected in the devices list after you remove and re-register the device.
Disconnected: Device is not logged in to the Control Room.
Offline: Device has been unregistered or disabled by the Control Room administrator.

The following actions are enabled:

Connect local device

The Bot Agent is a lightweight application that enables you to run bots on your device by connecting the device to the Control Room. To run bots on a local machine, install the Bot Agent and add the local device to the list of enabled host devices.

Run bot now with checked items

Runs the bot on selected device.

Export checked items to CSV

Exports the data to a CSV file based on:

Filters
Selection

Refresh table

Refreshes the table contents to view the updated status.

Customize columns

Show or hide specific columns.

View and edit device

With the View and manage ALL device(s) permission, you can view and edit the following device settings:

Name
Status
Bot Agent version
Device pool name
Nickname (optional)
Description
Device type (single user or multiple users)
In case of a multi-user device, you can edit the Concurrent sessions supported field.
Add or edit device permissions
Screen resolution
You can set the screen resolution by either selecting a value from the predefined resolution drop-down list or by selecting custom and entering the values.
- You can edit only the nickname, description, device type, and screen resolution fields.
- Ensure that you have selected the Allow devices to override resolution settings option in the Control Room settings for the device level resolution to take effect.
Note: The screen resolution settings are applicable only when you use RDP-based deployments. For regular deployments, a Windows session is created using the existing resolution settings of the device. In this case, the screen resolution set in the Control Room is ignored.
Lifespan
Device lifespan can be Persistent or Temporary. Temporary devices are created to support non-persistent virtual desktop infrastructure (VDI) and are automatically deleted after a specified time when the device is disconnected from the Control Room. You can specify the time to automatically delete temporary devices in the Control Room devices settings.
Persistent devices are created to support persistent virtual desktop infrastructure (VDI) and are not deleted after the device is disconnected from the Control Room.
Auto-login settings
You can customize the auto-login settings for each device. Choose between the settings configured in the Control Room or at the selected device level to either create new user sessions or use existing user sessions after a bot finishes running.
Installation type
This setting is based on whether the Bot Agent is installed at user level or system level on the user device.
Deployment type
This setting is based on the user type and installation type. For single users installed at the system level, the default deployment type is regular. For multi-users installed at system level, the default deployment is RDP.

Preload packages

Use preloaded packages to download the most commonly used or customized packages on your local device. As the packages are saved offline on your device, when you run a bot, the system skips the package download process and starts executing the bot, thereby reducing the bot execution time. You can download specific versions of the package to the user device folder C:\ProgramData\AutomationAnywhere\AAPreloadedPackages.

Device pools

Device pools provide a logical grouping of similar Bot Runners to run bots with the work items from a queue. For example, group devices of a particular department or unit and create a device pool for it.

Automation 360