This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You have a Microsoft Windows SharePoint application or a Microsoft Office SharePoint application that hosts multiple teams.
Each team has a site collection that works as a unique site in the sites/ path.
Access control is required on each of these team sites.
You want to provide a link to the SharePoint team site for each particular team instead of a link to the whole server.
The data on these team sites is confidential and cannot be shared or viewed between teams without explicit permissions.
You publish these team sites in Microsoft Intelligent Application Gateway (IAG) 2007 by using an Alternate Access Mapping template.
In this scenario, the SharePoint publishing operation does not work as expected. Specifically, Web Monitor reports application access errors for unknown applications. Additionally, some graphics, style sheets, or scripts are not loaded as expected.
This problem occurs because an issue in the initial implementation of the IAG SharePoint Alternate Access Mapping (AAM) template prevents publishing in this scenario.
When AAM publishing is implemented in IAG, the publishing operation does not work as expected because some graphics, style sheets, and scripts are not stored in the sites/collection/ directory. Instead, they are stored further down the path in the /* directories. IAG cannot enable access to the / directory without enabling access to the whole server. Therefore, IAG must restrict application access to only the sites/collection/ directory. This behavior causes an additional problem because the requests to the / URL do not match any configured application on the portal.
To resolve this problem, apply Intelligent Application Gateway 2007 Service Pack 2 Update 1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
968384 Description of Update 1 for Intelligent Application Gateway 2007 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates