<div>
To my knowledge, not without some third party software that is made for Mail migration. Autodiscover is used to discover the CAS server role so if you have autodiscover.domain.com pointing to two different IPs, it would DNS load balance them regardless of where the mailbox is. You would need something that knows that joe@domain.com is in this exchange org and Phil@domain,com is in this other Exchange org and can route inbound mail accordingly. Also, no matter what, you would never be able to send mail between the orgs.
</div>


<div>
I admit, I never thought of Forefront Identity Manager or TMG for it (since FIM is horrendously expensive and TMG is no longer offered) but I stand corrected. There seems to be a way using one of these products but not just using Autodiscover.
</div>


<div>
@Rahul - thank you for your comment.<br />
<br />
I should have specified that I'm referring to the autodiscover service working internally. Does the suggestion you gave still apply?
</div>


<div>
I never tried but i think its a Yes
</div>


<div>
Thanks! The autodiscover notes in one of the articles you posted were just what I was looking for.
</div>


<div>
welcome sw19-it. Hope will meet up in another session
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
We have two Active Directory forests, each containing an Exchange 2010 organisation, with no trust or communication issues between them.<br />
<br />
The two Exchange organisations share an SMTP namespace, so a mailbox could reside in either organisation. Is the autodiscover service capable of working in this scenario? <br />
<br />
I have exported SCP information from one forest to the other using the following PowerShell command:<br />
<br />

<pre><code class="code-1 nolinks" id="code-10-28935488-1"><span>Export-AutoDiscoverConfig -DomainController DomainControllerName -TargetForestDomainController TargetForestDomainControllerName -MultipleExchangeDeployments $true</span>
</code></pre>
<br />
This worked but for some reason, the domain whose namespace is being shared is not included in the list defined in the 'keywords' attribute, which lists the organisation's accepted domains. <br />
<br />
Does anyone know is what I'm trying to achieve is possible? I have a feeling that the fact the namespace is shared means we can't necessarily use autodiscover.<br />
<br />
Thanks<br />
Adrian
</div>
</div>


Hi,

We have two Active Directory forests, each containing an Exchange 2010 organisation, with no trust or communication issues between them.

The two Exchange organisations share an SMTP namespace, so a mailbox could reside in either organisation. Is the autodiscover service capable of working in this scenario? 

I have exported SCP information from one forest to the other using the following PowerShell command:

(CODE)

This worked but for some reason, the domain whose namespace is being shared is not included in the list defined in the 'keywords' attribute, which lists the organisation's accepted domains. 

Does anyone know is what I'm trying to achieve is possible? I have a feeling that the fact the namespace is shared means we can't necessarily use autodiscover.

Thanks
Adrian

Autodiscover in multi-forest Exchange 2010 environment with shared SMTP namespaces

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite. Although often used mainly as an email application, it also includes a calendar, task manager, contact manager, note-taker, journal, and web browser.

Outlook

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.