http://blogs.technet.com/kevinholman/archive/2008/03/26/using-a-recovery-in-opsmgr-basic.aspxThis is a simple overview of using a recovery for a custom Monitor in OpsMgr Lets say we create a simple service monitor in OpsMgr... for this example - I will use the Print Spooler service: Create a new monitor, unit monitor, and choose windows servicesen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/kevinholman/archive/2008/03/26/using-a-recovery-in-opsmgr-basic.aspx#3139326Mon, 20 Oct 2008 21:53:59 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3139326npagonor<p>Do you have a procedure for scenario that you talked about in your last paragraph? &nbsp;I have a need to attempt recovery about three times then raise an alert that can be forwarded to the responsible tech. &nbsp;Any help will be appreciated.</p> <p>send response to: npagonor@up.com</p> <p>Thanks.</p> http://blogs.technet.com/kevinholman/archive/2008/03/26/using-a-recovery-in-opsmgr-basic.aspx#3139352Mon, 20 Oct 2008 23:01:22 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3139352kevinhol<p>I dont - and I dont know offhand of any community examples.... basically the logic is, that you would write a script that attempts to restart the service three times with a sleep between, then if it doesnt start... you can have the script create an event in the opsmgr EVT log. &nbsp;Then have a rule watching for this event and generate an alert. &nbsp;You could always have the recovery just do a &quot;NET START &amp; NET START &amp; NET START&quot; but running these back to back isnt as good as a script, which can sleep, analyze the service state, kill processes, etc... but that all depends on your scripting skills and testing.</p>