Operational monitoring tools including System Center, Azure Monitor
Continuing work with Nick Wood on the Skype pack for additional operational features.
Previously Blogged about this July 2018, and continue to make improvements
The TechNet gallery bundle is updated with new functionality.
Skype KHI addendum
Pack gathers the Skype KHI performance counters
Packets * Discards performance rules where greater than 100 discards are seen on NIC’s,
Monitoring Tab folder/performance view
Skype Custom Overrides
Includes common overrides for noisy monitors/rules.
Updated and completed for Company Knowledge!
Many thanks to Nick Wood for his help deciphering user impact for these alerts.
Reach out to Nick on LinkedIn
This has been an arduous effort to complete the Skype alerts and components.
It’s taken a few steps along the way, to get all the content delivered.
To read the whole Skype Addendum journey, please read these additional blog posts
June blog
January blog
The initial Addendum pack with just service recoveries and Azure overrides
Old pack https://gallery.technet.microsoft.com/Skype-for-Business-2015-b005f49f
This download disabled Azure, set service recovery tasks
The new Gallery download contains the following:
Skype SCOM Alerts.xls
Microsoft.LS.2015.Monitoring.ComponentAndUser.Addendum.xml
Microsoft.SystemCenter.Notifications.Internal.xml
Skype.for.Business.Server.Management.Pack.Alert.Grooming.xml
NOTE The Skype.for.Business.Server.Management.Pack.Install.txt file contains the information as well
#############################################################
#
# Breakdown of files
#
#############################################################
#
# Skype SCOM Alerts.xls
# Skype SCOM Alerts XLS is is MP Export excerpt formatted for XLS workbook
#
# Feel free to search this file
# Column D is ‘Escalate to Who’
# This has values as SCOM Engineering, Messaging Ops, Telephony, Messaging Engineering
# Column E is impact
# This has values: P3-P5, *Email
# Column F is the Display String for the monitor
# Column H has the User Impact, Cause, and Troubleshooting steps
#
# Microsoft.LS.2015.Monitoring.ComponentAndUser.Addendum.xml
# Addendum management pack sets up company knowledge tab for each Skype monitor, with actionable troubleshooting steps.
#
#
# Microsoft.SystemCenter.Notifications.Internal.xml
#
# Backup the current MP first, and merge if you are adding this to your environment!
# Use this pack cautiously, as it will replace existing Channels, subscribers, subscriptions.
# On Management server, open PowerShell window as Admin
#
# cd <path>
# Example
cd $HOME/desktop
Get-SCOMManagementPack -Name *Notification* | export-SCOMmanagementpack -path “C:\”
Copy-item .\Microsoft.SystemCenter.Notifications.Internal.xml .\Original-<CompanyName>-Microsoft.SystemCenter.Notifications.Internal.xml
# Save the bundled Notifications pack to the same path
# YES it’s that important, the file can eliminate any alerts leaving SCOM!
#
# Save file to local drive
# Follow MP Fragment authoring if you need to merge existing Notifications with Skype pack
# https://kevinholman.com/2016/06/04/authoring-management-packs-the-fast-and-easy-way-using-visual-studio/
#
#
# Skype.for.Business.Server.Management.Pack.Alert.Grooming.xml
#
# This file is to set alerts per the XLS, making warnings for P4,P5, email, and P3 for Critical
#
#############################################################
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.