Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

Exchange Autodiscover and Co-Existence

Hello Experts,

I have a scenario where users are accessing Exchange via a 3rd party hosted Exchange provider.  We are in the process of building out a local dedicated Exchange server.  Prior to installing though, I'm trying to think of all the issues that may come up after I complete the Exchange install.  One such obvious issue is that the Outlooks will attempt to use the AD scp record for autodiscover, while the mailboxes are still connecting to the 3rd party provider.  This will present various issues and I wont be able to migrate everyone immediately and will need this co-existence while testing and migrating. To mitigate this issues, one option I'm thinking of is disabling the scp by setting the autodiscoverinternaluri to $null.  The other option is for me to edit the scp and point it to the 3rd party provider until I'm ready to cutover.  What do you guys think?  Also, is there any other user nuisances that I should be mindful about while running the co-existence ?
1 Solution
Simon Butler (Sembee)ConsultantCommented:
Setting the URL to the external provider is the method I have used in the past, but it will need to be changed as soon as users start coming back inside. If you don't change it, then Out of Office and free/busy information will not work.

No easy answer, because Exchange simply wasn't designed to coexist in this kind of scenario.


Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

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