Ensayo

SECTION 1 – Remote Access Overview
• Introduction
• Edge Topology Options
• Remote Access Best Practices
• Certificate Recommendations
• DNS Recommendations

Introduction
By default Office Communications Server 2007 provides instant messaging (IM), presence, conferencing—and if public switched telephone network (PSTN) integration is configured—voice capability for employees within yourorganization. To allow remote access to these features, it is necessary to install and configure one or more edge servers.

The sole purpose of this document is to assist with the remote access configuration process using reference architectures (one per edge topology) and proven best practices. If you are looking for remote access design guidance, refer to the following links:

• For OfficeCommunications Server 2007 R2 Edge, see http://go.microsoft.com/fwlink/?linkid=177977.
• For Office Communications Server 2007 Edge, see http://go.microsoft.com/fwlink/?linkid=177978.

This document is split into the following sections:
• Overview – Office Communications Server remote access best practices
• Scenarios – detailed certificate/port/Domain Name System (DNS) values for each supportedremote access scenario
• Step by Step – detailed setup information for configuring Edge and Reverse Proxy servers

Recommended Usage:
Step 1 – Review the information in the Overview section and determine which remote access scenario matches your business requirements.
Step 2 – Review the section associated with the specific scenario you want to deploy.
Step 3 – Search each of the tablesrelated to the chosen scenario replacing existing server fully qualified domain names (FQDNs)/IP addresses with your production values.
Step 4 – Print out the results and use it as a reference for ordering certificates, opening firewall ports, and creating DNS A/SRV records.
Step 5 – Optionally, you can use the step-by-step instructions to configure Office Communications Server for remote access. 
The best practice and related configuration information provided in the various sections is based on over 50 production remote access deployments, but please keep in mind they are recommendations only. It is possible to configure Office Communications Server remote access many different ways, but this document focuses on the approach proven to produce consistent results with a minimum oferrors.

Currently there are two versions of Office Communications Server 2007 deployed in production environments; the original version, which is referred to as Office Communications Server 2007 and the most recent version, called Office Communications Server 2007 R2. Between the two releases, there are a total of four primary Edge topologies, and this document covers all of them, starting with thesimplest and moving to the most complex. The focus will be on Office Communications Server 2007 R2, but configuration and operational differences between versions will be clearly defined when necessary.

Edge Component Review
Section 2 contains a deployment scenario that corresponds to each of the four primary Edge topologies. There are three Edge Server services total but the minimumrequirement for remote access is the Access Edge service; the other two services are dependent on the Access Edge service but not on each other. Below is a brief description of servers involved in providing remote access to Office Communications Server 2007 R2 (and Office Communications Server 2007) and their functionality:
• Access Edge. Provides the core functionality for collaboration between yourinternal users and users outside your internal network who are using Office Communicator or the Live Meeting 2007 client. The Access Edge Server provides a single, trusted connection point for both outbound and inbound Session Initiation Protocol (SIP) traffic.
• Web Conferencing Edge. Permits external users to join on-premise meetings by using the Live Meeting 2007 client. When your organization...