My problem simply stated is the autodiscover service is returning incorrect (or at least undesirable) values for "Server" and "Certificate Principal Name:" under the "Protocol: Exchange HTTP" section when the "Test E-mail AutoConfiguration" utility is run from Outlook. More specifically, it returns Exchange settings applicable to a child domain Exchange account when being queried on behalf of a user with a root domain Exchange address/account. More details regarding our implementation of Active Directory and Exchange, along the problem encountered, are below: --- Environment Overview --- * Single forest with multiple child domains* Exchange 2007 SP1 (Hub Transport, CAS, and Mailbox roles) is installed at the root of the forest (ex: contoso.com)* Users with mailboxes on the root Exchange servers have their primary smtp address set to either user@contoso.com or user@mail.contoso.com* Exchange 2007 SP1 (CAS and Mailbox) roles are installed in one of the child domains (ex: child.contoso.com)* Users with mailboxes on the child domain Exchange server have their primary smtp addresses set to user@child.contoso.com --- Problem Details ---* The resulting issue appears when attempting to configure Outlook 2007 from machines off of our internal network - i.e. a request coming from an Outlook Anywhere Exchange HTTP client. In those instances, the values returned by AutoDiscover don't always reflect the preferable settings relative a user's mailbox. Ideally a user with a mailbox on the root Exchange Servers would be directed to use the root-level CAS servers and users with mailboxes on the child domain Exchange server would be directed to use the child domain CAS server.* The behavior can be reproduced using the "Test E-mail AutoConfiguration" utility from Outlook 2007. Regardless of the e-mail address entered (ex: user@contoso.com for root accounts or user@child.contoso.com for child domain accounts), the resulting Server and Certificate Principal Name values returned seem to bounce back and forth between mail.contoso.com and mail.child.contoso.com when the "Test" button is pressed consecutively. I did find the http://msexchangeteam.com/archive/2008/09/26/449908.aspx post on the Exchange Team blog, which was helpful. However, I think the answer to the issue I'm posting about ultimately lies in the logic used to determine the "best CAS server" as is mentioned in section 6b of the article, excerpted below: "If the request is made by an Outlook Anywhere Exchange HTTP client, the EXPR provider will return the External URL configured on the best CAS server for the same services" Is there a setting that will allow us to configure the AutoDiscover services such that a user with a mailbox on the root Exchange Servers would be directed to use the root-level CAS servers and users with mailboxes on the child domain Exchange server would be directed to use the child domain CAS server? Thanks.

Hi,There is no setting in Exchange 2007 that can do this "Is there a setting that will allow us to configure the AutoDiscover services such that a user with a mailbox on the root Exchange Servers would be directed to use the root-level CAS servers and users with mailboxes on the child domain Exchange server would be directed to use the child domain CAS server?"The best CAS returned depends on the site the Exchange servers are located in. Sounds to me like all your exchange servers are located in the same AD site.Would it be possible for you to seperate the exchange servers into different AD sites?Leif

Thanks for the reply. All of the Exchange servers are in the same AD site. We'd rather not seperate the child domain into a seperate site, butthanks for the suggestion. Ultimately, from our user's perspective, this hasn't been a major issue (more of an annoyance)and probably isn't worth spending much more time on now that we a definitive answer regardingthe lack ofconfigurable options to address the issue.-Lance