Switching from a 32-bit installation of Kerio Connect to 64-bit

Use these links to find instructions for your operating systems:

Microsoft Windows

The procedure of switching from a 32-bit Kerio Connect version to a 64-bit version differ on both 64-bit Windows and 32-bit Windows. systems. In case of latter, you require a new 64-bit windows machine to run 64-bit Kerio application.

NOTE

It is recommended to keep a full backup of your current installation before proceeding.

Linux

The procedure of switching from a 32-bit Kerio Connect version to a 64-bit version differ on both 32-bit Linux and 64-bit Linuxsystems. In case of latter, you require a new 64-bit linux machine to run 64-bit Kerio application.

NOTE

It is recommended to keep a full backup of your current installation before proceeding.

Virtual appliances

Use these steps to move from a 32-bit Kerio Connect virtual appliance to the 64-bit virtual appliance.

NOTE

It is recommended to keep a full backup of your current installation before proceeding.

  1. Deploy the 64-bit version of the Kerio Connect VMware appliance.
  2. Stop Kerio Connect on both appliances.
  3. Use SSHSecure Socket Shell - A network protocol that provides administrators with a secure way to access a remote machines. to connect to the appliances.
  4. Use SCP to copy the following items from opt/kerio/mailserver on the 32-bit appliance to the same folder on the 64-bit appliance:
  • license folder
  • mailserver.cfg file
  • users.cfg file
  • cluster.cfg file
  • sslcert folder
  • store folder.
  • Pack the whole store before copying.
  • If you have the store folder on an external hard drive, this step is not required.
  • ldapmap folder if you have edited any files
  • fulltext folder if you have enabled the full text search feature.
  • Pack the fulltext folder before copying.
  • If you have the fulltext folder on an external hard drive, this step is not required.
  1. Start running the 64-bit Kerio Connect appliance.