Kaseya 2 (v6) System Requirements

Requirements for Each Managed Machine

Kaseya Agent

• 333 MHz CPU or greater
• 128 MB of RAM
• 30 MB of free disk space
• Network Interface Card (NIC) or modem
• Microsoft Windows NT, 2000, XP, 2003, Vista, 2008, 7
• Apple Mac OS X version 10.3.9 or above
• TCP/IP Outbound Port 5721 ⁽¹⁾
• No Inbound Ports

Endpoint Security

• 256 MB of RAM
• 60 MB of free disk space
• Microsoft Windows 2000, XP, 2003, Vista, 2008, 7

Backup and Disaster Recovery

• 256 MB of RAMk
• 300 MB of free disk space
• Microsoft Windows 2000, XP, 2003, Vista, 2008 ⁽⁵⁾

Desktop Policy & Migration

• 256 MB of RAM
• 30 MB of free disk space
• Microsoft Windows 2000, XP, 2003, Vista, 2008, 7

Requirements for Kaseya Server and Database

IMPORTANT: To qualify for server related support, the Kaseya server software must be installed on an instance of Windows that is dedicated to the Kaseya application.  The Kaseya server must not be installed on an instance of Windows that is hosting another server application (except SQL Server), such as Microsoft Exchange.

General Requirements for Kaseya Server

• Microsoft Windows - see supported versions below
• Microsoft Internet Information Server (IIS) version 5.1 or greater
• Microsoft Message Queuing (MSMQ)
• Microsoft .NET Framework 2.0
• Microsoft .NET Framework 3.5
• Microsoft SQL - see supported versions below ^{(3) (4)}
• Microsoft SQL Reporting Services ⁽⁴⁾
• TCP/IP open ports:
  • Web UI: port 80 or 443 inbound and outbound
  • Email Notifications: port 25 outbound
  • Agent connections: port 5721 inbound ⁽¹⁾

Minimum Kaseya Server Configuration

• Single processor (2.4 Ghz,160 Mhz front side bus, 1 MB cache)
• 3 GB RAM ⁽²⁾
• 40 GB hard drive
• Microsoft Windows
  • Server 2003 or 2008, or
  • XP Pro, Vista, and Windows 7 are supported for evaluation purposes only with systems that have no more than 5 Kaseya Agents
• Microsoft SQL
  • SQL Server 2005 or 2008, or ⁽³⁾
  • SQL 2005 or 2008 Express Edition with Advanced Services ⁽³⁾
• 100 Mbps Network Interface Card (NIC)
• DSL or Cable modem connection

Note: The actual hardware and software requirements for a production Kaseya server will vary depending upon the number of agents to be deployed, the add-on modules, and the actual usage of the system.

Kaseya 2 (v6) Production Server Guidelines

The Kaseya platform is flexible and scalable and will continue to operate reliably under severe loading conditions. Consider matching your anticipated needs to one of the recommended configurations below.

Base Configuration

The server configurations below are optimized for maximum performance assuming intensive use of the Kaseya platform in terms of:

• Deep use of Monitoring for all managed machines
• Deep use of SNMP Monitoring
• Frequent Audits for all managed machines
• Full use of Patch Management for all managed machines
• Extensive use of Agent procedures for all managed machines
• All Managed machines are located on remote networks accessible only via the Internet

Add-ons

• The Service Desk add-on will require an additional 2.4 Ghz core per 50 concurrent Service Desk users on single server installations on top of the base Kaseya configuration.
• KES will incur an additional %15 load on CPU and IO to the base configuration.
• On site replication in BUDR will cause heavy traffic between the client and the server and extra DB processing when using Full Synthetic Backups.

Virtual Machines

• Allocate sufficient virtual resources to meet the system requirements for physical machines. For VMware, allocate reservations of 50% for CPU and memory for the Kserver VM. If SQL Server is installed remotely from the Kserver on a different VM, allocate the same reservations (50%) for the SQL Server VM. Monitor effective CPU and swapped memory and adjust your ESX resources accordingly.

Depending upon actual usage, the hardware and software required may be more or less than the configurations specified below.

As a best practice, administrators are encouraged to monitor standard performance metrics on the Kaseya Server (CPU, memory, etc.) and SQL Server to establish the appropriate level of hardware and software based on actual usage.

Suggested Kaseya Server Configuration for Managing from 50 up to 250 Machines

• Single processor (Intel Xeon 2.4 Ghz Dual Core, 1066 Mhz front side bus, 4 MB cache) 
• 4 GB RAM ⁽²⁾ 
• 2x73Gig 7.5k SATA (hardware RAID 1) 
• Microsoft Windows Server 2003 or 2008 Standard Edition 32 Bit
• Microsoft SQL Server 2005 or 2008 32 Bit (with AWE enabled) ⁽³⁾
• 1 Gbps Network Interface Card (NIC) 
• 1 Mbps DSL or T1 connection

Suggested Kaseya Server Configuration for Managing up to 500 Machines

• Single processor (Intel Xeon 2.4 Ghz Dual Core, 1066 Mhz front side bus,4 MB cache) 
• 6 GB RAM ⁽²⁾ 
• 2x73Gig 10k SAS (hardware RAID 1) 
• Microsoft Windows Server 2003 or 2008 Standard Edition 64 Bit
• Microsoft SQL Server 2005 or 2008 32 Bit (with AWE enabled) or 64 Bit ⁽³⁾
• 1 Gbps Network Interface Card (NIC) 
• 1 Mbps DSL or T1 connection

Suggested Kaseya Server Configuration for Managing up to 1000 Machines

• Single processor (Intel Xeon 3 Ghz Dual Core, 1066 Mhz front side bus, 4MB cache)
• 8 GB RAM ⁽²⁾
• 3x73Gig 10k SAS (hardware RAID 5)
• Microsoft Windows Server 2003 or 2008 Standard Edition 64 Bit
• Microsoft SQL Server 2005 or 2008 32 Bit (with AWE enabled) or 64 Bit  ⁽³⁾
• 1 Gbps Network Interface Card (NIC)
• 1 Mbps DSL or T1 connection

Suggested Kaseya Server Configuration for Managing up to 2500 Machines

• Dual processor (Intel Xeon 3 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
• 10 GB RAM ⁽²⁾
• Database RAID: 3x73Gig 10k SAS (hardware RAID 5)
• tempdb/OS RAID: 2x73Gig 10k SAS (hardware RAID 1)
• Microsoft Windows Server 2003 or 2008 Standard Edition 64 Bit
• Microsoft SQL Server 2005 or 2008 Standard Edition 64 Bit ⁽³⁾
• 1 Gbps Network Interface Card (NIC)
• T1 connection

Suggested Kaseya Server Configuration for Managing up to 5000 Machines

Database Server

• Dual processor (Intel Xeon 3 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
• 16 GB RAM ⁽²⁾
• Database RAID: 5x73Gig 15k SAS (hardware RAID 5)
• Tempdb/OS RAID: 2x73Gig 15k SAS (hardware RAID 1)
• Microsoft Windows Server 2003 or 2008 EE 64 Bit
• Microsoft SQL Server 2005 or 2008 Standard Edition 64 Bit ⁽³⁾
• 1 Gbps Network Interface Card (NIC)
• High IO External Storage Device or SAN recommended able to support 1500 IOPS

Application Server

• Single processor (Intel Xeon 2 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
• 8 GB RAM ⁽²⁾
• OS: 2x146Gig 10k SAS (hardware RAID 1)
• Microsoft Windows Server 2003 or 2008
• 1 Gbps connection between the Kaseya Server and SQL Server
• 1 Gbps Network Interface Card for UI and Agents
• T3 connection

Suggested Kaseya Server Configuration for Managing up to 10000 Machines

Database Server

• Quad processor (Intel Xeon 3.0 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
• 24 GB RAM ⁽²⁾
• Database RAID: 8x73Gig 15k SAS (hardware RAID 5 or RAID 10)
• Tempdb: 2x73Gig 15k SAS (hardware RAID 10)
• OS RAID: 2x73Gig 15k SAS (hardware RAID 1)
• Microsoft Windows Server 2003 or 2008 EE 64 Bit
• Microsoft SQL Server 2005 or 2008 Standard Edition 64 Bit ⁽³⁾
• 1 Gbps Network Interface Card (NIC)
• High IO External Storage Device or SAN recommended able to support 3000 IOPS

Application Server

• Single processor (Intel Xeon 3 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
• 8 GB RAM ⁽²⁾
• OS: 2x146Gig 15k SAS (hardware RAID 1)
• Microsoft Windows Server 2003 or 2008
• Fiber channel connection between the Kaseya Server and SQL Server
• 1 Gbps connection between the Kaseya Server and SQL Server
• 1 Gbps Network Interface Card
• T3 connection

Suggested Kaseya Server Configuration for Managing more than 10000 Machines

• For server configuration from 10,000 machines and above please contact sales@kaseya.com for details.

Configuration Notes

¹ Agents connect to the Kaseya Server on port 5721. This port assignment may be changed by the administrator.

² An adequate amount of properly configured RAM is essential for good system performance. In order to insure enough memory resources are available, you must not include the /3GB switch in your boot.ini; otherwise, excessive paging can result impacting performance. However, to allow SQL Server to take advantage of memory above 4Gig, the use of the /PAE switch is highly recommended along with the AWE feature enabled in SQL Server. When SQL Server is running on the same machine as the Kaseya Server, Min and Max Memory settings must be configured to allow at least 2 Gigabytes of FREE RAM to the OS and Kaseya Processes.

³ SQL Server 2005 (including Express) must have SP3 or later, and SQL Server 2008 (including Express Edition) must have SP1 or later. SQL Server 2000 is not supported.

⁴ Running MS Windows 64-bit (XP, Vista, 7, Server), SQL Server 2005 64-bit (and the Kaseya Server) all on a single Windows machine is not recommend due to a Microsoft issue related to MS Reporting Services. The issue is described in this article: http://msdn.microsoft.com/en-us/library/ms143293(SQL.90).aspx. There is no issue if you are running SQL Server 2005 64-bit on a separate machine from the Kaseya Server.

⁵ Backup and Disaster Recovery supports the original Windows 2008 Server, but does not currently Support Windows Server 2008 R2.