How do I update Kerio Connect when a new version is available?

Summary

This article describes a process of updating Kerio Connect. It also describes possible issues and changes which are related to update.

Details

All changes, improvements and prerequisites for Kerio Connect are cumulative. So, if you want to skip some versions, it is highly recommended to read the parts of this article related to our milestones. It is necessary to meet all prerequisites of those skipped versions. Also all changes and improvements, which are parts of those skipped versions, will be applied to your Kerio Connect just after update.

Determining if a newer build is available

Before you proceed we recommend to make a full backup of the Kerio Connect, you can read more about this in our manual http://manuals.kerio.com/connect/adminguide/en/sect-backup. Also check that the Software Maintenance is valid for the latest version of Kerio Connect. Your Software Maintenance expiration date can be found on the splash screen of your Kerio Connect Administration console, you are only entitled to upgrade to the latest version that your Software Maintenance was valid for.

As a default option, the splash screen and the Debug log in the Administration Console will display a warning if a new build is available. You can click on the "Check Now" button found here Configuration → Advanced Options → Update Checker to run a manual check for a new build.

You can also visit the download page on our website to find the latest build available. http://www.kerio.com/connect/download

Upgrading Kerio Connect

When upgrading there are a few milestone versions that must be installed before you can proceed along the upgrade path. The list below shows these milestones, and the order in which you must install them. These are the only required versions and you need to install the version higher than the one you currently run, then the next one in the list. Those versions are required because of changes in installation process, so it is not possible to skip them. Those versions are available from our archive. http://download.kerio.com/archive/

• Kerio MailServer 5.1
• Kerio MailServer 5.5
• Kerio MailServer 5.7.10
• Kerio MailServer 6.0.0
• Kerio MailServer 6.0.10
• Kerio MailServer 6.5.2
• Kerio MailServer 6.7.3 Patch 1

For example, if you are running Kerio MailServer 6.4.1 then you will need to download and install Kerio MailServer 6.5.2 then Kerio MailServer 6.7.3 patch 1 before you can upgrade to Kerio Connect 7. Once you have Kerio MailServer 6.7.3 Patch 1 installed you can install any version of Kerio Connect 7.

How to do an upgrade on your platform

If using Windows

1. Double-click on the installer.
2. Select your language (e.g. English).
3. Select "Modify" and click "Next"
4. Leave all of the components selected and click "Next"
5. The installation should be completed and you can click "Finish"

If using OS X

1. Double-click on the *.dmg file.
2. Double-click on the installer.
3. Read the license agreement and click "Continue"
4. Click "Agree" to continue the installation
5. Select "Easy Install" and then click "Install"
6. Click on "Quit" once the installation has been completed.

If using RHEL or CentOS

Please note that the commands below are generic and "package_name.rpm" refers to the actual package file name that you download. A real example of the second command would be: sudo rpm -Uvh kerio-connect-7.2.3-4971-linux.rpm

Type the following commands

sudo /sbin/service kerio-connect stop
sudo rpm -Uvh package_name.rpm
sudo /sbin/service kerio-connect start

If using SUSE

Please note that the commands below are generic and "package_name.rpm" refers to the actual package file name that you download. A real example of the second command would be:sudo rpm -Uvh kerio-connect-7.2.3-4971-linux.rpm

Type the following commands

sudo /etc/init.d/kerio-connect stop
sudo rpm -Uvh package_name.rpm
sudo /etc/init.d/kerio-connect start

If using Debian or Ubuntu

Please note that the commands below are generic and "package_name.rpm" refers to the actual package file name that you download. A real example of the second command would be:sudo dpkg –i kerio-connect-7.2.3-4971-linux.deb

Type the following commands

sudo /etc/init.d/kerio-connect stop
sudo dpkg –i package_name.deb

The Linux commands are valid for Kerio Connect 7.0 and newer. Please, look at Kerio Connect's Administrator's Guide for more details. Installing the upgrade will leave your current settings intact.

Things to consider and prerequisites

Upgrade to Kerio Connect 7.3

• Kerio Connect engine

  • PowerPC Mac and non-x64 Mac platforms (Core 1 Single and Core 1 Duo) are not supported by Kerio Connect 7.3
    
  • If you change platform from PowerPC Mac to Mac Intel, the SpamAssassin database is erased and starts from scratch. For more information about issues releated to PowerPC support discontinuation, please see http://kb.kerio.com/715
  • If Out Of Office settings does not work in a Microsoft Entourage account, the user have to reconfigure the account using the new configuration tool, the Account Assistant.
    

• Kerio Outlook Connector (Offline Edition) upgrade

  • The local cache will be converted upon the first start of Outlook after the upgrade. This may take up to several tens of minutes, depending on the size of the local cache and hardware performance (expected upgrade speed is 1GB per 5 minutes). It is not possible to use Kerio Outlook Connector (Offline Edition) during the local cache conversion. See this knowledge base article for more details: http://kb.kerio.com/187/
    
  • The Kerio Updater Service is mandatory now. he Kerio Outlook Connector won't be upgraded without this service. See this knowledge base article for more details about Kerio Updater Service installation: http://kb.kerio.com/188/
    

Upgrade to Kerio Connect 7.2

• Kerio Connect engine

  • Kerio Connect 7.2 will perform various updates in your data store. Depending on the data store size and hardware configuration these updates may affect the server performance in the first 24 hours after the server upgrade.
  • Users of Microsoft Entourage may experience troubles while moving folders.
  • Apple iCal users are advised to restart their clients after server upgrade.
  • All users must reconfigure their profiles in Microsoft Outlook 2011 for Mac after upgrading from any previous beta version of Kerio Connect 7.2.

• Kerio Outlook Connector (Offline Edition) upgrade

  • The local cache will be converted upon the first start of Outlook after the upgrade. This may take up to several tens of minutes, depending on the size of the local cache and hardware performance (expected upgrade speed is 1GB per 5 minutes). It is not possible to use Kerio Outlook Connector (Offline Edition) during the local cache conversion. See this knowledge base article for more details: http://kb.kerio.com/187/
    
  • Since version 7.2.0, we have changed the mechanism of the automatic upgrade of Kerio Outlook Connector (Offline Edition). The upgrade process is newly performed by the new Kerio Updater Service. The service is installed within the first full installation of Kerio Outlook Connector (Offline Edition) 7.2.0 and higher. Installation of the service requires administration privileges. To ease the transition for users without administration privileges, the old upgrade mechanism will continue working through all 7.2.X versions. During this transition period, users and/or administrators have to perform full re-installation with administration privileges. See this knowledge base article for more details: http://kb.kerio.com/188/
    

Once you have upgraded to a version newer than Kerio Connect 7.1.4 Patch 1 you can only roll back to Kerio Connect 7.1.4 Patch 1. This is due to changes that have been implemented in the Kerio Connect software.

Upgrade to Kerio Connect 7.1

• Kerio Connect will re-create all CalDAV and CardDAV databases upon the first start. It can cause temporary inaccessibility of calendar and contact items in CalDAV and CardDAV clients.
• The integrated McAfee antivirus is replaced by Sophos antivirus. It is not necessary to change Kerio Connect's license immediately. The current license with McAfee antivirus will work in the new Kerio Connect with Sophos.

If the license with McAfee is updated for any reason, the license is converted to the new one with Sophos antivirus. This new license cannot be used in old Kerio Connect with McAfee antivirus. This means that it is not possible to downgrade Kerio Connect after renewal.

Upgrade to Kerio Connect 7.0

On completion of this installation the Kerio Connect server will rebuild the Indexes for all accounts within the message store directory. Your users will be able to continue to access their account, but may notice some slow response times while this action is completed.

Upgrade to Kerio MailServer 6.2

Since version 6.2, it has been required to use the exactly same version of Kerio MailServer and Kerio Outlook Connector. The upgrade to a new version of Kerio Outlook Connector is offered automatically during the first start of Microsoft Outlook after Kerio MailServer upgrade. If the automatic upgrade failed for some reason, it would be necessary to upgrade Kerio Outlook Connector manually. The Kerio Outlook Connector is available from our archive, http://download.kerio.com/archive.

Upgrade to Kerio MailServer 6.1

The most important step in this update is to convert the Kerio Outlook Connector user settings to a new database. This is a time consuming action (it can take few hours according to the Kerio MailServer's message store size) due to a lot of data which needs to be converted, therefore it is recommended to perform this upgrade at a time when it will not affect users (Kerio MailServer can be slow during this time due to a heavy load).

Upgrade to Kerio MailServer 6.0.10

Once Kerio MailServer has been updated to version 6.0.10, it is necessary to manually update Kerio Outlook Connector.

Upgrade to Kerio MailServer 6 series from Kerio MailServer 5 series.

When upgrading from Kerio MailServer 5.7.0 to Kerio MailServer 6.0.0. according to the upgrade process you may notice a problem with a version check. This problem happens occasionally and is caused by a missing version registry key in Windows. This problem can appear only on Windows platform and can be fixed using the attached registry key file (a zip archive).