Share via

Issue adding migration endpoint for cutover migration from exchange on prem

Anonymous
2021-09-01T16:29:55+00:00

Hello,

I am getting an error when adding a migration endpoint to exchange online. My server is an exchange 2010 SP3 with outlook anywhere configured and around 130 mailboxes. I am trying to get ready for a cutover migration. When adding the migration endpoint I get this:

We weren't able to connect to the remote server. Please verify that the migration endpoint settings are correct and your certificate is valid, and then try again. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues.

So i went to the webpage and everything passed with one warning about TLS, but otherwise it passes. BUT when i try to use powershell to verify migration server availability - Test-MigrationServerAvailability cmdlet, it returns result of failed. Down in the result I see the error 0x6ba The RPC server is unavailable.

This is conflicting information between the exchange connectivity page and powershell + the migration endpoint add results. Why would one pass and the others say cannot connect to server?

I verified the registry keys allowing ports 6001-6004 are there. Outlook anywhere is configured and enabled with basic authentication. Our SSL certificate is valid.

What else could possibly be wrong? I have been trying to figure this out for days with no luck.

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2021-09-02T14:39:31+00:00

Hi Alan,

Thanks for the reply. However I have already been through all those articles several times. I actually did find the problem thankfully! After days of research I finally stumbled across an article that described TLS and how Microsoft has been deprecating 1.0 and 1.1. After enabling TLS 1.2 and rebooting the server the communication was healthy from powershell tests and the migration endpoint successfully added.

I hope this helps someone in the future avoid the headache I have had over this.

Was this answer helpful?

0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2021-09-02T02:12:32+00:00

    Hi DavidsystemsIT,

    Very glad to have this chance to reply to your post here!

    Well for your issue (can't create the endpoint for your cutover migration on Office 365 side), there are 2 common factors:

    1. Authentication settings for Outlook Anywhere are incorrect.
    2. RPC proxy configuration settings for Outlook Anywhere are incorrect.

    Since you have confirmed that it gives error while you ran PowerShell cmdlet Test-MigrationServerAvailability, it means your Outlook anywhere hasn't been set up correctly. As you are Exchange 2010 SP3, you can refer to https://docs.microsoft.com/en-us/previous-versions/office/exchange-server-2010/bb123542(v=exchg.141) to check your Outlook anywhere again.

    Also, we have a similar case in https://docs.microsoft.com/en-us/answers/questions/315343/office-365-migration-endpoint-fails.html. And, you can refer to We weren't able to connect to the remote server error - Exchange | Microsoft Docs.

    We are always here for you.

    Regards,

    Alan

    Was this answer helpful?

    0 comments No comments