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 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/

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. System Center solutions to identify dependency mapping

    Hello guys, does Microsoft have some solution compatible with BMC Discovery that shows dependency Mapping from one solutions identified ? Or for network ? I appreciate your help . thanks

    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 →
  7. Windows Server 2019 Software Defined Networking (SDN) Monitoring Pack

    Upgrade Windows Server 2016 Software Defined Networking (SDN) Monitoring Pack to Windows Server 2019 Software Defined Networking (SDN) Monitoring Pack to support Windows server 2019, SCOM 2019.

    3 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. 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 →
  9. 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 →
  10. Alert view for Alerts with other resolution states

    I have several alerts per object in the Active Alerts, I am trying to right-click the object owning the alerts and open alert view per this object, and I get an empty window.
    We are using several resolution states, and we have noticed using SQL Profiler that the default view that is opening when right-clicking an object only scopes for NEW alerts. It should be all alerts without the closed ones

    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 →
  11. fix metric alert monitoring in Azure Management Pack

    Monitoring of Azure Metric Alerts hasn't been working since early this year. Objects are discovered fine, but whenever an Azure Metric Alert fires, the change is not comming down to the SCOM environment objects, and thus no SCOM alert is generated.

    3 votes
    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 →
  12. SQL Server 2017 AlwaysOn - clr strict security leads to console error after failover of the OperationsManager database

    Due to security changes in SQL server 2017 it is not allowed to run dll's that are not signed (clr strict security). Please update the documentation with a workaround like adding the dlls to the list of trusted assemblies (SELECT * FROM sys.trusted_assemblies) in SQL on the secondary replica. Maybe a permanent fix is to sign the files. See this thread also https://social.technet.microsoft.com/Forums/en-US/195c0bd5-115c-4cff-8ae3-4109f59c9b1e/could-not-load-file-or-assembly-microsoftenterprisemanagementsqluserdefineddatatype-in-an?forum=operationsmanagerdeployment

    1 vote
    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 →
  13. Allow changing SSRS permissions and do not ignore them

    If a user is member of the SCOM Security Role "Operations Manager Report Operators" or any other "Report Operator"-Group it is not possible to browse the Reports-Website (https://reportserver.domain.local/Reports).
    It is only possible to directly call the reports. (https://reportserver.domain.local/Reports/Audit%20Reports/Access_Violation_-_Account_Locked)

    The error message is the genereic error: "Could not load folder contents You are not allowed to view this folder. Contact your administrator to obtain the necessary permissions."
    The SSRS-logs also do not provide any other more detailed explanation.

    I verified that the group-ID of the security role has "Browser"-Rights on the Root-SSRS folder.
    These rights are inherited…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →
  14. SCOM 2019 - Data Warehouse failed to deploy reports for a management pack to SQL Reporting Services Server

    Please can anyone elighten me on this since I cannot find a proper solution!

    The management pack in case is the new SQL agnostic version.

    Data Warehouse failed to deploy reports for a management pack to SQL Reporting Services Server. Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried.
    Exception 'DeploymentException': Failed to deploy reports for management pack with version dependent id '2d2d34e7-0361-d464-dec6-babb19c69871'. System.Web.Services.Protocols.SoapException: Uploading or saving files with .rdl extension is not allowed. Contact your administrator if you have any questions. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ResourceFileFormatNotAllowedException: Uploading or saving files with .rdl extension is…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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 →
  16. @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 →
  17. PKI Certificate Monitoring for Unix/Linux

    In addition to developing the PKI Certificate Monitoring MP directly and not having to rely on 3rd party, add the ability to monitor PKI Certificates in Unix/Linux environments.

    3 votes
    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 →
  18. 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 →
  19. 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 →
  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.

    3 votes
    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