• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1375
  • Last Modified:

How to configure Autodiscover for mixed Exchange environment?

We have mixed Exchange environment:

1) Head Office domain: domain.com (parent domain)
    Exchange: 2003 (it is our bridge head server)
    Clients: mixed (Outlook 2007 & Outlook 2003)
    E-mail: user@domain.com

2) Site Office domain: branch.domain.com (child domain)
    Exchange: 2007 (all roles installed on one machine)
    Clients: Outlook 2007 & 2010
    E-mail: user@domain.com
    OWA, RPC and ActiveSync is published via ISA 2006
    Branch Site is connected to Head Office via IPSec VPN

We want to set up autodiscover for the site office exchange over the internet using ISA 2006.

We have UC certificate installed on Exchange machine and ISA.

A public DNS record is registered for autodiscover.domain.com which points to our ISA server's external IP.

Autodiscover external URL  is configured in Exchange as https://autodiscover.domain.com/autodiscover/autodiscover.xml

Our problem is:

Since all of us (both head office & site office) are using same e-mail address policy (user@domain.com), any user who is using Outlook 2007 and whose mailbox is in Exchange 2003 (head office) is also getting pointed to our Exchange 2007 (site office) because there is no way to disable autodiscover in Outlook 2007.

How autodiscover should be configured in our situation?

Is there a way to disable autodiscover in Outlook 2007 somehow? Group policy??
2 Solutions
Tony JLead Technical ArchitectCommented:
You're going to struggle here because one way or the other you're going to have to effectively break something.

You could try (try this on your internal DNS first as a test) - point the autodiscover address at a non-resolvable IP. Outlook'll fall back to traditional mechanisms such as RPC over http(s).

But that's theory I'm not sure off the top of my head if it would stop anything else working such as OOF.

Give it a go out of hours.
imranrftAuthor Commented:
Not complete solution.
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.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now