Diagnosing CodeTwo migration software

Problem:

CodeTwo assistance is required when you experience problems with CodeTwo Exchange Migration / CodeTwo Office 365 Migration or require advanced configuration of the software. You need to provide a description of your environment and/or send certain diagnostic files to CodeTwo.

Solution:

Please follow the steps below to provide comprehensive diagnostics to CodeTwo Support.

1. First of all, check with this article if the problem you encountered is already known. 
2. Take screenshots of error pop-ups or other unusual software behavior. Please make sure the error message is complete and readable - try expanding the error window so we can see the whole message on the screenshot or copy the error message text.

   Info

   In Windows 8 and newer, you can use Microsoft Problem Steps Recorder to conveniently document the problem.

3. Describe your environment and the migration scenario:
   1. What is the source server? Is it IMAP, Exchange or Office 365? What is the name of your IMAP service or which Exchange version (2010, 2013, etc.) and build number do you have? 
   2. What is the target server?
      • Exchange Online (Office 365) - which plan? Is it fully activated? 
      • MS Exchange Server on-premises (or hosted, but somewhere else than Exchange Online, e.g. on Azure) - how many servers, of which version (2010, 2013, etc.) and build number?
   3. Is it a cross-forest and/or cross-domain migration?

      Info

      It might be helpful to draw a diagram of the source and target environments' forests and any relations between them.

   4. If you migrate between two on-premises Exchange servers, is there a two-way trust setup between them?
4. Tell us about the machine on which our software is installed:
   1. Is the software installed directly on the source Exchange server or on another dedicated server or workstation?
   2. Is there MS Outlook present on the same machine? If so, in which version and architecture?
   3. What is the Windows version and architecture, how much RAM is available on that machine?
5. In performance or stability cases, please also export Event Viewer log files (branches: System and Applications) in .evtx format and gather necessary statistics:
   1. To acquire reliable results, performing a migration of only one mailbox will be the best option. Consequently, if you have been migrating multiple mailboxes, please remove the associations between them, leaving only one pair on the list. Then, please run the migration for at least an hour.
   2. Connect to your Office 365 / target Exchange Server using the PowerShell, execute the following cmdlet and include the results (the cmdlet obtains mailbox statistics):

      Get-MailboxStatistics -identity  | fl

   3. Go to this third-party website and start the Internet connection speed test, take a screenshot of the results.
6. Export ALL diagnostic files of the program (Go to: Help, Log Files and then navigate up one level). Compress all folders, except for the Cache directory, to a .zip file before sending them to CodeTwo. Your files are located in the following directory:

   %programdata%\CodeTwo\<name of the software>

7. Export all your .config files located in the main installation folder (simply copy/paste them somewhere and zip before sending to CodeTwo). By default, the installation folder is:

   C:\Program Files (x86)\CodeTwo\<name of the software>

8. In the case of problems with migration of particular items, please provide examples of failing items in .msg files or .pst archives.

   Important

   We need to get an exemplary item exported from the source server as well as from the target server so we can compare their properties. When connected to Exchange on-premises, please use the MFCMAPI tool to export to .msg; when connected to an IMAP server (e.g. Google Workspace [formerly G Suite]) or Office 365, you can drag items from Outlook onto your desktop to save as .msg.

   It is important to provide examples in either the .msg format or in a .pst container. This is to preserve items' properties. It is also important to zip such files prior to attaching to an email. MSG files get their properties modified by Exchange Servers the email travels through.

9. Compress all files (screenshots, log files, settings) into a single .zip file (Fig. 1.).

Fig. 1. Compressing all the files into a single ZIP file.

10. Use our file upload form to send the files and environment description to CodeTwo.