Bot Agent device requirements
- Updated: 2024/10/28
Bot Agent device requirements
Review the Bot Agent device requirements such as hardware components, compatible devices, supported operating systems and browser extensions.
Hardware requirements
The Bot Agent can be installed on devices that meet or exceed the following hardware requirements:
Device | Processor | RAM | Storage (free disk space) | Network |
---|---|---|---|---|
Single user machine |
CPU (Intel Core i3 2.6 GHz) with 4 multi-core or higher (vCPU) 64-bit |
|
|
|
Multi-user machine | CPU (Intel Core i3 2.6 GHz) with 4 multi-core or higher (vCPU) with two extra core for every additional user. | 4 GB per additional user |
- 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.
Device compatibility
A device running the Bot Agent to perform automation must meet the following requirements:
- Device requirements are different for the Control Room and Bot Agent.
For Control Room compatibility, see Operating system, environment, and platform supported for Control Room.
- For your device
to work properly on Amazon WorkSpaces, update the registry on all workspace
machines by renaming the spacedeskHookKmode.sys file to spacedeskHookKmode.sys.old in C:\Windows\System32\drivers. Restart your machine and verify
that
STXHD Hosted Application Service
is not running.For more information, see Troubleshooting Amazon WorkSpaces issues.
- If the deployment type for your device is set as Regular, you will not encounter any issues with bot deployments in Amazon WorkSpaces. If the deployment type for your device is set as RDP, you must enable RDP sessions on Amazon WorkSpaces for successful bot deployments. To enable the RDP sessions on Amazon WorkSpaces, see How to connect to WorkSpace with RDP.
- If you encounter any issues while connecting your device
to the Control Room, we recommend that you review one of the
following::
- Proxy auto-config (PAC) file
- The time zone that is set on the Bot Agent device and Control Room server are in sync with the Time server as per the respective time zones of the machines.
For information on troubleshooting this issue, see Unable to connect device to Control Room (A-People login required).
- On-Premises machines
- Physical machines running on supported operating systems.
- Terminal servers
- Remote desktop (RDP) running on supported operating systems from Enterprise A2019.11 or later.
- Virtual machines
- From Enterprise A2019.09 or later, the Bot Agent can be
installed on all virtual machines (VMs) with supported Windows OS.
For AIsense recorder to work on a VM, enable AVX instructions for both Bot Runner and Bot Creator.
For details, see Automation 360: AI Sense Recorder is crashing (A-People login required).
The Bot Agent is certified on all major versions of VMs and supports the following:
Environment Operating System and edition Amazon Web Services Elastic Compute Cloud (EC2) - Microsoft Windows Server 2022 (Standard and Datacenter)
- Windows 2019 Server (Standard and Datacenter), and Windows 2016 Server
- Windows 11 (Enterprise)
- Windows 10 (Professional)
Amazon Web Services WorkSpaces (4 vCPU, 16 GB memory). Note: For more information on choosing the correct Core Windows bundle, see Amazon WorkSpaces Core PricingHowever, if you are using the Amazon WorkSpaces Core Windows Bundles with Bring Your Own License (BYOL), see Bring Your Own Windows desktop licenses.
- Windows 2022 Server
- Windows 2019 Server
- Windows 11 (Enterprise)
- Windows 10 (Professional)
Google Compute Engine - Windows 2019 Server (Standard and Datacenter), and Windows 2016 Server
- Windows 11 (Enterprise)
- Windows 10 (Professional)
Microsoft Azure Virtual Machine (VM) - Microsoft Windows Server 2022 (Standard and Datacenter)
- Windows 2019 Server (Datacenter)
- Windows 11 (Enterprise)
- Windows 10 (Professional and Enterprise)
If the Windows OS certified for your Bot Agent is also supported on Microsoft Azure VM version, then Automation 360 will support that Windows OS on Microsoft Azure VM.
For information on the Windows versions certified with the Bot Agent, see Operating system compatibility.
Azure Virtual Desktop - Windows 11 (Enterprise)
- Windows 10 (Enterprise)
VMware VMs on ESXi 7.x/8.x - Microsoft Windows Server 2022 (Standard and Datacenter)
- Windows 2019 Server (Datacenter)
- Windows 11 (Enterprise)
- Windows 10 (Professional and Enterprise)
If the Windows OS certified for your Bot Agent is also supported on an ESXi version, Automation 360 will then support the ESXi version for that Windows OS.
For information on the Windows versions certified with the Bot Agent, see Operating system compatibility.
Citrix XenDesktop (VDI) Windows 2016 Server Citrix VM - Windows 10 (Enterprise)
- Windows 2016 (Server)
VMware Horizon Windows 10 (Enterprise) Windows 365 Cloud PC Windows 11 (Enterprise) Note: Multi-user deployment is supported only on the server based Windows versions.Note: When you install the Bot Agent on virtual machines, ensure that you change the virtual machine Power and Sleep settings to Never so that bot deployments from the Control Room can run without interruption.
Operating system compatibility
You can install the Bot Agent on machines running the following operating systems.
This compatibility applies to On-Premises, Cloud deployments, and Community Edition of Automation 360.
- Only 64-bit operating system version is supported.
- Bot Creator tasks are supported with all the listed operating systems.
- The Bot Agent cannot be installed on Linux systems. You cannot register a device that is running on a Linux system. 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 | Attended Bot Runner | Unattended Bot Runner | Bot Creator |
---|---|---|---|
Windows Server 2022 | Supported | Supported1 | Supported |
Windows Server 2019 | Supported | Supported1 | Supported |
Windows Server 2016 | Supported | Supported1 | Supported |
Windows 11 (Enterprise and Professional) | Supported | Supported1 | Supported |
Windows 10 | Supported | Supported1 | Supported |
Windows 8 2 | Supported | Supported | Supported |
Windows 7 2 | Supported | Supported | Supported |
- (1) Auto-login
- Auto-login is only supported on 64-bit systems.
- (2) Supported OS
- Windows 11 (64-bit) supported on Automation 360 Build 15459 or later.
Browser compatibility
The user interface for Bot Agent is through a browser. Log in to Automation 360 using the supported browsers to install and register your device.
For a list of supported browsers, see Supported browsers
Supported extensions
When you connect your Bot Agent device to the Control Room, you can enable supported extensions from your browser to record automations.
For a list of supported extensions, see Extensions for automation
Auto-login support
Auto-login is used to automatically log on to a device, run a scheduled automation, and restore the device to its original locked or logged off state after running the automation.
For operating system support specific to auto-login on Bot Agent devices, see Auto login support for Bot Agent