When an operator creates a maintenance schedules schedule this is only visible to that person. As a result this can also only be changed by that person.
Only when an administrator creates a schedule this is visible to other administrators.

It would be good that when an operator creates a schedule this is visible by members of his user role or even better it adheres the scoping structure. This would allow colleagues of the same team to modify schedules.

It would be great to customize the console like "personalize view" in the "fat" client.
And it would be good if columns would not auto-size - or at least just optional.

Thank you,
Patrick

A small but important issue have haunted SCOM since its very beginning: You cannot edit Company knowledge without installing Office on the machine you are using to connect to the managementserver, which for larger companies most likely is a TerminalServer.

I have used SCOM for a decade now and it puzzles me that Microsoft still does not manage to either incorporate a rich text editor or at least let us edit the textfield directly without formatting in the operations console.

As a result, we sadly are not using this feature.

Heartbeat frequency and number of allowed missed heartbeats should be overridable parameters on the monitor so they can be managed using the override screen as well. This adds the benefit of knowing when they have been changed. Currently only the frequency can be changed, and that is per agent or by bulk via powershell and even that is not done through a normal override as other SCOM monitors. Number of allowed missed heartbeats is only a global change at the moment so you cannot change it at all. I would like the ability to do both.

If you, for instance, put several Windows Computers in maintenance via the scheduler and one of them was already put in maintenance manually, that one will get out of maintenance when the scheduler ends.
Same deal for hosted objects that were put in maintenance manually.

Also check here: https://social.technet.microsoft.com/Forums/systemcenter/en-US/e2af78b9-70b2-4282-b647-71f41dc0b476/scom-20162019-maintenance-schedules-stop-manually-configured-maintenance?forum=operationsmanagergeneral

Regularly update the managementpack page versions and dates

The site https://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx were you can find all managementpacks is showing old dates and versions.
For example currently the pack for DHCP 2016 and higher is showing version 1.0.11.0 while there is already a newever version. You now only see this when you click into that pack so it's not easy to see which new or updated packs are released recently.
And while you work on it make also the date column sortable so i can overview the newest packs on top.

I have several alerts per object in the Active Alerts, I am trying to right-click the object owning the alerts and open alert view per this object, and I get an empty window.
We are using several resolution states, and we have noticed using SQL Profiler that the default view that is opening when right-clicking an object only scopes for NEW alerts. It should be all alerts without the closed ones

https://microsoft.qualtrics.com/jfe/form/SV_9GhktKqx11ojgkR

Please fill in this short survey and help us identify the areas of improvement and requested features in Azure Management Pack in SCOM. Thanks!

We are unable to migrate to SCOM 2019, but had already migrated Service Manager and Orchestrator to 2019. Service Manager servers report OS health without issues; however, anything related to the Service Manager environment just shows as "Unknown" - since SCOM doesn't have the ability to monitor 2008 R2 servers, upgrade SCOM isn't necessarily an option for everyone.

We need support in SCOM 2019 for agents that are running Server 2008 R2. Almost a quarter of our servers are still 2008 R2, and this is a huge hang up for us in moving up. Since these are more legacy systems, most are also unable to be updated.

Can a single Windows\Linux machine can be monitored with SCOM 2012 R2 and SCOM 2019.(in multi-home scenario).We have device with SCOM 2012 R2 agent installed and next wants to implement Multi-home with another Management Server SCOM 2019.

I can only assume the SCOM team is responsible for the SCOM CI-connector as well.

We're seeing a lot of disks being marked as "pending delete" from SCOM, and having them being set to Active again with the SCCM connector. In this case, the SCCM connector is correct. This poses problems since we use the disk size reported from SCCM to produce sizing reports and forecasts.

Now that SCOM 2019 is available, but lacking the mandatory support for 2008/2012 Operating Systems.

Customers with these Operating Systems cannot upgrade to SCOM 2019.

And although they trusted Microsoft and upgrade to SAC, they will no longer get fixes or new features.

And worse of all,
They will not get further support beyond the 18 monthly period for SCOM 1807.

Dear developers,
it would be great to see IM SCOM integration with Microsoft Teams, so IM alerting can be done for those who have migrated from SfB to Teams.

At the moment the only option is to either have SFB server onpremise and send IM notifcations to Teams/SFB Online or to use Hooks in Teams which isn't perfect because it actually sends posts on Teams Channel rather than sending IMs to people on Teams.

Hopefully IM notifications support for Teams will come one day.

I've run into an issue where after coming out of maintenance an agent goes back and reads events from prior to the maintenance mode end time. This generates alerts from events that occurred while the machine was in maintenance. It appears this has been an issue since at least 2009, but still exists in the SCOM 2016 agent:

https://social.technet.microsoft.com/forums/systemcenter/en-US/8a115e60-ef00-4eb0-a84d-1a420182e70e/sql-management-pack-failing-on-old-sql-agent-jobs

Ever since SCOM 1801, the Active Alerts view in WebConsole does not refresh automatically in non-IE browsers (Edge, Chrome, Firefox, etc.). An updated 'MonitoringBundle.js' file was provided by Microsoft support which made it work in modern browsers. But even in SCOM 2019, this issue is not fixed and I had to use the workaround script file. Could this be implemented as default for all versions? Internet Explorer may be hardly used anymore in the IT community.