Skip to main content

mom: resolveguid is a such a task!

isn't it though? none of the agents come configured with resolveguid set. all of this has to be done post installation, post agent rollout. there's no command-line tool or built-in task to simplify this process. at the request of one of the management mvps, i wrote a script to use as a mom task.

the background: by default, when security events are picked up, the sids/guids are not resolved. if you're into resolving them manually, you're set (or manic or crazy or [insert favorite word for getting institutionalized]). otherwise, using the resolveguid registry key will automatically resolve the sids/guids. microsoft published an article about it. if you want the more (frenetic) information with a canadian sense of humor, rory has blogged ad nauseum on this topic.

the foreground: i've linked to the script at the end of this blog. all you need to do is go to one of them, copy the contents into the clipboard and create a new script in mom. i used these parameters for the mom script properties:

  • name: [clever, easily identifiable name]
  • description: adds resolveguid registry key to mom agent
  • language: vbscript
  • script: [paste script here]
  • parameters: none
alright, now the first part is done. navigate to the tasks section. i created a new task under microsoft operations manager because this seemed to make the most sense. the script doesn't stop/start the mom agent after the key is added (even though its required in order to take effect). i figured they're probably things that should happen separately, at the discretion of some type of maintenance window. at any rate, the other tasks are located here for stop/start. anyway, wherever you feel comfortable...
  • run location: agent-managed computer
  • task type: script
  • target role: mom agent
  • script to run: [clever, easily identifiable name of your script above]
  • parameter default values: [none]
now to execute, open the operator console (or console refresh), the task will be available under microsoft operations manager. you can select multiple agents at once (up to 50) and run it. i've posted the script on a few of my favorite resources (momresources.org and myitforum.com) if you want to grab it. comments, rewrites, markups, whatever... always welcome. i'm no scripting guru.

Comments

  1. I totally forgot to leave a comment on this. This fix really helped me out on some auditing I set up in my MOM2005 environment. Very simple to set up and really easy to update your agents.

    thanks Marcus!!

    -Bryce

    ReplyDelete

Post a Comment

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