Hybrid On-premises user cannot see Free/busy for a cloud user

On-Premises user cannot see cloud user's Free/busy
On which version of Exchange is the on-premises users' mailbox located?
Log on to an on-premises user's mailbox and then try to view the Free/Busy for another on-premises user. This test is to verify that you do not have any issues with availability information retrieval within your on-premises environment. 

Were you able to see the Free/busy information?
Determine what error message you are receiving from OWA.
  1. Use the affected user's account to log on to the on-premises OWA.
  2. Create a new meeting request, and then add the on-premises user to the meeting.
  3. When the Hash marks are returned rest the pointer over them to display the error message. Note the error code number in the error message.
    P30_OnPremisesCannotSeeBusyFree
     
Select the appropriate error message in the following list to help narrow the troubleshooting steps that you must follow:
Verify that the Org Relationship settings are configured correctly to enable Free/busy for the users.
For Online Settings
Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect Windows PowerShell to the Service.
In Windows PowerShell, run the following command: Get-OrganizationRelationship -Identity "Exchange Online to On Premises Organization Relationship" | FL
The output should resemble the following:
  • TargetApplicatioURI: AppURL.Contoso.com
  • TargetAutodiscoverURI: https://autodiscover.contoso.com/autodiscover/autodiscover.svc/wssecurity
  • DomainNames: {Contoso.com}
  • FreeBusyAccessEnabled : True
  • FreeBusyAccessLevel: LimitedDetails
If a value must be changed, use the "set-OrganizationRelationship"cmdlet to fix the property. For more information about syntax and options to do this, see Set-OrganizationRelationship.
For On-Premises settings
From the Exchange 2010/2013 CAS, run the following command in Exchange Management Shell: Get-OrganizationReationship -Identity "On Premises to Exchange Online Organization Relationship”
The output should resemble the following:
  • TargetApplicatioURI: outlook.com
  • TargetAutodiscoverURI: https://podxxx.outlook.com/autodiscover/autodiscover.svc/wssecurity
  • DomainNames: {xxxx.mail.onmicrosoft.com,contoso.com}
  • FreeBusyAccessEnabled : True
  • FreeBusyAccessLevel : LimitedDetails
If a value must be changed, use the "set-OrganizationRelationship"cmdlet to fix the property. For more information about syntax and options to do this, see Set-OrganizationRelationship.

Did this solve your issue?
Verify that a token can be created that has test-federation trust.
From the on-premises environment, verify that you can retrieve a delegation token that will be used for Free/busy authorization. To do this, follow these steps:
  1. Open the Exchange Management Shell from the on-premises Exchange 2010 or 2013 server.
  2. Run the following command: Test-FederationTrust –UserIdentity User@company.com –verbose where User is the on-premises user who has issues viewing the cloud user's free/busy information.
  3. The output should show success for every test. If there is a failure, use the Hybrid Configuration Wizard again to try to reset the federation trust.
    P36_CannotSeeBusyFree
     
Did this solve your issue?
Determine whether the correct target address is specified on the MEU on-premises. Every Cloud Mailbox will have a corresponding on-premises object. This object must have the correct remote routing address (also known as the target address) specified. The remote routing address should contain a domain name similar to TenantName.Mail.OnMicrosoft.com.
To verify that the remote routing address is set, follow these steps:
  1. On the Exchange 2010 server or Exchange 2013 server, run the following command in the Exchange Management Shell: Get-RemoteMailbox Username |fl RemoteRoutingAddress, where username is the name of the cloud user that you are trying to see free/busy information for.
  2. Verify that the address contains TenantName.Mail.OnMicrosoft.com
    P34_CannotSeeBusyFree
     
Note: If you did not use the Hybrid configuration wizard, the domain name should reflect the remote routing domain that you have selected.

Did this solve your issue?
If you must have web proxy settings in your environment, verify that the on-premises Exchange 2010 and Exchange 2013 servers are set to use it.
On the on-premises Exchange 2010 and Exchange 2013 server(s) run the following command in the Exchange Management Shell: "Get-ExchangeServer | fl InternetWebProxy."
In most environments the results will be blank. However, if you have an outgoing proxy in your on-premises environment you may have to configure the correct proxy settings.
To resolve this issue, run the following command, where the address and port number http://192.168.5.56:8080 is replaced with your server address and port number:
Set-ExchangeServer -InternetWebProxy http://192.168.5.56:8080

Did this solve your issue?
Make sure that the time set on your server is not inaccurate by more than 5 minutes. If the server time is more than 5 minutes difference from real time, the communications with the federation gateway become invalid. This causes free/busy to fail.
For information about how to fix server time issues, see How to configure an authoritative time server in Windows Server.

Comments

Post a Comment

Popular posts from this blog

Hybrid Cloud user cannot see Free/busy for an on-premises user

Image
Does Free/busy work on-premises? Log on to an on-premises user's mailbox and then try to view the Free/Busy for another on-premises user. This test is to verify that you do not have any issues with availability information retrieval within your on-premises environment. Were you able to see the Free/busy information? Yes No 3 Cloud user cannot see On-premises user’s Free/Busy Use the following methods to verify that Autodiscover can be resolved from an external source and that the Firewall is open. Method one: Verify that Autodiscover is resolving to the on-premises Exchange CAS server From an external computer, open Command Prompt and type the following commands and press ENTER after each command: NSLookup autodiscover.< Your_Domain.com > In the response to the command, the "Address"value should be the external IP of the on-premises Exchan...
Read more