Exchange Autodiscover for multi-forest disjoint namespace

This is on Exchange 2010/2013 with Outlook 2010. CompanyA.com has merged with CompanyB.com to form NewCompany.com. Each company (A & B) has its own AD Forest, and its own separate Exchange server with its own users/mailboxes. These users now have a new default email address @NewCompany.com (that part has been configured fine). The problem is that Outlook tries to "autodiscover" the default email address (@NewCompany.com) and the mailboxes sit on two separate Exchange servers that know nothing about each other. Is there a way I can configure autodiscover so that users are "redirected" to the correct server? I do not want to user local XML files or do anything that requires changes to the client computers, I am looking for a solution that I can setup on the server side. Thanks!
criskritAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
There is no server side solution that I am aware of.
Obviously internally it isn't a problem, as the clients will query the domain for the information, but externally there is no mechanism for Exchange to redirect users to another server.
Therefore client side is your only option, almost certainly using an alternative URL than autodiscover.example.com.

Simon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Will SzymkowskiSenior Solution ArchitectCommented:
In situations like this I have also told that client to use a common namespace externally that ALL users will use. This is only for External access. Aside from that I agree with Simon there is no other way to accomplish this externally.

Will.
criskritAuthor Commented:
Hello guys and thanks for the answers. I feared there is no solution. Will, what do you mean by common external namespace? Obviously I can setup autodiscover.newcompany.com to point to an IP but the problem is distributing the users afterwards. Thanks.
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

Will SzymkowskiSenior Solution ArchitectCommented:
If you have your Exchange environment setup where there is one entry point you can setup multiple smpt domains (accepted domains) and or external relay domains. This way you only have to manage 1 entry point newcompany.com and then everyone connects using the same external mail.newcompany.com.

As you have currently stated in your initail question that you have 2 separate forests so there would be some work involved to get this working properly but it has to go to 1 common external dns name. From there you then Relay the email to another Exchange environment or create accepted domains and host the mail on the same server.

Will.
criskritAuthor Commented:
Email relay & flow is fine the problem is autodiscover. Autodiscover has to send some users to Exchange/Forest A and some users to Exchange/Forest B. Is this possible? If I setup autodiscover to point to ie Exchange/Forest A, is there a way to redirect users from there to Exchange/Forest B in the event that they are not found on the first server? Thanks.
Will SzymkowskiSenior Solution ArchitectCommented:
What you are specifically asking for is not possible for autodiscover. DNS has no intelligence to be able to decipher where connections should be going.

Unfortunately what you are trying to accomplish is not possible.

Will.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.