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. Release and maintain a 2019 version of the "System Center Operations Manager 2007 R2 Authoring Resource Kit"

    Release and maintain a 2019 version of the "System Center Operations Manager 2007 R2 Authoring Resource Kit".

    This tool is an absolute gem in training new people to SCOM, which also gives them a better understanding on how everything is pieced together and useful for design work...

    6 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 →
  2. Enforcing TLS1.2 - Error 1410

    Enforcing TLS1.2 - Error 1410 coming from Active Directory Certificate Services MPs - Discovery rule "Certificate Services Topology Discovery discovery rule"

    Connection string in Management Pack has to be updated to support TLS1.2

    9 votes
    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 →
  3. Fix the script used to monitor the cluster disks

    When monitoring the Windows 2016 Failover Cluster disks, the script (Microsoft.Windows.Server.MonitorClusterDisks.vbs) times out and also causes the clussvc.exe to use excessive amount of CPU usage (on average 25% with peaks to 100%) if the cluster has a higher amount of physical disks (100). The systems are physical servers, with Xeon CPUs (8 physical cores + HT). The script does eventually finish if ran manually, but it needs 25 minutes...

    67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Windows Server OS Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  4. Monitor named "Performance Data collection health" needs to be fine tuned in a way that it does not overload the SQL Server when enabled.

    The default SCOM monitor named "Performance Data collection health" which is disabled by default, needs to be fine tuned in a way that it does not overload the SQL Server when enabled for 1000 + Agents. The way the SQL query is built it looks like running it against 1000+ Agents will cause performance issues on the SQL server.

    The purpose to enable this monitor is to identify if Performance data is stopped collected / missing for specific Agents in last few hours.

    Request the product group to review the request to see we can ship this by default enabled…

    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 →
  5. 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 →
  6. 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 →
  7. mount point

    The Windows Server OS MP v6.0.7323.0 is discovering the System Reserved \\?\Volume as a mounted disk when you create an override to enable the Mount Point Discovery Rule. This appears to be the case only for Server 2008 and 2012 but not for Server 2016. This behavior was addressed in an older version of the OS MP v6.0.7297.0. Did Microsoft forgot to include the fix in the current version? We need to monitor the mount points on our servers but there isn't a way to exclude just the \\?\Volume from the mount point discovery. Please advise on a fix. Thanks!

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Windows Server OS Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  8. @Microsoft: Loosing of Sense in SCOM

    Hi,
    I have been involved with SCOM for about 2.5 years and have been working with all versions of SCOM starting from SCOM 2016.
    Microsoft makes "developments" in SCOM, and now we have switched to the newest version SCOM 2019.
    Actually, every development is connected with progress. The word "development" includes this meaning.
    Unfortunately, I cannot see this sense at SCOM absolutely. It's getting worse, not better. This is not a "development", but a "reversal".

    I have already listed the problems with SCOM 2019 in my other problem tickets in Technet forums, and looked at solutions. Now we have another…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Start-SCOMAgentMaintenanceMode should have -Force parameter

    Agent -initiated maintenance mode https://docs.microsoft.com/en-us/system-center/scom/manage-maintenance-mode-overview?view=sc-om-2019#enable-from-target-system-1 is great, however as of now it still forces an answer in the console prompt - preventing the use from automated scripts that run on target systems. Adding a -Force parameter that skips the "are you sure?" check would be very welcome and trivial to implement, without us having to reverse and simulate the behaviour to reach the same effect.

    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 →
  10. HP-UX Agent Support in SCOM 2019

    I was reviewing the supported UNIX/Linux OSs at the following location:https://docs.microsoft.com/en-us/system-center/scom/plan-supported-crossplat-os?view=sc-om-2019 and took note that support for HP-UX has been removed. This is creating a problem for my current customer since they use HP-UX and will continue to use HP-UX. According to my customer HP-UX is still supported through 2025, so removing monitoring support in SCOM 2019 is going to be a problem. While I understand there may be workarounds for this issue, I am also concerned about maintaining the customer's environment in a supported configuration.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  11. Reduce the timeout for Rules and monitors in Network Management Pack monitoring

    Please reduce the Timeout parameter for all Rules and monitors, which is configured to 3500 secs as default. This is causing loops in Management server workflows and making Management Server to drop critical data. The timeouts for all rules and monitors are set to 3500 despite the workflow interval is set to 300 secs or 900 secs. Please adverse the Management pack with priority and appropriate value for monitors and rules.

    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 →
  12. Azure Management Pack Features - Survey request from PG

    https://microsoft.qualtrics.com/jfe/form/SV_9GhktKqx11ojgkR

    Please fill in this short survey and help us identify the areas of improvement and requested features in Azure Management Pack in SCOM. Thanks!

    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 →
  13. Create role for application monitoring author that doesn't require SCOM admin

    Currently it requires SCOM admin access to run Authoring console templates like Web Transaction Monitoring. In large enterprise environment, dev team should be able to create and modify web transaction monitors in the SCOM authoring space themselves without needing SCOM admin.

    7 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 →
  14. Expand MySQL Management Pack

    Expand MySQL Management Pack to include features like monitoring individual databases and replication status. The current offering, while a good start, is lacking many needed features.

    2 votes
    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 →
  15. SCOM2016/2019 Web Consoles - Need Mgmt Group Name added to header bar

    Folks, we have multiple instances of SCOM running, many of which are accessed by the same teams. In the Web Console the Mgmt Group name is not visible anywhere on the screen and teams are finding it difficult to understand which console they are currently connected to. Can the Mgmt Group name be added to the header bar?

    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 →
  16. licensing structure of SCOM 2019 / System Center 2019

    How the licensing structure for SCOM 2019 is? If we have procured license for SCOM 1801 or 1807. Is the same license can be applied once upgrading to SCOM 2019?

    Is there any license structure change for SCOM 2019 / System Center 2019

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. After Management Server removal, some orphaned objects remain

    After the deletion of a management server according the description in https://technet.microsoft.com/en-us/library/hh456439(v=sc.12).aspx some objects will remain
    Those objects can just get deleted through manual operations in the database. ==> Custom SP dbo.sp_RemoveObjectByTypedManagedEntityId
    The Health Service Watcher Object always remains after deletion.
    This behaviour is reproducible with SCOM 2012 R2 and SCOM 2016

    Expected Behavior
    The customer expects that if he strictly follows the step-by-step instructions to remove a management server from the management group, nothing should remain somewhere, neither in the database nore in the filesystem, registry or somewhere else

    Analysis
    I reproduced the problematic behavior in two different environments…

    101 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Include performance data for Azure Stack PAAS Capacities (MSSQL, MYSQL, etc)

    I am able to gather performance data that includes the total storage, memory, and public IPs available for an Azure Stack region but i cannot get data for the PAAS storage capacities. This is viewable within the SQL adapter section of the admin portal dashboard of Azure Stack, but i would like to add it to the SCOM dashboard as a performance widget to give a holistic overview of the whole region.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support for Windows Server 2019 agents on SCOM 1807

    Please, provide support for Windows Server 2019 agents on SCOM 1807. I could bet it works fine, but haven't tested yet
    I can't migrate to SCOM 2019, as I still have to monitor some 2008 agents (that will still take some time to migrate)

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other Management Packs  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base