General Operations Manager Feedback

Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback.  Learn more


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. Fix the predefined command line parameters for the Command Notification Channel wizard settings

    When creating a Command Notification Channel under the Administration pane in the console, the predefined command line parameters for "WebConsole Alert Link" and "WebConsole Alert Source Link" given in the auxiliary menu for command line parameters is incorrect. It appears the Syntax has errors.

    When attempting to add for either of these presets we get:
    $Target/Property[Type="Notification!Microsoft.SystemCenter.AlertNotificationSubscriptionServer"]/WebConsoleUrl$/#/monitoring/drilldown/alert/$UrlEncodeData/Context/DataItem/AlertId$

    And
    $Target/Property[Type="Notification!Microsoft.SystemCenter.AlertNotificationSubscriptionServer"]/WebConsoleUrl$/#/monitoring/drilldown/object/$UrlEncodeData/Context/DataItem/ManagedEntity$

    The problem is the last part of each of these statements:
    $UrlEncodeData/Context/DataItem/ManagedEntity$

    Which should be formatted as
    $Data/Context/DataItem/ManagedEntity$

    The problematic form is incorrect and does not yeaild the epected information, however it is a predefined preset built into the UI.

    Kevin Holman…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  1 comment  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
  2. SCOM 2019 support for 2008 R2 Clients

    We need support in SCOM 2019 for agents that are running Server 2008 R2. Almost a quarter of our servers are still 2008 R2, and this is a huge hang up for us in moving up. Since these are more legacy systems, most are also unable to be updated.

    102 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. Please return the option “Raised by any instance of a specific source” in the “Scope” pane of the “Notification Subscription Wizard”

    In SCOM 2019, though there have been some phenomenal improvements in the flexibility now offered when defining notification subscriptions, the option to specify “Raised by specific rules or monitors (i.e. sources)” has been removed from the “Criteria” pane of the “Notification Subscription Wizard”. Though one could get around the problem by adding the “Alert name” criteria in the “Criteria” pane, I have the following 2 problems with this workaround:

    1. there is nothing stopping a MP developer from using an existing “Alert name”, which would have unintended consequences with such notifications;
    2. working in a multilingual SCOM environment, it is difficult to…
    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  Neha Garg responded

    This functionality is already present under subscription wizard.

  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  6. BUG in Microsoft SCOM 2016 Web Console: "500 - Internal Server Error" !!!! SOLVED !!!!

    Dear Microsoft IIS/SCOM Developer Team,

    we have a absolutely new SCOM 2016 infrastructure and had had until today issue with the SCOM 2016 Web Console.

    I created related to "500 - Internal server error" some forum questions. Also I read the similar 500 error on other discusiions in Technet forums.

    Finally I found the BUG in SCOM 2016 Web Console!

    I will list the bug in IIS/SCOM and my solution, and also want that MICROSOFT should make a statement to this issue!

    ISSUE:

    If any user try to access to SCOM 2016 Web Console, "500 - Internal server error" will…

    57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  8 comments  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  4 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  11. Global Service Monitor - Increase Test Limit

    Increase the limit of the number of tests allowed for Global Service Monitor. 25 total tests per subscription is very low, especially when you want to monitor sites from multiple locations.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add an alert view for Major Updates from Message Center

    Add an alert view per O365 service with Major Updates only from Message Center

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  0 comments  ·  O365 Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  13. RunAs profile for Office365 monitoring

    The guide mentions a RunAs Profile should be configured manually for the Subscription Proxy Secure Reference. However it does not mention what the RunAs account should be targetted to. Is "all targetted objects" the correct one to use?

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Windows Server OS Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  15. Office 365 - Use Auto Close Monitors instead of rules for Incidents

    Currently the O365 MP all alerts are generated by a rule, and then there's another rule to close the alert (eventually, have yet to see it work). Why not use the already present (and well working) workflows from OpsManager to determine health instead and THEN generate incident alerts based on health state?. The IncidentState information is already in the Datasource's PropertyBag, why not use it in the ConditionDetectionModule to determine health.

    Also, while there is a somewhat detailed HealthModel which can and should be used as targets for the monitors above, there are no monitors attached to the classes so…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base