Topic Last Modified: 2012-10-19

This topic highlights configuration settings you should be aware of prior to deploying your Lync Server 2013 Edge Server. This section only highlights key points you should consider as part of your pilot Edge pool deployment. For detailed steps, see Deploying External User Access in the Deployment documentation, which describes the deployment process and also gives configuration information for external user access.

As you navigate through the Define New Edge Pool wizard, review the key configuration settings shown in the following steps. Note that only a few pages of the Define New Edge Pool wizard are shown.

Define an Edge Pool

  1. Open the pilot pool topology using Topology Builder.

  2. Navigate to the Lync Server 2013 node. Right-click Edge pools, and click New Edge pool.

    Define the New Edge Pool dialog box

  3. An Edge pool can be a Multiple computer pool or Single computer pool.

    Define the Edge Pool FQDN dialog box

  4. On the Select features page, do not enable federation or XMPP federation. Federation and XMPP federation are currently routed through the legacy Office Communications Server 2007 R2 Edge Server. These features will be configured in a later phase of migration.

    Select Features dialog box

  5. Next, continue completing the following wizard pages: Select IP options, External FQDNs, Define the internal IP address, and Define the external IP address.

  6. On the Define the next hop page, select the Director for the next hop of the Lync Server 2013 Edge pool.

    Define New Edge Pool dialog, Next hop pool list

  7. On the Associate Front End pools page, do not associate a pool with this Edge pool at this time. External media traffic is currently routed through the legacy Office Communications Server 2007 R2 Edge Server. This setting will be configured in a later phase of migration.

    Define New Edge Pool dialog

  8. Click Finish and then Publish the topology.

  9. Follow the steps in Install Edge Servers in the Deployment documentation to install the files on the new Edge Server, configure certificates, and start the services.

It’s very important that you follow the guidelines in the topics Deploying External User Access in the Deployment documentation. This section merely provided some guidance on configuration settings when installing these server roles.

You should now have a legacy Office Communications Server 2007 R2 Edge server deployment, indicated by the presence of the BackCompatSite, in parallel with a Lync Server 2013 Edge server deployment. Federation is configured to use the Office Communications Server 2007 R2 Director. Verify that both deployments are running properly, services are started, and you can administer each deployment prior to moving to the next phase.

Topology Builder showing OCS Edge Server