Assessment Scan Schedule Time
I prefer choose when execute the Assessment scan because yesterday I installed new patches on my servers but in Advisor the state is not already updated.
On SCOM could be good have a global settings and also machine setting (like heartbeat).
For the new ‘vertical’ workload assessment Intelligence Packs (see idea here http://feedback.azure.com/forums/267889-azure-operations-insights/suggestions/6519186-sql-server-intelligence-pack and here http://feedback.azure.com/forums/267889-azure-operations-insights/suggestions/6519201-configuration-assessment-alerts-and-recommendation ) and the SQL Assessment that was just released http://blogs.technet.com/b/momteam/archive/2014/10/23/new-sql-server-assessment-intelligence-pack-in-advisor.aspx we have overridable scan frequency that you can control in OpsMgr with an override, now.
Anyhow, the default setting is only ONCE A WEEK – i.e. most people just need a a WEEKLY or MONTHLY scan: every week you review how much improvement you got since the previous week, and what is next in the to-do list, in order or importance (=how much actual improvement do I get if I do this?) so you can justify the effort required to fix things to upper management, in the terms they speak (‘if we do this we get a 25% improvement in our security posture’; if we change this setting it gets us a .25% extra availability, stuff like that).
As you can see from these examples, we are no longer thinking in terms of the current ‘Alerts’ that are mixed with the ‘reactive’ alerts in SCOM (and you rightfully want to go away from the console – consider disabling alert sync for that http://blogs.technet.com/b/momteam/archive/2014/07/24/how-to-stop-the-receiving-of-advisor-alerts-in-operations-manager.aspx ); that does not have to be the way results of the assessment are presented! It’s only the old implementation.