Why updating deployment share

Understand that while IPv4 addresses in these ranges cannot be routed to the Internet there may be cases where some of these subnetworks are actually in use inside the external firewall.

So any connections to hosts on any subnets within these ranges which can only be reached via the external interface can be handled in one of two ways.

Moving on with this series of deployment articles the next major component of the core Skype for Business (Sf B) infrastructure to address is the Edge Server role.This server role, from a deployment and architecture standpoint, is basically unchanged from previous Lync Server product releases.The externally-facing perimeter network contains a fully-routable public IPv4 subnet.The best practice approach of leveraging DNS Load Balancing will also be applied to this Edge pool, there will be no complicated Hardware Load Balancers (HLB) to address.The following diagram shows a typical network topology for a pair of Edge Servers.

Each server has two network interfaces which are connected to separate networks which cannot route traffic directly between them outside of the dual-homed Edge servers themselves.

These articles have all focused on a simple Skype for Business topology starting with a single Standard Edition server deployment.

The driving force for selecting that topology was primarily that the much-improved official documentation from Microsoft already covered the deployment of an Enterprise Edition Front End server pool.

For those following along with these deployment articles to create a lab environment then a simpler companion article entitled is also available which quickly addresses adding a single Edge Server to this example environment.

But for this article a different, much more verbose approach has been taken.

Note that following those articles verbatim only covers the deployment of a single Standard Edition Front End Server, which actually is sufficient to perform this deployment.