Skip to main content


Showing posts from May, 2008

how to audit maintenance mode in mom 2005

what i've discovered is that there are tons of postings, documentation, scripts and such on how to put a machine into maintenance mode -- and bring it back out -- by ui, a cmd shell tool, a script, etc.  however, there's really not much describing how to find out how a machine got into maintenance mode in the first place. it's actually very simple because mom likes to log the crap out of everything.  there are four relevant ids that you should be aware of.  based on this knowledge, you can create your own event views or reports to take a look at this data. the first set of ids refer to maintenance mode set by the console: 10015 - maintenance mode start (details are in the parameters tab) 10016 - maintenance mode stop the second set of maintenance mode ids are set by the cmd line tool or anything that accesses the sdk (sms client for example): 22153 - maintenance mode start request (details are in the description) 22154 - maintenance mode stop reques

monitoring event storms in mom 2005 ...

as an avid mom administrator, i'm sure you check your total # of events per day, right?  this is really, the only real way to know if events are firing off in a manner that's out of control or heading that way.  some events aren't set to alert when they're picked up so there's a high likelihood that this could be happening in your environment, without your knowledge. if you're old-school, you can walk in every morning, get your cup of coffee, fire up a t-sql query program and execute something like this: SELECT COUNT (*) AS 'Event Count' FROM SDKEventView WHERE TimeGenerated > GetDate()-1 a successful execution will bring back the total number of events from the day prior.  i suppose if that's all you need, you can stop reading right here and go back to the way you were.  but if you're a lazy, little squirrel then keep reading. still reading, aren't you? :)  since this method can be a monotonous pain in the ass, try som