This article aims to provide transparency regarding Automate server requirements and scalability based on agent count for ConnectWise Automate®. Use this guide to ensure your system meets the minimum requirements before Automate is installed or to scale the product to fit your agent count needs after it has been installed.
Note: These server requirements only apply to on-premises partners. See Control Center Requirements for Cloud partners for the minimum specifications for Cloud setups.
In this article, review the minimum specifications for:
The following server requirements may vary based on your environment (e.g., probe use, number of probes, number of agents, etc.). Depending on actual usage, the hardware required may be more than what is recommended. The agent count used should be the number of expected agents for the Automate server, 24 months in advance, as this accounts for anticipated growth within the business.
It is required that Automate servers be given both an internal and external static IP address where possible. When the Automate server contacts the licensing server, your licenses are associated with its external IP address. If the external IP address is dynamic, you may have to contact Automate occasionally to provide us with your renewed external IP address for the licenses to remain active. The Web Control Center also relies on this IP address, so if the IP address changes, you cannot access the Web Control Center unless you modify your registry to recognize the renewed IP.
Established and proven scalability with Automate is a fundamental objective. Automate progress and intent have continued marching that path. The resource investments are in place to continue this advancement.
The focus is on building a testing ground for large-scale optimization and performance planning that is extraordinary and state-of-the-art. As we move forward, we build what will solve current possible issues and resolve challenges and questions that have not yet been formed and identified.
ConnectWise exists to resolve limitations and provide new areas of growth and opportunity for all of our partners as a company. ConnectWise automates and innovates. Our continuous commitment to innovation, our partners, and the industry is clear with our pledge and commitment to true scalability and performance.
Resources have been dedicated to comprehensive testing facilities. Human and technical resources are in place to prove current endpoints of 12,000 and greater. The key mandate is successive iterations above 30,000.
The structure is in place to ensure collaboration in a well-defined testing ground to evaluate current issues. The specialized Partner Information Network (PIN) gives Automate real-world partnerships with those using 12,000 plus deployed endpoints. This will furnish hard data for functionality and database performance aspects as well.
The process is in place to examine multi-server implementations. Automate going beyond the boundaries of Front-End and Back-End improvements and reviewing the application architecture as a whole.
In this setup, the Database and Web installation for ConnectWise Automate reside on the same server.
Disk
Drive Space
Note: All RAID Sets represent separate LUNs, not partitions.
Note: All RAID Sets represent separate LUNs, not partitions.
After 5,000 agents, we recommend a split server setup. Split servers separate the Automate database from the Automate server applications. Once you exceed 10,000 agents, we also recommend a separate Reporting server.
Disk
Drive Space
Note: All RAID Sets represent separate LUNs, not partitions.
Note: All RAID Sets represent separate LUNs, not partitions.
Note: All RAID Sets represent separate LUNs, not partitions.
Note: All RAID Sets represent separate LUNs, not partitions.
Note: All RAID Sets represent separate LUNs, not partitions.
The following server roles should not be installed on the Automate server:
ConnectWise supports but does not recommend that Control and Automate share the same server beyond 1,200 agents. Use of Automate does not require the use of Control. For details, refer to ConnectWise Control Plugin Requirements.
Important: When installing Automate on Microsoft's Azure Cloud, we recommend using Ultra Disks to ensure the Automate server continues to operate as expected.
Component | Up to 2,000 Agents | Up to 5,000 Agents | Up to 10,000 Agents | Up to 20,000 Agents | More than 20,000 Agents |
Virtual Static RAM | 8 GB (4 GB OS, 4 GB Database) | 12 GB (4 GB OS, 8 GB Database) | Automation Server: 8 GB Database Server: 20 GB (6 GB OS, 14 GB Database) | Automation Server: 8 GB Web Server: 8 GB Production Database Server: 30 GB (6 GB OS, 24 GB Database) Reporting Database Server: 30 GB (6 GB OS, 24 GB Database) | Automation Server: 16 GB Web Server: 16 GB Production Database Server: 46 GB (14 GB OS, 32 GB Database) Reporting Database Server: 46 GB (14 GB OS, 32 GB Database) |
Operating System | Virtual Machines residing on the Host should be of the same OS family for more efficient memory ballooning (e.g., All VM's Server 2008 R2 SP1). | ||||
BIOS Settings | Hyper-threading Enabled | ||||
Page File | Set the Page File to 1.5X RAM allocated and be on a separate LUN (spindle) from the OS. | ||||
Network Path | More than 1 (For example, the storage network should be separated and different than the VM network). | ||||
Virtual Server Responsibility | You are responsible for your virtual server and must make sure to provide enough resources. ConnectWise does not troubleshoot performance issues in your virtual environment. |
Features | RAID 1 | RAID 5 | RAID 10 |
---|---|---|---|
Minimum # Drives | 2 | 3 | 4 |
Data Protection | Single-drive failure | Single-drive failure | Up to one disk failure in each sub-array |
Read Performance | High | High | High |
Write Performance | Medium | Low | Medium |
Read Performance (degraded) | Medium | Low | High |
Write Performance (degraded) | High | Low | High |
Capacity Utilization | 50% | 67%-94% | 50% |
Typical Application | Operating System, transaction databases | Data warehousing, web serving, archiving | Fast databases, application servers |