tag:blogger.com,1999:blog-4414432572587218573.post4012218218145679679..comments2023-05-06T15:20:16.638+02:00Comments on Thoughts on Azure, OMS & SCOM: 'Script or executable failed to run' - Part 2 'It is all about looks..'Marnix Wolfhttp://www.blogger.com/profile/09487479325587450184noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4414432572587218573.post-77376955722868936492009-03-05T11:52:00.000+01:002009-03-05T11:52:00.000+01:00Hi Ian.Thanks for your information. You are right ...Hi Ian.<BR/><BR/>Thanks for your information. You are right about the integers for the severity. I even have made a blogposting about it in the past but somehow I mixed them up in this posting. So I will adjust it.<BR/><BR/>Best regards,<BR/>MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-33821139006722792282009-03-05T11:45:00.000+01:002009-03-05T11:45:00.000+01:00It is something that I do with all installations. ...It is something that I do with all installations. If a script fails once or twice it is no big deal and once it is a few days old I clear it. The only ones that I am interested in are those with repeat counts. I was sure that I had blogged about changing those Script alerts to Information but it does not look like it. <BR/><BR/>The others I change to information are<BR/>WMI Probe Module Execution Failure<BR/>WMI Event Module Execution Failure<BR/>IIS Discovery Probe Module Execution Failure<BR/><BR/>Error serverity is 2, Warning is 1 and Information is 0.<BR/><BR/>Ian<BR/>http://ianblythmanagement.wordpress.com/Unknownhttps://www.blogger.com/profile/03502796502558317030noreply@blogger.com