question

AndrewSarratore-7716 avatar image
0 Votes"
AndrewSarratore-7716 asked AndrewSarratore-7716 commented

Exchange (2016) Hybrid Migration

I recently deployed a new Exchange server (2016). The end goal is to get rid of my 2010 server. The hybrid config wizard comes back with an autodiscover error, but the remote connectivity analyzer works without issue.
The bigger problem, is I can't migrate a new exchange mailbox to o365, the migration says it can't find my mail server. o365 support says this is an on prem server issue so they can't help. It's funny, because this is only here to facilitate the use of o365. Anyway, there is an internal DNS A record for autodiscover pointing to the Exchange server. Also the (Get-MigrationEndpoint).Identity command returns nothing, but I don't get any errors regarding the creation of the migration endpoint. I am stuck and going in circles!

Thanks!

office-exchange-hybrid-itpro
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AndyDavid avatar image
0 Votes"
AndyDavid answered AndrewSarratore-7716 commented

an internal DNS record isnt going to help here.
Have you met all the requirements including endpoints open on the firewall

https://docs.microsoft.com/en-us/exchange/hybrid-deployment-prerequisites



note:

Configure the Autodiscover record for your existing SMTP domains in your public DNS to point to your on-premises Exchange servers (an Exchange 2010/2013 Client Access server or an Exchange 2016/2019 Mailbox Server).

· 11
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Since Exchange server 2010 was working fine, do I still need to check this? I don't control public DNS records for our domain, they are done through a 3rd party. Mxtoolbox shows the autodiscover.mydomain.com has an A record pointing to one of our public IPs. However I can't find a nat on the firewall for it.

0 Votes 0 ·
AndyDavid avatar image AndyDavid AndrewSarratore-7716 ·

yes, if you want the 2016 server or the 2010 server to be the endpoint that is used to move mailboxes to 365, either server must meet those requirements

0 Votes 0 ·

Right, but the 2010 server was working just fine for migrations.

0 Votes 0 ·
Show more comments