Skip to main content

mom: receiving alerts for all servers ... with exceptions!

this is cool enough to blog about (which translates to "do not want to forget this later").  in a previous post a long while back, i wrote up a short summary of how to setup an alert rule to receive all notifications for a specified computer group.  let's take that one step further, shall we?

why do this?  imagine this scenario.  you're a domain administrator.  you decided to setup the alert rule specified above and tied it to your domain controllers computer group.  now you're receiving all the alerts for your domain controllers, just like you wanted.  and just like real life ... everything is going along happily until one day someone asks you to do something for them.  this time, they want a notification for security group changes.  not a problem!  you use a helpful little blog post like this to accomplish something pretty close to it.  (by the way, if you are doing this, just use parameter 3 for the group name.)

oh to your chagrin, your inbox fills up with monitoring alerts that you don't really care to see.  since you've got the master alert rule bound to your domain controllers, though, there doesn't seem to be a way out.

 

or is there?  here's how i resolved it.  i made two small modifications to both rules:

 

on the security event notification rule:

  • switch to the alert tab.
  • click the "custom fields..." button.
  • specify a value for customfield1.

crap

on the master alert rule:

  • switch to the alert criteria tab.
  • click the "advanced..." button.
  • choose field "custom field 1", set condition to "not equals" and the value matching what you specified above.

crap[4]

 

with that set, now you will stop receiving all those nagging notifications about other people's group changes.  hope that helps!

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