|
|
|
|
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
Minimum Kaseya Server Configuration
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.
Microsoft IIS will automatically be configured for security to operate with the Kaseya Application Firewall
When installing 7.0, 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 7.0.
7.0 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 SSL 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). In the next 7.0 beta release, we will provide a tool which will allow you to export your existing SSL certificate out of IIS and import it in KAF for it to secure web traffic.
Java Must be Installed on the Windows Server
Kaseya Server 7.0 requires Java SE 7, update 51 or later. You must manually download and install the Java package that is appropriate for the system hosting your Kaseya Server. A system check prevents the installation or upgrade from continuing unless the Java package is installed.
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, Developer and SQL Express. Other editions of SQL Server that support the core features provided by these four editions should be compatible with the Kaseya Server. SQL Server 2008 (including Express Edition) must have SP1 or later. SQL Server 2005 and prior versions are not supported. To ensure enough memory resources are available on 32 bit Windows systems, 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. Windows 2012 only supports x64 bit processors; therefore, the 32 bit settings mentioned above do not apply.