Topic Last Modified: 2014-02-04

Before you deploy your perimeter network and implement support for external users, you must already have deployed your Microsoft Lync Server 2013 internal servers, including a Front End pool or a Standard Edition server. If you plan to deploy the optional Directors in your internal network, you should also deploy them prior to deploying Edge Servers. For details about the Director deployment process, see Scenarios for the Director in the Planning documentation.

Microsoft Lync Server 2013 includes tools to facilitate planning and deployment of both internal servers and Edge Servers. After the topology is completed, publish the resulting topology definition to your production environment. To do this, you must be a member of the Domain Admins group and the RTCUniversalServerAdmins group.

If you designed your edge topology during your planning process, including running Topology Builder to define your edge topology, you can use those results to start your Edge Server deployment. If you did not finish building your edge topology earlier or you want to change the information you previously specified, you must finish running Topology Builder before proceeding with other deployment steps. For details about how to build your topology, see Scenarios for External User Access.

For details about the Planning Tool and Topology Builder, see Beginning the planning process in the Planning documentation.

The following table provides an overview of the Edge Server deployment process. To review the planning decisions that must be made before deploying external user access, see Scenarios for External User Access.

Warning:
The information in the following table focuses on a new deployment. If you have deployed Edge Servers in a Lync Server 2010, Office Communications Server 2007 R2 or Office Communications Server 2007 environment, see the Migration for details about migrating to Lync Server 2013. Migration is not supported from any version prior to Office Communications Server 2007 R2, including Office Communications Server 2007, Live Communications Server 2005, and Live Communications Server 2003.

To enhance Edge Server performance and security, and to facilitate deployment, apply the following best practices when you deploy your perimeter network and Edge Servers:

Deployment Process for Edge Servers

Phase Steps Permissions Documentation

Create the appropriate edge topology and determine the appropriate components.

  • Run Topology Builder to configure Edge Server settings and create and publish the topology, and then use Lync Server Management Shell to export the topology configuration file.

Domain Admins group and RTCUniversalServerAdmins or CsAdmins group

Note:
You can define a topology using an account that is a member of the local users group, but publishing a topology requires an account that is a member of the Domain Admins group and the RTCUniversalServerAdmins group.

Building an Edge and Director Topology in the Deployment documentation

Prepare for setup.

  1. Ensure that system prerequisites are met.

  2. Configure IP addresses (IPv4 and IPv6, if used) for both internal and public facing network interfaces on each Edge Server.

  3. Configure internal and external DNS records (host A and AAAA for IPv4 and IPv6), including configuring the DNS suffix on the computer to be deployed as an Edge Server.

  4. (Optional) Create and install public certificates. The time required to obtain certificates depends on which certification authority (CA) issues the certificate. If you do not perform this step at this point, you must do it during Edge Server installation. The Edge Server services cannot be started until certificates are obtained and installed.

  5. Provision support for public IM connectivity, if your deployment is to support communications with Windows Live, AOL, or Yahoo! users.

    Important:

    • As of September 1st, 2012, the Microsoft Lync Public IM Connectivity User Subscription License (“PIC USL”) is no longer available for purchase for new or renewing agreements. Customers with active licenses will be able to continue to federate with Yahoo! Messenger until the service shut down date. An end of life date of June 2014 for AOL and Yahoo! has been announced. For details, see Support for public instant messenger connectivity.

    • The PIC USL is a per-user per-month subscription license that is required for Lync Server or Office Communications Server to federate with Yahoo! Messenger. Microsoft’s ability to provide this service has been contingent upon support from Yahoo!, the underlying agreement for which is winding down.

    • More than ever, Lync is a powerful tool for connecting across organizations and with individuals around the world. Federation with Windows Live Messenger requires no additional user/device licenses beyond the Lync Standard CAL. Skype federation will be added to this list, enabling Lync users to reach hundreds of millions of people with IM and voice.

  6. Provision support for XMPP and federation support for Office Communications Server 2007, Office Communications Server 2007 R2, Lync Server 2010 partners, if your deployment will use these

  7. Configure firewalls.

As appropriate to your organization

Preparing for Installation of Servers in the Perimeter Network in the Deployment documentation

Set up reverse proxy.

  • Set up the reverse proxy (for example, for Microsoft Forefront Threat Management Gateway 2010 or Microsoft Internet Security and Acceleration (ISA) Server with Service Pack 1) in the perimeter network, obtain the necessary public certificates, and configure the web publishing rules on the reverse proxy server.

    Prepare the reverse proxy for Mobility services if you have planned for Mobility and are deploying the Mobility services on the Front End pool or Standard Edition server.

Administrators group or Reverse Proxy administrator

Setting Up Reverse Proxy Servers in the Deployment documentation

Setup a Director (optional).

  • (Optional) Install and configure one or more Directors in the internal network.

Administrators group

Setting Up the Director in the Deployment documentation

Set up Edge Servers.

  1. Install prerequisite software.

  2. Transport the exported topology configuration file to each Edge Server.

  3. Install the Lync Server 2013 software on each Edge Server.

  4. Configure the Edge Servers.

  5. Request and install certificates for each Edge Server.

  6. Start the Edge Server services.

Administrators group

Setting Up Edge Servers in the Deployment documentation

Configure deployment for external user access.

  1. Use the Lync Server Control Panel to configure support for each of the following (as applicable):

    • Media relay

    • Federation route

    • Remote user access

    • Federation with Lync Server, Office Communications Server and Live Communications Server

    • Public IM connectivity

    • XMPP federation

    • Anonymous users

  2. Configure user accounts for remote user access, federation, public IM connectivity, XMPP and anonymous user support (as applicable)

RTCUniversalServerAdmins group or user account that is assigned to the CSAdministrator role

Configuring Support for External User Access in the Deployment documentation

Verify your Edge Server configuration.

  1. Verify server connectivity and replication of configuration data from internal servers.

  2. Verify that external users can connect, including remote users, users in federated domains, public IM users, and anonymous users, as appropriate to your deployment.

  3. Verify configuration and communication using the Lync Server Remote Connectivity Analyzer https://www.testocsconnectivity.com

  4. Troubleshoot configuration and communication difficulties

For verification of replication, RTCUniversalServerAdmins group or user account that is assigned to the CSAdministrator role

For verification of user connectivity, a user for each type of external user access that you support

Remote users

Verifying Your Edge Deployment in the Deployment documentation