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

Posted on 2011-10-31
Last Modified: 2012-08-14
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?
Question by:garconer
    LVL 49

    Accepted Solution

    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
    LVL 24

    Assisted Solution

    Although you have stamped the rpcclientaccessserver on the databases, you need to configure the internal autodiscover properly, the autodiscoverserviceinternaluri.

    Check and

    Author Comment

    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.

    Featured Post

    Why spend so long doing email signature updates?

    Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

    Join & Write a Comment

    Granting full access permission allows users to access mailboxes present in their database. By giving full access permission one can open and read the content of any mailbox but cannot send emails from that mailbox.
    In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
    To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

    746 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now