Exchange 2010 Autodiscover is returning Mailbox FQDN name instead of CAS FQDN

Hi Everyone,

I have 2 CAS/HT and 2 MBX Servers. CAS/HT are using NLB.

RPCClientAccesServer had been properly configured to point to NLB fqdn.

When Outlook starts for the first time, Autodiscover returns Mailbox Server's FQDN instead of CAS or NBL's FQDN, which causes the auto configuration to fail. I have to manually change the server name to the CAS or NBL FQDN in order to get outlook configured.

Any Idea?
Who is Participating?
AkhaterConnect With a Mentor Commented:
there are quite a few things that could do this, usually it is a sign that the autodiscover process is failing all together

1) are these user connecting from inside the network or internet?
2) are these user joined to the domain ?

on a client open outlook CTRL + Right click on the outlook icon and test email autoconfiguration remove all check boxes and select ONLY autodiscover and run the test

is it successful ? go to the xml tab and copy paste the results
Rajith EnchiparambilConnect With a Mentor Office 365 & Exchange ArchitectCommented:
Although you have stamped the rpcclientaccessserver on the databases, you need to configure the internal autodiscover properly, the autodiscoverserviceinternaluri.

Check and
garconerAuthor Commented:
HI Guys,

Thanks for the reply. Actually I found the answer by myself. The problem was with ssl certificate. I changed the certificate but exchange hadn't update IIS configuration properly. In IIS Manager, within Default web Site, I choose the new certificate in the drop-down list at binding options. After that, autodiscover came back to work fine again.

I will share the points to both of you since you gave some efforts on helping me here.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.