Skip to main content

sms: dcm (desired configuration monitoring)

i decided it was about time i started looking at desired configuration monitoring since the likelihood that we'll move to sms v4 in the short term is pretty close to zero. anyway, to date, i haven't done a thing with it. the interface is clunky and unintuitive. oh well, there are probably plenty worse, and i can't hide from it forever. here are some links i found to more information (someone left me a comment on a previous post that directed me on this search). my hope is that if i post these links someone else will actually do all the work in understanding dcm and write up some cute, easy-to-follow guide. :) dcm technet site dcm technet documentation dcm download dcm developer's blog the dcm developer's blog is pretty good stuff. whoever dropped that note, thanks!

Comments

  1. Hey

    It was me who dropped that note about the DCM developers blog. Well, looks like someone has come up with a training on DCM now. I guess this product badly needed some kind of a training material. Check it out here: http://www.alpha-tech-solutions.com/ProductInfo.aspx?productid=TRN0601

    Thanks

    ReplyDelete
  2. cool deal. looks interesting but not sure how much i could glean off two hours of dcm training. to me, the biggest problem right now is that dcm doesn't really come with any decent manifests.

    i think having some base manifests to continue adding or modifying to your environmental specs would be ideal. i guess microsoft must have thought the same. they now offer this, but it can only be accessed through their professional services.

    one of the dcm developers posted a note on his blog suggesting that there was a manifest beta you could sign up for. i haven't been able to find it... but am still looking around. i've dropped him a note. i'll post something when if it does become available.

    ReplyDelete
  3. Wow, this training is pretty good. After a lot of thinking, I decided to buy the training. These guys did a splendid job! They actually explained each section of the UI. They have several sample scenarios and walked through the entire process of creating the manifest. At least now I understand when to use Substitution!!! :-) Microsoft did a pretty poor job with their documentation on DCM.

    I agree with him that this training is worth each dollar! Finally, there is a real training on DCM! I wonder why Microsoft did not create a training on this product when I assume they knew it was a complicated product!

    I too definitely recommend this training to any one using DCM. It does clear up a lot of concepts and helped me understand when to use active and passive rules.The substitution was a killer! By the way, its here: DCM Training!!!

    - Steve

    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