Kaseya 2 (v6.1) 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, 2003 R2, Vista, 2008, 2008 R2, 7
  • Apple Mac OS X version 10.3.9 or above
  • SuSE Linux Enterprise 10 and 11, RedHat Enterprise Linux 5.4/5.5, Ubuntu 8.04-10.4, and OpenSuSE 11 (6)
  • TCP/IP Outbound Port 5721 (1)
  • No Inbound Ports

Addon Module Requirements

Anti-Malware

KServer

  • The Anti-Malware module installs on VSA 6.0.1 or later

Requirements for Each Managed Machine

  • Anti-Malware can be installed on any Kaseya managed machine, excluding Mac and Linux machines.
  • Microsoft® Windows 2000 Service Pack 4 or higher.
  • 500MHZ processor.
  • 256 MB of RAM.
  • 15 MB free disk space.

Antivirus

KServer

  • The Antivirus module installs on VSA 6.1 or later

Requirements for Each Managed Machine

  • 800 MHz CPU or greater
  • 512 MB available RAM
  • About 480 MB free space on the hard drive
  • Microsoft Windows XP, Vista, 7 are supported.Microsoft Windows 98 and NT are not supported.
  • Microsoft Windows Installer 2.0

Backup

KServer

  • The Backup module installs on VSA 6.0.1 or later

Requirements for Each Managed Machine

  • 256 MB of RAM
  • 750 MB of free disk space
  • Microsoft Windows 2000, XP, 2003, 2003 R2, Vista, 2008, 2008 R2, 7 (5)

Desktop Policy and Migration

Kserver

  • The Desktop Policy and Migration module installed on 6.0 or later

Requirements for Each Managed Machine

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

Directory Services

KServer

  • The Directory Services module installs on VSA 6.1 or later

Requirements for Each Directory Services Probe Machine

  • Windows OS: XP, Vista, Server 2003, Server 2003 R2, Server 2008, Server 2008 R2, or Windows 7

Mac and Linux

  • If Linux and Mac computers are located in the domain hierarchy, these computers can be identified using Directory Services and agents can be installed on them manually outside of Directory Services.

Endpoint Security

KServer

  • The Endpoint Security module installs on VSA 6.1 or later

Requirements for Each Managed Machine

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

Imaging & Deployment

KServer

  • The Imaging & Deployment module installs on VSA 6.1, with all hotfixes applied, and later.

Minimum Requirements for Each Repository Machine

  • A Kaseya agent must be installed.
  • Only physical machines are supported, not virtual machines.
  • Microsoft Windows XP (SP3), 2003, 2003 R2, Vista, 2008, 2008 R2, 7
  • Linux and Macintosh are not supported.
  • 1 GB RAM for XP and 2003, and 2 GB or more for Vista and above.
  • 100 GB disk space. Image sizes can range between 300MB and several GBs.
  • At least one connected, physical ethernet adapter. Wireless adapters are not supported.
  • Network access to a DHCP server. The repository agent machine can have a static IP address, but the Virtual Server running on the repository machine must to be able to obtain a DHCP address.

Image Creation and Deployment Machines

  • Supported operating systems: Microsoft Windows 2000, XP, 2003, 2003 R2, Vista, 2008, 2008 R2, 7
  • Both physical machines and virtual machines are supported.
  • The destination drive must be equal or larger than the source drive.
  • Software RAID/fake RAID is not supported.
  • At least one connected, physical ethernet adapter. Wireless adapters are not supported.
  • The Windows directory must be called "Windows" and be located on the first or second partition of the boot disk drive.
  • The system setup, or BIOS, of each KID target computer must be configured to bootup using the network interface card (NIC) option at startup, regardless of whether an agent is installed or not. Most computers built within the last 5 years have the NIC bootup option enabled by default. The NIC bootup option must be sequenced before the hard disk (HDD) option. KID requires this for both image and backup deployment.
  • An installed Kaseya agent is highly recommended.

Network Discovery

KServer

  • The Network Discovery module installs on VSA 6.0.1 or later

Requirements for Each Agent Installed with a Network Discovery Collector

  • Windows OS: XP, Vista, Server 2003, Server 2003 R2, Server 2008, Server 2008 R2, or Windows 7
  • .Net 3.5 for Server 2008 and Server 2008 R2. All other operating systems install .Net 3.5 automatically.
  • 2 GB free space on the hard drive minimum
  • Microsoft Windows Installer 2.0
  • 800 MHz CPU or greater
  • 2 GB RAM minimum

Network Monitor

Requirements for Each Agent Machine Hosting a Network Monitor Server or Network Monitor Gateway

  • Windows 2003, 2008, or 2008 R2 with the latest service pack
  • Network Monitor comes with its own database.

Online Backup

KServer

  • The Online Backup module installs on VSA 6.0.1 or later

Requirements for Each Managed Machine

  • Microsoft Windows XP, 2003, 2003 R2, Vista, 2008, 2008 R2, 7
  • Apple Mac OS X 10.5 (Intel) and later, including Mac OS X 10.7 Lion

Policy Management

  • No additional agent requirements apply.

Service Billing

  • No additional agent requirements apply.

Service Desk

  • No additional agent requirements apply.

Browsers

Recommended

  • Windows
    • Chrome 8 and later.
  • Mac OS X
    • Safari 4 and later.

Supported

  • Windows
    • IE8, IE9, FireFox 3.x and later, Chrome 8 and later. ChromePlus is not supported.
  • Mac OS X
  • Safari 4 and later, FireFox 3.x and later, Chrome 8 and later. ChromePlus is not supported.

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 belowMicrosoft Internet Information Server (IIS) version 5.1 or greater
  • Microsoft Message Queuing (MSMQ)
  • Microsoft .NET Framework 2.0
  • Microsoft .NET Framework 3.5 SP1
  • Microsoft SQL - see supported versions below (3) (4)
  • Microsoft SQL Reporting Services (4)
  • TCP/IP open ports:
    • Web UI: port 80 or 443 inbound and outbound
    • Email Notifications: port 25 outbound
    • Agent connections: port 5721 inbound (1)

Minimum Kaseya Server Configuration

  • Single processor (2.4 Ghz,160 Mhz front side bus, 1 MB cache)
  • 3 GB RAM (2)
  • 40 GB hard drive
  • Microsoft Windows
    • Server 2003, 2003 R2, 2008, 2008 R2, 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, 2008 R2, with latest service pack, or (3)
    • SQL 2005, 2008, 2008 R2 Express Edition with Advanced Services, with latest service pack (3)
  • 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 Backup 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 (2)
  • 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), with latest service pack (3)
  • 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 (2)
  • 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, with latest service pack  (3)
  • 1 Gbps Network Interface Card (NIC)
  • 1 Mbps DSL or T1 connection

Suggested Kaseya Server Configuration for Managing up to 1,000 Machines

  • Single processor (Intel Xeon 3 Ghz Dual Core, 1066 Mhz front side bus, 4MB cache)
  • 8 GB RAM (2)
  • 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, with latest service pack  (3)
  • 1 Gbps Network Interface Card (NIC)
  • 1 Mbps DSL or T1 connection

Suggested Kaseya Server Configuration for Managing up to 2,500 Machines

  • Dual processor (Intel Xeon 3 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
  • 10 GB RAM (2)
  • 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, with latest service pack (3)
  • 1 Gbps Network Interface Card (NIC)
  • T1 connection

Suggested Kaseya Server Configuration for Managing up to 5,000 Machines

Database Server

  • Dual processor (Intel Xeon 3 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
  • 16 GB RAM (2)
  • 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, with latest service pack (3)
  • 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 (2)
  • 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 10,000 Machines

Database Server

  • Quad processor (Intel Xeon 2.0 Ghz or higher Quad Core, 1066 Mhz front side bus,4 MB cache)
  • 24 GB RAM (2)
  • 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, with latest service pack (3)
  • 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)
  • 12 GB RAM (2)
  • OS: 4x146Gig 15k SAS (hardware RAID 10)
  • 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 up to 20,000 Machines

There are various options to scale Kaseya to 20,000 Machines. It is possible to run the application servers under a virtualization product. We recommend using VmWare ESX 4.x or above for the application server. These versions allow you to exceed 4 cores if necessary on the VM’s and can provide a level of redundancy with V-Motion in an ESX Cluster. We only support configurations that allocate the correct reservations of Memory and CPU on the application VM’s. We don’t recommend SQL Server as a VM.

Database utilization with these agent counts will vary dramatically depending on the number and frequency of audits, patch scans, agent scripts and the various add-on’s like KES or Service Desk. We encourage you to monitor your Memory, CPU and IO usage to insure optimal performance of your environment.

Database Server

  • Quad processor (Intel Xeon Quad Core Hyper threaded enabled 3.0 Ghz)
  • 40 GB RAM Minimum (2)
  • The Kaseya database with 20,000 machines can generate approximately 4000-5000 IOPS during busy times. Please configure your storage solution to support this load appropriately. Typically, a SAS 15K Drive can manage 150-300 IOPS, however, we recommend a SAN for this sized solution.
  • Insure that tempdb is not located on the local drives since this database can generate high IO’s during audits and patch scans. The IOPS above include tempdb in the calculation.
  • OS RAID: 2x146 Gig 15k SAS (hardware RAID 1)
  • Microsoft Windows Server 2003 or 2008 EE 64 Bit
  • Microsoft SQL Server 2005 or 2008 Standard Edition 64 Bit or higher, with latest service pack (3)
  • 2ea 1Gbit or faster Interface Cards (NICs). Depending on load, you may wish to team the interface cards for better performance/redundancy to the application server.
  • 1Gbit or faster NIC for management and backups.
  • If you are going to setup SQL Server in a cluster, please read Microsoft’s documentation on the limitation of reporting services in a cluster and contact Kaseya sales for more information.

Application Server

Note: VMWare reservations should be set at 8Gig for memory and 6Ghz for CPU.

  • Dual processor (Intel Xeon 3 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
  • 16 GB RAM (2)
  • OS: 4x146Gig 15k SAS (hardware RAID 10) The application server may see up to 500 IOPS.
  • Microsoft Windows Server 2003 or 2008
  • 1 Gbit or faster connection between the Kaseya Server and SQL Server Instance
  • 1 Gbit Network Interface Card to Internet
  • 1 Gbit Network Interface Card for Backup
  • T3 connection

Suggested Kaseya Server Configuration for Managing more than 20,000 Machines

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

Configuration Notes

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

2 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.

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

4 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.

5 Backup 3.2 and later supports Windows Server 2008, Windows Server 2008 R2 and Windows 7. Backup and Disaster Recovery 3.1 supports Windows Server 2008, but does not support Windows Server 2008 R2 and Windows 7.

6 The Linux agent icon and agent menu are not currently supported for SuSE Linux Enterprise 10. While untested, the Linux agent is likely to work on other LSB-compliant Linux distributions published in the last 2 years. The Linux Standard Base is a group funded by the Linux Foundation (www.linuxfoundation.org) to manage compatibility between separate Linux distributions. Only Chrome and Firefox browsers are supported in Gnome Linux sessions. Only Gnome Windows Manager is supported.