Skype for Business Server Edge Pool deployment has four parts to cover end to end deployment process. See Part I, Part II, Part III and Part IV for step by step process.
This post is a continuation of #Skype4B – Edge Pool Deployment Part I and focus on SfB topology configuration for Edge pool. Open Topology Builder on one of the FE / SfB management server and follow the steps as given below:
Open topology builder and select “Download Topology from existing deployment”
Right click on Edge Pools and click on New Edge Pool…
Click on Next
Define Edge Pool FQDN
Enable federation if you want
Server this option if you are using single FQDN and IP address.
Select “The external IP address of this Edge pool is translated by NAT” if you are using NAT for external interfaces.
Define External FQDNs
Click on Add to add FQDN of your Edge servers.
Define internal ip address and FQDN of your first Edge server
Define external ip addresses of your first Edge server
In the same way, add second edge server.
Select the Next hop pool. Select you FE pool if not using director otherwise use director.
Select FE and Mediation pools which you want to associate with this Edge server pool.
Once you are done, publish the topology.
Once topology is published successfully. Export this configuration to install the edge server.
Next part of this post will cover the step by step installation of Edge server.
Skype for Business Server Edge Pool deployment has four parts to cover end to end deployment process. See Part I, Part II, Part III and Part IV for step by step process.
Thanks for this excellent write up. I have a question regarding the creating of external FQDNs on the Edge server.
Do i have match the names for AccessEdge, Webconf and AV to the simple urls that was configured on the FE server?
Example: Assuming the simple url for meetings on the FrontEnd server is meet.testdomain.com, do i have to match the webconf FQDN on the Edge server to meet.testdomain.com?
Thanks
LikeLike
Thanks!
You don’t have to mention any simple url on Edge server because for the external users Reverse proxy takes care of it.
See this blogpost: https://insidemstech.com/2014/05/14/iis-arr-on-windows-8-1-for-lync-2013-2/
LikeLike