AutoDiscover for Exchange Hybrid

Question

Hi I have been removing our Old Exchange server 2010 from our Hybrid Environment (Exchange 2010 & Exchange 2016 & Office 365) . Now if I turned off Exchange 2010 server, seems AutoDiscovery is very slow, took about 2 minutes to find the user profile when setting up Outlook. So what would be the best way to check and move Autodiscover to the new Exchange sever? DNS Autodiscover has been pointing to Exchange 2016 server already.

Thanks
ML

Answer 1

Hi,

What is the value set on the AutoDiscoverServiceInternalUri for Exchange 2010 and Exchange 2016?

Let's suppose it is set to autodiscover.domain.com for both Exchange 2010 and 2016, does the DNS record for autodiscover.domain.com is pointing to the Load balancer VIP? If so, please check if the Exchange 2010 IP is still added in the VIP in load balancer. Try removing it if its added.

You can also add host file entry on the client machine for autodiscover.domain.com to point to Exchange 2016 to make sure if the delay is actually on the Exchange server or reaching the server.

Also, can you let us know if this happens for Exchange 2016 mailbox or Office 365 mailbox? For all users or specific users? or recently migrated users to office 365?

Answer 2

Hi @Namless Shelter , agree with the troubleshooting steps provided above to your question.

In Exchange hybrid environment, we need point autodiscover record to On-premise Exchange server.
For On-premise mailbox, it remain use previous autodiscover lookup behavior to find endpoint and access to Exchange.
For migrated mailbox, autodiscover service will redirect On-premise autodiscover record to Office 365 (autodiscover-s.outlook.com), and access to Office 365.

What's the configuration of your DNS records and the virtual directories? Point the autodiscover.domain.com to Exchange 2016 server. Please also check the log of test Email AutoConfiguration, you could share the result here, to help determine the steps of autodiscover.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hi There,

In our local DNS, Autodiscover.domain.com is definitely pointing to the new Exchange server 2016.

Also, there are lots Mailboxes are migrated from Old Exchange 2010 to Exchange 2016 and to Office 365.

Also, I did

Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri

AutoDiscoverServiceInternalUri : https://ex2010.mydomainname.edu/Autodiscover/Autodiscover.xml

AutoDiscoverServiceInternalUri : https://ex2016.mydomainname.edu/Autodiscover/Autodiscover.xml

There are two autodiscoverInternaluri...Should I remove the old Exchange 2010 AutoDiscoverServiceInternalUri??

Thanks,
ML

Answer 4

Hello,

Yes remove it

set-ClientAccessServer -identity old2010 -AutoDiscoverServiceInternalUri $null

You can also diagnose the autodiscovery process with oultook
ctrl + right clic on outlook button

and check the autodiscover way

Answer 5

Hi thanks for that now I can see definitely it is checking: ex2010.domainname.edu/autodiscover/autoxxx.xml... and then redirection to user@domainname.mail.onmicrosoft.com

so if I delete this entry, would it generate any issues if external DNS autodiscover.domain.external.au is still pointing to the old server?

I meant can I add it back by the command:

Set-ClientAccessServer -Identity ex2010 -AutodiscoverServiceInternalUri https://autodiscover.domainname.edu/Autodiscover/Autodiscover.xml

Can you clarify this is right command to add the AutoDiscover back please?

Thanks
ML