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.

SCOM powershell module cant work with -Split [Environment]::NewLine

Bug found here:

https://social.technet.microsoft.com/Forums/systemcenter/en-US/b4524a65-c784-445e-8dea-99e217e35e1b/powershell-discovery-ignores-loop-but-works-in-vsae-mp-simulator?forum=operationsmanagerauthoring

The new REST API should expose the ability to use Maintenance Mode. This would make it easier to use Maintenance Mode programmatically

Agentless objects under “Administration\Device Management\Agentless Managed” representing virtual cluster servers should ideally be situated under the node that currently hosts them.

As it stands, the objects reside under the cluster node that they were first discovered on. This is highly confusing for the user.

currently within the HTML5 dashboards you cannot selecta large group and display Top N , this can be selected per user but does not save across different users.

Also when sorting columns with numerical values these need to be sorted numerically rather than as a string like being done at present

I understand that this is one of Microsoft's first passes with HTML 5, but really? Why isn't there a 'home' link when you use the alert link to first access the SCOM web console. One has to delete everything beyond /operationsmanager to get back to the other views. Also, why can we only select 1 object at a time (i.e. Windows computers, for maintenance mode and bulk alert management?

Any plans for improvement? Is there a subscription that's available to tell me when new updates are available?

Have a OM shell commandlet that deletes a SCOM agent (like right-click Delete in Management, Agent Managed Computers), something like this: Get-SCOMAgent –DNSHostName "server01.contoso.com" | Remove-SCOMAgent