• Article

Introduction to the Office Communications Server 2007 Edge Server Guide

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

If you need to communicate with users and organizations outside your internal network by using your Microsoft® Office Communications Server 2007 deployment, you need to deploy one or more edge servers. You install edge servers in your perimeter network (also known as screened subnet) so that users outside your organization’s firewall are authorized before they obtain access to your Office Communications Server deployment.

This document guides you through the deployment of edge servers in your Office Communications Server 2007 topology. You typically deploy edge servers after you have deployed Office Communications Server in your internal network.

You can use the information in this guide to deploy your edge servers by completing the following steps:

  1. Step 1. Get Ready for Edge Server Deployment. This includes deciding which edge servers you need, meeting prerequisites, establishing your deployment process, and choosing deployment topologies.

  2. Step 2. Set Up the Infrastructure for Edge Servers. This includes configuring DNS, firewalls, and a reverse proxy, as well as configuring a Director (if appropriate).

  3. Step 3. Set Up Edge Servers. This includes deploying and configuring a load balancer, individual edge servers, and certificates.

  4. Step 4. Configure the Environment. This includes configuring anonymous participation settings, connecting internal servers with edge servers, and configuring users for external connectivity (federation, remote access, and public IM connectivity).

  5. Step 5. Validate Your Edge Configuration. This includes validating server configuration, as well as verifying that the edge servers can communicate with internal servers.

Additionally, you can use the information in Appendix A to configure an array of Standard Edition servers that are connected to a load balancer as a Director.