Skip to main content

mom: if it keeps up, man will atrophy all his limbs...

...but the push-button finger. and aren't we better creatures for it, mr. frank lloyd wright? by the way, pass me the remote. i'm already starting off on a very bad note. blogger just ate my homework so to speak. i was nearly done with this post when it decided to go rabid and eat the whole thing before my eyes. oh spare me the virtues of saving often. i'm quite annoyed. oh well. i hear that you actually write better when you write the same thing twice... uh huh. so to get started, recently the idea was tossed around that if we lost our management packs because of some errant corruption, we'd most likely have to reimport the stock management packs, trudge through the years of change data, and reset everything back to the way it was. either that or we have to restore the database. since neither of these options are really any better than eating a handful of chalk, we decided we should export management packs as a part of a weekly process. this way, if anything is corrupted, we've only lost a week's worth of changes. so since it was my buddy's brilliant idea, i told him to go ahead and get started. after two hours of teeth grinding and mouse-clicking, he was finally done with the mountain of management packs he had to export. at that point, i decided i should write a script. partly because i felt sorry for the guy, and mostly because i didn't want to go through that exercise myself. i would liked to have used managementmoduleutil.exe as it came from the factory, but alas, it's missing some parts that are simply required to be categorized under "automated". first of all, you have to direct the utility to the processing rule group that you want to export. i suppose you could export your list of top-level PRGs and feed it to the utility in some kind of inelegant for loop. however, if you add a management pack, that list will have to be updated each time. so, i set off to find where this data was held. turns out, it's in the database... in the most unintuitive way. (i want to quietly thank all of those that helped me with this that i can't mention their names for one reason or another...) rory alluded to a procedure on the database server that would do exactly what i was looking for. i found it. :) in case you're interested, the name of the stored procedure is ProcessRuleSelectAllTopLevelGroups. i took the relevant query from the procedure and put it in the script. now i get a dynamic list of all the top-level processing rule groups on a given management group that can be fed into the managementmoduleutil.exe. push-button that, wright. now, it'll export .AKM files to a share. that wasn't enough for me. i wanted that information on both of my management servers. in order to do this i dropped a line in to copy the AKM file to the same share on the other management server. oh by the way, it'll create a folder with the current date in case you want to run it every day and keep a rolling log of AKMs (more or less). it's a really simple script. i'm sure it's inefficient as hell so please do liberally modify it to suit your needs. be warned, there is barely a hint of error checking. these are the things you'll need. i put them all in the same directory.
  • mom_MPBackup.vbs
  • ManagementModuleUtil.exe
  • MOMCommon.dll
the script, unmodified, requires three arguments in this format:
cscript.exe mom_MPBackup.vbs databaseserver mgmtserver1 mgmtserver2
if your database server is on an instance, just specify it like [databasename\instance]. i've uploaded it to momresources.org and myitforum.com if you want a copy.

Comments

  1. FYI - I did this exact same thing a few months back and posted it to the MOMResources site. It sounds like mine is quite similar to yours (it runs as a scheduled task and it backs up the top level rule groups and creates folders for them with dates).

    http://www.momresources.org/momscripts/MP%20Backup%20Script.zip

    Justin

    ReplyDelete
  2. i should probably pay more attention, shouldn't i? :)

    ReplyDelete

Post a Comment

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
192.168.1.101
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 …