The hardware and software requirements presented in this document refers to the minimum and recommended resources needed for one robot to run automations. Workflow complexity and additional software installed on the machine might affect the robot's performance.
|CPU||2 x 1.8GHz 32-bit (x86)||4 x 2.4GHz 64-bit (x64)|
|RAM||4 GB||8 GB|
|Disk Space||3.5 GB for new installations, 5 GB for upgrades (including temporary files required during installation)||N/A|
You can also check out hardware requirements for Studio and Orchestrator.
|Operating System||Windows 8.1|
Windows 8.1 N
Windows 10 N
|Microsoft Azure Windows 10 Enterprise Multi-Session||Works in conjunction with Azure Virtual Desktop (AVD) as well.|
|Windows Server 2012 R2|
Windows Server 2016
Windows Server 2019
Windows Server 2022
|Windows Server Core 2016|
Windows Server Core 2019
Windows Server Core 2022
|Can run background unattended jobs.|
The jobs run under the local system account by default. To use a specific user (credentials specified in Orchestrator), you need to configure the
|Citrix environments||XenApp v6.5 or greater|
|XenDesktop v7.0 or greater|
|.NET Framework||Version 4.6.1 or greater||If your machine runs Windows OS in a language other than English, install the corresponding language pack for the .Net framework version you are using.|
This is required for running Studio in any of the available languages. The .Net framework and related language pack version must correspond, and any conflicting .Net framework versions installed on the machine should be removed.
|Web Browsers (for browser automation)||Internet Explorer v8.0 or greater|
|Google Chrome version 64 or greater||Automated with the extension for Chrome or the Webdriver protocol.|
|Mozilla Firefox version 52.0 or greater||Automated with the extension for Firefox or the Webdriver protocol.|
|Microsoft Edge on Windows 10 version 1803 or greater||Automated with the extension for Edge.|
|Microsoft Office (for projects created in the StudioX profile)||Office: 2013|
1 When using unattended robots on Virtual Machines, do not leave the Azure Virtual Desktop sessions in
disconnected state (user is connected to a host pool in an AVD environment, but they are still connected to the session hosts). The robot is not able to use the disconnected session as it was created via AVD and does not have access to it. Because of this, it attempts to create a new session to run the unattended job, but fails because the AVD session is already created and in
disconnected state. When this scenario happens, the job eventually fails due to a time out.
Updated 16 days ago