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. how to get a scsm service request to close a scom alert

    I am able to get SCOM to create SCSM incidents fine. I am able to convert the incidents to service requests fine. I need to figure how to work the service request and complete it then have that close the scom alert. Anyone have any ideas on how to do that?

    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. Notify on duplicate snmp engine id

    Monitoring ~500 network devices and have sometimes an issue with a device being greyed out while SNMP seems to be working fine. Underlying cause is mostly a duplicate snmp engine id which causes the SNMPv3 communication to break with an usmStatsNotInTime report from the device.

    The fix is mostly easy but finding the cause is hard as the SNMP module does not give any clues on what's wrong and everyting we test seems to work (SNMP GET from console, probing outside of SCOM, etc.).

    It would be very helpfull if the SNMP module would give something like a warning event…

    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 →
  3. Integration with Meraki Network Devices

    Currently, only devices supporting all of the properties in the system MIB-II are able to be discovered in SCOM using SNMP (as far as I understand).

    Cisco/Meraki do not support some of these properties which results in a failure to discover the device with SNMP.

    Whilst this is a lack of support from Meraki, I assume to persuade customers to use their Meraki dashboard, this IS possible to add such devices in SolarWinds, even though information is restricted. It still allows the device to be discovered.

    Meraki devices can be managed and monitored via API, therefore SCOM needs to be…

    3 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. 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 →
  5. Enable SCOM to monitor network devices(Access Points) using hostname as well.

    During discovery using hostname , SCOM works. But since the network device is using DHCP ( in most cases ,the APs) , it will keep changing if it is been rebooted. Once the AP got new IPs, SCOM will no longer monitor it as SCOM is monitoring it via IP .Even if the discovery is made recurring , SCOM will create a new record with different IP but same hostname. Thus the AP is "greyed" out. The only way now is to delete the existing record and manually rediscover.

    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 →
  6. Suppress Network Alert Storms/ Multiple Server Down Alerts /Notifications when a core network switch/router fails

    Currently if one switches goes down, we'll get 100's of notifications, which we don't want. This causes a nightmare for our Service Desk Teams to triage and close which takes hours on our ticketing system. We'd like Alert/notifications emailed that the switch is down, but we don't want a server down notification emailed for each of the servers attached to the switch. And following the same logic, we don't want notifications emailed that multiple switches & servers are down if the core switch goes down itself.

    So implement some logic or ability for customers to suppress alert storms when a…

    6 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 →
  7. 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

    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 →
  8. 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

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

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

    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 →
  11. 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 ...

    8 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 →
  12. Support for SNMP v3 Traps

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

    50 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  ·  Network Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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).


    • added support for…

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

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

    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 →
  16. 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

    26 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 →
  17. 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 →
  18. 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.

    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 →
  19. 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 →
  20. 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 →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base