Red Hat 8 needs to be supported in SCOM 2016 ASAP. It is not acceptable to not provide an MP that covered RHAT 8.
If we moved to SCOM 2019 we'd loose the ability to monitor our existing RHAT 5 and 6 servers so would be in an even worse situation that we are now with 2016.

Ubuntu 20 was first released in April 2020 but is not yet supported in SCOM 2019. The number of servers migrating to Ubuntu 20 has increased a lot in the last months and we don't have it monitored by SCOM. You should provide it urgently

Situation: When the unix agent state is grey and agent is down.
Then when you start the agent you have to wait the 2 full cycles of the heartbeat (default 2 every 630 sec) before the agent becomes healthy in scom, even when the 1st heartbeat check is succesful.

Why wait 2 cycles for switching to the healhy state? Go to healthy after the 1st successful heartbeat check.

Example:
During upgrading agents I want to be able to filter that view for all redhad 7.x agents with an old agent version

After updating the IP addresses for my Linux computers, I noticed that the IP Address attribute for the computer object in SCOM did not get updated. Even after waiting many days, the address does not get updated. The only way to update the IP Address in SCOM is to remove the agent and re-install.

Support for TLS 1.2 (and likely 1.3) in Solaris 10 agent. Currently this doesn't work and the agent needs a recompile to resolve the issue.

The current Linux agent parser does not allow for special characters when reading the output.

For example, "df: ‘/tmp/tmp2’: No such file or directory" will cause the parser to crash with an "unprintable characters" error in /var/opt/microsoft/scx/log/scx.log. Note the "special" single quotes; this is what causes the error.

Because the parser stops, the SCOM server never gets anything back from the agent. Removing the special characters resolves the issue.

Linux server version is RHEL 7 and I have upgraded scom agent to 1.6.4-7 .
Space is getting filled up by Core.* files in /var/opt/omi/run path . I tried to re-install agent and reboot the machine.Still no luck.

SCOM version 2019 UR1

Support for container monitoring in SCOM.

We would like to know, if Product Group team can help\create a SCOM Management Pack for JVM Memory Utilization. Additional Information : This is not a application, it is a component level utilization in Linux server. our client(standard Insurance) is prime client of Microsoft and it would be great to have this Management Pack

We would like to know, if Product Group team can help\create a SCOM Management Pack for JVM Memory Utilization. Additional Information : This is not a application, it is a component level utilization in Linux server. our client(standard Insurance) is prime client of Microsoft and it would be great to have this Management Pack

really need support for 64bit versions of Solaris, the current version installs as 32-bit even on 64-bit

Can we have failed to connect to computer monitor(icmp ping) alert for linux devices as we have for windows devices op

There is no monitoring above the physical volume for linux. I do realize that LVM is software management above the physcial volume and is centric to Linux thus not a standard health across both OS (Linux and Windows) but this topic came up as LVM is a standard for linux that was question why SCOM doesn't have a MP for it, but other Linux Monitoring Platforms does (e.g. Zabbix)

This will help to provide such MP in the Linux stack to show Microsoft is keeping thier promise that Microsoft loves linux.

when ever UNIX/LINUX OS Subversions are updated, SCOM should reflect the subversion automatically on SCOM UI. for example currently we are monitoring SUSE 12.3, as part of upgrade team has upgraded to 12.4 this version never reflect on SCOM UI until we remove the server from SCOM, and re-discover.
this needs to be fixed.

Kerberos authentication for Linux was a step forward. But this option is not available for AIX agents. So AIX monitoring is left with basic auth which isn't very good, to say the least.

You need to provide some kind of modern athentication for all platforms supported.

I was reviewing the supported UNIX/Linux OSs at the following location:https://docs.microsoft.com/en-us/system-center/scom/plan-supported-crossplat-os?view=sc-om-2019 and took note that support for HP-UX has been removed. This is creating a problem for my current customer since they use HP-UX and will continue to use HP-UX. According to my customer HP-UX is still supported through 2025, so removing monitoring support in SCOM 2019 is going to be a problem. While I understand there may be workarounds for this issue, I am also concerned about maintaining the customer's environment in a supported configuration.

Please extend MSC Operations Manager version 2019 to support Red Hat Linux to version 6.x and SUSE Enterprise Linux versions 10.x and 11.x. One issue for SUSE Linux is the supported version of OpenSSL.

We have 1200 win agents and 250 unix agent in SCOM

So, nix agents produces more perf data than all windows agents

Reason: there are no optimization for performance counters at all

Yes, you can rewrite and add module , but its almost impossible due CMDB sync in big companies

It will be great to add overridable percentage perf. optimization

(Same situation in sql mp, dfs mp...everywhere)

is there a way to install a Scom agent on Linux Sles 11?
there is a problem with Openssl, max 0.9.8 under Sles 11 but the agent requests Openssl 1.0 minimum
is there another compatible agent (older?)?
thank you
Stéphane