Read time: 4 minutes
When on-premises Exchange Server and Exchange Online (Microsoft 365) are used together, it is considered a hybrid deployment where both Exchanges remain operational. There are mailboxes that the administrator can migrate between on-premises and online versions. Due to improper settings and lack of necessary permissions, the migration can fail at any stage of the process, and you can get a random error. Generally, the admin can delete a migration batch and restart the process again, but you can also perform some troubleshooting tricks to overcome such errors without deleting the batch.
First, check how Exchange Server considers migration in a hybrid environment.
Onboarding – Migration of on-premises mailboxes to Exchange Online is called onboarding.
Offboarding – Migration of Exchange Online mailboxes to on-premises Exchange is called offboarding.
How does onboarding start?
In Exchange Admin Center, you can create a new move request for the selected mailboxes.
- Open Exchange Admin Center and log in with the admin credentials.
- Go to the Migration option, click + icon, and choose ‘Migrate to Exchange Online.’
- Follow ‘Select a migration type’>>’ Remote move migration’ and click Next.
- Choose the mailboxes that you require to migrate to Exchange Online.
- Provide the on-premises Exchange account details on the ‘Enter on-premises account credentials’ page.
- Choose an existing migration endpoint in the ‘Confirm the migration endpoint page and ensure that the endpoint is MRS proxy enabled.
- Please provide a name to the migration batch and start it. It will migrate Live Exchange Server to Office 365 mailboxes.
- Login to Microsoft 365 with your admin account and go to the Admin app.
- Open Exchange Admin Center from the Admin list.
- Go to the Migration section, click Add (+), and then choose ‘Migrate from Exchange Online.’
- Choose the Remote move migration option in the ‘Select a migration type page’ as the migration type.
- Choose all the mailboxes that you require to migrate to on-premises Exchange.
- The next page is ‘Enter on-premises account credentials,’ where you must input the full name of the on-premises database name.
- The ‘Confirm the migration endpoint’ page will ask you to access the endpoint, and it should have MRS Proxy enabled for migration.
- Input a name to the migration batch and begin the migration.
The troubleshooting methods are based on the cause of migration errors, and you should use them in accordance with your type of error. The errors can occur in any kind of migration like Office 365 cutover migration, staged, or even hybrid one. We are giving some general methods that may prove helpful in running a safer Exchange migration.
Method 1 – Check the current status of the migration request
Before troubleshooting, you should determine the status of the current migration request.
- Connect Windows PowerShell with Exchange Online and run the following cmdlet:
Get-MigrationBatch |fl *status*,Identity
- If the status of the migration batch shows completed, then it is great as the migration is completed successfully.
- If the status is queued/suspended/syncing/in-progress or failed, then go to other methods.
Method 2 – Check the accepted domains
Sometimes, the domain names of the user in Exchange Online are not accepted by the service, and the migration batch may fail due to such unaccepted domains. You must verify them in the service.
- Start Exchange Management Shell and run a special command-
(Get-Mailbox’ username’).EmailAddresses.
- Open Windows PowerShell and connect with the Exchange Online account.
- Run the cmdlet-
Get-AcceptedDomain
In the resultant list, note down the name of domain names.
In the new list, check if there are domain names that you took in the first step. If not, then add them with the help of your domain registrar.
Method 3 – Make sure that IIS Server is accepting migration
IIS network server responds to the current migration request with the help of some traffic handlers like EWS and Autodiscover. If the migration batch shows syncing state for a longer period, you can check if the traffic in the IIS server is mapped properly.
- In Administrative tools, open IIS Manager.
- Follow server name>>sites>>default web site>>EWS.
- Open the Handler Mapping option. Look for a specific mapping where the name is ‘svc-integrated,’ path is ‘*svc,’ and State is ‘Enabled.’
- Check the same process for Autodiscover virtual directory.
- If the values are missing, then in the Exchange System, open the command prompt and change the directory to the given path-
Drive:\Windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\
- Input the command-
Input enter and restart the migration batch.
Method 4 – Run the migration batch through PowerShell
Running the migration request through PowerShell brings better results, and it requires lesser steps too.
- Open Windows PowerShell and connect it with Exchange Online.
- In a user-defined variable, input the credentials of your on-premises Exchange Server.
- Run the other cmdlet to start the migration batch –
New-MoveRequest -Identity ‘User’ -Remote -RemoteHostName ‘example.contoso.com’ -RemoteCredential $ExchangeCred -TargetDeliveryDomain ‘example.mail.onmicrosoft.com’
Conclusion
Proper troubleshooting is required to fix errors during manual migration between Exchange on-premises and Exchange Online platforms. And many work hours will be consumed in troubleshooting, which can also damage the databases. You should use a professional Exchange Migration tool like Kernel Migrator for Exchange and create a batch in which the information of source and destination will be saved. There are ample filters and scheduling features to ease the migration and lower the chances of errors.
