Operating system, environment, and platform supported for Control Room
- Updated: 2026/02/16
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 兼容性.
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 软件包 on the Control Room host machine. For more information about the 软件包, 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: 内部版本 40179 (v.38) or later |
Microsoft Windows Server 2022 Standard and Datacenter
| Environment | Automation 360 deployment type and release details |
|---|---|
| Amazon Web Services Elastic Compute Cloud (EC2) | On-Premises: 内部版本 19688 (v.30) or later |
| Microsoft Azure Virtual Machine (VM) | On-Premises: 内部版本 21094 (v.31) or later |
| VMware VMs on ESXi 7.x/8.x |
|
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 更新到 Windows Server 2022 Datacenter.If you are currently using the Microsoft Windows Server 2019 Datacenter or 2016 Datacenter, review the following update recommendations:
- Microsoft Windows Server 2019: Ensure that you have updated your Automation 360 to v.33 version or later. See 更新到 v.33 版本
- Microsoft Windows Server 2016: Ensure that you have updated your Automation 360 to v.34 version. See 更新到 v.34 版本.
- 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) |
|
| Google Compute Engine | On-Premises: 内部版本 7103 (A2019.17) or later |
| Microsoft Azure VM |
|
| VMware VMs on ESXi 7.x/8.x |
|
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 |
|
| Google Compute Engine | On-Premises: 内部版本 7103 (A2019.17) or later |
| VMware VMs on ESXi 6.x |
|
| VMware VMs on ESXi 7.x/8.x |
|
Microsoft Windows Server 2012 and 2012 R2 Standard and Datacenter
Note: Starting from v.32
(内部版本 22278), Automation 360 is not certified
on the Microsoft Windows Server 2012 and 2012 R2. For more
information, see Completed feature deprecations.
| Environment | Automation 360 deployment type and release details |
|---|---|
|
Amazon Web Services Elastic Compute Cloud (EC2) |
|
| Microsoft Azure VM |
|
| Google Compute Engine | On-Premises: 内部版本 7103 (A2019.17) or later |
Linux CentOS
| Environment | Automation 360 deployment type and release details |
|---|---|
| Amazon Web Services Elastic Compute Cloud (EC2) |
For Linux CentOS 7.7:
For Linux CentOS 7.9and 8.3:
|
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:
|
| Amazon Web Services Elastic Compute Cloud (EC2) |
For Red Hat Enterprise Linux
7.9:
|
For Red Hat Enterprise Linux 7.7:
|
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 Upcoming feature deprecations.
- 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. Therefore, we recommend that you use the AWS’s rehydration process for migrating from AL2 to AL2023.