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 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
This has been fixed with SCOM 2019.
Can we please have the ability to select more than one alert in the Web Console?
At present (v1801), you can only select one update at a time
This makes changing the likes of the Resolution State time consuming if there are a few of them..5 votes
2019 RTM has this functionality.
Allow Group Managed Service Accounts as Run As Accounts.
Managing Passwords of RunAs Accounts can be a pain, why not using Group Managed Service Accounts for Windows account type.7 votes
gMSA will be supported from 2019 UR1
A lot of customers close alerts generated by monitors. Although they got very good instructions, they don't reset the monitors. PowerShell and Greenmaschine, don't do a very good job in resetting monitors. there should be a way to automatically reset monitors when an alert is closed and/or an option to reset all monitors to a green state.582 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
This problem has been solved and will be shipped in SCOM 2019 (which will release in Q1 2019).
Details on the solution for this problem:
- An alert generated by monitor will not be allowed to close, if the corresponding monitor is still unhealthy. This will ensure that the health of the monitor and the corresponding alert are in sync.
- A new dashboard (“Alert Closure Failure”) has been created in Web console, which displays the list of active alerts which have been tried to close but could not close as the corresponding monitors where still unhealthy. This dashboard also allows you to forcefully close any such alerts by resetting the health of the corresponding monitor.
A monitor generated alert closure triggered from ticketing/incident management systems will receive an exception with the alert details, if the alert closure has failed because the corresponding monitor is still unhealthy.
Do any of you have a requirement to use gMSA accounts in your SCOM environment? If you do, please upvote this suggestion and kindly add the scenario you hope to use it for and how it would help you.304 votes
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 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
This has been fixed with SCOM 2019.
Maintenance Mode can only be startet via console.
We have a lot of server administrators and automatic scripts which initiate sometimes a reboot.
It would be great when a machine can be switched to Maintenance Mode by the agent, for example with a Powershell CMDlet.261 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
We have made several improvements in the schedule maintenance mode capability in SCOM 2016, may that be to do with surfacing this functionality for operators in the monitoring pane or the client side support. All of this is captured in the blog – https://blogs.technet.microsoft.com/momteam/2016/10/24/improvements-to-scheduling-of-maintenance-mode-client-side-via-agent-and-accessibility-to-operators-via-monitoring-pane/
The subscriptions are very limited in setting criterias. A more granular targeting and options would help deliver more accurate notifications. E.g. there is no way to exclude.235 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
We have done enhancements to Notifications and subscriptions area, these enhancements will be shipped with SCOM 2019 (which will be available in Q1 2019).
Enhancements made in Notifications and Subscriptions area:
- Powerful criteria builder: Administrators will be able to leverage the advanced/flexible criteria builder which enables you to perform “Exclusions”, “OR” operation, regular expressions and multi-level “AND”/“OR” grouping in criteria
- Rich HTML email: Administrators will be able to leverage the default HTML email template or create their own HTML email content. Operators will be able to directly launch the “Alerts details page”, “Alert Source details page” or the “Rule/Monitor details page” directly from the email to get access to more relevant information.
Add a possibility to check for Management Pack updates from console, and possibility to update them.3 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
MP updates and recommendations capability shipped with SCOM 2016 solves this.
Provide access to enable scoped users leverage the functions offered in the Maintenance Schedule wizard, without imposing the requirement that the user must als0 be delegated access to the administration workspace17 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
From SCOM 2016 RTM, Scheduled Maintenance Mode is available in Monitoring pane.
14 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
With SCOM 1801 we have shipped HTML5 dashboards removing Silverlight dependency and allowing access of Web Console from multiple browsers. With this release Web Console is completely HTML based.
More information on System Center 1801 release is available here: https://azure.microsoft.com/en-us/blog/first-system-center-semi-annual-channel-release-now-available/
Documentation for HTML5 is available here: https://docs.microsoft.com/en-us/system-center/scom/manage-overview-html5-webconsole?view=sc-om-1801
Blog series on HTML5 dashboards:
The all new Dashboards: https://blogs.technet.microsoft.com/momteam/2018/02/12/new-scom-web-console-blog-series-post2-the-all-new-dashboards/
The new HTML5 Widgets: https://blogs.technet.microsoft.com/momteam/2018/02/12/new-scom-web-console-blog-series-post3-the-new-html5-widgets/
The all new Drilldown experience: https://blogs.technet.microsoft.com/momteam/2018/02/12/new-scom-web-console-blog-series-post4-the-all-new-drilldown-experience/
Sample Custom Dashboard walkthrough: https://blogs.technet.microsoft.com/momteam/2018/02/12/new-scom-web-console-blog-series-post5-sample-custom-dashboard-walkthrough/
Permit the enablement of automation and scripting scenarios, including ITIL processes, patching solutions, and many other business scenarios;
Please provide command-lets in the PowerShell module to support this new feature.4 votes
Hi Damian, Thanks for your feedback. This feature is already a part of SCOM 2016 Technical Preview 3. Do check it out and let us know if you have any feedback.
- Don't see your idea?