VSAE should support Visual Studio 2019 and System Center 2019

HI, Brian Wren had mentioned that Microsoft would always have a Management Pack for every Microsoft product. Currently Microsoft does NOT have an MP to monitor ADFS

Release and maintain a 2019 version of the "System Center Operations Manager 2007 R2 Authoring Resource Kit".

This tool is an absolute gem in training new people to SCOM, which also gives them a better understanding on how everything is pieced together and useful for design work...

SCOM cannot monitor or collect data for 32-bit performance counters on 64-bit operating systems. A workaround is to use a PowerShell script which calls 32-bit PowerShell and makes use of the Get-Counter command, but this causes significant load on the system processor when collecting data for multiple counters. I feel that there should be native support for this scenario that avoids this need to launch 32-bit PowerShell separately.

Currently it requires SCOM admin access to run Authoring console templates like Web Transaction Monitoring. In large enterprise environment, dev team should be able to create and modify web transaction monitors in the SCOM authoring space themselves without needing SCOM admin.

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.

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

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.

Ability to monitor websites that ask for client certificate

There is no consistency regarding the scripting language used in MP's. Some use VBS, Jscript and a few use powershell. It would be nice if at least all the core MP's "Windows OS"; SQL, AD are changed to PowerShell.