Here’s a couple of methods whereby you can quickly check the update status for a device, updates installed or missing, via WMI Explorer or WBEMtest. Sometimes it’s just quicker to eyeball the status directly on a device.
Using WMI Explorer
If you don’t use WMI Explorer then you should really change your thinking. It’s a nice easy method to dril down WMI and check things. It’s super simple to use.
You can download WMI Explorer from https://github.com/vinaypamnani/wmie2/releases.
Start off by typing in the computer name in the Computer field at the top left hand corner and then clicking Connect.
Now we are connected we can drill down the WMI in an almost directory style view by double clicking on each entry.
To check for the Software Update status on a device let’s drill down. Start off by clicking ROOT\ccm and then ROOT\ccm\SoftwareUpdates.
ROOT\ccm will expose all the namespaces which are created by ConfigMgr. Here is a list of all those namespaces.
- root\ccm\CCMPasswordSettings
- root\ccm\CIModels
- root\ccm\CIStateStore
- root\ccm\CIStore
- root\ccm\CITasks
- root\ccm\ClientSDK
- root\ccm\ContentTransferManager
- root\ccm\DataTransferService
- root\ccm\dcm
- root\ccm\DCMAgent
- root\ccm\evaltest
- root\ccm\Events
- root\ccm\InvAgt
- root\ccm\LocationServices
- root\ccm\Messaging
- root\ccm\NetworkConfig
- root\ccm\PeerDPAgent
- root\ccm\Policy
- root\ccm\PowerManagementAgent
- root\ccm\RebootManagement
- root\ccm\ScanAgent
- root\ccm\Scheduler
- root\ccm\SMSNapAgent
- root\ccm\SoftMgmtAgent
- root\ccm\SoftwareMeteringAgent
- root\ccm\SoftwareUpdates
- root\ccm\StateMsg
- root\ccm\VulnerabilityAssessment
- root\ccm\XmlStore
- root\cimv2\sms
- root\smsdm
- root\sms
- root\sms\site_<site code>
As mentioned, we have drilled into the root\ccm\SoftwareUpdates namespace.
Under this namespace are three further namespaces. We are interested in the UpdatesStore name space and if we double click on that you will see that two classes are exposed. CMM_SourceStatus and CCM_UpdateStatus.
CCM_UpdateStatus is the one we are interested in, as this will give us the status of updates for the device.
If you look at the Query field at the bottom, this has already populated a WQL query for us. SELECT * FROM CCM_UpdateStatus and by clicking the Execute button we can return the details we need.
From my results, I can see that the Feature Update for 1909 is Missing. Well that’s good news for me as I wish to target this device for a 1909 upgrade.
Using WBEMtest
WBEMtest is built into the OS. It’s a little trickier to use, you can’t browse though the namespaces for example, and I like to keep things simple, so I always use WMI Explorer. But what if I can’t download WMI Explorer and use it on site. Well WBEMtest will do quite nicely.
Start off by running the WBEMtest command from CMD. Click the Connect button.
Type in the path to the namespace. If connecting to a remote device, type in \\hostname followed by the path.
I’ve drilled directly down to the root\ccm\SoftwareUpdates\UpdateStore namespace.
Click the Query button.
OK now I can query the CCM_UpdateStatus class in the query window. Click Apply.
Click the Show MOF button.
The results will display a list of updates.
I can reference the update I want from the Unique Update ID column in the updates node in ConfigMgr. I have to add in the column as this is not here by default.
After clicking the update I require, I can see the update and the status – i.e. it is missing from this device.
Hope this helps.
SCCMentor - Paul Winstanley 