Posted in : Exchange By Joel Jerkin

3 years ago

Recently in an Exchange Hybrid environment with Exchange Server 2016 on-premise and Exchange Online in Office 365 I encountered the following error message when trying to move a mailbox from on-premise to Exchange Online using New Migration Batch on Remote MRS proxy server:
”The connection to the server ’mail.domain.com’ could not be completed”

On the on-premise Exchange Server I ran the Test-MigrationServerAvailability command with the following parameters to verify the availability with migrating cross-forest:

Test-MigrationServerAvailability -ExchangeRemoteMove -Autodiscover -EmailAddress mailbox@domain.com -Credentials (Get-Credentials)


The result returned with Failed and looking at the error message, we can see the following:
The call to ’https://mail.domain.com/EWS/mrsproxy.svc’ failed”.
Trying manually to go to the URL, it returned with an error code of: ”Server Error in ’/EWS’ Application.”
Normally it would have returned ”The webpage cannot be found” with an 404 error code.
Going to the on-premise Exchange Admin Center, Servers > Virtual Directories > EWS (Default Web Site) I wanted to verify that MRS is enabled for that server – but as the picture shown below, it wasn’t.
I enabled the MRS Proxy Endpoint for the server by selecting the checkbox and press Save:

Restarting the WebAppPool MSExchangeServersAppPool on the specific server using the following command to make sure everything applied and any cache are cleared:

Restart-WebAppPool MSExchangeServicesAppPool

Going again to the URL https://mail.domain.com/EWS/mrsproxy.svc I now received the correct ”error code” of ”The webpage cannot be found” and 404.

Rerunning the Test-MigrationServerAvailability command, I now received a Success as the result:
Going back to the new migration batch, I could now proceed with the move of the mailbox to Exchange Online.

Tags : Exchange, Exchange Server, Hybrid, Office 365

Add comment

Your comment will be revised by the site if needed.