Installing Kerio Connect Multi-Server


This information relates to Kerio Connect Multi-Server 9.

Kerio Connect Multi-Server is available as a VMware virtual appliance with 64-bit Debian Linux.

Please follow the guide, Downloading Kerio Connect Multi-server, to download the Kerio Connect Multi-server.

The installation file is the same for all server roles. However, you must install the individual servers in the specified order:

Installation Order Server Name Description
1 Puppet master

Puppet master is responsible for configuring all other servers in Kerio Connect Multi-Server and server upgrades.

The puppet master also contains a Syslog server which stores all logs from the Kerio Connect servers.

2 Directory server The directory server (OpenLDAP) is the central storage location for user and group information in the multi-server deployment. All back-end servers are connected to this directory.
3 Back-end servers

Back-end servers represent individual installations of Kerio Connect.

These servers work as home servers for individual users and store users' mailboxes.

You can install two or more back-end servers, and you can install them now or at any later time.

4 Front-end server The front-end server is a proxy server that routes connections to individual back-end servers with user accounts and hosts a session server.
5 Instant messaging server (Optional). The instant messaging server also has Kerio Connect installed. All XMPPExtensible Messaging and Presence Protocol is a protocol used for real-time communication (chat). communication is routed directly to this server.
6 Zabbix monitoring server (Optional). Zabbix monitors all servers in Kerio Connect Multi-Server. For more information refer to Monitoring Kerio Connect Multi-Server with the Zabbix server.


If you are upgrading from a current installation of Kerio Connect, read Migrating from current installations to Kerio Connect Multi-Server before you start the installation.

Use these links to understand the Kerio Connect Multi-Server installation and configuration process: