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. SCOM CI-connector keeps setting Logical Disks to Pending Delete

    I can only assume the SCOM team is responsible for the SCOM CI-connector as well.

    We're seeing a lot of disks being marked as "pending delete" from SCOM, and having them being set to Active again with the SCCM connector. In this case, the SCCM connector is correct. This poses problems since we use the disk size reported from SCCM to produce sizing reports and forecasts.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. Invalid ‘Data Access Service SPN Not Registered’ entries in the ‘Operations Manager’ event log

    As per Kevin Holman’s article entitled ‘OpsMgr 2012: What should the SPN’s look like?’ (i.e. https://kevinholman.com/2011/08/08/opsmgr-2012-what-should-the-spns-look-like/), please correct the following erroneous event log entries that are logged when the SDK service is restarted (and configured with an AD account):

    Event Log: Operations Manager
    Event ID: 26371
    Event Source: OpsMgr SDK Service
    Event Level: Warning
    Event Description:

                The System Center Data Access service failed to register an SPN. A domain admin needs to add MSOMSdkSvc/MS1 and MSOMSdkSvc/MS1.contoso.com to the servicePrincipalName of CN=MS1,CN=Computers,DC=contoso,DC=com
    

    The events are still being logged, even in SCOM 2019.

    Thank you,

    61 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. implement ssh server on scom and support python scripts

    Due to the need for hybrid environments with opensource systems and the scom's apliances to stay competitive with, market chains should enable native support for secure ssh communication but without fully depending on the requested agent, thereby opening up numerous possibilities for direct execution of Hi, I have a ssh command. I have a ssh command. I have a ssh command that interprets bash commands via ssh but it does not have native support. It is mandatory to install an ssh service on the windows server, there is also a need to run python scripts, such as zabbix and splunk…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  4. Design Scom to support Kusto language instead of SQL Query

    Currently we are able to collect monitoring data, Audit through ACS or dashboard deployment, either by Scom Console or VSAE or other partner tools. Depending on the dashboard and customer skill, it's a struggle to create these tasks and many give up and move for a easier competitor monitoring tool.
    With Kusto Language used by Azure Monitor, many customers had a good feedback because it's easier to create dasboards and query data. However some ones are restrict to use Cloud Solution due to company policy and prefer using on-premises solutions.
    Another barrier for using SQL query is a dependence from…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Comparison of should and is the network discovery

    Network devices that are to be explicitly determined are sometimes discarded. They do not appear in pending management. It is also possible to double-monitor the same network device (SNMP only and ICMP only). Here would be a comparison between SOLL and IST very helpful.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  6. False "Zone Query Overload" alerts from DNS Management Pack 10.1.0.0

    The data source that the "Windows DNS Server 2016 and 1709+ Detect Zone Query Overload" monitor and "Windows DNS Server 2016 and 1709+ Number Of Queries Performance Collection Rule" has an issue. If the server is under heavy CPU load at the time the data source runs, it fails and records a value of "0". This causes false alerts, as the "Zone Query Overload" is a "Delta" type monitor, so it sees a huge increase in queries when the next attempt succeeds.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other Management Packs  ·  Flag idea as inappropriate…  ·  Admin →
  7. UPN support in Webconsole

    Just installed an SCOM2019 environment. UPNs still do not work in the web console login ...

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
  8. Change SCOM 1807 support from SAC to LTSC

    Now that SCOM 2019 is available, but lacking the mandatory support for 2008/2012 Operating Systems.

    Customers with these Operating Systems cannot upgrade to SCOM 2019.

    And although they trusted Microsoft and upgrade to SAC, they will no longer get fixes or new features.

    And worse of all,
    They will not get further support beyond the 18 monthly period for SCOM 1807.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. IM alerting to Microsoft Teams

    Dear developers,
    it would be great to see IM SCOM integration with Microsoft Teams, so IM alerting can be done for those who have migrated from SfB to Teams.

    At the moment the only option is to either have SFB server onpremise and send IM notifcations to Teams/SFB Online or to use Hooks in Teams which isn't perfect because it actually sends posts on Teams Channel rather than sending IMs to people on Teams.

    Hopefully IM notifications support for Teams will come one day.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. Microsoft Teams monitoring

    Dear developers,

    would love to see you making adjustments to O365 management pack with the ability to monitor the status of Microsoft Teams. Currently o365 management pack is really not transparent and its based on ticket system. It would be great to have something like it is for SfB on premise where you can use synthetic transactions. I would love to see synthetic tests checking if PSTN and Peer-to-Peer calls are working from/to Teams.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  O365 Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  11. Agent Reads Prior Events After Exiting Maintenance Mode

    I've run into an issue where after coming out of maintenance an agent goes back and reads events from prior to the maintenance mode end time. This generates alerts from events that occurred while the machine was in maintenance. It appears this has been an issue since at least 2009, but still exists in the SCOM 2016 agent:

    https://social.technet.microsoft.com/forums/systemcenter/en-US/8a115e60-ef00-4eb0-a84d-1a420182e70e/sql-management-pack-failing-on-old-sql-agent-jobs

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  12. Active Alerts view - not refreshing in non-IE browsers

    Ever since SCOM 1801, the Active Alerts view in WebConsole does not refresh automatically in non-IE browsers (Edge, Chrome, Firefox, etc.). An updated 'MonitoringBundle.js' file was provided by Microsoft support which made it work in modern browsers. But even in SCOM 2019, this issue is not fixed and I had to use the workaround script file. Could this be implemented as default for all versions? Internet Explorer may be hardly used anymore in the IT community.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  13. SCOM Installer Failure with RC4 Protocol Disabled

    SCOM 1801/1807 installer and discovery wizard fails to work until I had to enable RC4 on the DC, SCOM management server, and the SCOM database server. Please remove the RC4 dependency. I had to find this article to figure out that RC4 was my issue. https://nathangau.wordpress.com/2018/06/22/scom-installer-failure-with-rc4-protocol-disabled/

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ability to turn off alerts not able to be closed in SCOM 2019

    We need to be able to disable the feature preventing alerts from being closed if the monitor is in an unhealthy state.

    As it currently stands integration with a Service desk such as Netcool is problematic as if the alert is closed in the service desk when the writeback happens to SCOM the chain breaks as the alert cannot always be closed in SCOM.

    Feature below:

    If you close an alert generated by a monitor (from the Operations Console “Active alerts” view) which is in a unhealthy state then the following message will be displayed and the alert will not…

    227 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  15. Enable delivery address field for commands

    Enable delivery address field for commands, so it will be possible to send alerts to subscribers through Powershell scripts

    command : "myScript.ps1" '$Data/Recipients/To/Address/Address$' ...

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 →
  17. 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…)
    0 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  18. Service Level Tracking - Add 'Business Hours'

    Please add the ability to define 'business hours' or schedules when authoring SLO objects. This would allow SLO tracking of objects only at given times or schedules to match business needs.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Authoring  ·  Flag idea as inappropriate…  ·  Admin →
  19. Optional Event Collection MP for DNS MPs version 10.0.9.3 Doesn't Enable 2016 Rules

    Looks like maybe the optional event collection MP wasn't updated to enable the 2016 rules?

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other Management Packs  ·  Flag idea as inappropriate…  ·  Admin →
  20. Provide option for alternative installation directories on Operations Console for agent installation on unix/linux servers other than /tmp/

    Currently default directory for agent installation on Unix/Linux servers using Operations Console is /tmp/scx-username. However, if /tmp directory is hardened due to security reasons for unix/linux servers on customer environment, they will have to manually install scom agent on unix/linux servers and does not have an alternative to install the agent from Operations console on other directory.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base