good job!
On Wed, Jul 23, 2014 at 6:15 PM, Orlebeck, Geoffrey < [email protected]> wrote: > Spent some time today and worked through the problems, so in case this > helps save anyone time in the future: > > > > Testing organization relationships failed on both Exchange servers stating > they couldn’t resolve “autodiscover.domain.org”. Both sites use split DNS > and because we setup domain trusts, DNS was resolving to the stub zones for > both domains (internally). The SRV record I created previously was only on > the external-facing DNS side. I added the SRV record on the internal DNS > servers of both domains and everything is working as expected. Hope this > helps. > > > > Thanks, > > Geoff > > > > *From:* Orlebeck, Geoffrey > *Sent:* Wednesday, July 23, 2014 11:36 AM > > *To:* '[email protected]' > *Subject:* RE: [Exchange] Exchange 2010 Federation > > > > That sounded confusing, I meant to say “With the guide you shared, I have > already been able to setup federation trusts between two domains”. > > > > Thanks, > > Geoff > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Orlebeck, Geoffrey > > *Sent:* Wednesday, July 23, 2014 11:14 AM > *To:* '[email protected]' > *Subject:* RE: [Exchange] Exchange 2010 Federation > > > > As a follow up, I was already able to setup federation trusts between two > domains already. The only caveat is I had to manually specify the > Application URI and the Autodiscover URL path. > > > > All four sites leverage TMG 2010 to publish OWA/ActiveSync. I had to add > an Autodiscover rule and Microsoft’s Exchange Test Connectivity completes > successfully for Outlook Autodiscover, but even after reporting success on > Microsoft’s Remote Connectivity Analyzer, trying to establish the > Organization Relationship automatically still fails. > > > > If this is a one-and-done type setup, I suppose it’s not that big of a > deal, but I also would think if Autodiscover works…then this should work, > too. Perhaps my lack of experience is missing something? > > > > Thanks, > > Geoff > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Candee > *Sent:* Wednesday, July 23, 2014 9:54 AM > > *To:* [email protected] > *Subject:* Re: [Exchange] Exchange 2010 Federation > > > > always welcome. > > good luck! > > > > On Wed, Jul 23, 2014 at 11:06 AM, Orlebeck, Geoffrey < > [email protected]> wrote: > > This guide is much clearer than the others I had come across. Thank you > for sharing! > > > > Geoff > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Candee > *Sent:* Wednesday, July 23, 2014 4:48 AM > *To:* [email protected] > *Subject:* Re: [Exchange] Exchange 2010 Federation > > > > 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. > > > > > > 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. > > > > 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. > 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. >
