Kaseya Production Server Guidelines

Every environment that is running Kaseya VSA is different. These recommended requirements are a general guideline based on data taken from multiple customer environments.

Warning: 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.

Software

The VSA supports the following versions of Microsoft Windows Operating System
- Windows Server 2022
- Windows Server 2019
- Windows Server 2016
Versions of Microsoft SQL Server supported are
- SQL Server 2022 Web Edition, Standard Edition, Enterprise Edition (64-bit)
- SQL Server 2019 Web Edition, Standard Edition, Enterprise Edition (64-bit)
- SQL Server 2017 Web Edition, Standard Edition, Enterprise Edition (64-bit)
- SQL Server 2016 Web Edition, Standard Edition, Enterprise Edition (64-bit)
Microsoft Internet Information Server (IIS)
Microsoft Message Queuing (MSMQ)
Microsoft .NET Framework 2.0 SP2, 3.5 SP1, 4, 4.7.2, Microsoft .NET Core 3.1
SQL Server Reporting Services is required to be installed as part of the SQL Server Installation if you require Kaseya Reporting to use SSRS.


Suggested Hardware Requirements
	Number of Active Agents
	20,000	10,000	5,000	1,000	1,000 - 10
Application Server Requirements
CPU based on 2.4Ghz	8 cores minimum	4 cores min	4 cores min	2 cores min	2 cores min
RAM (GB)	24	16	16	16	16
Disk (GB) Kaseya Application Volume**	C:\120 D:\500
Storage	SSD storage for fastest and optimal performance
TCP/IP open ports:	Web UI: 443 inbound and outbound Email Notifications: port 25 outbound Agent connections: port 5721 inbound***
Database Server Requirements
CPU based on 2.4Ghz	16 cores	8 cores	8 cores	8 cores	8 cores
RAM (GB)	64	32	20	16	16
Disk (GB) SQL Data & SQL Logs Total**	C:\120 D:\300	C:\120 D:\300	C:\120 D:\250	C:\120 D:\150	C:\60 D:\100
Storage	SSD storage for fastest and optimal performance

For 20k+ agents please contact your account manager for custom configuration.

* Specs are provided as a guide. Resource utilization of the VSA with these agent counts are based on average utilization and will vary dramatically depending on the number and frequency of audits, patch scans, agent scripts, reporting, log history retention, script distribution and the various add-on’s like Service Desk. Customers are encouraged to monitor standard performance metrics on the Kaseya Application Server (CPU, IO usage, memory, etc.) and SQL Server to establish the appropriate level of hardware and software based on actual usage.

** For all SQL server database and log files. Suggested drive size which may require to be extended or reduced depending on your use of the VSA.

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

Supported Browsers

Your browser must have cookies and JavaScript enabled in order to proceed. Enabling popups for the VSA website is recommended.

Windows
- Chrome
- FireFox
- Edge
Apple OS X
- Safari 7 and later
- Chrome
- FireFox

IIS Configuration

When installing R95, Kaseya will automatically configure Microsoft IIS to listen on port 80 and 443. 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.

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.

Additional Configuration

SQL Server tempdb: We recommend configuring as per Microsoft's recommendations
SQL Server Max Server Memory: Set to 80% of RAM
The Service Desk add-on may require an additional 2.4 Ghz core per 50 concurrent Service Desk users on single server installations on top of the base Kaseya configuration.
Clustering: 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.
When running a virtual machine ensure your servers are set to optimum performance power setting.
Some useful KB articles with further information can be found here:
- Ports for Peer-to-Peer Connectivity: https://helpdesk.kaseya.com/hc/en-gb/articles/229013508-VSA-Agent-Peer-to-Peer-P2P-ConnectivityPorts-dynamic
- Anti-Virus Exclusions: https://helpdesk.kaseya.com/hc/en-gb/articles/229039488-Does-Kaseya-support-Anti-Virus-software-installed-on-the-Kaseya-Application-Server-and-or-SQL-Server-
- Ports: https://helpdesk.kaseya.com/hc/en-gb/articles/229026208-What-ports-does-Kaseya-use-

SQL High Availability Configuration for VSA

Should configure Always On Availability Groups on SQL Server Enterprise Edition.
Should indicate Availability Groups Listener instead of IP address of server in VSA connection string. This will route traffic from your application automatically to the Primary replica without having to manually update the connection string after every failover.
Configure Always On Availability Groups on Synchronous Commit mode to prevent data loss and inconsistent database state across replicas.
It’s recommended to include MultiSubnetFailover=TRUE option in VSA connection string even if the availability group only spans a single subnet. For limitations related to MultiSubnetFailover option, please check Microsoft documentation.
It takes up to 10 seconds to reconnect VSA to Primary SQL Server after failover action