OK, I was saying NO way is it this easy…… as long as autodiscover and EWS is working……
1. Create acct without mailbox on both domains (i.e.ID: domainx.com\Freebusy, Pass: P@ssw0rd
2. On Foobar
* Set-AvailabilityConfig -OrgWideAccount “domain1.com\freebusy”
* $a = get-credential (domain2.com\Freebusy, Pass: P@ssw0rd)
* Add-AvailabilityAddressspace -Forestname domain2.com -Accessmethod OrgWideFB -Credential:$a
3. On Ex2010.net
* Set-AvailabilityConfig -OrgWideAccount “domain2.com\Freebusy”
* $a = get-credential (domain1.com\Freebusy, Pass: P@ssw0rd)
* Add-AvailabilityAddressspace -Forestname domain1.com -Accessmethod OrgWideFB -Credential:$a And that’s it right?!
umm NO, that quite that easy… well it is IF you have internal DNS resolution and are syncing the contacts with the partner domain… Interorg uses the INTERNAL URL for EWS which means that needs to be resolvable (This can be remedied by split DNS and change the internal URL or use WAN\VPN link to the partner network) Also you must have contacts for the associated org in you org, best to use a tool like GALSync, ILM, or other identity management software. http://technet.microsoft.com/en-us/library/bb125182.aspx [http://feeds.wordpress.com/1.0/comments/exchangemaster.wordpress.com/240/] [http://feeds.wordpress.com/1.0/delicious/exchangemaster.wordpress.com/240/] [http://feeds.wordpress.com/1.0/stumble/exchangemaster.wordpress.com/240/] [http://feeds.wordpress.com/1.0/digg/exchangemaster.wordpress.com/240/] [http://feeds.wordpress.com/1.0/reddit/exchangemaster.wordpress.com/240/] [http://stats.wordpress.com/b.gif?host=exchangemaster.wordpress.com&blog=10618152&post=240&subd=exchangemaster&ref=&feed=1] http://exchangemaster.wordpress.com/2010/01/18/exchange-2010-interorg-freebusy-without-using-federation-gateway/
2. On Foobar
* Set-AvailabilityConfig -OrgWideAccount “domain1.com\freebusy”
* $a = get-credential (domain2.com\Freebusy, Pass: P@ssw0rd)
* Add-AvailabilityAddressspace -Forestname domain2.com -Accessmethod OrgWideFB -Credential:$a
3. On Ex2010.net
* Set-AvailabilityConfig -OrgWideAccount “domain2.com\Freebusy”
* $a = get-credential (domain1.com\Freebusy, Pass: P@ssw0rd)
* Add-AvailabilityAddressspace -Forestname domain1.com -Accessmethod OrgWideFB -Credential:$a And that’s it right?!
umm NO, that quite that easy… well it is IF you have internal DNS resolution and are syncing the contacts with the partner domain… Interorg uses the INTERNAL URL for EWS which means that needs to be resolvable (This can be remedied by split DNS and change the internal URL or use WAN\VPN link to the partner network) Also you must have contacts for the associated org in you org, best to use a tool like GALSync, ILM, or other identity management software. http://technet.microsoft.com/en-us/library/bb125182.aspx [http://feeds.wordpress.com/1.0/comments/exchangemaster.wordpress.com/240/] [http://feeds.wordpress.com/1.0/delicious/exchangemaster.wordpress.com/240/] [http://feeds.wordpress.com/1.0/stumble/exchangemaster.wordpress.com/240/] [http://feeds.wordpress.com/1.0/digg/exchangemaster.wordpress.com/240/] [http://feeds.wordpress.com/1.0/reddit/exchangemaster.wordpress.com/240/] [http://stats.wordpress.com/b.gif?host=exchangemaster.wordpress.com&blog=10618152&post=240&subd=exchangemaster&ref=&feed=1] http://exchangemaster.wordpress.com/2010/01/18/exchange-2010-interorg-freebusy-without-using-federation-gateway/
JC's Blog-O-Gibberish 