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. Network Vicinity View - manually edit Topology

    There needs to be an option to manually edit the network topology created by the network discovery. At the moment the process is not transparent why some associations between network components are not visible in the vicinity view.

    17 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 →
  2. Receive any version of a SNMP-trap by default.

    Make SCOM by default receive any version of SNMP trap regardless of discovered device version, to relieve us from the pain of manually removing the <Version>-tag from each

    and every custom rule, AND/OR make it possible to discover a device as ONLY version v1 (even if it responds to v2).

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  3. Parsing SNMP traps

    Some good network devices has the feature of parsing the SNMP traps. SCOM is still missing it. Undiscovered devices (which are not generis or certified) need this parsing so that received SNMP data can be processed and presented the way we wanted.

    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  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  4. Discover Windows server as Network devices

    A way to discover windows server as Network devices for setting up snmp configuration in scom 2012 without editing .asl file. This requirement is required for windows server hardware monitoring where for some of the hardware vendor will not provide the respective hardware mp's

    4 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 →
  5. Build Network Vicinity View based on all devices

    Currently the Network Vicinity View is build inside the discovery rule, this leads to a scoped network vicinity because links between nodes in difference discovery rules aren't known.

    To administer the network monitoring enviroment the discovery rules are split over several management servers. It would be nice if this doesn't impact the vicinity view.

    An idea would be too build the vicinity view in a seperate discovery with the objects managed by a resource pool as boundry.

    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  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  6. Network Vicinity View - Include VLANs interconnecting devices in the View as an object

    Add the VLAN object in the Network Vicinity View to help understand how the servers are connected and also the networking layer 2 topology. The VLAN object is already stored in SCOM DB.

    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  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base