4  Initial synchronization

4.1  How the initial configuration works
4.2  Default synchronization settings
4.3  Impact on the server's and client's performance
4.4  KOFF deployment

Initial synchronization is a process started upon the first logon to a new profile in Outlook extended by KOFF. Within the process, data is copied from the server to the user's computer thus creating the KOFF's local database.

4.1  How the initial configuration works

To make managing of email accounts in offline mode (without connection to the server) possible, all user data (email messages, contacts, events, tasks and notes) must be stored in a local database on the client's system. Synchronization of the local database with the server runs in the background without user's interaction. Instead of PST files, KOFF uses a proprietary built-in database (Firebird, version 2).

4.2  Default synchronization settings

The default configuration of the initial synchronization is as follows:

  • The Inbox folder is fully synchronized (i.e. complete email messages including attachments are stored in the local database).

  • In other email folders, only message headers are involved in the synchronization.

  • Encrypted and digitally signed messages are always fully synchronized.

  • Other folders (contacts, calendar, tasks and notes folders) are always fully synchronized.

Default settings can be changed (see documentation). Let us focus on the issue of how to set full synchronization of all folders. Right-click on the root folder (Mailbox of...) and select Folder properties... / Folder synchronization / Synchronize whole messages and then Apply these settings to all subfolders.

4.3  Impact on the server's and client's performance

Initial synchronization is very demanding with respect to system resources of both the client and the server. Speed and total time of initial synchronization depends on several factors:

  • Load on the server depends above all on number of clients being synchronized at the particular moment. The hard disk performance is the main limiting factor on the server's side. For example, when performing tests on a PC (Pentium 4, 2.4 GHz, 1 GB RAM, 7200 RPM HDD), during a synchronization of several clients at once, the measured data transfer speed in the server-to-client direction was approximately 120 MB per minute. If possible, it is recommended to install KOFF on one client station after another to stretch and thus reduce load on the server. Queued users can use KOC meanwhile.

  • Load on the client depends on data volume and complexity of the folder tree structure in the particular user account. However, during the initial synchronization process, the response time of Outlook can get longer and uncomfortable. The icon in the system tray's notification area displays the current status of the synchronization. When the synchronization is finished, the system's response will become smoother again.

4.4  KOFF deployment

This section provides recommended instructions for implementation of KOFF in a production environment. The base configuration is Kerio MailServer 6.5.0 installed on the server and KOC 6.5.0 installed on all clients.

Step 0

Install Kerio MailServer 6.5.0 on the server and KOC 6.5.0 on client stations.

Step 1

Install KOFF on one workstation, perform the initial synchronization and get familiar with all functions.

Step 2

Install KOFF on a few clients (approximately 5), perform the synchronization and monitor load on the server and speed of individual synchronizations.

Step 3

Put gained information (load on the server and synchronization speed) in practice by setting optimal number of synchronized clients and perform their upgrade and initial synchronization.

Step 4

Repeat the previous step as many times as necessary to include all clients in the deployment.

Notice that following of these instructions is recommended but not necessary!