SCOM: Updated SQL Server Management Packs v6.7.7.0

Share on Social Media

New versions of the SQL Server management packs are out! They are available from the below links:

Note: Be aware that there have been some serious issues with previous versions of the SQL management packs this year. I cannot stress enough the need for testing before using these in a live environment.

SQL Server 2016: here
SQL Server 2014: here
SQL Server 2008 / 2012: here
SQL Dashboards: here

New in this version

SQL Server 2008 / 2012

  • Fixed issue: SQL Server 2012 Always On discoveries fail after stopping WSFC service
  • Fixed issue: “Set DB offline” task does not work when the database is in Availability Group
  • Fixed issue: user policy discovery script fails with “Invalid namespace “ROOT\Microsoft\SqlServer\ComputerManagement12″‘ error
  • Fixed issue: Always On console task does not work
  • Updated the visualization library

SQL Server 2014 / 2016

  • Fixed issue: “Set DB offline” task does not work when the database is in Availability Group
  • Fixed issue: Always On console task does not work
  • Updated the visualization library

Dashboards

  • Fixed issue: expanding “arrow” has low-contrast color when a health group is collapsed in Instance view (High-Contrast #2 color scheme)
  • Fixed issue: in Web console, Dashboards continuously send requests to the database
  • Fixed issue: not the first object gets selected in the object list after drill-down
  • Fixed issue: horizontal scroll position resets after refreshing the Instance view
  • Fixed issue: “No Data” message is displayed on some tiles after upgrading Dashboards management pack from version 6.7.2.0 to 6.7.4.0 or later version
  • Fixed issue: on Web console, Dashboards crash when drilling down from Datacenter view to Instance view
  • Restored the correct group order in SQL Server Summary dashboard views

7 thoughts on “SCOM: Updated SQL Server Management Packs v6.7.7.0

    1. Warren Kahn Post author

      That may be true but remember they were all stable until 6.0.0.0 suddenly had problems. It wouldn’t be the first time a MP had an issue that wasn’t picked up in QA. Testing before going live just helps avoid these scenarios.

      Reply
  1. Tommy

    I think u can remove SQL 2005 from your post, as that is no longer supported;

    Removed files of SQL 2005 MP from the installer since this MP is no longer supported

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.