Ever try to figure out a Skype alert, for which server in the pool(s) is failing?

While maybe not the clearest to find root cause, the Skype pack brings a bunch of functionality, including synthetic transactions.

I was lucky enough to collaborate with Nick Wood, Skype PFE, to help provide more detail, troubleshooting, impact on what is critical versus warning.

What the addendum pack brings

Do you think 656 monitors can all be critical?

Here is a visual of our Skype efforts for integrating troubleshooting details into SCOM console.

NOTE: Company Knowledge tab would be accessible from the alert as well

Company Knowledge

SCOM Console, Authoring tab, Dispatcher Queue monitor

Highlight monitor, right click, choose properties

Click on ‘Company Knowledge’ tab

Incorporated the XLS into SCOM under Company Knowledge for additional information on user impact, causes, and troubleshooting (under resolutions)

Continuing the Addendum tradition 🙂 Skype was next on the list.

To understand options and methods available on the Server and SCOM, re-read the Active Directory Addendum blog

Skype for Business 2015 (SfB)

Now that we understand the methods available, let’s get to the Addendum.

This Skype Addendum MP adds Recovery Tasks to the Skype for Business 2015 Service Monitors.

The recovery tasks verify service state, start ‘not running’ services, and recalculate health.

36 services monitored, with 36 recovery tasks.

The recovery tasks verify service state, start ‘not running’ services, and include the option to recalculate health.

My goal is automation that helps anyone work smarter versus harder, with the goal to avoid being woke up at 2am just to restart a service.

Skype-for-Business-2015-b005f49f

Tag: skype for business 2015