Due to some interest on the SMS list, attached is a vbscript (rename the .txt to .vbs), and a .jpg of how it looks in Resource Explorer on 1 test lab client.
I only tested it on 1 XP client in the lab; and I used fake User GPOs 'cause I was too lazy to create real User GPOs. So please test the results from the HKCU area really thoroughly. Please test, test, test. If there's something missing you want added, let me know. I had it all done and tested and then I thought "how about a column with the machine name for the machine ones, and the username of the current user for the HKCU user ones?" I thought of another column--the date the script ran so you know how dated the info might be.
The vbscript would need to be run on the clients on some kind of recurring basis, only when a user logged in w/user rights in order to read the HKCU keys to transfer the data from the HKCU keys to WMI to be read by Hardware Inventory.
The Mof Edit (for your mini or sms_def.mof):
#pragma namespace("\\\\.\\root\\cimv2\\sms")
[SMS_Report(TRUE), SMS_Group_Name("GPO History"), SMS_Class_ID("SMSEXPERT|GPOHistory|1.0")]
class GPOHistory : SMS_Class_Template
{
[SMS_Report(TRUE)] string DisplayName;
[SMS_Report(TRUE)] string DSPath;
[SMS_Report(TRUE)] string FileSysPath;
[SMS_Report(TRUE)] string GPOName;
[SMS_Report(TRUE)] string Link;
[SMS_Report(TRUE), Key] uint32 Key1;
[SMS_Report(TRUE)] string Type;
};
The picture: http://myitforum.com/cs2/blogs/skissinger/GPOhistory.JPG
The vbscript: http://myitforum.com/cs2/blogs/skissinger/GPOHistory.vbs.txt
