Batch migration stopped at Synced

%3CLINGO-SUB%20id%3D%22lingo-sub-204616%22%20slang%3D%22en-US%22%3EBatch%20migration%20stopped%20at%20Synced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-204616%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20an%20Exchange%202007%20server%20and%20we%20are%20migrating%20to%20O365.%20Followed%20the%20documentation%20for%20migrating%20by%20installing%20an%20Exchange%202013%20server%20to%20act%20for%20use%20in%20a%20hybrid%20environment%20as%20we%20wish%20to%20manage%20onsite.%3C%2FP%3E%3CP%3EI%20have%20used%20AzureAD%20Connect%20to%20synchronize%20the%20user%20accounts%20and%20I%20just%20did%20the%20first%20batch%20migration%20from%20the%202007%20server%20to%20office%20365.%20However%20I%20have%20encountered%20an%20issue.%20The%20trial%20mailbox%20is%20stuck%20in%20the%20Synced%20status%20and%20has%20not%20finalised.%3C%2FP%3E%3CP%3EI%20have%20attached%20a%20screenshot.%20When%20I%20use%20powershell%20I%20can%20see%20the%20move%20with%20get-migrationbatch%20but%20there%20is%20no%20move%20request%20associated%20with%20it.%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20how%20to%20get%20this%20to%20a%20finalised%20state%20as%20at%20present%20it%20appears%20to%20be%20both%20on%20premise%20and%20in%20office%20365%20but%20with%20the%20Office%20365%20side%20being%20where%20new%20email%20arrives.%3C%2FP%3E%3CP%3EI%20want%20the%20mailbox%20gone%20from%20the%20on%20premise%20and%20available%20only%20on%20Office%20365.%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-204616%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMigration%20issue%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-205479%22%20slang%3D%22en-US%22%3ERe%3A%20Batch%20migration%20stopped%20at%20Synced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-205479%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20it%20was%20a%20test%20account%20I%20followed%20the%20article%20and%20it%20worked.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20mailbox%20no%20longer%20appears%20in%20the%20Exchange%202007%20management%20console%20but%20appears%20in%20the%20Office%20365%20portal.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20top%20of%20that%20opening%20outlook%20within%20the%20organisation%20automatically%20opens%20the%20users%20mailbox%20and%20outlook%20anywhere%20and%20active-sync%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20going%20to%20test%20a%20couple%20of%20more%20mailboxes%20and%20if%20I%20get%20the%20some%20results%20then%20this%20will%20be%20the%20method%20I%20use.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-205104%22%20slang%3D%22en-US%22%3ERe%3A%20Batch%20migration%20stopped%20at%20Synced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-205104%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20John%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20have%20Hybrid%20with%20Exchange%202013%20that%20article%20would%20not%20help%20you%2C%20please%20review%20the%20batch%20if%20it%20has%20a%20complete%20button%2C%20or%20stop%20and%20start%20again%2C%20if%20it%20does%20not%20work%20please%20open%20a%20support%20ticket%2C%20but%20do%20not%20follow%20that%20article%2C%20that%20will%20break%20mailbox%20in%20an%20hybrid%20configuration.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-205090%22%20slang%3D%22en-US%22%3ERe%3A%20Batch%20migration%20stopped%20at%20Synced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-205090%22%20slang%3D%22en-US%22%3E%3CP%3ENo%20finalize%20button.%20Only%20stop.%3C%2FP%3E%3CP%3EI%20found%20this%20article%20which%20I%20was%20going%20to%20try%20as%20it%20sounds%20like%20the%20thing%20to%20do.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fconvert-exchange-2007-mailboxes-to-mail-enabled-users-a1f79f3c-4967-4a15-8b3a-f4933aac0c34%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%20color%3D%22%230563c1%22%20face%3D%22Calibri%22%3Esupport.office.com%2Fen-us%2Farticle%2Fconvert-exchange-2007-mailboxes-to-mail-enabled-users-a1f79f3c-4967-4a15-8b3a-f4933aac0c34%3C%2FFONT%3E%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-204625%22%20slang%3D%22en-US%22%3ERe%3A%20Batch%20migration%20stopped%20at%20Synced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-204625%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F154183%22%20target%3D%22_blank%22%3E%40John%20Oliveira%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDo%20you%20have%20the%20finalize%20button%20%3F%20When%20you%20create%20the%20batch%20you%20have%20selected%20to%20complete%20automaticly%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi, 

I have an Exchange 2007 server and we are migrating to O365. Followed the documentation for migrating by installing an Exchange 2013 server to act for use in a hybrid environment as we wish to manage onsite.

I have used AzureAD Connect to synchronize the user accounts and I just did the first batch migration from the 2007 server to office 365. However I have encountered an issue. The trial mailbox is stuck in the Synced status and has not finalised.

I have attached a screenshot. When I use powershell I can see the move with get-migrationbatch but there is no move request associated with it.

Does anyone know how to get this to a finalised state as at present it appears to be both on premise and in office 365 but with the Office 365 side being where new email arrives.

I want the mailbox gone from the on premise and available only on Office 365.

Any help would be greatly appreciated.

4 Replies
Highlighted

Hi @John Oliveira,

 

Do you have the finalize button ? When you create the batch you have selected to complete automaticly ?

Highlighted

No finalize button. Only stop.

I found this article which I was going to try as it sounds like the thing to do.

support.office.com/en-us/article/convert-exchange-2007-mailboxes-to-mail-enabled-users-a1f79f3c-4967...

Highlighted

Hi John,

 

If you have Hybrid with Exchange 2013 that article would not help you, please review the batch if it has a complete button, or stop and start again, if it does not work please open a support ticket, but do not follow that article, that will break mailbox in an hybrid configuration.

Highlighted

As it was a test account I followed the article and it worked.

 

The mailbox no longer appears in the Exchange 2007 management console but appears in the Office 365 portal.

 

On top of that opening outlook within the organisation automatically opens the users mailbox and outlook anywhere and active-sync work.

 

I am going to test a couple of more mailboxes and if I get the some results then this will be the method I use.