How identify the root cause and stabilize mailbox migrations during an Exchange SE rollout

Question

How identify the root cause and stabilize mailbox migrations during an Exchange SE rollout

Hanah Cori 60

My second question:

After upgrading part of our messaging infrastructure to Exchange Server SE, several user mailbox migrations began failing intermittently, causing delays for business-critical teams.

Any cmdlet to diagnostic what happen and how to fix it ?

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hi Hanah Cori

Thank you for reaching out to Microsoft Q&A forum

In this context, you can try the below approach:

First of all, consider using move/batch statistics with the detailed MRS report to see whether errors are TransientFailure, CommunicationError/ProxyFailed, Authentication/TLS, or throttling/concurrency:

# Move requests (local or cross-forest)
Get-MoveRequest -MoveStatus Failed |
  Get-MoveRequestStatistics -IncludeReport | Format-List *
# Batches and per-user details (EAC/EH or EMS)
Get-MigrationBatch -Identity "<BatchName>" | Format-List
Get-MigrationUser -BatchId "<BatchName>" |
  Get-MigrationUserStatistics -IncludeReport |
  Export-Csv .\Batch_UserStats.csv -NoTypeInformation

For more information:

Get-MigrationUserStatistics

Get-MoveRequestStatistics

Moreover, from my experience, intermittent failures after upgrading often trace to EWS/MRS Proxy settings, load‑balancer pre‑auth, idle timeouts, or cert/TLS changes, therefore you can verify and test the MRS Proxy on all internet‑facing EWS virtual directories, by running:

Get-WebServicesVirtualDirectory |
  Format-Table Server,Identity,MRSProxyEnabled,InternalUrl,ExternalUrl
//
Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -MRSProxyEnabled $true
//
$cred = Get-Credential
Test-MigrationServerAvailability -ExchangeRemoteMove -Autodiscover -EmailAddress ******@contoso.com -Credentials $cred
Test-MigrationServerAvailability -ExchangeRemoteMove -RemoteServer mail.contoso.com -Credentials $cred
//
Test-WebServicesConnectivity -ClientAccessServer <ServerName> -TrustAnySSLCertificate

You can take a look for more information at:

Enable the MRS Proxy endpoint, Test‑MigrationServerAvailability and Test‑WebServicesConnectivity

And at the last steps, kindly check that required services are running and no components are Inactive/Draining (which can interrupt moves) by running:

Test-ServiceHealth
Get-ServerComponentState -Identity <ServerName> |Format-Table Component,State,Requester

Additionally, kindly ensure TLS 1.2 is consistent, the cert chain for the EWS URL is complete, SSL offloading isn’t applied to /EWS/mrsproxy.svc, pre‑authentication is disabled, and session persistence/idle timeouts are sufficient about 30–60 minutes.

You can try the above approach, if the problem still persists, kindly let me know in the comments for further support.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.