Kerio Connect Multi-Server System requirements and Prerequisites
This topic outlines the system requirements and prerequisites for installing Kerio Connect Multi-Server.
System Requirements
For better performance it is recommended to run the listed servers on multiple physical servers running VMware vSphere Hypervisor. See the Kerio Connect Tech Specs page for the supported VMware product versions.
These are the minimum system requirements for the virtual appliances:
| Virtual AppliancePre-configured Kerio Connect virtual machine image for VMware. | CPU | RAM | Disk space | LAN |
|---|---|---|---|---|
| Puppet master | 2 CPU cores (Intel Xeon E5 recommended) | 4 GB | 100 GB virtual disk | 1 Gbit |
| Directory server | 2 CPU cores (Intel Xeon E5 recommended) | 4 GB | Default virtual machine disk space | 1 Gbit |
| Back-end server (200 or more users) | 2 quad-core CPUs (Intel Xeon E5 recommended) | 16 GB | 7.2-15K RPM, SAS-SATA, 3.5", 1+ TB, RAID10 recommended 1000 IOPS read / 800 IOPS write | 1 Gbit |
| Instant messaging server | 2 CPU cores (Intel Xeon E5 recommended) | 4 GB | Default virtual machine disk space | 1 Gbit |
| Front-end server | 1 quad-core CPU (Intel Xeon E5 recommended) | 8 GB | Default virtual machine disk space | 1 Gbit (10 Gbit recommended) |
| Zabbix server | 1 CPU | 1 GB | Default virtual machine disk space | 1 Gbit |
Prerequisites
Before you begin Kerio Connect Multi-Server installation, it is recommended to have the following ready:
- Internet access
- Correct time set on the hypervisor
- DHCPDynamic Host Configuration Protocol - A protocol that automatically gives IP addresses and additional configuration to hosts in a network. server
- DNSDomain Name System - Enables the translation of hostnames to IP addresses and provides other domain related information. server.
Manual configuration when the DNS server is not available
If you install all servers and don't have a DNS server available in your network, you must configure the proper domain names manually on all servers except the puppet master.
On each server:
- Run the following commands:
hostname -f
hostname
- Open the file
/etc/hosts. - Add the following lines to the file, and save it:
127.0.1.1 <result of `hostname -f`> <result of `hostname`><puppet master IP addressAn identifier assigned to devices connected to a TCP/IP network.> <fully qualified name of puppet master> <puppet master hostname>
- Run the following command to finish the configuration:
puppet agent -t