Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Autodiscover and Exchange Multiple Forest

$
0
0

Hi Guys,

Appreciate input here.

Environment:

2 x Windows 2003 Forests with two way trusts ( ForestA, ForestB)

ForestA = Exchange 2007

ForestB = Exchange 2010

Clients = Outlook 2007/2010

Scenario:

We are migrating ForestA mailboxes to ForestB. This is been done with the Quest tools where the user's mailbox is migrated to  Exchange 2010 and its created as a linked mailbox in ForestB to the user account in ForestA. There will be some coexistence time between the two Exchange infrastructure. But eventually Exchange 2007 in ForestA will be killed.

Issue:

Now as we are going to have some Outlook clients in ForestA logging into ForestA Exchange 2007 and others logging into ForestB Exchange 2010. My main concern is with autodiscover. When Outlook user in ForestA opens Outlook it will do an SCP lookup and the info provided will be ForestA Exchange 2007 and this will be fine if the user mailbox resides on Exchange 2007 but if it resides on Exchange 2010 the information is all wrong. So I was thinking of the solution below to fix this or is there a better way?

Solution?:

- Create and autodicover A record in ForestA point to Exchange 2010 in ForestB

- Disable SCP on the client to be migrated to Exchange 2010 this will then force them to use the autodiscover A record I created

Will this work, is there a better way. I saw this command that will export the scp record from ForestB to ForestA. But how can the Outlook client tell what SCP record to connect to if the email alias namespace is the same in both Forests?

Export-AutoDiscoverConfig -DomainController DomainControllerName -TargetForestDomainController TargetForestDomainControllerName -MultipleExchangeDeployments $true

Thanks


Celtic


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>