Skype for Business

[Tonia K]

When adding skype for business one of the steps is to install SDN 2.2 or 2.4.1 or 3.0. Which is to be used with Skype 2015 and I heard one if these has a glitch.

Tonia

[Scot_Clark]

Hi Tonia,

There is a known issue with with SDN 3.0 where the following scenarios are in effect:

Multiple SfB sites.
Each SfB site has one or multiple front-end pools with a Dialog Listener installed on each front-end server.
All Dialog Listeners point (populate data) to a single SDN Manage

There is a manual work around in place which involves running some power shell commands.

I can send you more information about that via email later on when you are getting ready to set up Skype for Business monitoring.

[Robert_Guth]

Please send me the same workaround. We have just completed the SDN 3.0 installation and would like to configure Prognosis to query it.

[Scott_Clement]

Hi Robert,

The online help has been updated to include a description of the known issue Scot's referring to above. This includes instructions on how to work around the issue.
If you search the online help for "SDN 3.0 - Known Issue - Skype", it should return details of the workaround you can use to avoid this.

Hope this helps!

[Robert_Guth]

Yep. Verified.
One note on the 3.0 SDN Dialog Listener. When you install this on a Front End, it removes any previous SDN22 Server Applications in the Central Management Store. This doesn't affect running dialog listeners but it will when the server is rebooted or the dialog listener service recycled - resulting in the listener service never starting. The services will not be able to connect to SfB throwing a "Application Unauthorized" result.

Our work around was to issue a New-CsServerApplication for each pool once all the listeners were installed (30 front ends), thus repopulating the central management store.

Another learning is that once the dialog listener is installed it must wait for replication before the service will actually start. You can monitor this in Event Viewer. You should NOT start another dialog listener installation on another server until the current installation service actually starts. This is because of the aforementioned learning that the installer removes all previous entries. If the second installation completes and that server replicates faster than the first, the first one will never start the service because it's entry in CMS is now gone.

[Scott_Clement]

Awesome information Robert, thanks for sharing lessons learned "the hard way".