It's a bit more complicated then that (see option #2 here: 
http://blogs.technet.com/b/exchange/archive/2011/06/28/cross-org-availability-using-federation-trust-and-organization-relationship.aspx)
 but yea... It wont be possible unless you create a separate namespace for each 
organization.

The reason for this is because when the source domain performs a lookup from 
EWS to the GCS, it doesn't see the address but the mail contact. It sees the 
Organizational Sharing policy and then papow (patent pending phrase) - it 
proxies the request to the target CAS so the EWS availability service fulfills 
the lookup and throws another proxy to the target CAS.. Then to the client.


There is a tad bit more to that... But the light is about to turn green 😅

Sent from my Windows Phone
________________________________
From: Javier Santana<mailto:[email protected]>
Sent: ‎4/‎29/‎2014 6:30 PM
To: [email protected]<mailto:[email protected]>
Subject: [Exchange] RE: Quick question

Did you end up coming up with a solution for this?

You have 2 separate forests with the same namespace? I'm guessing you aren't 
able to setup a federation either then?

If you aren't then once the federation is setup supply the forest name to the 
add-availabilityaddressspace command: add-availabilityaddressspace  -forestname 
exch2007forest

From: [email protected] [mailto:[email protected]] On 
Behalf Of Michael B. Smith
Sent: Sunday, April 27, 2014 11:01 PM
To: [email protected]
Subject: [Exchange] RE: Quick question

That is a real problem.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Nicholas Turner
Sent: Friday, April 25, 2014 4:49 AM
To: [email protected]<mailto:[email protected]>
Subject: [Exchange] Quick question

I've got 2 separate corporate entities here, one running 2010 and one running 
2007 both using out main domain as the primary SMTP for sending.  However our 
new CTO wants to share free/busy data between the two.  I can't personally 
(through reading the documentation) see how this can work with the native 
exchange autodiscover based systems as they are sharing the same primary 
namespace.  Any help please!

Regards

Nick

This electronic message contains information from CACI International Inc or
subsidiary companies, which may be confidential, proprietary,
privileged or otherwise protected from disclosure.  The information is
intended to be used solely by the recipient(s) named above.  If you are not
an intended recipient, be aware that any review, disclosure, copying,
distribution or use of this transmission or its contents is prohibited.  If
you have received this transmission in error, please notify us immediately
at [email protected]<mailto:[email protected]>
Viruses: Although we have taken steps to ensure that this e-mail and
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus free.

CACI Limited. Registered in England & Wales. Registration No. 1649776. CACI 
House, Avonmore Road, London, W14 8TS.


Reply via email to