The topics in this section describe some of the commonly used topologies for deploying servers running SharePoint Products and Technologies through Forefront Unified Access Gateway (UAG).
For each topology, the following relationships are explained:
- Relationships between the servers running
SharePoint Products and Technologies and Forefront UAG.
- Relationship between the SharePoint site's
internal address, which is used to access the site from
within the organization, and public address, which is the
public-facing address that is used to access the site remotely.
For further information about designing SharePoint extranet farm topologies, see Design extranet farm topology (Office SharePoint Server).
 Note: |
|---|
| In each of the topologies, it is assumed that external users will access the SharePoint site using a secure HTTPS connection. Although it is possible for external users to access the SharePoint site using HTTP, the connection to the site will not be secure. |
The following topics describe some considerations you should be aware of before publishing SharePoint applications, and the main topologies and steps for publishing SharePoint applications in your network using Forefront UAG:
- Before you publish
SharePoint applications
- Publishing a SharePoint
application
- Publishing multiple
SharePoint applications on unique ports
- Publishing a SharePoint
application with identical internal and public host
addresses
- Publishing multiple
SharePoint applications on a single port
- Configuring error
reporting
- Publishing an AD RMS
server
- Publishing the Forefront
UAG portal as a SharePoint Web Part
- Blocking automatic
SharePoint library synchronization