Are you trying to create a query in the SMS Admin Console, or are you trying to run a query against thw WMI layer?

If you are in the admin console and the fields are simply not listed in the drop down boxes, then either your MOF didn't work, or you need to choose a different base class in the very first "Create Query" dialog box.

If you are trying to script a query (essentially Ad-Hoc), then you should use WMI CIM Studio to browse the WMI namespace on the server to find the tables and see if there is any valid data being reported.

When editing the SMS_Def.MOF file, you should ALWAYS test the MOF file by running (in a dos window) "MOFCOMP.EXE SMS_Def.MOF".  This will tell you if there are syntax errors.  If there are syntax errors, then the data isn't getting retrieved from the client.

Overall, I would say you should figure out if it's breaking at the client (use MOFCOMP.exe), or if it's breaking at the server (use WMI CIM Studio).

Since the updated MOF is alread deployed, check the client's hardware inventory log for any error messages concerning the section you've added to the SMS_DEF.MOF.

Make sure you've followed the instructions here:

http://www.myitforum.com/articles/view.asp?t=How%20to%20Apply%20the%20MOF%20Files&id=193&z=1&s=SMS%202.x

While this pertains to the MOF files submitted by the SMS community, you should verify your MOF file has made it through its process.

Rod Trent
http://www.myITForum.com
Microsoft SMS Installer ISBN:0072124474
Admin911:SMS ISBN:0072130229
IIS 5.0: A Beginner's Guide - ISBN:0072133724
 

Thanks for the help. It was dead on.  The HINV log showed that the new MOF file never made it to the client.  MOFCOMP showed compile errors, which were caused by my not having the current ver of MOFMAN.   Jon