This is something we have wanted to start using for a while and now we are I thought I would share my findings.
For those that don’t know DCM (Desired Configuration Management) as it was known in ConfigMgr 2007 is now simply referred to as compliance and comprises configurations items and configurations baselines. Basically baselines are deployed much like applications to workstations. These baselines are usually made up of configurations items used to check compliance to a particular setting or application. Baselines can also include other baselines. At the uni we have had incidents where a machine is deployed with OSD and for some reason or another an application will fail to install. These applications have all been thoroughly tested so we know they work both in and out of task sequences. So we need to be able to see which machines in our classrooms are missing software. We have around 1500 – 1800 teaching machines so it needs to be something we can manage centrally. DCM/Compliance fits the bill here.
We like the built in reports but they aren’t flexible and require quite a bit of drilling down. We ideally want something for our junior technicians to be able to quickly say X machine in location Y is not compliant, we need to go see whats wrong and in the same breath see that a machine is compliant so no in depth checks are required.
The way we decided to approach this issue was with powershell and WMI. We can use the WMI namespace root\ccm\dcm and the class SMS_DesiredConfiguration to pull information on configuration baselines. (more…) (57)