Skip to main content

using repeat count to detect a problem in a window of time

i realized when someone asked me how to do this that i was totally remiss about posting it.

for the purpose of this exercise, i’m going to walk you through creating an event monitor which will check if a high number (subjective) of bad attempts to logon is detected within a finite period of time.  so follow along… it’s much easier in opsmgr than mom 2005 (as i described in this much earlier blog post.)

here are the steps:

  • create a monitor / unit monitor
  • windows events / repeated event detection

at this point, you have three choices: manual, timer, and windows event reset.  choose the one most appropriate for the situation.  i chose the timer.

  • name it “OH MY GOD!  SOMEONE IS TRYING TO HACK ME!” or something else equally shocking! ;)
  • target your windows domain controller or whichever group makes sense for you
  • i put the rule under the parent monitor of security
  • set the event log name to “Security” and move along
  • in the following area, i specified these values:
    • Event ID Equals 529
    • Event Source Equals Security
    • Parameter 1 (leave it blank if you don't want to specify anything, otherwise, provide a filter that works for you)
    • Parameter 2 Equals “myDomain”

image

parameter 2 helps cut out some of the chatter from local security context.

  • on the repeat settings tab, i specified the following:
    • Trigger on count, sliding – compare 20
    • Interval – 30 minutes

image

 

this is basically stating that if within 30 minutes, i receive the same event 20 times or more, flip this switch.

  • for the auto reset timer, i specified 3 minutes.  all these values you’ll want to slide around to make it work in your environment.

 

 

 

that’s all there is to it.  you can use these sliding window concept to anything else such as chatty script error problems (which kevin will chastise you publicly if you admit to doing this) or repeating indications in a log file of a problem, for instance.  have fun with it.

Comments

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

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.   DETECTION status messages take 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 m