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

Exchange Autodiscovery

Exchange Autodiscovery

I have a client that’s has migrated away from their sister Org
We have a trust set up and they want to share some PC’s these are in two different forest.
They can log in to each others PC’s ok and the roaming profiles follower ok..
The issue is the Auto discover, each domain has its one DNS set up and correctly setup and keep their configurations. If are user logs in to its sister Orgs PC is auto discovers and try’s to connect to the local PC. I can stop by setting a GPO say not to auto discover, but my customer does not want this long term.

How can I sort this, I have few answers in my  mind but what have you done in the past?

1 Solution
Simon Butler (Sembee)ConsultantCommented:
If you have Exchange in both networks then Autodiscover is going to get in the way.
There is no simple answer to this - you can put local entries in for Autodiscover, but that is a per machine setting.

The only sure fire way is to ensure that everything is unique to the two sites. so the usernames are different etc.

Autodiscover doesn't use DNS internally, it makes a query to the domain. If it finds that then it will use it.

The other option would be to use OWA.

NytramAuthor Commented:
As I thought but always worth asking!
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

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

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