You are here: Integration > Microsoft Lync / Skype for Business > Adding more on-prem nodes or locations

Adding more nodes or locations to an existing on-prem Lync / Skype for Business deployment

This section explains the steps involved if you need to add additional Conferencing Nodes, or new Lync / Skype for Business* servers and Conferencing Nodes in a new geographic location, to an existing on-prem Lync/SfB environment.

* Note that where this documentation refers to "Lync/SfB", it represents both Microsoft Lync and Skype for Business unless explicitly stated otherwise.

Adding a new Conferencing Node to an existing location

Within Pexip Infinity

Using the names of the example environment described in this guide, you need to:

  • Assign a hostname to the Conferencing Node, e.g. in the format
  • Assign a DNS A record for this Conferencing Node, registered as
  • Add a DNS A record to the pool domain so that Lync/SfB will also load balance over this new node.
  • Generate a new single certificate for all of the Conferencing Nodes in the application pool. This new certificate should contain the same name information as the existing certificate, with the addition of the FQDN of the new node as another SAN (Subject Alternative Name).

    The new certificate must be uploaded to all of the Conferencing Nodes in the application pool.

    For example, before adding the new node, the certificate name information in our example would be:,,,

    The name information in the new certificate would be (assuming the new hostname is,,,,

Within Lync/SfB

You need to add the identity of the new Conferencing Node to the existing Trusted Application Pool, in our example

New-CsTrustedApplicationComputer -Identity -Pool

and then enable topology:


Adding new Front End pools (FEPs), locations and Conferencing Nodes

If you have Lync/SfB servers and Conferencing Nodes in other geographic locations, then you should apply the same configuration model for these other locations as described for the Europe location configuration.

For example, if you had the following devices located in the USA:

  • 2 Lync/SfB Front End Servers us-lyncfe01 and us-lyncfe02 in a pool
  • 2 Conferencing Nodes us-px01 and us-px02 in System location US and to be placed in an application pool

Within Pexip Infinity

  1. Generate and assign a server certificate to the US Conferencing Nodes:

    commonName =
    altNames =,,

  2. Configure the US system location to use:
    • the Front End pool
    • DNS servers on the inside of the network
    • a TURN server
    • a STUN server.
  3. Configure DNS records for the US Conferencing Nodes:
    • A-records for each Conferencing Node us-px01 and us-px02
    • another A-record per Conferencing Node with the host name (the application pool name of the Conferencing Nodes).
  4. Configure the SIP TLS FQDN setting for each US Conferencing Node to reflect its DNS FQDN e.g. and

Within Lync/SfB

  1. Create a trusted application pool for the Conferencing Nodes.

    This command adds a trusted application pool for the Front End pool and adds the first node ( as a computer in the application pool:

    New-CsTrustedApplicationPool -Identity -ComputerFqdn -Registrar -Site 1 -RequiresReplication $false -ThrottleAsServer $true -TreatAsAuthenticated $true

  2. Add the other Conferencing Nodes in that location to the trusted application pool.

    This command adds us-px02 to the new trusted application pool:

    New-CsTrustedApplicationComputer -Identity -Pool

  3. Create a trusted application for the pool of Conferencing Nodes.

    This command creates a trusted application for the pool:

    New-CsTrustedApplication -Applicationid us-px -TrustedApplicationPoolFqdn -Port 5061

  4. Create a static SIP domain route and associate it with the trusted application.

    This example creates a static route from the US Front End pool ( to the nodes for the domain

    $newroute = New-CsStaticRoute -TLSRoute -Destination "" -Port 5061 -MatchUri "" -UseDefaultCertificate $true

    Set-CsStaticRoutingConfiguration -Identity "" -Route @{Add=$newroute}

    Note that if there is no existing routing configuration for this registrar, this can be created via:

    New-CsStaticRoutingConfiguration -Identity ""

  5. Enable the new topology using the following command: