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. SCOM 2019 Web Console, App Advisor & App Diagnostic URL does not support Edge or Chrome Browser.

    We have customers who would like to use the SCOM 2019 Web Console, specifically the App Advisor & App Diagnostic URL on other web browsers such as "Chrome" and "Edge". Currently with SCOM 2019 the App Advisor & App Diagnostic URL only works with Internet Explorer. It would be good to see the SCOM product group add support to other web browsers as well in future update rollup's.

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Application Performance Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  2. [PG Feedback] SCOM Management Pack needing Version update and Feature updates

    All - This poll is from SCOM Product Group. As a SCOM user, you would be using a lot of MPs and some of them could be outdated in terms version, monitors, rules and features. We are looking to revive Management Pack as a whole and we want to hear your feedback on the below topics.

    1. What are top 5 MPs (in terms of usage) used at your SCOM infra?
    2. Which top 5 MPs critically need version update (agnostic)?
    3. What are the top 3 issues that arise on MPs (in general)?
    4. What are top 3 workloads for which MPs are…
    44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  16 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow SCOM 2019 to uncheck "Install APM" by default in the deployment wizard

    It's a big PITA to remember to uncheck the APM box when deploying agents. It's often forgotten by some and we have to go back and strip APM from the target agent. I want to be able to change the default behavior!

    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  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add a column that shows Alert type "Rule" or "Monitor"

    Add a column that shows Alert type "Rule" or "Monitor". Also add a filter in there for alert type to display Rule or Monitor or both

    29 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  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
  5. 64bit version of VSAE missing

    Now that VSAE is available for recent versions of Visual Studio we are missing a 64bit version of the extensions. MP Simulator (32bit) won't work when run on a 64bit OS with a 64bit SCOM agent installed.

    In the past Microsoft had made available versions for both architectures.

    54 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Authoring  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to Monitor Hyper-V 2019 with SCOM 2019

    Client got new Hyper-V 2019 & we need to do Host level, Cluster level and storage level monitoring in SCOM. Searched the internet and also raised case with MS, got to know the MP is still not released. Request MS to build\release the MP ASAP.

    38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Other Management Packs  ·  Flag idea as inappropriate…  ·  Admin →
  7. Remove voting limitations

    Why should we not being able to vote for all ideas/feedback if we'd like to support them?
    With the current limitation (and the fact that I near to never received votes back) the platform is not useful to me and I don't feel participation makes sense.

    Here is the feedback from UserVoice itself:
    "Hi Patrick - voting limitations is a feature imposed by the site administrator. If you wish for them to disable this feature, I recommend creating an idea on their web portal requesting them to remove this functionality."

    Please disable it.

    Thank you,
    Patrick

    2 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 →
  8. Red Hat Enterprise Linux 8 support (RHEL 8)

    Any idea when is RHEL 8 going to be supported? My customers are already deploying servers in RHEL8 and we cannot provide monitoring for them.

    135 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  9 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  10. VSAE Support for Visual Studio 2019 and System Center 2019

    VSAE should support Visual Studio 2019 and System Center 2019

    108 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  12 comments  ·  Authoring  ·  Flag idea as inappropriate…  ·  Admin →
  11. Fix SSRS 2017 Integration

    When rolling out SSRS 2017, once you add the SCOM Report Server role to it, the Reports page only gives a 500 error. Reports work in the console, but can no longer get to the web interface.

    110 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  14 comments  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support for 2012 Agents for SCOM 2019

    We need support in SCOM 2019 for agents that are running Server 2012. And, really, for 2008R2 agents. I understand that 2008 is EOL in January, but it is now March (we also have plenty of 2008 in production) At this point we cannot upgrade to SCOM 2019 without at least 2012 support, and preferably 2008R2.

    113 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SQL Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  14. Bug in Microsoft System Center Management Pack for AD CS 2016 Management Pack

    There is a bug in this Management Pack which causes it to fail when TLS 1.2 is enforced. The error is:

    Topology10.0Discovery.vbs : Unable to connect to the database with the specified configuration string. Please make sure that your connection string is valid and that your credentials are authorized to access the database. Cause: [DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error.

    The bug in the discovery is in Topology10.0Discovery.vbs in this line of code:

    GetOpsMgrDBConnectionString = "Provider=SQLOLEDB;Data Source=" & sDBServerName & ";Initial Catalog=" & sDBName & ";Integrated Security=SSPI;"

    Provider=SQLOLEDB fails when TLS 1.2 is enforced. Per this article, it should be updated:

    https://blogs.technet.microsoft.com/kevinjustin/2017/11/08/sql-native-client-for-tls1-2/

    18 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  ·  Other Management Packs  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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/

    54 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  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Node properties should reflect currently effective data

    Current design for node location property is to show the last known value. For example a device is added and has a location this location is shown. If the location field is made empty the property in SCOM is not updated. This behavior is a deviation from the normal behavior for object properties as they do reflect the current effecitve data. Please remove this deviation and always show the current effective value, if we want to know a historical value we do have a data warehouse and reporting capabilities.

    32 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  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    We're glad you're here

    Please sign in to leave feedback

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

    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 →
  19. Fix maintenance Schedule replication on HA SQL for SCOM

    With SCOM Always On sql architecture. Whenever a maintenance schedule is created it is not replicated to secondary DB. This requires manual effort with DB permissions to replicate the SQL agent job. The schedule is not effective until its replicated which eliminates the self service feature for end users. Not every one has DB permissions.

    50 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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...

    75 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  ·  Windows Server OS Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

Feedback and Knowledge Base