General Operations Manager Feedback

Do you have an idea or suggestion based on your experience with SCOM? We would love to hear it! Please take a few minutes to submit your idea in the one of the forums available on the right or vote up an idea submitted by another SCOM customer. All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building SCOM. We have already added some of the feedback we received through the TAP program and the recent SCOM survey.

This forum (General Feedback) is used for any broad feedback related to SCOM.
Be specific on your feedback. The more specific, the easier and quicker for us to review. Please be concise!!

If you have technical questions or need help with SCOM, please try visit our MSDN forums.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. SQL Version Agnostic MP Remove overrides stored in "Microsoft SQL Server on Windows (Monitoring)"

    storing overrides in a sealed MP limit the possibilities to tune management packs

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  2. SQL Version Agnostic MP (7.0.15.0) PrincipalName Removed for DBEngines

    The new SQL 2017+ management pack for SCOM changes the PrincipalName for DBEngines. It now shows the NetBIOS type instance name instead of the Parent FQDN of the host. Additionally, the alerts do not have the field PrincipalName populated.

    This is a breaking change to orchestration and reporting.

    Would it be possible to return the PrincipleName and the Instance name?

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  3. SCOM Monitoring Failure with PowerBI Report Server / SSRS Updates

    Hello,

    We are using SCOM 2019 to monitor our SSRS and Power BI Report Server deployments using the SQL 2017+ Reporting Services management pack (v7.0.15.0).

    This management pack is able to successfully monitor SSRS 2017 and Power BI Report Server deployments up to May 2019, however when upgrading or deploying to Power BI Report Server September 2019, the "Report manager accessible - PBIRS" monitor in SCOM becomes critical and the following error appears in the RSPortal log file under C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles:

    2019-12-05 10:41:19.4770|ERROR|37|DOMAIN\SCOMRunAsAccount ::1: HEAD - 0:00:00.0004824
    Exception: System.Net.ProtocolViolationException: Bytes to be written to the stream…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  4. Description Bug: MSSQL on Windows: Some securables are inaccessible

    In the MSSQL on Windows: Some securables are inaccessible alert the Alert description states that the following objects are views;
    - msdb.dbo.sysjobschedules
    - msdb.dbo.log_shipping_primary_databases
    - msdb.dbo.log_shipping_secondary_databases

    These are actually Tables in MSDB. This can be confusing for non-SQL SCOM admins when trying to troubleshoot and resolve issues

    This should be updated to reflect that they are tables not views.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  5. SCOM SQL 2017+ DB Log Free Space in Megabyte

    In the SQL 2017+ Management Pack is a Monitor to monitor the free DB log space in percent. We would like to monitor the free DB log space additionally in MB. We need this because we have very much DBs, and they are from very small to very big. Its to much effort to set for every DB another percent treshold. And if we set a threshold 10%, this is good for small DBs, but if we have a big DB, there is no problem when free space is for example 10% but still 100GB. So we wanna set a…

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  6. Update DB Virtual Log File workflow to use sys.dm_db_log_info instead of DBCC LOGINFO

    Hello,

    When the Version Agnostic management pack attempts to collect VLF counts, it uses DBCC LOGINFO("dbname") to achieve this. Would it be possible to update this workflow to use sys.dmdblog_info instead? This replaces DBCC LOGINFO as described in the below documentation:

    https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-db-log-info-transact-sql?view=sql-server-ver15#remarks

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  7. SQL Server British English RunAs (login) accounts don't work properly

    I have reported a problem to MS support that they have been able to successfully repro but it has been suggested that I post it on here as well.
    On SCOM 2012R2 and SQL2017, if the RunAs account is British English then failing database backups don't report. If you change it to English and restart the SQL Server it all works. If you change it back and restart it doesn't.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  8. Version Agnostic MP (7.0.15.0) Clustered Instance Discovery Issues

    The version agnostic management pack (v7.0.15.0) appears to have issues discovering clustered SQL Server instances. I deployed it alongside a fresh SCOM 2019 build without any of the old SQL Server management packs imported, and only some instances/databases are being discovered – it’s a very strange mix of results. We have a SQL 2014 instance that gets discovered fully (including databases), a SQL 2016 instance which is discovered with its databases but are not monitored, and SQL 2016/2017 instances that aren’t discovered at all.

    I then imported the SQL 2016 management pack (v7.0.15.0) and it discovered all the clustered instances/databases…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  9. SQL Integration MP Discovers Duplicate Integration Services

    The 2014 and 2016 SQL Integration packs have "Discover SQL Server 2014 DB Installation Source (seed)" discoveries that are targeted toward the "Windows Server" class. In environments where SSIS may be installed on SQL Clusters (and SCOM has the clustering MPs imported), this can lead to duplicate instances of the Integration services being discovered. Clustered resource "servers" are also populated into the "Windows Server" class. I creates groups populated with "Windows Server" objects with the "Is Virtual Node" property set to "True", and override the discoveries using these groups. Pan Optional MP could be included that would be imported if…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  10. SQL Integration MP Discovers Duplicate Integration Services

    The 2014 and 2016 SQL Integration packs have "Discover SQL Server 2014 DB Installation Source (seed)" discoveries that are targeted toward the "Windows Server" class. In environments where SSIS may be installed on SQL Clusters (and SCOM has the clustering MPs imported), this can lead to duplicate instances of the Integration services being discovered. Because clustered resource "servers" are also populated into the "Windows Server" class, they too discover SSIS instances. In one example here, one cluster that only has two base nodes had five different SSIS instances discovered, when only the base nodes should be discovered. I had to…

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  11. SQL MP wrongly specifies Service Pack Level

    SQL MP wrongly discovers Service Pack Level attribute which shows 0 but the SQL 2016 is already installed as 13.1 which is SP1 version. Please correct.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  12. SSMS != SQL Server

    SCOM is apparently assuming that a machine with SSMS (SQL Server Management Studio) installed must also have SQL Server installed and is alerting with "MSSQL 2014: Monitoring warning" or "MSSQL 2016: Monitoring warning" for all of our RDS VMs used by our IT group. SSMS has been a separate install for quite some time now and the SQL Management Pack needs to be updated to handle that properly.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  13. The tasks to Stop/Start SQL Server Analysis Services and SQL Reporting Services are no longer available since breaking out SQL 2014 and SQL

    Please add tasks to Stop/Start SQL 2014/2016 Analysis Services and Reporting Services. This is available in SQL 2005-2012 MP but was not put into the SQL 2014-2016 SSAS/SSRS MP's. SQL 2014-2016 DB Engine has these tasks. We have DBAs that have used this task in SCOM for years but are unable to Stop/Start services since SQL 2014.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  14. Make the monitors on SQL agents jobs more flexible

    Currenly it is not possible to configure the SQL Agent Job monitors Long Running Jobs and Last Run State to check on specific days a week. The parameters Start Time, End Time and Days Of Week Mask would be most welcome.

    Many SQL Agent jobs are configured to run once week or even once a month.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  15. Handle unreadable SQL AlwaysOn instances better

    VBScripts that log into the SQL instance attempt to open secondary copies that are (intentionally) set to not be readable. This causes a steady stream of discovery permission alerts.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  16. SQL MP should be enterprise ready

    Today sql MP is recommended for max 50 databases. That's not very enterprise-ish. Maybe a complete rewrite is needed.

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  17. Advanced Mirroring Monitor with automated Resume Recovery

    Current SQL Management Packs provide reactive insight/notification into issues with mirroring, but there are no automated recoveries/ability for automated proactive maintenance when an issue is discovered. Mirroring outages require custom code, or manual intervention to resolve. This translates into added cost for customers in terms of in-house development, or if a recovery is manual it means longer outage durations.

    Request is for a monitor that looks at the current state of mirrors + a automated recovery which executes a RESUME for any mirrors that are DISCONNECTED, SUSPENDED or UNSYCHRONIZED. It then should wait to give the mirrors a chance to…

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  18. Easier to discover SQL Cluster

    It seems there is no easy way to determine why a SQL Cluster is not being discovered. The host OS gets discovered, but if you don't have all the accounts right and sometimes it still doesn't get discovered. there doesn't seem to be anything in the logs to say why its not being discovered.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  19. Improve SPN detection on SQL MP

    Today the SQL MP will not check the IP adresse the SQL Instance is listen. The SQL MP looks for the port. It then assumes that the IP Adresse is the adresse of the FQDN of the server. But this is not always the case. Please improve the system and look for the IP adresse. Then you can derive the right FQDN.
    In my opinion at the moment this is just not correct implemented.

    Thank's

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  20. Monitoring of free space in AlwaysOn cluster does not work in SQL 2014

    The scripts in SQL 2014 MP does not handle AlwaysOn correct. When evaluated if the database is a replica the property secondaryroleallow_connections is checked and if set to <= 1 the database is skipped. However, this is true even if the script is connected to the primary node which is accepting connections. This causes all free space monitoring for AlwaysOn databases that do not allow connections to secondary nodes to fail without any notice to the users, even when the script is connected to the primary node.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base