I helped a customer creating a OpsMgr Monitor for checking if the there has been a SQL Full or Differential Backup within a specified number of hours. David Scheltens created the SQL query.
Remark: Please read information on System Center Central for more info on this article.
This is how you could create this kind of monitor in your own environment.
15. Enable the Monitor via an Override.
Remark: You may need to Use a Run As Account with the right permission for this Monitor.
In Operations Manager 2007, Run As Profiles and Run As Accounts are used to select users with the privileges needed for running rules, tasks, and monitors. Management Pack authors create a rule, task, or monitor, and then associate it with a Run As Profile. The named Run As Profile is imported along with the Management Pack into Operations Manager 2007.
The Operations Manager 2007 administrator creates a named Run As Account and specifies users and groups. The administrator then adds the Run As Account to the Run As Profile and specifies the target computers that the account should run on.
The goal in this short tutorial is to create a Timed Script Two State Monitor and associate a run as account to this monitor and save it all in a Management Pack. The Timed Script Two State Monitor is a vbscript that uses WMI to check if BizTalk orchestrations are not started.
I’ve got some great help from Jakub Oleksy (http://blogs.msdn.com/jakuboleksy/default.aspx) and Steve Wilson (http://www.authormps.com/dnn/)
You can download the tutorial here.
Check out the blogpost on System Center Central about an issue with above blogpost.
I recently came across a db that had a while space in the name ie. "DB Test" and so when the three parameters are passed to the vbscript there is now a total of four input parameters and the vbscript fails and its logged in the event viewer. Have you worked out a how to resolve this?
PK and I collaborated to resolve the 'space in the DB name issue'. I've documented the fix on the systemcentercentral site. Stefan, you may want to revise your process above and change the screenshots to show this difference. It should fix the problem for anyone that has a space in the DB name (Bad practice, btw!) and should not interfere with normal operation of the script for other DBs.
For anyone that for some reason can't get to the SCC site, it's simply a matter of adding quotations around the 2nd parameter. That way when the DB name is passed to the script, it's recognized as a single variable instead of multiple.
The link to the script is 404.
Stefan, can you please post the script here? The link doesn't work.
please post the script here. The link doesn't work (404).
I uploaded the script to my skydrive. Try that.