Cross-forest or Hybrid free/busy availability lookups fail in Exchange Server
Original KB number: 2734791
Symptoms
Cross-forest or hybrid free/busy information lookups fail in Microsoft Exchange Server. However, standard free/busy information lookups for users in the same forest work as expected.
This issue occurs in these product versions:
- Microsoft Exchange Server 2016
- Microsoft Exchange Server 2013
- Microsoft Exchange Server 2010 Service Pack 2 (SP2) Update Rollup 1 and later versions
- Microsoft Exchange Server 2007 Service Pack 3 (SP3) Update Rollup 6 and later versions
- Microsoft Exchange Online
Note
The Hybrid Configuration wizard that's included in the Exchange Management Console in Microsoft Exchange Server 2010 is no longer supported. Therefore, you should no longer use the old Hybrid Configuration wizard. Instead, use the Microsoft 365 Hybrid Configuration wizard that's available at Microsoft 365 Hybrid Configuration wizard.
Cause
This issue occurs if the external URL for Exchange Web Services is not configured in the target forest.
Resolution
Configure the external URL for Exchange Web Services for the target forest. To do this, run this command in Windows PowerShell for Exchange:
Set-WebServicesVirtualDirectory -identity "server_name\EWS (Default Web Site)" -ExternalURL
https://mail.contoso.com/ews/Exchange.asmx
Note
In this command, contoso represents the actual domain name.
More information
The versions of Exchange Server that are listed in the Symptoms section use the external URL for Exchange Web Services to connect to the target forest. Because the AutoDiscover service cannot return the external URL for Exchange Web Services if Outlook Anywhere is not enabled in the target forest, the cross-forest or hybrid lookup fails.
If either of the following cmdlets returns a value of $False, the mailbox is not set to allow external connections by using Outlook Anywhere.
To verify that the mailbox is set to allow connections by using Outlook Anywhere, run this cmdlet:
Get-CASMailbox <mailbox identity> | fl MAPIBlockOutlookRpcHttp
For Exchange Server 2016 and Exchange Server 2013, to verify that the mailbox is set to allow external connections by using Outlook Anywhere, run this cmdlet:
Get-CASMailbox <mailbox identity> | fl MAPIBlockOutlookExternalConnectivity
References
For more information about the Set-WebServicesVirtualDirectory
cmdlet, see Set-WebServicesVirtualDirectory.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for