How to Migrate from Kerio Control (Windows Edition) to the Appliance Editions

From the Kerio  blog…

As of version 8 (announced earlier this month), Kerio Control is available only as as a software, virtual, or hardware appliance. This means customers who currently run the Windows version should strongly consider migrating to one of the appliance editions. There is no cost to transfer your license to the Software or Virtual Appliance, and in most cases, you can continue using the same hardware.

The actual migration process is not complicated, but there are several “best practices” to make the process a smooth one. I’ve listed the key steps below, and also some special considerations to be aware of:

http://www.kerio.com/blog/how-migrate-kerio-control-windows-edition-appliance-editions

Steps:

  1. Export the current Kerio Control configuration, including DHCP leases and SSL certificates. This backup will include the Kerio Control configuration and product license.
  2. Install the new Kerio Control software appliance/box with the same version of Control and same number of network interfaces as you have on Windows. We do recommend installing a new virtual appliance from OVF, or in case of a physical PC, use an ISO image.
  3. Setup your new Kerio Control appliance with different temporary IPs. The appliance needs a working Internet connection in order to finish setup.
  4. If you use Active Directory, connect the appliance to the AD. Do not use the same hostname as you have for Windows. You can change that later.
  5. Import your configuration to the appliance, and be sure to match network interfaces (LAN/WAN).
  6. Check if you have any additional IPs on Windows network interfaces or Windows custom static routes. If so, be sure to save them.
  7. Shutdown the Windows Kerio Control application.
  8. Use the appliance console to change the IPs to the same ones you that you had on Windows. If you had some additional IPs on the interfaces, use product web administration and add them as well.
  9. Log into the admin interface and make sure everything works as intended.

Special considerations:

  • When exporting the configuration, don’t forget to select also SSL certificates and DHCP leases.
  • Custom Windows settings (like custom routes, Dial-in interfaces etc.) won’t be transferred – you must configure those again on software appliance.
  • Note that export and import does not transfer IP addresses of the interfaces.
  • Due to the differences between Linux and Windows, any additional IPs on Windows interface won’t be transferred and must be configured manually on the appliance.
  • User statistics cannot be transferred to the new appliance.
  • If you use AD/OD for user authentication, we recommend creating a temporary Kerio Control local admin account in case of issues with AD/OD.

I hope this helps. Quite a few common questions that may come to mind are addressed in KB article titled: “Kerio Control (Windows Edition) to the Appliance Editions (Software/Virtual/Hardware)” More details about license and configuration transfer between the various editions of Kerio Control can be found in an article titled: ”Can I transfer my configuration and license from the Windows version of Kerio Control to the Software Appliance Edition?”

If you have any questions, please use the comments below and I will be sure to respond.

-Petr Dobry