Is it at all possible to monitor running Opalis workflows from SCOM? I'm wondering if it's possible to use a SCOM monitor targetted at a certain Opalis workflow. When this workflow stops for some reason I want to configure a recovery task in SCOM to restart this workflow. The problem is, every workflow that starts uses a (seamingly) random process ID, so you can target it once it's running, but when te workflow restarts it gets a completely different process ID.

if you just want to restart a policy that have been stopped you could do it with two policies : Policy1 : Contains a Custom start and a Trigger Policy objects. Trigger policy is used for starting your policy2. For beeing sure that you policy is automatically restart when stopped, you just have to enable the looping on the Trigger Policy object and configure "Do not exit" when your policy2 returns success, warning, failure. Policy2 : Your policy with your actions. It will be more easy with printscreens : :D http://img196.imageshack.us/i/31979093.png/ http://img705.imageshack.us/i/70023257.png/ http://img833.imageshack.us/i/87737784.png/ Christopher Keyaert - My OpsMgr / SCOM & Opalis blog : http://www.vnext.be

This is a solution, however I'm looking for an external way of monitoring the workflows. If there was a major problem in Opalis this solution wouldn't work either probably. Maybe expand the scope of the question: Will there be a proper SCOM management pack for Opalis or will this be postponed beyond the release of SC Orhestrator and therefor skipping Opalis 6.2/6.3 alltogether?

Currently, there is no mp for Opalis, if you want to start it to build in one, I'm interested to be part of the project ;-). A mp will be available for Orchestrator directely when released, but I don't know if it will be compatible with Opalis.Christopher Keyaert - My OpsMgr / SCOM & Opalis blog : http://www.vnext.be