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.

Just installed an SCOM2019 environment. UPNs still do not work in the web console login ...

Enable delivery address field for commands, so it will be possible to send alerts to subscribers through Powershell scripts

command : "myScript.ps1" '$Data/Recipients/To/Address/Address$' ...

Would like it so the Alert window is resizable as when I use Edge or Chrome I can't resize the alert window.

would like a powershell script to export all the detail of a subscriptions monitoring criteria which includes all the names and descriptions; not just a GUID.

when we setup a channel we don't have the ability to log its output for troubleshooting

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

When creating a new subscription, it would be nice not to rely on custom scripts but have custom HTTP API webhook to send the alert to. Webhooks seem to be a standard way in 2019, and would give a nice refreshment to next iteration of SCOM.

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

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

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

Change permissions on Dashboards and Views takes forever to save, currently +/- 40 min. This seems to be related to the number of classes, relations and views in the database.

This must be changed. It's not a workable situation that it would take 40 minutes to change just 1 view permission in 1 role.

With SCOM Always On sql architecture. Whenever a maintenance schedule is created it is not replicated to secondary DB. This requires manual effort with DB permissions to replicate the SQL agent job. The schedule is not effective until its replicated which eliminates the self service feature for end users. Not every one has DB permissions.

I wish there was more of a user friendly way of creating queries for SCOM group, I been working on a group of non prod SQL server DB engine from 2005 -02017. using regular expression it is so messy. wish there was a better way to build the query.

Multi-homed Gateways would allow to...
a) reduce the number of servers if you have a small number of agents within the same DMZ reporting to 2 separate Management Groups.
b) allow failover of agents from a production to a DR management group.
c) accommodate agent failover for Red Forest security scenarios.

Prior to SCOM 2012, AD Integration workflows could be run on a Management Server or on gateway in a remote domain. Beginning in 2012, the AD Publishing Pool owner performed any publishing, which removed the ability to publish SCOM containers in non trusted domains.

SCOM 2016 has a issue that becomes evident over enough time where unused space on Performance and Event Tables grows and eats up the space in the SCOM SQL Database to the point that SCOM can not perform its nightly maintenance and then a Group job across the 62 partitions needs ran to clear out this unused space. The maintenance to clear out this space should already be included to accommodate the issue where SQL 2016 changed its bulk insert.