Hello! I think it would be great if you created VSCode extension that adds to authoring of Management Packs - features like intellisense, class definitons and so on. I guess VSCode would be a nice tool to edit XML files, if it had proper definitions.

Thanks!

Please add the ability to define 'business hours' or schedules when authoring SLO objects. This would allow SLO tracking of objects only at given times or schedules to match business needs.

Provide Operations Console authoring functionality as a HTML portal in Web Console.

For better alert Distribution it would be great to be able to create dynamic Groups that contain all objects based on a given criteria. I create a Group, provide a servername as criteria for example and all objects that have a relation to the Server become members of the Group (SQL DBs, IIS Websites, Hyper-V Host, HDDs, etc.). Right now it his very hard to accomplish this task. This feature would be awesome.

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.

Currently we could create web tests in Visual Studio and run them from agents in GSM, but it works only for public facing web sites. That would be awesome for internal use as well.

Microsoft would offer a new great feature to SCOM and would have the opportunity to sell more VS Ultimate Editions ;-)

Thanks,
Patrick

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

We need an option to associate components to each other to prevent an alert storm created by a failure of a central component.
For example if a central router on a remote location fails we get alerts from each component monitored at the location even though its still available locally.

The 2007 MP Authoring Console for SCOM 2008 R2 was a very easy to use GUI driven tool. I know I can use MP Author, Visual Studio, etc...but this tool was SO much more intuitive and easier for MP authoring and editing. We need a 2012/2016 version to work with the new MP schema of 2012 MPs.

Powershell agent only executes Powershell 2.0 commands and does not have support for any other Powershell versions/commands. Add a support to create Powershell script monitor that supports commands from PS 3,4,5.

It is hard to put a machine with dependicies in maintenance mode.
For example in cluster you have to put the machine in maintenance mode, the cluster, some services on the other machines in the cluster.
If that could be simplifyed it would be good.
Like: maintenance mode for machine and dependencies.

This was semi-dormant as a ticket on Developer Community for two months before it was very recently closed: https://developercommunity.visualstudio.com/content/problem/318019/visual-studio-crashes-using-scom-vsae.html

It is basically impossible to with with MP projects in VS 15.8.3 and later.

I need to be able to use the later versions of Visual Studio 2017 AND VSAE together, and I cannot really have a bunch of versions installed side-by-side. (Already running VS2015 besides VS2017).

That would make script rules and monitor creation so much easier and less error prone.

Thank you :-)

It would be great to be able to configure the default value of a reference Alias in VSAE. The function within the Authoring Extensions always chooses the first letter of each node in the XML Name.I'd like to change it to use my default..
For example, If I add Unix.Authoring.Library, the default value of the alias will be UAL, in each new project....

I have had multiple customers ask if we can dynamically compile product knowledge.

By this I mean an alert is raised within Operations Manager, the knowledge associated with the alert could be tailored for a specific Rule or Monitor AND Discovered Instance.

This would then allow such knowledge as internal escalation procedures to be concise and contextual.

A suggested example of this could be applying some sort of condition detection using the Full Path Name as a string and if it matches, display certain text for that specific instance.

visual studio tools such as mp simulator are not usable now. Improving these developing tools and the extension itself, will make authoring new management packs a more easier job.

If you open a VSAE project on a new machine, the version number for the MP (if using Auto-increment) will reset to the default 1.0.0.1. However this Mp could be on version 1.0.41 and won't install unless you rebuild the soltion 40+ times or turn off Auto-Increment.

It would be nice if we could set the value in the deployment tab of the MP properties and VSAE increment from that number on the next build

Brian Wrens documents and MVA course are excellent, however they could be complimented by some examples (i.e. how to create a relationship based on a reg key etc). Information of this type currently needs to be gleamed from forums, Community MPs and at times just hours of experimentation. Which takes a long time and is extremely frustrating. Surely there is enough content in the standard Microsoft MPs to be able to quickly create a library of examples. I