Kaseya Server Minimum Requirements & Configuration

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)
  • Microsoft Message Queuing (MSMQ)
  • Microsoft .NET Framework 2.0 SP2
  • Microsoft .NET Framework 3.5 SP1
  • Microsoft .NET Framework 4
  • Microsoft .NET Framework 4.7.2
  • Microsoft SQL - see supported versions below (3)
  • 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 (1)

Minimum Kaseya Server Configuration

  • 2.4 Ghz processor,160 Mhz front side bus, 1 MB cache
  • 4 GB RAM (2)
  • 80 GB hard drive
  • Microsoft Windows
    • Server 2012, 2012 R2, 2016 or 2019
  • Microsoft SQL
    • SQL Server 2012 R2 SP4, 2014, 2016 with latest service pack, or (3)
    • SQL 2012 R2 SP4, 2014, 2016 Express Edition with Advanced Services, with latest service pack (3)
  • 100 Mbps Network Interface Card (NIC)

IMPORTANT  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. Refer to the Module Minimum Requirements section before proceeding.

Microsoft IIS will automatically be configured for security

When installing R95, Kaseya will automatically configure Microsoft IIS to listen on port 18081. This will overwrite any existing IIS configurations and IIS will only operate as the web GUI for the Kaseya applications. If you have other websites installed on IIS, they will not function after installing R95.

R95 Installs the Kaseya Application Firewall (KAF) which will terminate all incoming/outgoing web traffic in order to provide a deeper level of security to mitigate application security attacks. As such, KAF will handle all web traffic on port 80 and 443 and, after inspecting it, pass it internally to IIS on port 18081.

If you are using SSL/TLS (i.e. secure web traffic, HTTPS), Kaseya will utilize a self-signed security certificate that ships with the product. This will generate a browser warning (because the certificate is self-signed as opposed to being issued by a trusted certificate authority). Kaseya Server Setup provides a tool which allows you to export your existing SSL certificate out of IIS and import it in KAF for it to secure web traffic.

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 especially with SQL server; the more memory for SQL Server, the less IO experienced by the disk subsystem and the higher cache/hit ratio’s you should attain.

3 "Supported editions include Standard, Enterprise, and Developer. Other editions of SQL Server that support the core features provided by these editions should be compatible with the Kaseya 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.