Overview

When moving a Kerio Control Virtual Appliance (VA) from one VMware ESXi hypervisor to another, it's essential to follow a structured process to ensure service continuity and avoid licensing issues. Customers may encounter problems like network misconfiguration, double license activation, or loss of configuration if this migration is not performed correctly.

This guide walks you through the entire migration process—from preparation and backup to reactivation and testing.

Solution

Follow these steps to safely migrate your Kerio Control VA:

1. Prepare for Migration

• Confirm both source and destination ESXi hosts run compatible VMware versions.

• Verify the destination host has enough storage and system resources.

• Ensure both ESXi hosts are network-connected for file transfer.

2. Back Up the Virtual Appliance

• Use Kerio Control’s built-in tools to create a full backup - Exporting and Importing configuration backups.

• Store the backup in a safe, accessible location for recovery if needed.

3. Power Off the Virtual Appliance

• Gracefully shut down the Kerio Control VA from the source ESXi host.

4. Export the VA as an OVF Template

• Open vSphere Client, right-click the Kerio Control VA.

• Select Export OVF Template, and save the resulting files.

5. Transfer the OVF Files

• Copy the exported OVF and VMDK files to a location reachable from the new ESXi host.

6. Import the VA on the New ESXi Host

• In the vSphere Client connected to the new host, go to File > Deploy OVF Template.

• Follow the deployment wizard and assign correct resources (e.g., datastore, network).

7. Power On and Validate Configuration

• Start the newly imported VA.

• Confirm all previous settings (firewall rules, interfaces, DHCP, etc.) are intact.

• Test network connectivity and Kerio Control services.

8. Re-register with GFI App Manager

• After license activation, proceed with adding your new appliance to GFI AppManager.

• Ensure the old instance is no longer registered.

9. Test Functionality

• Perform a full feature check (e.g., VPN, bandwidth management, filtering) to ensure all services work as expected.

10. Decommission the Old Instance

• Once validated, safely remove the old Kerio Control VA from the source ESXi host.

Summary

Migrating a Kerio Control VA between ESXi hypervisors requires careful preparation, licensing management, and post-migration verification. Following these steps ensures minimal downtime and preserves your network configuration and security posture.

For additional guidance, refer to the articles on Installing Kerio Control Virtual Appliance for VMware and Migrating Configuration from one Kerio Control hardware appliance to another.

FAQ

Q1: Will my settings be preserved during migration?
A1: Yes, exporting and importing the OVF preserves settings, but always verify configurations post-import.

Q2: Can I keep both the old and new VAs running during the transition?
A2: A license will become inactive when the appliance where it is installed in is offline, and it is important that there are no 2 appliances running on the same license. Therefore, my suggested path forward would be to obtain a trial license for the Kerio Control destination server (make sure you use an email address that hasn't been used before to generate a trial). 

Q3: What happens if I forget to unregister the old VA from GFI App Manager?
A3: Licensing conflicts may occur. Always deactivate the old VA to allow clean registration on the new host.