In this topic, you will install the Office Communications Server 2007 Edge Server roles.

Tasks

  1. Install Prerequisites for the Edge Server Roles
  2. Enable Public and Private Network Interfaces
  3. Configure DNS Records for Edge Server Roles
  4. Install the Edge Server
  5. Activate the Edge Server

Install Prerequisites for the Edge Server Roles

Procedure W03-DWHO.28: To install prerequisites for the Edge Server roles

  1. Install the 32-bit version of Windows Server 2003 R2 Standard Edition with SP2 on OCSEDGEAV01.

  2. Install IIS and ASP.NET.

  3. Install the Microsoft .NET Framework 2.0 with SP1.

  4. Install the Windows Server 2003 Support Tools.

  5. Leave OCSEDGEAV01 as a Workgroup member. Do not join it to the Fabrikam domain.

Enable Public and Private Network Interfaces

OCSEDGEAV01 requires a minimum of two Network Interfaces, with the following IP address requirements:

  • One static IP address is required for the private (internal) Network Interface
  • Three static IP addresses (one for each Edge Server role) are required for the public-facing (external) Network interface
    • External IP Address A: Access Edge Server role
    • External IP Address B: Web Conferencing Edge Server role
    • External IP Address: A/V Edge Server Role
      The external IP address of the A/V Edge Server must be an external IP address that is directly contactable by external parties. This requirement does not apply to Access Edge Servers and Web Conferencing Edge Servers. These server roles do not require a publicly routable IP address on the external interface.
      Note:
      To conform to the requirement of a publicly routable IP address of the A/V Edge Server, the external firewall of the perimeter network must not act as a NAT (Network Address Translator) for this IP address.Additionally, the internal firewall must not act as a NAT for the internal IP address of the A/V Edge Server. The internal IP address of the A/V Edge Server must be fully routable from the internal network to the internal IP address of the A/V Edge Server.

Procedure W03-DWHO.29: To enable public and private network interfaces

  1. Enable a Network Interface on OCSEDGEAV01 and label it Private. Assign it an internal IP address that will allow it to communicate with the Office Communications Server 2007 Pool server roles.

    Note:
    The edge server OCSEDGEAV01 should be configured to use the internal DNS servers AD01 and AD02 as Preferred and Alternative DNS server, for internal name resolution.

  2. Enable a Network Interface on OCSEDGEAV01 and label it Public. Assign it three external IP addresses (one for each Edge Server role).

Configure DNS Records for Edge Server Roles

When combining multiple Edge Server Roles on a single computer, you should use a separate external IP address for each role. Specific DNS settings must be configured on each external and internal interface of each edge server. In general, this includes configuring DNS records to point to appropriate servers in the internal network and configuring external DNS records as appropriate for each edge server.

The following table describes the DNS records that must be configured for the external interface and the internal interface of edge servers in the single-site edge topology.

Table: DNS records for the consolidated edge topology

Internal/External Record Server DNS Settings

External

Collocated Access Edge Server, Web Conferencing Edge Server, and A/V Edge Server
  • An external DNS A record that resolves the external name of the Access Edge Server to the external IP address of the Access Edge Server.
  • A DNS SRV (service location) record for _sip._tls.<domain>, over port 443, where <domain> is the name of your organization's SIP domain. This SRV record must point to the A record of the Access Edge Server.
  • An external DNS A record that resolves the external name of the Web Conferencing Edge Server to the external IP address of the Web Conferencing Edge Server.
  • An external DNS A record that resolves the external FQDN of the A/V Edge Server to the external IP address of the A/V Edge Server. This IP address must be a publicly routable IP address.

Reverse proxy

An external DNS A record that resolves the external Web farm FQDN to the external IP address of the reverse proxy. The client uses this record to connect to the address book web server via the reverse proxy.

Internal

Collocated Access Edge Server, Web Conferencing Edge Server, and A/V Edge Server

An internal DNS A record that resolves the internal FQDN of the edge server to the internal IP address of edge server. Office Communications Server 2007 servers within the organization use this DNS A record to connect to the internal interface of the edge server.

Procedure W03-DWHO.30: To create external DNS Host records for Edge server roles and reverse proxy

  1. Open the DNS MMC on the external DNS server DNS01.

  2. Create the following host (A) records in the consolidatedmessenger.com DNS Zone according to the following table:

    Host Record

    IP Address

    Description

    sip.consolidatedmessenger.com

    (external IP address A of OCSEDGEAV01)

    Access Edge DNS record

    webconf.consolidatedmessenger.com

    (external IP address B of OCSEDGEAV01)

    Web Conferencing Server

    AVEdge.consolidatedmessenger.com

    (external IP address C of OCSEDGEV01)

    A/V Edge Role

    web.consolidatedmessenger.com

    (IP Address of Reverse Proxy)

    Reverse Proxy for Address Book web server

Procedure W03-DWHO.31: To create external DNS SRV record for Access Edge role

  1. In the DNS MMC on the external DNS server DNS01, right-click the consolidatedmessenger.com DNS zone, and click Other New Records.

  2. In Select a resource record type, click Service Location (SRV), and then click Create Record.

  3. Set the following information:

    • Service: _sip
    • Protocol: _tls
    • Port Number: 5061
    • Host offering this service: The external FQDN of the Access Edge server role (for example, sip.consolidatedmessenger.com the reference architecture)

Procedure W03-DWHO.32: To create internal DNS Host record for the Edge server

  1. Open the DNS MMC on the AD01.

  2. Create a host (A) record in the fabrikam.com Active Directory-integrated DNS Zone according to the following table:

    Host Record

    IP Address

    Description

    OCSEDGEAV01.fabrikam.com

    (internal IP address of OCSEdgeAV01)

    Internal FQDN of Office Communications Server 2007 Edge Server

Procedure W03-DWHO.33: To configure the DNS suffix on the Edge server

  1. Log on to OCSEDGEAV01 as a member of the local Administrators group.

  2. Open the Computer Name Changes dialog box, and then click More.

  3. In the Primary DNS suffix of this computer field, type the internal DNS domain name and suffix (for example, fabrikam.com in the reference architecture).

  4. Complete the setting and restart the computer.

Install the Edge Server

Procedure W03-DWHO.34: To install the Edge server

  1. Log on to OCSEDGEAV01 as Administrator.

  2. Run Setup.exe from the Office Communications Server 2007 Enterprise Edition media to start the Office Communications Server 2007 deployment wizard.

    Note:
    If you are prompted to install a C++ Redistributable component, do so.

  3. Select Deploy Other Server Roles, and then select Deploy Edge Server to open the Deploy Edge Server page.

  4. Next to Step 1: Install Files for Edge Server, click Install.

  5. Follow the steps in the installation wizard to install the Edge Server role.

Activate the Edge Server

Procedure W03-DWHO.35: To activate the Edge server

  1. On OCSEDGEAV01, from the Office Communications Server 2007 deployment wizard, on the Deploy Edge Server page, next to Step 2:Activate Edge Server, click Run.

  2. At the Select Enterprise Pool screen, select OCSPool01.fabrikam.com.

  3. At the Edge Server Roles page, select the following:

    • Activate Access Edge Server
    • Activate Web Conferencing Edge Server
    • Activate A/V Edge Server

  4. At the Select Service Account screen, select Create A New Account, and accept the default account name of RTCProxyService. Enter a password that meets your password complexity requirements.

  5. When the wizard is complete, select View the log when you click Finish check box, and review the deployment log after installation completes to verify a successful Edge Server activation.