Troubleshooting Hybrid Migration
When you’re administering an Exchange Hybrid deployment, sometimes, the remove move migration don’t work anymore. Hereunder a few steps you can follow to help you understand how you can fix it.
Troubleshooting Hybrid Migration – MigrationServerAvailability
First, check the migration server availability :
Test-MigrationServerAvailability -ExchangeRemoteMove -RemoteServer mail.itfordummies.net -Credentials (Get-Credential -Message 'Onprem Creds')
You need to pass this step in order to complete a migration batch creation. You can also use this line :
Test-MigrationServerAvailability -ExchangeRemoteMove -Autodiscover -EmailAddress firstname.lastname@example.org -Credentials (Get-Credential -Message 'Onprem Creds')
You need to change the email or the domain name to fit your needs.
Depending on the error you have, you can check other things, hereunder some exemples, this is not a exhaustive list :
Troubleshooting Hybrid Migration – Endpoints
You should see your endpoint here, you can try to recreate it to be sure it uses the right account/DNS name :
You can also verify the permissions assigned to the service account of the endpoint.
Troubleshooting Hybrid Migration – MRS
You need to run this on your Exchange server on premise.Each test should pass in order to move forward in your troubleshooting.
You can also check at some settings of the Mailbox Replication Service itself :
Get-WebServicesVirtualDirectory | Format-List MRSproxyEnabled,WSsecurityAuthentication
Both of these should be set to true, if you modify them, you need to run an “IISReset” for them to applied :
Set-WebservicesVirtualDirectory -Identity 'YourServerNameEWS (Default Web Site)' -MRSproxyEnabled:$True -WSSecurityAuthentication:$True iisreset
You need to change the server name to fit your needs.
After each step you can run the “Test-MigrationServerAvailability” cmdlet, once it succeeds, you’re good to go :
You can now create your migration batches like you were used to.