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. Support for 2012 Agents for SCOM 2019

    We need support in SCOM 2019 for agents that are running Server 2012. And, really, for 2008R2 agents. I understand that 2008 is EOL in January, but it is now March (we also have plenty of 2008 in production) At this point we cannot upgrade to SCOM 2019 without at least 2012 support, and preferably 2008R2.

    113 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. Create a Technical Community Blog for SCOM

    There are a whole ton of great SCOM blogs out there. There are also a whole great number of blogs for other products like config manager on techblogs but nothing for SCOM. Could we start a blog? https://techcommunity.microsoft.com/t5/custom/page/page-id/Blogs

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. SLES 15 agent for SCOM 2016

    Monitoring of SLES 15 systems is currently not possible with SCOM 2016. Please provide an agent and management pack to monitor SLES 15 systems with SCOM 2016 at the same level as SLES 11 and 12.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  4. Later versions of Visual Studio 2017 crashes with VSAE installed

    This was semi-dormant as a ticket on Developer Community for two months before it was very recently closed: https://developercommunity.visualstudio.com/content/problem/318019/visual-studio-crashes-using-scom-vsae.html

    It is basically impossible to with with MP projects in VS 15.8.3 and later.

    I need to be able to use the later versions of Visual Studio 2017 AND VSAE together, and I cannot really have a bunch of versions installed side-by-side. (Already running VS2015 besides VS2017).

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Authoring  ·  Flag idea as inappropriate…  ·  Admin →
  5. Fix maintenance Schedule replication on HA SQL for SCOM

    With SCOM Always On sql architecture. Whenever a maintenance schedule is created it is not replicated to secondary DB. This requires manual effort with DB permissions to replicate the SQL agent job. The schedule is not effective until its replicated which eliminates the self service feature for end users. Not every one has DB permissions.

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
  6. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Other Management Packs  ·  Flag idea as inappropriate…  ·  Admin →
  7. Bug in Windows Server Active Directory Federation Services (ADFS) 2016 Management Pack

    The ADFS 2016 MP is alerting "The AD FS configuration database that is stored in SQL Server 'false' is unavailable." Alert is false positive when using non-default sql port (servername,portnumber). Hence when trying to ping the "servername" string returns a bad syntax. A fix in the script used by the MP to delimit the "servername" and ping the name before the comma ","

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. DFS Replication Management Pack

    Many Enterprise organisations are still reliant on File Services such as DFS-R and need to effectively monitor it. With no new release of the DFS Replication Management pack to support Windows Server 2016 and 2019, Organisations are failing to monitor key parts of their infrastructure, with failures affecting hundreds of users.

    Please provide further support for DFS-R Monitoring

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other Management Packs  ·  Flag idea as inappropriate…  ·  Admin →
  9. Alert history is not updated correctly from within widgets

    The alert history is not updated when the resolution state of an alert is modified from within an alert widget.
    In our case we have a dashboard with two alert views. Our ops guys use the context menu to set specific resolution states on the various alerts. That kind of action is not recorded in the history information of the alerts. However, it gets recorded when doing the exactly same steps from the default alerts view. Or by opening the alert and changing the status in there directly.

    We had opened a premier ticket and were told that this is…

    37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. Windows Server 2016 Core OS MP TimeOffSet script fails depending on regional settings

    Windows Server 2016 Core OS MP's Microsoft.Windows.Server.TimeOffset.Monitortype.ps1 gives an error message from all our servers with Finnish time format.

    The error message is:
    "System.Management.Automation.MethodInvocationException: Exception calling "ToDecimal" with "1" argument(s): "Input string was not in a correct format."At line:747 char:1
    + [Decimal]$toffset = [convert]::ToDecimal($Time_Offset)
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
    at Microsoft.EnterpriseManagement.Common.PowerShell.RunspaceController.RunScript[T](String scriptName, String scriptBody, Dictionary`2 parameters, Object[] constructorArgs, IScriptDebug iScriptDebug, Boolean bSerializeOutput)"

    Finnish is using the following date/time formats:

    Short date: d.M.yyyy
    Short time: H.mm
    Long time: H.mm.ss

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Windows Server OS Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  11. Remove Dependency on SQL Server Agent for SCOM 2016 Maint Mode

    Currently, the Maintenance Mode scheduler makes use of SQL Server Agent jobs to schedule the maintenance windows. This creates issues in highly available environments and an unnecessary dependency. Scheduled maintenance should be handled by a rule like other tasks.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
  12. Pull the latest release of the Management Pack for Windows Server Operating System 2016 and 1709 Plus

    The recent release of this management pack has over-sensitive monitors which have turned an entire test environment critical. See my post on Technet here for further details.
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/e7265916-7da2-4412-97c1-27c150a573ec/caution-new-windows-server-management-packs-and-alert-storms?forum=operationsmanagergeneral#e7265916-7da2-4412-97c1-27c150a573ec

    Also the download link for the Management pack guide is broken, so we have no way to ascertain the changes in this reease!

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Windows Server OS Management Pack  ·  Flag idea as inappropriate…  ·  Admin →
  13. Fix "Management Pack Recommendations" MP 7.3.13165.0

    I have just updated to this latest version of the 'Management Pack Recommendations MP' via the Updates and Recommendations feature in SCOM2016. I now have a couple of hundred powershell failed to run warnings from a large number of servers for 'Lightweight non server roles discovery' filling my alerts pane. Previously zero script errors.

    So far been unsuccessful in resolving this issue.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  4 comments  ·  Other Management Packs  ·  Flag idea as inappropriate…  ·  Admin →
  14. Correct the fact that all UNIX/Linux-based monitor health states are reset when a Management Server (or Gateway) is rebooted.

    When a Management Server (or Gateway) is rebooted, all UNIX/Linux-based monitor health states are reset, resulting in the subsequent re-generation of a slew of alerts for all related x-plat agents

    118 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  15. WebConsole missing form authentication Integrated with AD

    ) In SCOM2012 R2, it was possible to login to the SCOM web console with a different user via a form based authenticated through AD.
    If a user would try to connect with a non permitted user to the console, a form would load up within the webconsole and would ask for Username/Password. It would then be possible to use another account with the rights permissions to access the console.
    This feature is now gone in SCOM2016 and doesn't seem to be any work around in the current context.
    In a company where users have 2 different account (1 for…

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  16. we are running out of votes because ideas are not getting closed...

    @MSFT, could you please provide active feedback and close those ideas which are solved and/or will not be solved so we get back our votes?

    YOU are asking for our feedback and so we expect that you provide feedback to us as well. We spend our time, so please do you.

    Thank you

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. SCOM 2016 support SQL Server 2016SP1

    Currently SCOM 2016 does NOT support SP1. SP1 touts consistent programmability across SQL Server editions. This should also benefit the development team to streamline customizations.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Keep NOAPM=1 as default setting for all MMA versions

    The APM component (regardless of APM being enabled) frequently breaks .NET applications. Re-installing agent with NOAPM=1 means we cannot leverage the SCOM console to deploy agents. Request

    155 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Setup and Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    This ask has been shipped with SCOM 1807, which enables you to disable the APM component when you deploy the Operations Manager agent from Discovery Wizard in the console, when performing a repair of the agent from the Operations console, and similarly controlling behavior when using the PowerShell cmdlets Install-SCOMAgent and Repair-SCOMAgent.

    This feature ask will also be shipped in SCOM 2019.

    Issues related to APM, crashing the IIS application pools has been fixed and shipped with SCOM 2016 UR6: https://support.microsoft.com/en-us/help/4459897/update-rollup-6-for-system-center-2016-operations-manager#enable

    Fix to these issues, will also be available in SCOM 2019.

  19. Linux OpenSSL out of Supported range

    I am trying to install SCOM agent 1.5.1-256.universal.1.x64.deb for an Ubuntu Server and when the wizard is completing the installation I received the message below .

    Unsupported OpenSSL version - must be either 0.9.8* or 1.0.*.

    I am using the version OpenSSL 1.1.0 out of supported range.

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  3 comments  ·  Unix/Linux Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  20. DNS Management Pack 10.0.6.0 bug in DS for monitor "Microsoft Windows Server DNS Zone NSLookup"

    A script bug has been introduced with MP version 10.0.6.0, causing the monitor "Microsoft Windows Server DNS Zone NSLookup" to fail.

    DataSource: Microsoft.Windows.Server.DNS.NSLookup.DS
    Error: The system cannot find the file specified
    Cause: Line 103 - chcp 437 && nslookup.exe...

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  8 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base