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.

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add powershell command for adding SNMP devices

    After discovering SNMP devices by PS Script it would be nice to add them to SCOM also by script. Within OM2007 it was possible ...

    7 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support for SNMP v3 Traps

    Simple, says it on the tin, most network devices support SNMP v3 these days, it's more secure.

    40 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  4. improve network monitoring

    Monitoring network has several issues that need to be addressed.

    - very unclear how it works (the discovery is 1 big black box. it's not "open" like system monitoring) and what it captures is not understandable for network admins (e.g. a switch has mem-1, mem-5 and mem-6 found by scom, but this is not understood by a network admin who only sees memory and not this division).

    - key property is mac address which keeps popping up in several views instead of a understandable name (the default performance views don't even have the option to show the mibII name/dnsname).

    -…

    34 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  5. Better Network Monitoring including Netflow

    Currently Network Monitoring is pretty basic and if you want something decent you have to pay for a third party solution

    25 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  6. Netflow / jflow / sflow integration

    Operators and users of SCOM are asking for integration of information about the packet flow within the network. Think about information coming from netflow, jflow or sflow implementations on the network devices.

    16 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  7. provide network device root cause analysis

    Ability to discover all network devices relationship to avoid many alerts when a switch core is unavailable. There is a monitoring like this in the Exchange management pack

    11 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  8. Network Vicinity View / Port Stitching Documentation

    At the moment the whole feature network vicinity view topology creation and port stitching is not documented. We need a transparent technical documentation of the feature.
    Even your own technical support does now know how to troubleshoot this feature in scom.

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  9. Possibility to add custom OID fields to the displayname of Network Device discovery

    While discovering Network device items (such as custom classes) the discovery created by the Network Monitoring MP Generator does not allow to use a different property of the discovered object to use as displayname. Now it will use the Index as the name (object-1, object-2, object-3). While in SNMP we see the objects have several fields we can use, some of which have information such as location or description or otherwise included. We would like to use that in the name or description of the device-objects discovered.

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  10. Network Monitoring Cisco switch WS-C2960-24PC-L (approved) is being discoverd as network adapter (Common)

    Network Monitoring Cisco switch WS-C2960-24PC-L (approved) is being discovered as network adapter (Common) This does not offer needed performance metrics. It should be discovered as network Adapter (netcor base)

    9 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  11. Make Network dashboards available to non-administrators

    Hi, today I found out that for example the "Network Vicinity Dashboard" or the "Network Node Dashboard" is only available to SCOM Admins!
    Certainly these views need to be available to at least the operatiors role.
    Regards
    Peter

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  17. Out of the box monitoring for power supplies and fans for network devices

    Most of the devices do not have out of the box monitoring for fans and power supplies. I believe that this is a required feature for SCOM to be beneficial.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  18. End Node Network Monitoring including Port Visibility without SCOM Agent similar to NNMi

    We have a lot of systems that do not have the SCOM agent installed. We currently use HP NNMi for Network Monitoring and would like to move this to SCOM. However, NNMi uses SNMP to discover the network equipment and end nodes. It then provides visibility of the entire network including the port on a switch that a node is attached to. It does this without any agent on the end nodes. I need similar functionality in SCOM. I understand it will do it with an agent installed via port stitching, but I need similar visibility to the end nodes…

    2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base