Discussion:
SCOM07 SQL Agent Jobs
(too old to reply)
Romker
2007-10-29 11:04:00 UTC
Permalink
Hi all!

In SCOM 07, my "SQL Agent Job State" view is empty, but we have a number of
Jobs on our SQL servers. What can I do, to discover and monitor my SQL-jobs?
Yann Gainche [MVP MOM]
2007-10-29 16:49:07 UTC
Permalink
Post by Romker
Hi all!
In SCOM 07, my "SQL Agent Job State" view is empty, but we have a number of
Jobs on our SQL servers. What can I do, to discover and monitor my SQL-jobs?
Hi

If I remember, the SQL Job discovery is disabled by default. You have
to create an override to enable it.
--
Yann Gainche

MVP - Windows Server System - MOM]
http://msmvps.com/blogs/opsmgr
SilloSyben
2008-02-13 15:08:01 UTC
Permalink
I 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.

Thank you
Post by Yann Gainche [MVP MOM]
Post by Romker
Hi all!
In SCOM 07, my "SQL Agent Job State" view is empty, but we have a number of
Jobs on our SQL servers. What can I do, to discover and monitor my SQL-jobs?
Hi
If I remember, the SQL Job discovery is disabled by default. You have
to create an override to enable it.
--
Yann Gainche
MVP - Windows Server System - MOM]
http://msmvps.com/blogs/opsmgr
CJ
2009-01-27 21:03:02 UTC
Permalink
Post by SilloSyben
I 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?

Loading...