Greetings my fellow OpsMgr admins! I’m back from vacation with 100% more married then before! And I come bearing gifts! ((Even though no one bought me anything OR even got me a giftcard. I guess I’m the only one that does that stuff at other peoples sites heh))
Yes, that’s right, it’s contest time again. This time I’m offering up 2 things: 1 autographed copy of System Center Operations Manager 2007 Unleashed. This is a fairly rare item as it’s one of less then a half dozen signed by all the authors. I had to do dirty dirty things to Cameron to get it. I’m not proud, but for my peeps I go the distance!
The second item is a little teaser prize package from the wonderful folks over at Sapien Technologies. Soon I’ll be posting a new contest with oodles of Sapien prizes – from the PrimalScript Universal Resource Kit to flying monkies and more! That entire contest/post will be centered around setting up PrimalScript as the development environment for us OpsMgr Admins. You’ll love it! This current package, however, isn’t as illustrious: It contains a Sapien portfolio, PicoPad, Post-It notes, a credit card sized flash drive and an awesome pen!
Additionally I’d like to offer up some SDK app loving I’ve been baking all day!
I’m working on a neat console application that was initially called Alert Utility, and is now just called the OpsMgr Utility. It reports on a variety of things and allows you to interact with the system in a variety of ways.
I’m not much of a programmer, so I need to start out slow – so the first thing I whipped up is a little utility called SCOM-CloseAll. Simply put, it takes 2 arguments – your RMS and an optional comment to insert when you resolve the alert. It then connects to the SDK service on the RMS, retrieves all open alerts, then resolves them. And yes, it does ask if you truly want to do this. It’s in beta, so I’d love it if you all could test it out for me. This is a perfect solution to handle those pesky alert storms and another tool in the box.
Take a look at the screenshots then download it here.






what was wrong with
get-alert | resolve-alert | out-null
?
Yes, I am teasing – nice exercise!
Ah, you do have a valid point. Until you get enough alerts that your command shell dies with an Out of Memory exception, and then it does the same thing on your RMS. MS has you flip a memory a value in the registry and you can eventually get it to work, but it’s slow. This lil program handles 10s of thousands of alerts without missing a beat
Hi Jeremy,
I downloaded the zip, extracted the exe to C:\temp on my test RMS and then ran it.
I get a Black box that appears for a few seconds, then it disappears.
What am I doing wrong?
Thx,
John Bradshaw
Hey John,
What happens when you open up cmd.exe and cd to the location, then run it?
Although not mentioned in the post, remember that .NET 3.0 and the OpsMgr assemblies will need to be installed locally on the system where this .exe is run.
Hi Jeremy,
This is a very nice utility, however I would like to recommend an enhancement. I am working for the company where we have multiple resolution states, so it would be useful for us to be able to close alerts based on the resolution state and not just the “new” ones.
-Dmitriy
Oh, how did you know that’s what I was working on now?