Hi @CodedNote Admin ,
Welcome to the Microsoft Q&A platform!
Based on your description, using EWS settings to switch on a "Remote Move" migration can be quite complex, and the problem you are experiencing could be caused by a number of factors. Let's break down your problem and address each one individually:
- The error message you are seeing indicates that the call to the MRS Proxy service is denied access. This could be due to a permissions issue, a network connectivity issue, or a misconfiguration of the MRS Proxy service.
- When you first add the endpoint, you may see different options because the migration batch creation process can infer certain settings from the endpoint configuration. It is important to ensure that the endpoint is configured correctly before creating a migration batch.
- If you have to check "Do not verify" to add the endpoint, this indicates that there may be a problem with the verification process. This could be due to a certificate issue or the endpoint could not be accessed at the time of verification.
- You have verified that the ApplicationImpersonation role is running, which is good. However, the migration process may require additional permissions or configuration to run properly.
- The fact that the migration reads the account but cannot transfer data could indicate a problem with the MRS Proxy service or the way the migration batch is configured. The service may be able to enumerate the mailboxes but encounter errors when trying to move the data.
- Using different credential formats will not impact the migration as long as the credentials are correct and have the necessary permissions.
- Excessive transient errors usually indicate a problem with the connection to the source or target server. This could be due to network issues, server load, or throttling policies.
- The MRS Proxy service is required for remote move migrations because it facilitates communication between the source and target servers. While EWS can be used for impersonation and other operations, the MRS Proxy service is designed for mailbox replication and migration scenarios.
You may want to check the following:
- Ensure that the MRS Proxy service is enabled and correctly configured on the source Exchange server.
- Verify that there are no network issues that prevent access to the MRS Proxy service.
- Check the event logs on the source and target servers for any errors related to the migration.
- Ensure that the certificate used by the MRS Proxy service is valid and trusted by the source and target servers.
If the problem persists, it may be helpful to enable verbose logging for the migration process to get more details about the errors that occur. Additionally, reviewing the documentation on moving mailboxes in hybrid deployments and cutover migrations can provide more insight into the problem.
Please feel free to contact me for any updates. And if this helps, don't forget to mark it as an answer.
Best,
Jake Zhang