Here's the guide I used: http://www.expta.com/2011/07/how-to-configure-exchange-2010-sp1.html
Candee On Wed, Jul 23, 2014 at 7:44 AM, Candee <[email protected]> wrote: > Federation trust is absolutely the way to go. It's pretty easy to set up. > you set up the Microsoft Federation trust; and then you add your sister > companies as organization relationships. > It has to be set up in both domains, and then (usually) it just works. > > > On Tue, Jul 22, 2014 at 4:39 PM, Orlebeck, Geoffrey < > [email protected]> wrote: > >> Hello group! >> >> >> >> We have a couple sister companies with their own AD/Exchange environments >> that we manage. It’s come to a point where the main campus and the sister >> companies want to share calendar information for scheduling >> meetings/resources between their domains. >> >> >> >> This will be my first time setting up Exchange calendar sharing between >> external entities. We have trusts between each of the domains, but it >> appears Exchange 2010 doesn’t even require AD trusts, rather it leverages >> Exchange Federation Trusts. However, looking online I’m getting confused by >> the terminology and the “Microsoft Federation Gateway” component. The >> TechNet articles didn’t clear up the matter for me, and different guides >> I’ve come across make it sound like MFG is required, but that it’s an >> online service provided by Microsoft. That doesn’t seem accurate to me that >> we should have to go through MS to setup this type of trust. But I don’t >> know and could be wrong. Is there a guide someone can point me to for >> setting up calendar free/busy information for two on-premise Exchange 2010 >> SP3 servers? Is Federation Trusts the go-to method or am I missing the boat >> entirely on other options for sharing free/busy calendar information across >> domains? >> >> >> >> Thank you for your time. >> >> >> >> -Geoff >> Confidentiality Notice: This is a transmission from Community Hospital >> of the Monterey Peninsula. This message and any attached documents may be >> confidential and contain information protected by state and federal medical >> privacy statutes. They are intended only for the use of the addressee. If >> you are not the intended recipient, any disclosure, copying, or >> distribution of this information is strictly prohibited. If you received >> this transmission in error, please accept our apologies and notify the >> sender. Thank you. >> > >
