|
Article ID: 2545080 - View products that this article applies to. SymptomsAssume that you configure the cross-forest Availability service between two forests that have Microsoft Exchange Server 2007 installed. In this situation, users who use Microsoft Office Outlook or Outlook Web Access (OWA) in the source forest cannot view the free/busy information of the mailboxes in the target forest. CauseThis issue occurs because the Client Access server in the source forest uses internal URLs of the Availability service in the target forest. When a user requests free/busy information, the Client Access server in the source forest uses the Autodiscover service to determine which URL of the Availability service in the target forest to query free/busy information. The Autodiscover service retrieves both the external URLs and the internal URLs that are configured for Exchange Web Services in the target forest. However, the source Client Access server only uses the internal URLs of the Availability service. Because the internal URLs of the target forest cannot be resolved by DNS, the request fails. ResolutionTo resolve this issue, install the following update rollup: 2608656
(http://support.microsoft.com/kb/2608656/
)
Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3 StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. More informationFor more information about how to configure the Availability service for cross-forest topologies, visit the following Microsoft website: General information about how to configure the Availability service for cross-forest topologies For more information about the Autodiscover service in Exchange Server 2007, visit the following Microsoft website:
(http://technet.microsoft.com/en-us/library/bb125182(EXCHG.80).aspx)
General information about the Autodiscover service in Exchange Server 2007
(http://technet.microsoft.com/en-us/library/bb332063(EXCHG.80).aspx)
PropertiesArticle ID: 2545080 - Last Review: Monday, 28 January 2013 - Revision: 2.0 Applies to
|
Contact us for more help |
