Hardware requirements for registered devices

You communicate with the Control Room, through a registered local machine (device). Bot Creators and Bot Runners use the registered devices to create and run bots. Part of registering a device with Automation 360 is installing a Bot Agent.

Note: You cannot install a Bot Agent on a device with an existing Enterprise 10 or Enterprise 11 Enterprise Client.

The Bot Agent can be installed on devices that meet or are equivalent to the following hardware requirements:


Device	Processor	RAM	Storage (free disk space)	Network
Machine	Intel Core i3 2.6 GHz with 4 multi-cores or higher 64-bit	4 GB (Minimum) 8 GB (Recommended)	32 GB Add 100 through 150 KB per Automation Anywhere script Add 40 through 50 GB per long-term project	5Mbps (Minimum) 20Mbps or higher (Recommended)
Additional users on a multi-user device	2 CPU per additional user	4 GB per additional user	No additional storage required	No additional network needed

Additional RAM requirements for the registered devices

Add additional RAM to account for applications and services running on the registered devices, for example:

Microsoft Office applications (example: Excel)
Browsers (example: Google Chrome)
Enterprise applications (example: CRM, Oracle EBS, and SAP)
VDI infrastructure applications
Anti-virus software
AISense Recorder

Additional disk space on registered devices

Automation 360 scripts average approximately 100-150 KB. Additional free disk space is required to develop automation projects because temporary files such as screenshots, server logs, and audit files are created during the execution of the automation scripts.
Free space required increases with the project size. Recommendation: Have at least 40-50 GB of free disk space for each long-term project.
Increase storage space configuration after installation, as needed, depending on product usage. For example, depending upon the complexity of your bot, generating log files and logic creation require additional disk space later.

Additional CPU or processor on registered devices

AISense Recorder: Additional CPU or processor is required on a device if the existing CPUs are utilized by customer applications. It is also required in case of a VDI infrastructure where CPU or processors are shared across the infrastructure.

Platform compatibility for registered devices

A device used to connect to the Control Room and perform bot tasks must meet the platform requirements.

Note: Platform requirements are different for Control Room and Bot Agent.

Registered devices: Physical machines that you want to use for creating bots or deploying bots and running any of the supported operating systems.
Terminal servers: Using remote desktop (RDP), running any of the supported operating systems is supported on Automation 360 Version A2019.11 or later.
Virtual machines: Bot Agent is supported on all VMs where the supported Windows OS has been hosted on Version A2019.09 or later. For example, Virtual Desktop Infrastructure (VDI) are supported on Amazon Web Services, Microsoft Azure, Google Cloud Platform, VMware virtual machines, and Oracle Virtual Box.

Supported operating systems for registered devices

A device used to run the Bot Agent, connect to the Control Room, and perform bot tasks as a Bot Creator and Bot Runner must meet the operating system requirements.

Note:

Only 64-bit operating system version supported.
Bot Creator tasks are supported with all the listed operating systems.
You cannot register a device that is running on a Linux system. The Bot Agent cannot be installed on Linux systems. However, you can use a registered device running on a Windows system to access a Control Room that is installed on a Linux system.


Windows version	Windows edition	Attended Bot Runner	Unattended Bot Runner	Bot Creator
Windows Server 2019	Datacenter and Standard	Supported	Supported¹	Supported
Windows Server 2016	Datacenter and Standard	Supported	Supported¹	Supported
Windows Server 2012	Datacenter and Standard	Supported	Supported ¹	Supported
Windows 11	Enterprise	Supported	Supported¹	Supported
Windows 10	Professional and Enterprise	Supported	Supported¹	Supported
Windows 8 ²	Professional and Enterprise	Supported	Supported	Supported
Windows 7 ²	Professional and Enterprise	Supported	Supported	Supported

(1) Auto-login

Auto-login is only supported on 64-bit systems.
If the Auto-login fails, configure the Local Security Policy settings. For example, in Windows, select Security Settings > Local Policies > Security Options. Enable the Interactive logon > Do not require CTRL+ALT+DEL option.
Recommendation: Enable the Interactive logon > Do not require CTRL+ALT+DEL option to ensure your device is able to bypass the screen to create a user session.
When you deploy a bot from the Control Room on a device, Bot Agent receives the deployment and creates an interactive user session for deployment. If the option is disabled, the Bot Agent will not be able to bypass the screen to create a user session. Therefore, we recommend you enable this option.
For more information, see Why does the policy (Interactive logon: Do not require CTRL+ALT+DEL) need to be enabled for Auto Login to work? (A-People login required).

(2) Supported OS

Windows 8 (64-bit) supported on Enterprise A2019 Builds 1598 and 1610 or earlier.

Windows 7 (64-bit) supported on Enterprise A2019.12 or later.

Supported browsers for registered devices

The user interface for Automation 360 is accessed through a browser. Log in to your device, and then log in to Control Room through a browser.


Browser	Browser version
Google Chrome	57 or later
Microsoft Internet Explorer	11

Automation 360 Bot Runner device requirements

Hardware requirements for registered devices

Additional CPU or processor on registered devices

Platform compatibility for registered devices

Supported operating systems for registered devices

Supported browsers for registered devices