Category Archives: SCOM 2012 R2

SCOM: Updated MP for Talon FAST Storage v1.0.0.149

Talon have released an updated version of their FAST storage management pack for SCOM get it here.

In this version

  • Operational Management
    • Systems level inventory
    • Patch level inventory
  • Availability Management
    • Systems Health Status
    • Event Viewer
    • SCOM alerting
    • i.e. Key services not running
  • Systems Optimization
    • % Cache Utilized
    • Cache Purge alert via SCOM

SCOM 2016: Error while connecting to management server: The client has been disconnected from the server

When trying to install a second management server in a SCOM 2016 management group, after entering the OpsDB details,  a few moments later the wizard would return to the SQL details screen.

A brief investigation revealed the following error in the installation log file (OpsMgrSetupWizard.txt this is your best friend for troubleshooting SCOM installations):

Info:Error while connecting to management server: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.
Error: :Couldn’t connect to mgt server stack: : Threw Exception.Type: Microsoft.EnterpriseManagement.Common.ServerDisconnectedException, Exception Error Code: 0x80131500, Exception.Message: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.

First confirming that the Data Access service was in fact running on the original management server and that a connection could be made to the SDK.

It turns out that the two servers times were out of sync by more than 5 minutes causing a Keberos time skew. After correcting the server time the second management server installed with no issues.

SCOM 2016: Updated SQL Server Management Packs v6.7.31.0

New versions of the SQL management packs were released a short while ago links for all of the versions 6.7.31.0 MPs can be found below:

SQL Server

SQL Server 2008/2012 – here
SQL Server 2014 – here
SQL Server 2016 – here

SQL Server Dashboards

SQL Server Dashboards – here

SQL Server Replication

SQL Server 2008 Replication – here
SQL Server 2012 Replication – here
SQL Server 2014 Replication – here
SQL Server 2014 Replication – here

SQL Server Analysis Services

SQL Server 2008 Analysis Services – here
SQL Server 2012 Analysis Services – here
SQL Server 2014 Analysis Services – here
SQL Server 2016 Analysis Services – here

SQL Server Reporting Services (Native Mode)

SQL Server 2008 Replication(Native Mode) – here
SQL Server 2012 Replication(Native Mode) – here
SQL Server 2014 Replication(Native Mode) – here
SQL Server 2014 Replication(Native Mode) – here

 

New in this version:

Important Notes About This Release

  • Please note that we implemented a new alerting rule for SQL Server event #18456 “Login failed” in this release. However, this rule may become rather noisy due to the fact that the target events appear quite frequently in some environments. The rule is enabled by default; thus, if it creates too many alerts in your environment, consider disabling it via the override. The ideal would be to resolve the underlying issues causing the alert but we understand this is not always a priority.
  • We are introducing a new monitor in this release (see the first bullet below) based on customer feedback. You have now a better solution for monitoring backups of AG databases.

SQL Server 2008-2016

  • Added new “Availability Database Backup Status” monitor in Availability Group to check the existence and age of the availability database backups (this monitor is disabled by default)
  • “Database Backup Status” monitor has been changed to return only “Healthy” state for the databases that are Always On replicas, since availability database backups are now watched by the dedicated monitor
  • Improved performance of DB Space monitoring workflows
  • Added new “Login failed” alerting rule for SQL Server event #18456
  • Fixed issue: “Active Alerts” view does not show all alerts
  • Fixed issue: DB space monitoring scripts fail with “Cannot connect to database” error.
  • Fixed issue: PowerShell scripts fail with “Cannot process argument because the value of argument ‘obj’ is null” error
  • Fixed issue: Alert description of “Disk Ready Latency” and “Disk Write Latency” monitors displays the sample count instead of the performance value that was measured
  • Fixed issue: Different file location info from “sys.master_files” and “sysfiles” causes error when Availability Group secondary database files are in different path
  • Fixed issue: “DB Transaction Log Free Space Total” rules return wrong data
  • Introduced minor updates to the display strings
  • Deprecated “Garbage Collection” monitor and the appropriate performance rule
  • Resource Pool Discovery is disabled by default for pools not containing databases with Memory-Optimized Tables
  • “XTP Configuration” monitor now supports different file path types (not only those starting with C:, D:, etc.)
  • Fixed issue: “Resource Pool State” view shows incorrect set of objects
  • Fixed issue: Invalid group discovery in SQL Server 2016 Always On
  • Updated the visualization library

SQL Server Dashboards

  • Increased the version number to comply with the current version of SQL Server MPs

SQL Server 2008-2016 Replication

  • Added Distributor name caching to Subscription discovery
  • Restricted the length of some string class properties
  • Improved the internal structure of SQL scripts storage
  • Fixed variable types in SQL scripts
  • Fixed connectivity issues in SmartConnect module
  • Introduced minor updates to the display strings
  • Updated the visualization library

SQL Server 2008-2016 Reporting Services

  • Reimplemented Instance seed discovery: replaced the managed module with a PowerShell script
  • Reimplemented Deployment seed discovery: added a retry policy and improved error handling
  • Updated the visualization library

SQL Server 2008-2016 Analysis Services

  • Restricted length of some string class properties
  • Updated the visualization library

SCOM: Updated NiCE DB2 MP 4.20

Another updated MP released over at NiCE this time for IBM DB2 get more info here.

New with this release

  • Feature: Support of DB2 BLU Acceleration
  • Feature: Monitoring of InDoubt Transactions
  • Security: Support of DB2 restrictive databases
  • Security: Support of non-root setup and operation
  • Security: DB2 Instance attach extensions for user and password options
  • Platform: New platform support for IBM AIX 7.2
  • Platform: Support of non-standard paths for both installation path and instance user home directory

SCOM: Updated NiCE PowerHA MP 1.20

Our friends at NiCE have released an updated MP for PowerHA go here for more info.

What´s new with this release

  • Logical Disk Monitoring for Cluster File Systems
  • No False Files Systems Alarms from Microsoft® AIX Management Pack anymore!
  • Cluster-aligned Service Model
  • Improved Discovery for Cluster Resources
  • Updated Product Knowledge

SCOM: New MP for Office 365 v7.1.5138.0

An updated management pack is available for Office 365 you can get it here.

Updates and Fixes

  • Automatically created SPN is never expired.
  • Fixed issue: no alerts were generated for identical feature names related to different services.
  • Improved discovery logic according to the latest version of Office 365 (support for services with similar display names).
  • Updated “Office 365 Incidents and Messages” section.
  • Updated “Import the Management Pack” section.
  • Updated “Specify permissions your app requires to access Office 365 Management APIs” section.
  • Updated “Appendix: Known issues and troubleshooting” section.

SCOM and Deprecating SHA1 Certificates what you need to know!

With the recent deprivation of SHA1 certificates in favour of the more secure SHA2 it’s important to know that SCOM uses  SHA1 to manage workloads for cross platform monitoring (Unix / Linux).

Have no fear the MS SCOM team have released an article on how to replace your existsing SHA-1 certificates with the newer SHA256 certificates.

It is important to note that you will need to update your 2012 R2 environments to UR 12 and your 2016 environments to UR2 respectivly in order to use the new SHA256 certificates by default.

The article is available here