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

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?
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

  1. From an external computer, open Command Prompt and type the following commands and press ENTER after each command:
    • NSLookup
    • autodiscover.<Your_Domain.com>
  2. In the response to the command, the "Address"value should be the external IP of the on-premises Exchange CAS server. For example: Name: autodiscover.contoso.com Address: 38.96.29.10

Method two: Verify that you can send an Autodiscover POST request to potential Autodiscover URLs

  1. Go to https://www.testexchangeconnectivity.com
  2. On Microsoft Office Outlook Connectivity Tests select Outlook Autodiscover, and then click Next.
  3. Complete the Outlook Autodiscover form (Email address, User Name and password), then click Perform Test.
If the Exchange connectivity tests fail for autodiscover, check the on-premises Autodiscover Internet Access configuration. For more information about how to do this, see the Microsoft TechNet topic Configure the Autodiscover Service for Internet Access.

Did this solve your issue?
Is the domain name present in the org relationship?
To verify the domain name value in the Organization Relationship, follow these steps:
  1. Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect to Exchange Online using remote PowerShell .
  2. In Windows PowerShell , run the following command: Get-OrganizationRelationship -Identity "Exchange Online to On Premises Organization Relationship" | FL
  3. Check DomainName value. The vanity domain (yourdomain.com) should be present.
  4. If the DomainName value is missing your vanity domain, run the following command: Set-OrganizationRelationship -Identity "Exchange Online to On Premises Organization Relationship" –DomainName yourdomain.com
Did this solve your issue?
Verify that the autodiscover endpoint is pointing to the on-premises Exchange Hybrid Server(s).
Check the IIS logs on the Exchange Hybrid server to verify that the Autodiscover POST request is being received by this server:
  1. On the Exchange Hybrid Server, click Start, click Run, type %SystemDrive%\inetpub\logs\LogFiles, and then press ENTER.
  2. Open the W3SVC1 folder, then open the most recent IIS log file
  3. Search for "Autodiscover"
  4. The following screen shot shows an example of the Autodiscover POST request on IIS log: 
P10_error5039
 


If you do not see any entry for Autodiscover in your on-premises Exchange hybrid deployment server, the firewall may be pointing to a wrong CAS server.

Did this solve your issue?
Verify that the Microsoft Exchange Web Services (EWS) are resolvable and there are no firewall issues.
Check IIS logs on the Exchange 2010/2013 CAS server(s) to confirm that Web Services request is being received by this server. To do this, follow these steps:
  1. On the Exchange 2010/2013 CAS server, click Start, click Run, type %SystemDrive%\inetpub\logs\LogFiles, and then press ENTER.
  2. Open the W3SVC1 folder, and then open the latest IIS log file.
  3. In the latest IIS log file, search for "exchange.asmx/wssecurity”. The following screen shot shows an example of the request in the IIS log:
    P15_error5016
     
  4. If you do not see any entry for "exchange.asmx/wssecurity"in your on-premises Exchange 2010/2013 hybrid deployment server, the firewall may be pointing to a wrong CAS server, or you may have pre-authentication configured on the firewall. For information about how to bypass firewall pre-authentication, see How to Configure TMG for Office 365 (Exchange) Hybrid deployments.
Did this solve your issue?
Follow these steps to verify if EWS has External URL set:
  1. On the on-premises Exchange hybrid deployment server, open Exchange Management Shell, and then run the following cmdlet: Get-WebServicesVirtualDirectory | FL Name,Server,externalURL
  2. If the ExternalURL is missing on the Exchange hybrid deployment server, run the following cmdlet: Set-WebServicesVirtualDirectory -Identity "ServerName\EWS (Default Web Site)" -ExternalUrl https://mail.contoso.com/ews/exchange.asmx
Did this solve your issue?
Is WSSecurity enabled as an authentication method?
On the on-premises Exchange hybrid deployment server, run the following command in Exchange Management Shell: Get-WebServicesVirtualDirectory | fl name,server,externalURL,ExternalAuthenticationMethods
If the WSSecurity is missing for ExternalAuthenticationMethods is missing on Exchange hybrid deployment server run the following command: Set-WebServicesVirtualDirectory -Identity "ServerName\EWS (Default Web Site)" –WSSecurityAuthentication $true

Did this solve your issue?
Is IIS handler mapping missing on EWS?
Determine whether Internet Information Services (IIS) configuration is missing the svc-Integrated handler mapping for the EWS endpoint
  1. On the on-premises Exchange hybrid deployment server, open Internet Information Services (IIS) Manager.
  2. Expand ServerName -- > Site -- > Default Web Site, and then click EWS.
  3. In the IIS area, open Handler Mappings. The following screen shot shows an example of the svc-Integrated handler mapping in IIS:
    P17_HandlerMapping
     
  4. If the IIS is missing the svc-Integrated handler mapping, see the support article "Exception has been thrown by the target" error in a hybrid deployment of Office 365 and your on-premises environment.
Did this solve your issue?
Is IIS handler Mapping missing?
Determine whether Internet Information Services (IIS) configuration is missing the svc-Integrated handler mapping for the Autodiscover endpoint.
  1. On the on-premises Exchange 2010 hybrid deployment server, open Internet Information Services (IIS) Manager
  2. Expand ServerName -- > Site -- > Default Web Site, and then click Autodiscover
  3. On IIS section, open Handler Mappings. The following screen shot shows an example of the svc-Integrated handler mapping in IIS:
    P12_HandlerMapping
     
If the IIS is missing the svc-Integrated handler mapping, see the topic "Exception has been thrown by the target" error in a hybrid deployment of Office 365 and your on-premises environment.

Did this solve your issue?
Verify Org Relationship settings are configured correctly to enable Free/busy for the users.
For Online Settings
  1. Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect to Exchange Online using remote PowerShell.
  2. 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: FYDIBOHF25SPDLT.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, see Set-OrganizationRelationship.
For On-Premises settings
  1. On the Exchange 2010/2013 CAS, run the following command in the 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, see Set-OrganizationRelationship.

Comments

Post a Comment

Popular posts from this blog

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

Image
On-Premises user cannot see cloud user's Free/busy On which version of Exchange is the on-premises users' mailbox located? Exchange 2003 Exchange 2007 Exchange 2010 Exchange 2013 3 Exchange 2010/2013 user cannot see cloud user's free/busy 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 4 On-premises user cannot see cloud user's Free/busy Determine what error message you are receiving from OWA. Use the affected user's account to...
Read more