Tag Archives: 2019

SCOM: OpsLogix has updated their Oracle Management pack v1.3.1683.0

The great crew over at OpsLogix has a new Oracle MP for us to ring in 2020, it’s available here

What’s different?

Changes

  • Rewritten the complete backend to make usage of a collector service. This way we detach the SCOM modules from the Oracle client resulting in a way less footprint and more performance.
  • Moved the Oracle configuration dashboard from monitoring pane to Administration pane.
  • Rewritten the Oracle configuration dashboard. Please read documentation how to use.
  • Added Opslogix General Reports MP to the install package.
  • The container DB discovery is now by default disabled.

Fixes

  • The connection monitor now only reports an error when it is x times (2 default) in unhealthy state.
  • When creating a connection alert a parameter could not be resolved for the alert description.
  • During getting sysstats information with containing very big numbers the converting to SCOM data could be broken

and yes it is upgradable from  V1.3.0.0 or later

SCOM: Updated SQL Management Pack v7.0.20.0

A new version of the sql agnistoc MP is out get it here

What’s New

  • Updated MP to support SQL Server 2019 RTM
  • Added filter by edition to “Local DB Engine Discovery”
  • Redesigned DB Space monitoring to improve performance: Enabled by default
  • monitors and performance rules targeting Database which watch for disk space consumption by ROWS Filegroups and Logfiles
  • Redesigned DB Space monitoring: Added two monitors and two performance rules
  • targeting Database to watch for disk space consumption by In-Memory and
  • FILESTREAM data
  • Redesigned DB Space monitoring: Read-only filegroups now count as well
  • Redesigned DB Space monitoring: Disabled by default all workflows targeting
  • Filegroups, Files, Logfiles
  • Redesigned XTP performance counters to make them completely version-agnostic
  • Added attribute “TCP Port” to “SQL DB Engine Class” and updated “DB Engine
  • Discovery” to populate the new property
  • Added summary dashboard for SCOM 2019 Web Console (HTML5)
  • Added support for cluster nodes with disjoined namespaces
  • Added sampling to algorithm of monitor “WMI Health State” in order to eliminate
  • false alerting on cluster SQL Server instances
  • Updated alert descriptions of monitors “Availability Database,” “Availability Replica,”
  • and “Availability Group” (generating alerts still disabled by default)
  • Updated monitor “Product Version Compliance” with versions of most recent public
  • updates to SQL Server
  • Disabled by default monitor “Buffer Cache Hit Ratio” and changed its threshold
  • from 0% to 90%
  • Disabled by default monitor “Page Life Expectancy”
  • Removed monitors “Availability Database Join State” and “Availability Replica Join
  • State” as not useful
  • Updated display strings
  • Revised columns on DB Engine state views

Bug Fixes

  • Fixed: monitor “Service Principal Name Configuration Status” raises false alerts
  • because of case-sensitive comparison
  • Fixed: “Local DB Engine Discovery” crashes when Windows has Turkish locale
  • Fixed issue that caused performance degradation in workflows “General Always On
  • Discovery,” “Database Replica Discovery,” and “Always On System Policy
  • Monitoring”
  • Fixed: “General Always On Discovery” throws errors on environments with several
  • Distributed Availability Groups
  • Fixed monitoring issue in case of Database is replicated by Always On Availability
  • Group
  • Fixed empty property bag when Availability Group has cluster type NONE
  • Fixed wrong target in alerting rule “DB Backup Failed to Complete”
  • Fixed rule “MSSQL Integration Services on Windows: The package restarted from
  • checkpoint file” and its alert
  • Fixed rule “OS Error occurred while performing I/O on pages“ and its alert
  • Fixed: “DB Disk Write Latency” and “DB Disk Read Latency” monitors and
  • performance rules get wrong performance metric
  • Fixed alert description of monitor “WMI Health State”

SCOM: Updated Management packs for HP Storage

HP has released updated MPs to go with the new version of HP Oneview

It’s a solid update with useful new features such as integration with the new HTML 5 console.

What’s new in HPE OneView for Microsoft System Center 9.4?

The new version is available for download the HPE OneView Partner integration page and the HPE Storage Integration with Microsoft System Center page. It includes the following improvements:

  • HPE OneView for Microsoft System Center v.9.4 the latest HPE Storage array software. For more information, see Integration Matrix
  • HPE Storage Management Pack for System Center v.5.0 supports monitoring of HPE 3PAR StoreServ Storage systems with IPv4 and IPV6 connectivity
  • HPE OneView SCVMM Integration Kit v.5.0 supports HPE 3PAR StoreServ Storage systems with IPv4 and IPV6 connectivity
  • Support for HPE OneView 5.0
  • The System Center Operations Manager 2016 web console integration is now fully HTML5 compliant. The dependency on legacy frameworks has been removed to enable a predictable, consistent user experience for the web console users

SCOM: Updated SSRS and SSAS management pack v7.0.17.0

Updates to SQL Server Reporting Services and Analysis Services Management Packs have been released you can get them at the below links:

SSRS
SQL Server 2008 Reporting Services (Native Mode)
SQL Server 2012 Reporting Services (Native Mode)
SQL Server 2014 Reporting Services (Native Mode)
SQL Server 2016 Reporting Services (Native Mode)
SSAS
SQL Server 2008 Analysis Services
SQL Server 2012 Analysis Services
SQL Server 2014 Analysis Services
SQL Server 2016 Analysis Services


Fixes and changes for SSRS

  • SSRS 2016: Updated monitoring of Memory Consumption and CPU Usage in order to collect performance data for all subprocesses in addition to the main SSRS service process.
  • SSRS 2016: Updated monitors “Report manager accessible” and “Web service accessible” to consider specifics in how appropriate SSRS 2016 web services work
  • Added support for cases when connection string to SSRS Database is set up the way different from “MachineName\InstanceName” (e.g., <IPAddress,Port>) and SSRS Database is in Availability Group or hosted either by named instance or SQL Cluster instance
  • Improved descriptions of events thrown by management pack to make it easier to figure out error reason
  • Improved error handling and error descriptions for cases when workflows can’t get responses from WMI
  • Improved error handling in workflows that watch for memory consumption
  • Fixed Start/Stop tasks
  • Fixed issue that caused some workflows to throw error events when SQL Server instance hosting SSRS Databases happened to stop operating or refuse connections
  • Fixed issue which caused Reporting Service instance to get undiscovered when WMI didn’t respond to calls
  • Updated display strings

Fixes and changes for SSAS

  • Added performance collections for MDX Query performance counters
  • Added retry logic to some workflows in order to reduce “Category does not exist” errors thrown when WMI fail to respond
  • Improved error handling in workflows that watch for memory consumption
  • Improved descriptions of events thrown by management pack to make it easier to figure out error reason
  • Fixed Start/Stop tasks
  • Fixed issue when “SQLServerInstalled” property was set to “False” if SQL Server DB Engine was of higher version than SSAS instance
  • Updated Dashboards configuration to show tiles for new MDX performance collections
  • Updated display strings

SCOM: Updated Lenovo Hardware Management Pack v7.6.0.8

A new version of the Lenovo Hardware management pack is available get it here

What’s New

  • View and monitor XClarity Integrator Service in the Operations Manager console.
  • Disable BMC node auto-discovery and authentication by default.
  • Support to only manage the BMC of servers already managed by Operations Manager.
  • Monitor the BMC authentication state.
  • Support to remove BMC nodes in batch.
  • Support Microsoft System Center Operations Manager 2019.

SCOM: Updated IBM Storage MP v2.7.0

It’s been a little while since we’ve talked about the IBM Storage MP and there have been some improvements, as always you can get it here but remember you will need the serial number of your IBM device in order to download.

So what’s new?

Version 2.7.0 adds support for Microsoft System Center Operations Manager 2016 and the following storage system releases:

  • IBM FlashSystem® A9000 versions 12.0.x, 12.1.x, and 12.2.x
  • IBM FlashSystem A9000R versions 12.0.x, 12.1.x, and 12.2.x
  • IBM® Storwize® V3500 versions 7.8 and 8.1.x
  • IBM Storwize V3700 version 7.8 and 8.1.x
  • IBM Storwize V5000 version 7.8 and 8.1.x
  • IBM Storwize V7000 version 7.8 and 8.1.x
  • IBM SAN Volume Controller version 7.8 and 8.1.x
  • IBM FlashSystem V9000 7.8 and 8.1.x
  • IBM DS8880 8.2 and 8.3

This version also includes the following enhancement:

The following properties have been added to the IBM Storage Management Pack for Microsoft System Center Operations Manager user interface for the IBM Spectrum Virtualize™ Family management pack to make it easier to distinguish between different IBM Spectrum Virtualize Family storage systems being managed:

  • code_level: The software release version on the storage system being managed.
  • product_name: The IBM product name of the storage system being managed.

SCOM: Updated MP For Windows Server 2016 and 1709+ v10.1.0.0

The updated version of Windows Server Operating System 2016 and 1709 Plus can be found here

New in this version

  • Added Microsoft.Windows.Server.Html5.Dashboard.mp
  • Updated WMI query exceptions scenarios for OS discovery
  • Fixed  “Process and Port Monitoring” ProcessCmdDim table grooming bugs
  • Added support Logical Disk Volume Information task for Windows Server 2019
  • Added support Display Server Statistics for Windows Server 2019
  • Fixed incorrect frequency and threshold values for CPU Percentage Utilization, CPU DPC Time Percentage, CPU Percentage Interrupt Time monitors

SCOM 2019 is now available!

New SCOM Specific features

  • With HTML5 dashboards and drill down experiences in the SCOM web console, you will now be able to use a simplified layout and extend the monitoring console using custom widget and SCOM REST API.
  • Taking modernization a step further, email notifications in SCOM have been modernized as well with support for HTML-email in SCOM 2019.
  • SCOM 2019 brings a new alerts experience for monitor-based alerts whereby alerts have to be attended to and cannot be simply closed by operators when the respective underlying monitors are in unhealthy state.
  • SCOM has enhanced your Linux monitoring by leveraging Fluentd; and now is resilient to management server failovers in your Linux environments.
  • All the SCOM management packs will now support Windows Server 2019 roles and features.
  • With Service Map integration with System Center Operations Manager (SCOM), you can automatically create distributed application diagrams in Operations Manager (OM) that are based on the dynamic dependency maps in Service Map.
  • With Azure Management Pack, you can now view perf and alert metrics in SCOM, integrate with web application monitoring in Application Insights, and monitor more PaaS services, such as Azure Blob Storage, Azure Data Factory, etc.
System Center Operations Manager web console

Important changes to release cadence

Finally, we are making changes to System Center release cadence to optimize the way we are delivering new features. System Center has two release trains today – LTSC and SAC. There is also a release train called Update Rollups (URs).

Most of our customers use Long Term Servicing Channel (LTSC) like System Center 2016 to run their data center infrastructures. LTSC provides five years of mainstream support and five years of extended support – with Update Rollups (UR) providing the incremental fixes and updates. From talking to customers, we learned that LTSC works better for most System Center deployments as the update cycles are longer and more stable.

Based on the learnings, we will start to focus our resources on innovation plans for System Center in LTSC releases and stop SAC releases. System Center 2019 will support upgrades from two prior SAC releases so customers running System Center 1801 or System Center 1807 will be able to upgrade to System Center 2019; just as System Center 2016 can be upgraded to System Center 2019.