Skip to main content

sms: dcm - alpha tech solutions

a few folks have posted comments regarding training on dcm that's available from alpha tech solutions. i wasn't sure how seriously to take it since i'd never heard of it before ... but after talking to one of the dcm dev folks, i decided to look into it a little bit. i emailed their sales person and asked for an eval so that i could go through the training set and review it. to my surprise, they were more than willing. :) training is broken down into two parts. the first part covers the following:
  1. introduction
  2. installing the dcm authoring tool
  3. creating and customizing manifests
  4. customizing scenarios (part 1)
    • check service state
    • check file version
    • verify automatic updates
    • verify smtp default domain
    • verify minimum password length
the second section covers the following:
  1. customizing scenarios (part 2)
    • verify if a hotfix is installed
    • verify if a service exists
    • check file existence
    • number range
    • firewall status
  2. deployment and execution
  3. reporting
by the time you've gone through the training, if you follow along, you'll have built a decent manifest by which you should be able to go back and edit it for your own use. it's not necessary though since the manifest is available with the training material. there are a quite a few examples of advanced rule building that you will want to pay attention to such as the number range which can determine if a machine's memory is within a tolerable range to meet compliance. there are some assumptions about the level of knowledge the viewer should have. having sms knowledge is helpful since they don't cover any of the how-to parts on deploying packages, creating collections, etc, etc, etc. also, having some knowledge about wmi will be very helpful since most of the scenarios happen to use wmi. i haven't gone through the dcm documentation (the one released by microsoft) to any reasonable extent so i'm not sure how much overlap there is. however, i can say that it is much easier to watch the examples given in the demonstrations than read it on paper (or screen). there are some scenarios that i wished had been covered in greater detail such as the formulaic parts of an xpath expression and detail about the various query functions. none the less, it's more than you're going to find out there. by the way, the whole thing is done in flash so you can navigate around the topics, fast forward through scenarios to get to the part you want, reverse, stop, etc. if your organization is looking at using dcm for configuration monitoring, you may want to consider looking at this available training guide. much cheaper than sending someone to class since it runs a buck shy of $200. it's about two hours long so it can be consumed in the space of a couple of lunches. :) they seem to believe in this stuff. i say that because they've got a product called rulegen that apparently will build a manifest from a golden machine. kind of neat. check them out...

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