ConfigMgr Client Hotfix Queries

After the release of ConfigMgr 2007 R3 the need to update Client Agents with hotfixes suddenly became all that more interesting. Some optional patches have been released earlier, but for Power Management to work on clients in R3 a hotfix is required.

So, how do you check what kind of hotfixes are actually installed on your clients? For the quick solution, skip to the end.

The first thing I tried was to query the client for the Client Agent version. From SP1 to SP2 this version does change, ad this is reflected in both the Client Agent and in the ConfigMgr database, 4.00.6221.100 for SP1 and 4.00.6487.2000 for SP2. However, even though the Client version on the agent changed with the R3 client hotfix (screenshot), the version in ConfigMgr remained the same.

Now, if you check under the Components tab you can see that the CCM Framework version has changed, that the Power Management Component version has changed (the Power Management Component was added in SP2), and that all the other component versions also have remained the same. If we use this information instead and make a query, we can see that they have in fact changed in the ConfigMgr database. For this we need to use a different class than the System Resource class, namely the SMS Advanced Client State class.

In this example I used the R3 client hotfix (KB977384), and you can use the query bellow to find clients with the right Power Management Component version. This has been taken from the ConfigMgr 2007 Hotfix Installation Guide over at technet.

select * from SMS_R_System
inner join
SMS_G_System_SMS_ADVANCED_CLIENT_STATE
on
SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceID = SMS_R_System.ResourceId
where SMS_R_System.ClientType = 1
and
SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Name = “CcmFramework”
and
(SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version < “4.00.6487.2012″)

Now, for other hotfixes, Jason Sandys has done a great job checking the other versions and hotfixes, and I’ll simply quote him. Check his blog to read the whole post.

Clients with hotfix 977385 also have these components bumped in version: