Skip to main content

inventory sms advanced client component configuration...

i've read numerous sources about how to disable components of the sms advanced client.  now trying to find which clients have that setting off was another mystery all together.  alas, not totally hidden.  it's exposed in root\ccm\policy\machine\actualconfig.

by the way, did you know you can turn off the inventory agent?  i'm not sure what kind of usefulness could derive from that, but it's there.  if you've turned off the inventory agent, good luck.  this won't help you.  :) 

this is going to require a sms_def.mof change.  fortunately, it doesn't require a client compile so wipe that sweat off your brow and keep reading.

 

i found two ways to do this.  one is what i refer to as the long way (which i was doing when i was trying to figure out how everything worked.)  the other, i will refer to as the short way.  obviously (and just like in real life), the short way is always better.  so first, i present to you ... the short way!

//  *Software Distribution
    #pragma namespace ("\\\\.\\root\\cimv2\\sms")

    [SMS_Report     (TRUE),
    SMS_Group_Name ("SMS Advanced Client Config"),
    Namespace      ("root\\\\ccm\\\\policy\\\\machine\\\\actualconfig"),
    SMS_Class_ID   ("MCO|SMS_CLIENT_CONFIG|1.0") ]

    class CCM_ComponentClientConfig : SMS_Class_Template

    {
    [SMS_Report (TRUE),key  ]    string   ComponentName;
    [SMS_Report (TRUE)      ]    boolean  Enabled;
    };

 

for my environment, componentname and enabled were the only two fields i needed.  it's for this reason that i can utilize the short way approach.  you see, in the short way, i'm drawing from the single class "ccm_componentclientconfig".  (this appears to be some combined class of all the other configuration classes.)  behind the scenes, we're actually performing a wmi query that would look like this:

select componentname, enabled from ccm_componentclientconfig

 

clear?  okay, moving on.  if i wanted to extract other columns from all 5 of the component configuration classes, they would have to match each other or the query would fail.  for instance, one like this would bomb out since cachecontenttimeout only exists in ccm_softwaredistributionclientconfig :

select componentname, enabled, cachecontenttimeout from ccm_componentclientconfig

 

because of this limitation, if you want to draw additional items out, you should consider using the mof below.  note that in the long way mof, the class utilized for each section is different.  i just happened to stumble upon the one up above, otherwise, this is the way i would have gone...

and now, the completely exaggerated, only really, slightly longer (4x as many queries that execute client side though but who cares, ho hum) the long way!

// *Software Distribution #pragma namespace ("\\\\.\\root\\cimv2\\sms") [SMS_Report (TRUE), SMS_Group_Name ("SMS Advanced Client Config"), Namespace ("root\\\\ccm\\\\policy\\\\machine\\\\actualconfig"), SMS_Class_ID ("MCO|SMS_CLIENT_CONFIG|1.0") ] class CCM_SoftwareDistributionClientConfig : SMS_Class_Template { [SMS_Report (TRUE),key ] string ComponentName; [SMS_Report (TRUE) ] boolean Enabled;

[SMS_Report (TRUE)      ]    uint32   CacheContentTimeout;

}; // *Software Metering [SMS_Report (TRUE), SMS_Group_Name ("SMS Advanced Client Config"), Namespace ("root\\\\ccm\\\\policy\\\\machine\\\\actualconfig"), SMS_Class_ID ("MCO|SMS_CLIENT_CONFIG|1.0") ] class CCM_SoftwareMeteringClientConfig : SMS_Class_Template { [SMS_Report (TRUE),key ] string ComponentName; [SMS_Report (TRUE) ] boolean Enabled; }; // *Inventory [SMS_Report (TRUE), SMS_Group_Name ("SMS Advanced Client Config"), Namespace ("root\\\\ccm\\\\policy\\\\machine\\\\actualconfig"), SMS_Class_ID ("MCO|SMS_CLIENT_CONFIG|1.0") ] class CCM_InventoryClientConfig : SMS_Class_Template { [SMS_Report (TRUE),key ] string ComponentName; [SMS_Report (TRUE) ] boolean Enabled; }; // *Remote Tools [SMS_Report (TRUE), SMS_Group_Name ("SMS Advanced Client Config"), Namespace ("root\\\\ccm\\\\policy\\\\machine\\\\actualconfig"), SMS_Class_ID ("MCO|SMS_CLIENT_CONFIG|1.0") ] class CCM_RemoteToolsConfig : SMS_Class_Template { [SMS_Report (TRUE),key ] string ComponentName; [SMS_Report (TRUE) ] boolean Enabled; };

 

notice that the group name and class id stays consistent?  because of that, it flows into the same table.  now look carefully at the section pertaining to CCM_SoftwareDistributionClientConfig.  notice how it has an additional reporting field called "cachecontenttimeout"?  because of this, you'll see additional columns in the output for all the fields.  who cares.  at least you got the data... and in one location!

screenshots below should explain all the mumbling i've been doing.  first, the short way:

image

and once again, the long way.  make note of the column "cachecontenttimeout".

image

and that is that.

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