General Operations Manager Feedback

Do you have an idea or suggestion based on your experience with SCOM? We would love to hear it! Please take a few minutes to submit your idea in the one of the forums available on the right or vote up an idea submitted by another SCOM customer. All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building SCOM. We have already added some of the feedback we received through the TAP program and the recent SCOM survey.

This forum (General Feedback) is used for any broad feedback related to SCOM.
Be specific on your feedback. The more specific, the easier and quicker for us to review. Please be concise!!

If you have technical questions or need help with SCOM, please try visit our MSDN forums.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Red Hat 8 needs to be supported in SCOM 2016 ASAP!

    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.

    188 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  2. Linux Agent 1.6.3 (SCOM 1801) should not update sudoers and create users

    If you deploy the Linux omsagent using the "Discovery Wizard", the following modification on the system are done:
    - three (!) users are added (omi, nxautomation and omsagent)
    - some extensive sudoers permissions are given to them via /etc/sudoers.d/omsagent

    Many of our clients do not allow scripts to be run as root, where the executed has write permissions on the script. Exactly this is the case for most of the scripts.

    REQUESTS:
    1. More documentation why these modifications are required
    2. Can the fluenD, omsagent work without them
    3. creating users must be optional. Many centrally maintain users and sudoers…

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  3. Container Monitoring in SCOM

    Support for container monitoring in SCOM.

    68 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Neha Garg responded

    We want to understand the ask in details here. Please upvote this idea and share your ask in comments. We will contact you via email to understand the scenario better. Thanks.

  4. solaris

    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.

    59 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  5. Possibility of changing the data type when creating Linux monitors

    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

    48 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  6. Linux Agent initiated Maintenance Mode feature

    This feature is intended for triggering maintenanace mode from Linux agent system with superuser previliges.

    47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  7. Solaris 64bit agent support

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

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  8. implement ssh server on scom and support python scripts

    Due to the need for hybrid environments with opensource systems and the scom's apliances to stay competitive with, market chains should enable native support for secure ssh communication but without fully depending on the requested agent, thereby opening up numerous possibilities for direct execution of Hi, I have a ssh command. I have a ssh command. I have a ssh command that interprets bash commands via ssh but it does not have native support. It is mandatory to install an ssh service on the windows server, there is also a need to run python scripts, such as zabbix and splunk…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support wildcard in UNIX/Linux Log File Monitoring

    Make us be able to use wildcards in the log file path of the "UNIX/Linux Log File Monitoring"-template.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  10. Provide option for alternative installation directories on Operations Console for agent installation on unix/linux servers other than /tmp/

    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.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  11. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow special characters in Linux script outputs

    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.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  13. Monitor that a Unix Server is not reachable

    In the Windows Monitoring the Management Pack has two different monitors, which monitor "heartbeat failure" and "Computer not reachable".
    In the Unix/Linux monitor you only provide a heartbeat monitor that run automatically the Task for an ICMP ping. We also need the monitorinformation if the System is not reachable because this is an important information for the Unix/Linux admins.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow SCOM Unix Agent to Run as a non-root account with elevated privileges

    At current time, the Unix agent for SCOM 2012 R2, 2016 and 1801 requires that the agent software run with root user credentials. Any software that runs directly as the root user is a security risk.

    I'd like to see a future version of the SCOM Unix Agent that could run as a non-root user, with elevated privileges, so that the agent can properly monitor the Unix client while minimizing security risks.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  15. discover Linux mounted file systems

    Mounted disks are not discovered, you should have an option to do this

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  16. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  17. Invoke-SCXDiscovery cmdlet need to support referencing SCOM RunAs accounts

    Currently there is no way to leverage a built in RunAs account that is pre-configured in SCOM to use Invoke-SCXDiscovery cmdlet, while it is possible to reference that when pushing an agent via the console. Inability to rely on SCOM RunAs accounts requires keeping another copy of the credentials together with the script, which in turn adds some overhead with regards to keeping those creds secure and in consistence with the SCOM store.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  18. HP-UX Agent Support in SCOM 2019

    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.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  19. Fix Unix Log Monitoring during Maintenance Mode

    You have unix/linux log monitoring deployed on a server.
    You put the server on maintenance mode for x hours.

    <During Maintenance Mode>
    During x hours, there are lines that written to the log which would trigger the alert. But alert not triggered since it's in maintenance mode.
    </>
    <Maintenance Mode Over/>
    Log monitoring policy kicks-in. It scans the log file again using the counter BEFORE the maintenance mode. The lines that written during maintenance mode got scanned and triggered an alert. This should not happened.

    Current workaround:
    - Clean the counter file after maintenance mode over.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  20. REHL 8 Server Monitoring through SCOM 2016

    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.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base