bjblackmore
asked on
Free/Busy Federation Between Office365 Tennent & Hybrid Office365/On-Premise Tennent
We're trying to setup free/busy time calendar sharing between our company, and another we are partnering with.
We are running a hybrid environment, with an on-premise Exchange 2010 server, and Office 365 cloud, where all our mailboxes have just been migrated too.
The other company is running fulling Office 365, with no remaining on-premise servers.
We have both setup the Microsoft Federation Gateway and then run the following PowerShript:
Get-FederationInformation -DomainName thepartner.com | New-OrganizationRelationsh
However, although we can see their free/busy time (although only via OWA and Outlook 2010 SP1 - Outlook 2007 SP3 doesn't work). The partner company can't see any of our free/busy time, with OWA or Outlook.
Could anyone offer any suggestions on how to fix, or where to start troubleshooting?
We are running a hybrid environment, with an on-premise Exchange 2010 server, and Office 365 cloud, where all our mailboxes have just been migrated too.
The other company is running fulling Office 365, with no remaining on-premise servers.
We have both setup the Microsoft Federation Gateway and then run the following PowerShript:
Get-FederationInformation -DomainName thepartner.com | New-OrganizationRelationsh
However, although we can see their free/busy time (although only via OWA and Outlook 2010 SP1 - Outlook 2007 SP3 doesn't work). The partner company can't see any of our free/busy time, with OWA or Outlook.
Could anyone offer any suggestions on how to fix, or where to start troubleshooting?
ASKER
Thanks for the reply. I've run the PS command, and it completed successfully. I'm now waiting for feedback from the partner company to see if this has resolved the issue. I will report back as soon as I hear anything!
ASKER
I've received a reply from the partner federated company, and the issue remains, they are unable to see our free/busy time in Outlook 2010 or OWA.
I have attached the below pic as an example of what the federated company can see via OWA.
free-busy-issue.jpg
I have attached the below pic as an example of what the federated company can see via OWA.
free-busy-issue.jpg
Follow this: http://howexchangeworks.com/2009/07/diagnostic-logging-in-exchange-2010.html
And enable high or expert logging for all options under the availability service, then have your partner attempt to access a calendar for one of your on-prem users. Once they do, turn the logging back down and check the Application log for errors relating to the Availability service. That will give you more information about where the failure is occurring.
This will also help you figure out what's going on: http://support.microsoft.com/kb/2555008
And enable high or expert logging for all options under the availability service, then have your partner attempt to access a calendar for one of your on-prem users. Once they do, turn the logging back down and check the Application log for errors relating to the Availability service. That will give you more information about where the failure is occurring.
This will also help you figure out what's going on: http://support.microsoft.com/kb/2555008
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Had to raise a premier support ticket with Microsoft to resolve.
get-federationtrust | set-federationtrust -refreshmetadata
If you set up ADFS earlier than January, they have the wrong SSL information to properly pass free-busy data.