Now we can see that the migration completed successfully. Give it a few minutes depending on your connection to complete. You can now click new to do the migration. To get your mailbox database you can run the command as in the PowerShell window behind the main screenshot to get the name.
Give the move a friendly name, ensure that your domain is entered in Step 2. Now select the user, in this case it was User 5.
The New Migration Batch window opens, click the + button. On the Office 365 Tab, select Recipients, Migration and then click the + button and choose the second option as per the screenshot above. Once the Full sync has run we can now perform the migration. In Step E we are going to run a sync so that O365 knows about the changes, etc. Open up the EMS and run the following command: In Step D we can now set the GUID on the Mailbox on your on-premises server. Now in Step C we can check the GUID of the Mailbox: You can refer to this TechNet article if you want to see the commands: $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $UserCredential -Authentication Basic -AllowRedirection Once we click OK and it will appear nothing happened but it has connected. This will bring up the window as shown above and we can enter in our tenant login details. The first command to run is "Connect-MsolService". In Step B, we will connect to Azure AD using the Windows Azure AD PowerShell Module. This will give the result in the screenshot above, notice it shows 0's. In Step A, on the Exchange Management Shell, we run the following command:
You could also just copy the GUID in the error above as well.ĭ) Set the ExchangeGUID on-premises with the GUID from the Remote Mailbox. Here is the list of steps we are going to complete in order to get the mailbox to migrate back:Ī) Check the Exchange GUID of the mailbox on the on-premises Exchange Server.ī) Connect to Azure-AD, New-PSSession, Import the PSSession and check the Exchange GUID in the cloud.Ĭ) Check the ExchangeGUID of the Cloud Mailbox. In this example, User 5 was setup to move back to on-premises however after validation it fails with a mailbox GUID error. If you try to move a mailbox from O365 back to Exchange on-premises using the EAC on Office 365 it will fail, more below: To move a Mailbox from Exchange Online (O365) back to Exchange On-Premises has a few steps more involved.
0 kommentar(er)
