eddy wrote:

> We use a Driver Health Job to execute an ECMAscript when a driver is
> stopped or started. But I'm not able to 'get' which driver actually
> started the ECMAscript.

No idea what you are trying to achieve with this setup, but maybe you could
have a NULL service driver listen to changes to DirXML-DriverState and fire
your ECMA that way.


(If you find this post helpful, please click on the star below.)