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. Allow Powershell script in Agent task

    Currently only vbs is supported, when creating Agent based task. For now, PS is mostly installed on all recent OS please implement support for adding Powershell scripts here.
    You can mark it somehow- to distinguish VBS/PS based tasks, so users are not running ( or know and accepts) it on systems which do not support PS.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Authoring  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add PowerShell cmdlets to create views, rules and monitors in SCOM

    Today, there is a measley three PowerShell cmdlets for making new items in SCOM. The only thing we can do with PowerShell is make a New ScomLocation (pretty useful, I will admit), and make a new Management Group connection, or a new resource pool.

    That's it. There is very little useful scripting support for SCOM. If you take a look at ConfigMgr, there are more than 100 cmdlets for making new items! This needs to change.

    My vote is to first create cmdlets to support making new rules, then new monitors, and finally new views.

    The syntax should be something…

    78 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Authoring  ·  Flag idea as inappropriate…  ·  Admin →
  3. A GUI based approach to create PowerShell rules and monitors

    Within the GUI there is no easy way to create PowerShell script monitors and rules. Please add a GUI driven wizard to create those.

    334 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  10 comments  ·  Authoring  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base