Exchange 2013 Mailbox Migration Error

One of Directions Training’s Microsoft Technical training experts wanted you to know…

During a recent Exchange 2010 to 2013 migration, I ran into a problem when performing mailbox migrations. This only appeared to happen on larger mailboxes, roughly 1.5-2GB or larger. The result is stated as “Stalled duration” in the Migration Batch details.

The issue is caused by a Content Indexing failure on the target database. As it turns out, this is a known problem which is caused by a missing element of the AD Prep portion of setup. The problem may also manifest itself, in a multiple DAG configuration when attempting synchronization.

The following steps will correct the problem and cause the migration process to continue on as expected:

  1. Add a ContentSubmitters group to AD. I did this manually, creating a Security enabled Universal group.
  2. Assign Network Service and Administrators groups “Full Control” permission. This can be done in the GUI or I used the following PowerShell commands:
    Add-ADPermission -Id ContentSubmitters -User “Network Service” -Access Rights GenericAll
    Add-ADPermission -Id ContentSubmitters -User “Administrators” -Access Rights GenericAll
  3. Stop the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services.
  4. Delete the Content Index data for the affected database(s). This is the folder with a GUID name inside the folder where the mailbox database lives.
  5. Start the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services.

After a few minutes, the status of the content index went from FailedAndSuspended to Crawling, at which point the mailbox move resumed.

Note: The problem is documented here. For more Microsoft Technical Training information visit www.directionstraining.com or call 1-855-575-8900.