Operating system, environment, and platform supported for Control Room

Automation 360 can be hosted on AWS, Microsoft Azure, Google Cloud Platform, IBM, and any public, private, or hybrid cloud service that meets the Control Room and Bot Agent hardware and software requirements.

Automation 360 is currently certified on AWS, Google Cloud Platform, and Microsoft Azure. For Bot Agent operating system and platform compatibility, see the Bot Agent compatibility matrices in Bot Agent compatibility.

Automation 360 supports the 64-bit version of the Microsoft operating system.

Recommendation: Enable Desktop Experience when using the server or client operating system.

Considerations

  • When you install the Control Room on Microsoft Windows Server 2012 and 2012 R2, a warning message indicating installation prerequisites is displayed. However, you can still proceed with the installation without any issues.
  • Before you install the Control Room for On-Premises, ensure that you have installed the Visual C++ Redistributable for Visual Studio 2015 package on the Control Room host machine. For more information about the package, see Visual C++ Redistributable for Visual Studio 2015.
  • If a Windows OS version is certified for use with your Control Room and that same version is supported by the listed cloud providers, then Automation 360 will support running that Windows OS version on those cloud providers as well.

The following sections list the environment and deployment types with the release or build number applicable to each supported operating system:

Microsoft Windows Server 2025 Datacenter

Environment Automation 360 deployment type and release details
Amazon Web Services Elastic Compute Cloud (EC2) On-Premises: Build 40179 (v.38) or later
For information on the Bot Agent operating system compatibility, see Exigences d\'appareil Bot Agent pour Windows

Microsoft Windows Server 2022 Standard and Datacenter

Environment Automation 360 deployment type and release details
Amazon Web Services Elastic Compute Cloud (EC2) On-Premises: Build 19688 (v.30) or later
Microsoft Azure Virtual Machine (VM) On-Premises: Build 21094 (v.31) or later
VMware VMs on ESXi 7.x/8.x
  • On-Premises: Build 22278 ( v.32) or later
  • Cloud: Build 22278 ( v.32) or later
For more information on the compatible Automation 360 builds, see Bot Agent compatibility.
Note: Review the following considerations about Microsoft Windows Server 2022:
  • This version is not certified for the disaster recovery (DR) deployments.
  • Automation Anywhere has certified Microsoft Windows Server 2022 Datacenter. For information on updating to 2022 Datacenter, see Mise à jour vers Windows Server 2022 Datacenter.
    If you are currently using the Microsoft Windows Server 2019 Datacenter or 2016 Datacenter, review the following update recommendations:
  • When you update to Microsoft Windows Server 2022 Datacenter from Microsoft Windows Server 2019 or 2016, Bot Agent might fail to establish a connection with the Control Room. If you encounter this issue, copy and paste the Automation Anywhere folder from your backup into the following location on the Bot Agent device:
    C:\Windows\System32\config\systemprofile\AppData\Local\

Microsoft Windows Server 2019 Standard and Datacenter

Environment Automation 360 deployment type and release details
Amazon WorkSpaces On-Premises: Build 17542 (v.28) or later
Amazon Web Services Elastic Compute Cloud (EC2)
  • On-Premises: Build 1089 (A2019.07) or later
  • Cloud: Build 1089 (A2019.07) or later
Google Compute Engine On-Premises: Build 7103 (A2019.17) or later
Microsoft Azure VM
  • On-Premises: Build 2079 (A2019.09) or later
  • Cloud: Build 2079 (A2019.09) or later
VMware VMs on ESXi 7.x/8.x
  • On-Premises: Build 22278 (v.32) or later
  • Cloud: Build 22278 (v.32) or later

Microsoft Windows Server 2016 Standard and Datacenter

Microsoft Windows Server 2016 is the recommended operating system.

Environment Automation 360 deployment type and release details
Amazon WorkSpaces On-Premises: Build 17542 (v.28) or later
Microsoft Azure VM
  • On-Premises: Build 2079 (A2019.09) or later
  • Cloud: Build 2079 (A2019.09) or later
Google Compute Engine On-Premises: Build 7103 (A2019.17) or later
VMware VMs on ESXi 6.x
  • On-Premises: Build 7103 (A2019.17) or later
  • Cloud: Build 7103 (A2019.17) or later
VMware VMs on ESXi 7.x/8.x
  • On-Premises: Build 22278 (v.32) or later
  • Cloud: Build 22278 (v.32) or later

Microsoft Windows Server 2012 and 2012 R2 Standard and Datacenter

Note: Starting from v.32 (Build 22278), Automation 360 is not certified on the Microsoft Windows Server 2012 and 2012 R2. For more information, see Obsolescences de fonctionnalités terminées.
Environment Automation 360 deployment type and release details

Amazon Web Services Elastic Compute Cloud (EC2)
  • On-Premises: Build 4105 (A2019.12) or later
  • Cloud: Build 4111 (A2019.12) or later
Microsoft Azure VM
  • On-Premises: Build 4105 (A2019.12) or later
  • Cloud: Build 4111 (A2019.12) or later
Google Compute Engine On-Premises: Build 7103 (A2019.17) or later

CentOS Linux

Environment Automation 360 deployment type and release details
Amazon Web Services Elastic Compute Cloud (EC2)
  • CentOS Linux 7.9 and 8.3 - From On-Premises Build 9664 (v.21) or later`.2
  • CentOS Linux 7.7 - From On-Premises Build 2545 (A2019.10) or later
  1. If you are updating Control Room from any of the earlier versions (n-3) to On-Premises Build XXXXX (v.40) or later, ensure that you follow the rehydration process, which has the following outcomes:
    • Only the Elasticsearch data is retained.
    • Elasticsearch settings are truncated.
    • Audit or custom logs are (not retained) deleted.
    Note: Audit or custom logs will be deleted after the rephydration process. Ensure that you back them up if required.
  2. Direct update to CentOS Linux Stream 10 (Coughlan) is not supported. If you are currently on any of the CentOS Linux 7.x or 8.x versions, you can only perform a fresh installation of CentOS Linux Stream 10 (Coughlan).

Red Hat Enterprise Linux

Environment Automation 360 deployment type and release details
Amazon Web Services Elastic Compute Cloud (EC2) For Red Hat Enterprise Linux 9.5:
  • On-Premises: From Build 37526 (v.37) or later
  • Cloud: From Build 37528 (v.37) or later
Amazon Web Services Elastic Compute Cloud (EC2)
For Red Hat Enterprise Linux 7.9:
  • On-Premises: From Build 9664 (v.21) or later
  • Cloud: From Build 9664 (v.21) or later
For Red Hat Enterprise Linux 7.7:
  • On-Premises: From Build 2545 (A2019.10) or later
  • Cloud: From Build 2545 (A2019.10) or later

Amazon Linux

Environment Deployment type
Amazon Web Services Elastic Compute Cloud (EC2) Amazon Linux 2023
Amazon Web Services Elastic Compute Cloud (EC2) Amazon Linux 2
Note:
  • Amazon will end the support for the Amazon Linux 2 operating system in June 2026. It is recommended that you update to Amazon Linux 2023 (AL2023) as this operating system optimizes boot time to reduce the time from instance launch to running your workload. For more information, see Prochaines dépréciations de fonctionnalité.
  • Amazon Linux 2 (AL2) and Amazon Linux 2023 (AL2023) operating systems are fundamentally different in architecture and package management. Therefore, direct update of Amazon Linux 2 (AL2) to Amazon Linux 2023 (AL2023) operating system is not supported. We recommend that you use the AWS’s rehydration process for migrating from AL2 to AL2023.