Implementation of dynamic application discovery like former BlueStripe software and building the corresponding distributed application with all it's dependencies.

The alert object does not always contain the source FQDN of the generating server. This property should be able to get by PowerShell. This would help building connectors using PowerShell / SMA etc.

• Groups: Add column for MP (where group is defined/stored)


• Groups: add column to view "total members"


• Group Explicit Members: Only the DisplayName of classes appear. There are many, many duplicate class names and it's nearly impossible to select the correct one. Add columns for MP and class Name.


• Subscriptions: add column to view "subscription giud"


• Performance View: when adding specific rules to a perf view only the DisplayName of the rules appear. Add columns for Name and MP.


• Management Pack/Alert Tuning: Add path information


• State Views: Add column for class Name and Monitoring Object ID

Better Multi Tenancy support. As an hoster with both datacenter and on-premise customers we need better support for customers integration and general setup in the console.

Make a bool setting on each Management Server object to check mark, that this MS cannot be accidentally put into Maintenenance Mode. This would avoid a lot of Problems for customers who put servers into Maintenance Mode.

The group functonality is not good. You should be able to use active directory groups to target MP:s/views and so on.

It would be handy to De-Activate a MP instead of deleting it. Or set a MP in maintenance.

PowerShell Cmdlet to populate "Explicit Membership" groups. Should accept pipeline input or as string. Option to specify class. Here is an Example: Get-SCOMGroup _Displayname *Windows|Get-SCOMClassInstance | Add-SCOMGroup -GroupName 'Custom Windows Computers'

Another Example $list = Get-Content 'C:\servers.txt'
$list |Add-scomgroup -ClassDisplayName 'Windows Computer'

On the current SCOM console, only the display name of the monitoring class is visible. Would be nice if the actual monitoring class name, and the monitoring object ID can be displayed in the console (i.e. in the state views). This would help MP developers and SCOM users looking up objects when writing MPs, dashboards and scripts.

Please add this paramater for autoSignOutInterval to new SCOM Web console so session time-out can be customized properly.

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

Provide the option for SCOM Administrators to allow roles such as Advanced Operators to view but not edit existing maintenance schedules. This functionality would be beneficial to some customers as it would allow users to prevent creating duplicate schedules or to verify the existence of an expected schedule before beginning work.

There is no easy way to figure out where the SCOM Group is located. A column in the GUI Authoring/Groups with the MP Name where the SCOM Group is stored.

I can change the SCOM operational database grooming settings from within the SCOM console. If I wanted to change SCOM Datawarehouse grooming settings, I have to download the dwdatarp utility from a blog post, get access to the DB and then set the groom settings. This is a request to add Datawarehouse groom settings to the Administration pane.

Agent -initiated maintenance mode https://docs.microsoft.com/en-us/system-center/scom/manage-maintenance-mode-overview?view=sc-om-2019#enable-from-target-system-1 is great, however as of now it still forces an answer in the console prompt - preventing the use from automated scripts that run on target systems. Adding a -Force parameter that skips the "are you sure?" check would be very welcome and trivial to implement, without us having to reverse and simulate the behaviour to reach the same effect.

I want better design possibilities when creating dashboards in the webconsole.

1. Want possibilities to change the size of tiles.




2. Want possibilities to create headlines that can be formated.




3. Want possibilities to group objects in the dashboard.

The current way for immediate agent removal is not supported via SCOM SDK, but involves some SQL tweaking, in order to cleanup the database in advance from remnants of the object. The reason is that all discovery workflows should pass (on their respective schedule) before all references to the objects are removed. More details here: https://kevinholman.com/2018/05/03/deleting-and-purging-data-from-the-scom-database/

Steps to reproduce:
Multi-select a group of objects/targets. Example: Agent (from Agents by Version state view)
Launch Task: "Flush Health Service State and Cache"
Symptom: Task initiation will fail for ALL targets if any one object is grey.

This is incredibly annoying when selecting large groups of objects as it is incredibly tedious to scroll through the sluggish Console to UNselect any grey items.

Add a column that shows Alert type "Rule" or "Monitor". Also add a filter in there for alert type to display Rule or Monitor or both