It's very important that you follow the guidelines in the topics in the Deployment documentation.
This setting will be configured in a later phase of migration.Ĭlick Finish, and then Publish the topology.įollow the steps in the Deployment documentation to install the files on the new Edge Server, configure certificates, and start the services. External media traffic is currently routed through the legacy Edge Server.
On the Associate Front End or Mediation pools page, do not associate a pool with this Edge pool at this time. On the Define the next hop server page, select the Director for the next hop of the legacy Edge pool. These features will be configured in a later phase of migration.Ĭontinue completing the following wizard pages: External FQDNs, Define the internal IP address, and Define the external IP address. Federation and XMPP federation are both currently routed through the legacy Edge Server. On the Select features page, do not enable federation or XMPP federation. Right-click Edge pools, and click New Edge pool.Īn Edge pool can be a Multiple computer pool or Single computer pool. Navigate to the Skype for Business Server 2019 node. Log on to the computer where Topology Builder is installed as a member of the Domain Admins group and the RTCUniversalServerAdmins group. Note that only a few pages of the Define New Edge Pool wizard are shown. This section only highlights key points you should consider as part of your pilot pool deployment.Īs you navigate through the Define New Edge Pool wizard, review the key configuration settings shown in the following steps. The deployment and configuration processes for Skype for Business Server 2019 are very similar to Skype for Business Server 2015. This topic highlights configuration settings you should be aware of before deploying your Skype for Business Server 2019 Edge Server.