An update to SQL Server Reporting Services 2017+ Management Pack is released. This update introduces Power BI Report Server monitoring capabilities to the existing SSRS MP. It considers Power BI Report Server as a special kind of SSRS and provides the same monitoring for PBIRS instances as it does for SSRS instances.
It’s great to see new features like this, Power BI is a powerful tool.
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.
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.
Lenovo have updated their management pack to integrate SCOM with XClarity get it here
It now supports even more Lenovo systems
Key features include:
Extensive monitoring of the health of hardware components for System x and ThinkSystem servers, Flex chassis nodes and BladeCenter blades via BMC (out-of-band mode).
Extensive monitoring of the health of hardware components for System x servers, Flex chassis nodes and BladeCenter blades running Windows (in-band mode).
Rich monitoring of the health of Flex and BladeCenter chassis/modules via the SNMP protocol.
Easy determination of overall system health by the aggregation of hardware health monitors.
Power Monitoring of UEFI/BMC System x Servers and Blades running Windows. Offers the ability to monitor overall system power usage, and generates alerts when power consumption rises above predefined consumption thresholds. Enable Power Capping and set the maximum power consumption wattage via Operation Manage Agent task.
BladeCenter and Blade hardware health correlation and event propagation providing BladeCenter specific hardware health condition monitoring under the Windows health explorer view.
Remote power on and off of Blades Servers via the Operations Manager console.
Offer the ability to launch a CMM Web Console of a Flex System Chassis from the Operations Manager Console.
Offer the ability to view System x power data using the System x Power Data Chart.
Offer the ability to support SQL Server database and migrate data from the PostgreSQL to the SQL Server.
Offer the ability to discover and manage system BMC automatically.
Offer the ability to configure Lenovo XClarity Integrator Service from the Operations Manager Console.
Support to install XClarity Integrator Service on a separated system.
Support multiple Management Servers in same management group, and connect to another online Management
Server if the current Management Server stops responding.
Support to refresh BMC data in Management Server in time.
Provide the High Availability (HA) suggestion based on Windows or VMWare HA solution.
A brief overview of the recently released UR6 for SCOM 2016 – get it here
Updates and Fixes
Application pool crashes and SharePoint application crashes because of APM agent and the profiler are now fixed. These occurred because the profiler was always on. This issue is fixed by disabling the profiler by default and enabling it only when APM is configured.Note If you’re using APM, restart IIS after you deploy the patches.
Improved logging to display error messages and suggest that you check performance counters when PdhExpandWildCardPath fails.
Fixed: Session Events tab in Application Diagnostics web console doesn’t display any data.
Fixed: Scheduled Maintenance Mode doesn’t work in an availability group that uses SQL Always-On configuration. In case of a failover to a secondary node, the Maintenance Mode Schedules that are created on the primary node don’t run. This has now been fixed. For details, see the “Enabling Schedule Maintenance Mode with SQL Always ON” section.
Updated fix: The Get-SCOMGroup cmdlet is slow to query large (more than 2,000) groups. A previous fix has been improved for faster querying of any number of groups.
Fixed: Users could not edit the Maintenance Schedule in the SCOM console if all the objects were removed. The schedule can now be edited. However, it cannot be saved unless it contains at least one object.
Fixed: SCX cannot connect with Linux machine if the KEX algorithms are configured as any of the following: ecdh-sha2-nistp256, diffie-hellman-group-exchange-sha256, or diffie-hellman-group14-sha256.
Fixed: Using MI APIs causes MonitoringHost.exe to crash. This event is logged in the Application log, but no crash events are reported in the Operations Manager event log. After this fix, MonitoringHost doesn’t crash even if the useMIAPI registry key is enabled.
OMS (now Azure Log Analytics) connection onboarding wizard isupdated to communicate with the new APIs. This is because the OMS services were moved to the Azure Portal (link), and also because of the planned retirement of the OMS portal. This change will not affect any existing connection to OMS. However, for new connections or to reconfigure existing connections, the relevant management packs that are bundled together with this update rollup must be imported.
This update rollup creates a new “omi” user (system account).