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.

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.

Support for container monitoring in SCOM.

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

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.

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.

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.

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

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)

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.

In addition to developing the PKI Certificate Monitoring MP directly and not having to rely on 3rd party, add the ability to monitor PKI Certificates in Unix/Linux environments.

We has been approached by our UNIX Team and they would like to know how soon we can on-boarding REHL8 Server for monitoring through SCOM 2016 UR5. we have invested time to find out relevant information over the internet, but could not find anything and that is the reason why we have raise case with Microsoft REG:119051521002564 for same.

Currently default directory for agent installation on Unix/Linux servers using Operations Console is /tmp/scx-username. However, if /tmp directory is hardened due to security reasons for unix/linux servers on customer environment, they will have to manually install scom agent on unix/linux servers and does not have an alternative to install the agent from Operations console on other directory.

The ability for SCOM Operations Manager to monitor when a Linux file system goes into read only mode

When you create a Linux Monitor the default data type is String, then when your script receive a Integer data (for example) the linux monitor doesn't work properly

need to update help documents for new version of unix/linux management packs. we never come to know what are fixes released or newly introduced with latest version of MP's