Share via

O365 migration endpoints

Anonymous
2015-11-23T14:30:08+00:00

Hi

I've seen this error several times across this forum, but it was often diagnosed through private message. So I thought I'd also give a try.

Ok we have enabled hybrid mode and we want to try the migration of some mailboxes before we move prod mailboxes.

On Office 365, I went to migration--> Migration Endpoints, click the + sign and try to create a migration endpoint using

  1. Exchange Remote migration type
  2. the email address of an on-prem mailbox that will be moved
  3. an account on my internal domain in Organization Management group

I get the following error:

We couldn't detect your server settings. Please enter them. The ExchangeRemote endpoint settings could not be determined from the autodiscover response. No MRSProxy was found running at ‎'(fqdn of my domain)‎'.

Remote MRS proxy server:

The FQDN of the Exchange server that the Mailbox Replication Service (MRS) Proxy is on.

Any help is welcomed

Thanks,

Martin

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

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

9 answers

Sort by: Most helpful
  1. Anonymous
    2015-11-30T10:27:24+00:00

    Hi

    A few things have been done, and I don't know which one resolved our issue

    1. Restart IIS on the on-prem server
    2. In the Exchange Server properties, Outlook Anywhere, I've un-checked Allow SSL offloading
    3. Give Organization Management AND Recipient Management rights on the admin AD account

    I was finally able to create my Migration Endpoint.

    Thanks,

    Martin

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2015-11-24T10:32:05+00:00

    Hi David

    On the first URL, 3 questions were asked:

    1.  Do the problematic on-premises mailboxes have the related SMTP email address?
    2.  Do you configure such as TMG server?
    3.  Make sure you have added Organization Management and Recipient Management to migration administrator.

    I know the mailbox have the correct SMTP address, and we don't use any kind of TMG. For the migration admin account, we only gave him Organization Management rights. I'll give Recipient Management and try.

    The person who posted the question mentioned he resolved the issue by adding the SPF record to his DNS server.

    I'm not an expert in DNS, but if I add "v=spf1 include:spf.protection.outlook.com ~all", most of destination mail servers would mark our mails as spam, or even reject them.

    Am I wrong?

    I've also noticed adding that spf is not mandatory for hybrid environment technet.microsoft.com/.../Checklist

    (Recommended as a best practice for all hybrid deployments)

    Thanks,

    Martin

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-11-24T09:48:16+00:00

    Hi Richard

    autodiscover DNS entry is already in place, and Remote Connectivity Analyzer test (outlook autodiscover) works fine.

    and yes, I can get to https://<external FQDN>/EWS/mrsproxy.svc without any problems (it asks for username and password)

    Martin

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Anonymous
    2015-11-24T03:20:07+00:00

    Hi Martin,

    In general, the Autodiscover DNS record needs to be pointed to on-premise Exchange Client Access server in a hybrid deployment. For detailed information, I suggest you run the Exchange Server Deployment Assistant. Expend the Configure Hybrid Deployment Prerequisites option, and click Configure DNS records. By doing so, Autodiscover can work for both the Office 365 users and the Exchange On-premises users.

    Also, please make sure that you can access 'https://<external FQDN>/EWS/mrsproxy.svc' from external network by using browser.

    Thanks,

    Richard

    Was this answer helpful?

    0 comments No comments