Just need an additional pair of eyes to possibly identify something I might have missed.
Org 1 - Exchange 2007 SP2
Org 2 - Exchange 2010 SP2
These two Orgs are actually trusted with an internal pipe. Per the miscrosoft instructions Org 1 installed the required CAS 2010 SP2 box. Then they had to run the following cmdlet to proxy the free\busy requests (Add-AvailabilityAddressSpace -AccessMethod InternalProxy -ProxyUrl https:// theirserver.domain.com/ews/exchange.asmx -ForestName ourdomain.com -UseServiceAccount $True.
Then they were able to setup the Organization Relationship by placing our domain name in the "Automatically discover configuration information" and it worked just fine. Their 2007 CAS box has the "WSSecurityAuthentication" set to false while their 2010 CAS box has "WSSecurityAuthentication" set to true.
Now when we attempted to add their domain name in the "Automatically discover configuration information" GUI, it fails every time with the following error "Error - "Federation information could not be received from the external organization". So then I added it manually by inserting the domain name, Application URI, and autodiscover endpoint. When I did it this way it took it and showed to complete successfully.
Issue is this:
Their organization can see our free\busy and schedule meetings etc without any trouble (seems to work exactly the way its intended too). Our organization however cannot see anything.
Everything I have looked at shows its setup right, but we are still unable to see their free\busy. I also verified that their autodiscover shows to be setup right, but I'm still confused as to why then the GUI org relationship setup would fail? I do know that their WSSecurityAuthentication is set to true on their 2010 CAS as is ours. I also know that their 2007 CAS WSSecurityAuthentication setting is set to false, but apparently that cannot be changed.
Does anyone have any thoughts as to why we are unable to see their free\busy time. Everything looks right from where I'm sitting.
Thanks,
Blind