OFFICE 365 MIGRATION FAILURES

MFCMAPI CORRUPT MAILBOX ITEMS

When mailboxes fail to onboard correctly, the two main reasons are invalid folder structures or corrupt mailbox items. This document will deal with the second scenario.

When the Exchange synchronisation engine is synchronizing folder structures, if it encounters any corrupt items and the baditemcount has not been modified, the action will fail with an error:

Mailbox_OnboardingErrors_img1.png


To solve this error we first need to attempt a mailbox repair using Powershell.

Mailbox_OnboardingErrors_img2.png


To monitor the restore request we need to examine the application context event logs on the mailbox server hosting the content. Examine the event logs and see the result of the repair request:

Mailbox_OnboardingErrors_img3.png


Attempt the onboarding request again and examine the migration log. Any failures are likely to be corrupt items in the folder referenced in the failure log. In this example, there are multiple, corrupt items in the deleted items folder.

Mailbox_OnboardingErrors_img4.png


It is likely that any attempt to delete these using Outlook will fail with the following message:

Mailbox_OnboardingErrors_img5.png


We will need to use the MFXMAPI tool to delete these objects. Download the latest stable binaries of MFCMAPI from Sourceforge: https://github.com/stephenegriffin/mfcmapi/releases/tag/18.2.18068.37 (correct as of 10/4/2018) Unzip the MFCMAPI and ensure that you have FullAccess permissions to the mailbox within Exchange. We will also need to ensure that we disable cached Exchange mode to allow full availability of all mailbox contents.

Mailbox_OnboardingErrors_img6.png


Create an Outlook profile in the usual manner and open MFCMAPI with elevated privilege. Then click Session and Logon:

Mailbox_OnboardingErrors_img7.png


Select your Outlook profile and click OK

Mailbox_OnboardingErrors_img8.png












Double click the object that is listed as the default store for the profile.

Mailbox_OnboardingErrors_img9.png


Expand Root Container > Top Of Information Store and right click the folder where the corrupted items are reportedly located and choose Open Contents table.

Mailbox_OnboardingErrors_img10.png


Locate the corrupted items from their time stamps and group select, right click and select Delete Message:

Mailbox_OnboardingErrors_img11.png


Select Permanent delete Passing DELETE_HARD_DELETE (unrecoverable) and click OK.

Mailbox_OnboardingErrors_img12.png


Now click Session and Logoff

Mailbox_OnboardingErrors_img13.png


Repeat the process until no migration errors are encountered when onboarding the mailbox to Exchange online.

Flexera Clean Machine procedure

This document will outline the process for running the Flexera Remote Repackager on a clean virtual machine.

Locate your Remote Repackager Setup file. This should be located in: C:\Program Files (x86)\AdminStudio\10.0\Repackager\Remote Repackager

You may want to provide this/deploy this to your developers or map a drive to the machine with Admin Studio installed for them to carry out the install.



  Set the Admin Studio Shared location. UNC path \\\Admin Studio Shared ought to do it.

Set the Repackager location. This will be your machine which has Admin Studio installed on it. Possibly a server. You require to provide the location as a UNC e.g. \\TestServer\AdminStudio\10.0\Repackager

You should now have the below shortcut on your VM’s desktop. This starts a wizard which creates an MSI snapshot of your Virtual Machine consisting of file changes detected during an application installation.



Best practice would be to stop the Windows defender service on the clean machine and reboot the machine