Post by SilloSybenI am having a similar issue. I created overrides to enable job discovery.
The DB engines are discovered however on some SQL instances, jobs are
discovered and others are not.
We wish to use the OpsMgr action account so we dont use the SQL profiles
from the MP. In a secure environment, do we need to grant permissions in
SQL? In a low-priv scenario, we would add the OpsMgr dbr account DBO to
msdb. We tried that and a few other combinations but it will not work.
Similar problem here too.
Good SQL Practise includes removing Builtin\Administrators account from the
database. However SCOM seems to require it to monitor some pieces. Have
found a few additional privs that have reduced the monitoring holes left by
Builtin\Admins being removed (such as granting "view server state" to the
action account) however haven't found the combination that makes agent jobs
show up in SCOM.
Have I missed some doucmentation?