• Article

Walkthrough: Configuring New Front End Servers

Topic Last Modified: 2009-10-15

Configuring New Front End Servers

You are now ready to set up the consolidated Front End Servers that will be used in the load balanced array. These servers will be added to your existing pool, and they will use the same back-end database. Follow the standard setup procedure for an Enterprise Edition server, and add each server to your existing pool. In our example, this procedure would involve the following steps:

  1. Obtain a new physical server, assign it an IP address of 10.0.1.41, install the prerequisite operating system for Office Communications Server 2007 R2, and then install IIS.

  2. Name the computer ocsfe01.contoso.com, and then add it to your enterprise DNS server.

  3. Run the Office Communications Server 2007 R2 Enterprise Edition setup.

  4. Select the option to add a consolidated Enterprise Edition server to an existing pool.

    Ee323605.note(en-us,office.13).gif
    If your existing server is a Standard Edition server, you will need to create an Enterprise Edition pool on the associated back-end database at this stage.

  5. Select ocspool.contoso.com as the existing pool and add your new consolidated Front End Server to the pool.

  6. When you request the certificate, set the Subject Name to ocspool.contoso.com and add ocsfe01.contoso.com and sip.contoso.com as Subject Alternate Names.

  7. Run the Activation portion of the setup procedure on ocsfe01 and during the wizard**, use the existing service account and start all Office Communications Server services.**

  8. Configure IIS to allow load balancer FQDN loopback as described in Configuring IIS to Allow Load Balancer FQDN for Loopback in the Deploying Office Communications Server 2007 R2 Enterprise Edition documentation.

  9. Repeat the above steps on a second physical server with IP address 10.0.1.42 and named ocsfe02.contoso.com.

Ensure the following requirements are met:

  1. The two Front End Servers must be capable of routing to each other. There can be no NAT device in this path of communication. Any such device will prevent successful intrapool communication over RPC.
  2. Front End Servers must have access to the Active Directory Domain Services environment.
  3. Front End Servers must have static IP addresses that can be used to configure them in the load balancer. In addition, these IP addresses must have DNS registrations.