Exchange 2016 CU5, migration status syncing in ecp, but completed in Powershell

Question

_{Wednesday, May 31, 2017 8:44 PM}

Hi all,

I have a lab at home with 2 server in a dag. Running Exchange 2016 cu5. When I move mailbox using ecp from one database to another (they on different servers), the status in ECP is stuck in syncing even after many hours (small mailbox less than 50mb).

Same if I run get-migrationbatch

When I run get-moverequest they show as completed and I see they are successfully moved to another database.

Anyone has same issue?

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

All replies (7)

_{Thursday, June 1, 2017 2:38 AM}

Hi,

Tested in lab, it seems like though the mailbox move is completed, the Migrationbatch status doesn’t gets immediately.

It’s recommended to logout the ECP and login again then check the result, you can also change to another explorer to log into the ECP.

Recycle Mailbox Replication Service.

We can also move the following Arbitration mailboxes from the one E2k16 to another:

1. Move Migration Arbitration mailbox from one E2k16 to another.

2. Move SystemMailbox{...} from one E2k16 to another.

Then new mailbox move request in ECP and check again.

Hope it helps.

Regards,

Jason Chao

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, June 1, 2017 7:01 AM}

Hi Jason and thanks for prompt reply.

I did as you recommended:

Move arbitration mailbox to another server using:

Get-mailbox -arbitration | new-moverequest -targetdatabase EXDB01

When move completed I remove completed moverequest.

Confirmed that arbitration and system mailboxes are on the new server.

Logged in to ecp from another computer and did another move using gui.

Same problem, status still syncing even after 1 hour. Run Get-moverequest I get completed. Waited another 30 min, logged in to ecp from another computer, still in syncing. I will let migration batch stay like this until next day and see what happens :)

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

_{Thursday, June 1, 2017 7:14 AM}

Thanks for your response and effort, please update when you get the results, thanks.

Regards,

Jason Chao

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, June 1, 2017 9:25 AM}

Seems like status is now completed, not sure when the status changed.

Running get-migrationbatch also provides incorrect time

If I look in the migration log, request is complete at 8:55 AM

Will try another move and see how long delay it reports on migration batch :)

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

_{Thursday, June 1, 2017 9:49 AM}

Glad to hear the status has changed! Please keep updating.

Regards,

Jason Chao

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, June 1, 2017 10:09 AM}

Then did another move:

Started migration from ECP at 11:28 AM local time

In the log of migration batch, completed status was 11:34 AM

Confirmed status also completed at same time **(**11:34 AM) when run get-moverequest, but get-migrationbatch status is still syncing

In ECP status was completed at 12:05 PM

Same time (12:05 PM) when run get-migrationbatch.

Cant remember if 30 min delay has been default, but for sure when moving small mailboxes it usually never take more than 5-10 minutes.

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

_{Tuesday, June 13, 2017 1:50 AM}

Thanks for your response.

It seems it's get better. Per my experience, it always sometime delay in ECP.

Regards,

Jason Chao

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].