Start a conversation

Migration from the Source Server fails when using KIMT/KEMT

Overview

When migrating user data from the source Exchange or IMAP server, the Kerio Exchange Migration Tool (KEMT) or Kerio IMAP Migration Tool (KIMT) might experience an unexpected stop or hang. As a result, KEMT/KIMT partially migrates the user accounts' data.

A possible reason for inconsistently migrated data is having an empty User list. It happens when the migration user account doesn't have Administrator rights.

KEMT_004.jpg

 


 

Prerequisites

The OS meets Migration Tools requirements

Prepare the KEMT or the KIMT

Diagnosis

Faulty, huge, or corrupted items on the IMAP or Exchange source server. In-between devices (firewall, Antivirus, etc) are blocking the proper communication.

 

Back to top


 

Information

 

Workaround for KIMT and KEMT

 

  1. Create an IMAP or Exchange account in Outlook.
  2. Synchronize the IMAP/Exchange account with an existing MailHost provider.
  3. Install Kerio Outlook Connector (KOFF).
  4. Manually copy folders (or particular items) from the IMAP/Exchange account to the Kerio Connect KOFF account.

 

Workaround for KEMT

 

  1. Run the following command in Exchange Shell for each Exchange user. This will create a PST file for the user.

    New-MailboxExportRequest –Mailbox user –FilePath file.pst

  2. Import the PST file into a Kerio Connect account configured in Outlook (KOFF, Exchange ActiveSync).

 

Back to top


 

Related Article

Downloading Kerio Connect Directory Extensions and Migration Tools

Back to top

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments