Skip to main content

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'
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 something a little more automated.  you have mom for crying out loud.  make it work.  instead of walking in every morning and doing this ourselves, wouldn't it be so much more productive to have mom do it for us?  with that in mind, all we need is a script.  mom will handle the rest. 

for that, here's a script that will perform the exact same thing above with an added feature.  it will take the event count and throw it into the performance data stream and write it to the database as a performance counter.  we can do all kinds of things with it in that format.  to start off... here's the script:

Dim objConn
Dim objRS

Set objConn=CreateObject("ADODB.Connection")
Set objRS = CreateObject("ADODB.Recordset")

sDataBase = ScriptContext.Parameters.Get("DataBaseName")
sMgmtGroup = ScriptContext.Parameters.Get("ManagementGroup")

objConn.ConnectionString = _
     "Driver={SQL Server};" &_
     "Server=" & sDataBase & ";" &_
     "Database=Onepoint;" &_

'Open the database connection

'Define the SQL query
strSQLQuery =       "SELECT COUNT(*) AS 'Event Count' " & _
                       "FROM SDKEventView " & _
                       "WHERE TimeGenerated > GetDate()-1"

'Open the recordset
objRS.Open strSQLQuery, objConn ', adOpenForwardOnly, adLockReadOnly, adCmdText

iTotalEvents = objRS.Fields(0)

'Close up the objects
Set objRS = Nothing
Set objConn = Nothing

CreatePerfData "MOM",sMgmtGroup,"Total Events",iTotalEvents

Sub CreatePerfData(strObjectName,strInstanceName,strCounterName,numValue)
    Set objPerfData = ScriptContext.CreatePerfData
   objPerfData.ObjectName = strObjectName
    objPerfData.InstanceName = strInstanceName
    objPerfData.CounterName = strCounterName
    objPerfData.Value = numValue
    ScriptContext.Submit objPerfData
End Sub

it's not going to work if you just copy and paste it into mom.  you'll have to create a script in the "scripts" container (no, really?) and add some parameters.  if you look at the script, you'll see the parameters you need.  they're prefaced by paramters.get.

  • DatabaseName
  • ManagementGroup

once you've got the script in there, create a rule group, attach it to your mom management server computer group and create a timed provider to execute the script.  i set mine to synchronize every 24 hours at 00:01 just to make sure that it executes around the same time every day.  for the responses, add the script you created above with the parameters filled out to match your environment.

once the script executions begin, you'll be able to graph the performance counter of your total events.  it should come in like this:

  • performance object name: MOM
  • performance instance: [ManagementGroup]
  • performance counter: Total Events

when you graph it out, you'll be able to see the results of your labor:



Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …