A new management pack for monitoring Skype for Business Server 2019 is out and available here

Install guide – here

What’s New

The following features are new to Skype for Business Server 2019 Management Packs.

• Automatic discovery for Client Sign-In Client applications that sign-in to Skype for Business Server 2019 often automatically discover the server to sign-in to. Synthetic transactions now support verification that automatic discovery is configured correctly.
• Customized synthetic transaction run intervals To simplify the set up process of Watcher Nodes, synthetic transactions can share user accounts. This slows down the frequency at which the tests are run as the tests are serialized to avoid conflicts. By default, synthetic transactions run every 15 minutes to ensure all tests have time to run. Administrators who choose to use more users or fewer tests per user may now reduce the run interval, as well.
• Video Interop Services synthetic transaction Customers who are migrating to Skype for Business Server 2019 from other vendor solutions often desire to continue using the video teleconferencing devices (VTCs) from these other vendors. Video Interop Server is a new Skype for Business Server 2019 server role that enables customers to continue to use Cisco VTCs in their conference rooms by connecting to Cisco CUCM via a video SIP trunk. This feature also adds a synthetic transaction to help verify that the Video Interop Server is up and can handle incoming connections over a video SIP trunk.
• Application Sharing Conferencing synthetic transaction End-to-end scenario validation for Application Sharing Conferences is now supported.

Windows Cluster services management packs have recently been updated and are available at the following locations:

2016 and 1709+
2012 R2

Updates and Fixes

• Fixed issue: resources group view displayed 2012 and 2012 R2 Clusters
• Changed Availability Storage group monitoring logic:
  • If the group state was empty or offline, the monitor did not change state to Critical.
  • If the group state was in partially online state, the monitor did not change to Warning state.
  • If physical disk was in offline state, the monitor did not change state from Healthy to Critical.
• Fixed issue with Network and Network Interfaces discovery in case Cluster Network Interface name was longer than ~40 characters and contained ‘-’ characters.
• Fixed issue: Cluster Resource tasks execution was failing if cluster.exe was not installed.
• Fixed issue: Cluster Network Interfaces were not discovered on Windows Server 2008 Core.
• Fixed issue: Cluster Network Interfaces were not fully discover on Windows Server 2016 Standard.
• Fixed issue: Cluster Network Interfaces were not discovered on Windows Server 2016 Nano.
• Fixed issue: Tasks did not have output on Windows Server 2016 Nano.
• Fixed issue: “Pause Node” and “Resume Node” tasks had unexpected output.
• Added support for resource groups’ tasks with names containing WMI reserved symbols.
• Fixed issue: Cluster Resources were not discovered if the Cluster had File Server role.
• Fixed issue: Cluster Resource groups could not be moved to another node due to failure of “Move Group” task. The logic was changed, see “Move Group” Task Specifics” section.
• Fixed issue: “Check Cluster Group” diagnostic task did not work on Windows Server 2003-2008 R2 platforms without PowerShell, and on Windows Server 2012 and higher without PowerShell and Cluster cmdlets installed.
• Fixed issue: If a cluster object name contained WMI reserved symbols, monitoring of this cluster object did not work.
• Added support for resources with long names (up to 4000 symbols).
• Fixed issue: “10000” warning event occurred on all platforms if the discovery did not return the data.
• Fixed issue: Several resource tasks do not work if Cluster.exe is not installed.
• Updated the display strings.

The Server 2012 DHCP management pack has been updated and is avaliable for download – here

Updates and fixed

• Added “Known Issues and Troubleshooting” section to the guide.
• Updated “Supported Configurations” section of the guide.

The following bugs have been fixed in the Management Pack:

• “DHCP Server 2016 IPV4 Individual Scope Addresses Available Percentage Monitor” was not generating the corresponding alerts in case of 0% percentage available.
• “DHCP Server 2016 IPV4 Individual Scope Addresses Available Percentage Monitor” was failing if multiple scopes had the same name.
• “DHCP Server 2016 IPV6 Individual Scope Addresses Available Percentage Monitor” was not generating the corresponding alerts in case of 0% percentage available.
• “DHCP Server 2016 IPV6 Individual Scope Addresses Available Percentage Monitor” was failing if multiple scopes had the same name.