Managing Kerio Connect Multi-Server
NOTE
This document relates to Kerio Connect Multi-Server 9
You configure Kerio Connect Multi-Server the same as any single-server installation of Kerio Connect, but take a note of the following important points:
- Users, groups, aliases, mailing lists, and resources are distributed to all servers. Other configuration, such as domain settings, must be done on each server separately.
- If you configure DKIMDomainKeys Identified Mail - An authentication method that signs outgoing messages from Kerio Connect with a special signature for identification. on the master server, Kerio Connect Multi-Server distributes the configuration to all back-end servers. For more information refer to Authenticating messages with DKIM.
- If you use SpamAssassin, Kerio Connect Multi-Server distributes the database to all back-end servers.
- You must configure backup and archiving on each back-end server separately. Read Configuring backup in Kerio Connect and Archiving in Kerio Connect for additional information.
- To use Chat in Kerio Connect Client, enable it per domain on the master server. For more information refer to Enabling chat in Kerio Connect Client.
Accessing the administration interface
You can access the administration interface of the individual back-end servers only from the Kerio Connect Multi-Server internal network.
Log in to the administration interfaces of all back-end servers using these credentials:
- username:
admin - password: the password you typed when installing the puppet master.