
New-CsTrustedApplicationComputer -Identity confNN.vc. -Pool confpool-eu.vc.Įnable-CsTopology Adding new Front End Pools (FEPs), locations and Conferencing Nodes You need to add the identity of the new Conferencing Node to the existing Trusted Application Pool ( confpool-eu.vc., in our example): The name information in the new certificate would be (assuming the new hostname is conf04.vc.):ĪltNames = conf01.vc., conf02.vc., conf03.vc., conf04.vc., confpool-eu.vc.

The new certificate must be uploaded to all of the Conferencing Nodes in the application pool.įor example, before adding the new node, the certificate name information in our example would be:ĪltNames = conf01.vc., conf02.vc., conf03.vc., confpool-eu.vc. 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). Generate a new single certificate for all of the Conferencing Nodes in the application pool.

Adding a new Conferencing Node to an existing location

* Note that where this documentation refers to " SfB/Lync", it represents both Microsoft Skype for Business and Lync unless stated otherwise.
Skype for business add ons manual#
It also describes a manual pool failover process. This section explains the steps involved if you need to add additional Conferencing Nodes, or new Skype for Business / Lync * servers and Conferencing Nodes in a new geographic location, to an existing on-premises SfB/Lync environment. Adding more nodes or locations to an existing on-premises Skype for Business deployment
