Deploy pilot Edge Server
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. The deployment and configuration processes for Lync Server 2013 are very similar to Lync Server 2010. This section only highlights key points you should consider as part of your pilot pool deployment. For detailed steps, see Deploying external user access in Lync Server 2013 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
Log on to the computer where Topology Builder is installed as a member of the Domain Admins group and the RTCUniversalServerAdmins group.
Navigate to the Lync Server 2013 node. Right-click Edge pools, and click New Edge pool.
An Edge pool can be a Multiple computer pool or Single computer pool.
On the Select features page, do not enable federation or XMPP federation. Federation and XMPP federation are both currently routed through the legacy Lync Server 2010 Edge Server. These features will be configured in a later phase of migration.
Next, continue completing the following wizard pages: External FQDNs, Define the internal IP address, and Define the external IP address.
On the Define the next hop page, select the Director for the next hop of the Lync Server 2010 Edge pool.
On the Associate Front End or Mediation pools page, do not associate a pool with this Edge pool at this time. External media traffic is currently routed through the legacy Lync Server 2010 Edge Server. This setting will be configured in a later phase of migration.
Click Finish and then Publish the topology.
Follow the steps in Install Edge Servers for Lync Server 2013 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 Lync Server 2013 in the Deployment documentation. This section merely provided some guidance on configuration settings when installing these server roles.
You should now have a legacy Lync Server 2010 Edge Server deployed in parallel with a Lync Server 2013 Edge server deployment. Verify that both deployments are running properly, services are started, and you can administer each deployment prior to moving to the next phase.