Thorbjorn wrote on this subject once before on this list. Essentially, there is no built-in way to form a WQL statement to look for a particular registry value. WMI uses the StdRegProv provider to talk to the registry and it does not expose an information model that allows for simple select queries. However, I believe Thorbjorn's approach involved writing and compiling your own MOF file on each target system to expose this. Not trivial. I think your better bet is to simply do that reg. value query within the startup script. That information is much more accessible using standard vbscript methods than trying to make a WMI filter do this. Darren From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Delaney, Doug Sent: Wednesday, October 17, 2007 9:14 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] WMI filter on registry keys Does any know how to use a WMI filter for a GPO that will return true if a registry value (not key) contains expected data. We are essentially trying to make startup scripts run once to resolve major issues. In that, once the script completed it's work, it writes to the registry, then the WMI filter would prevent subsequent attempts to apply the GPO (Denied WMI filter) if the registry entry contained the defined value. Apparently direct access to the registry is not available in a class. But the registry is exposed as a method in Root\CimV2 Doug Delaney EDS - Integration Engineering-GM GM Desktop Engineering 1075 W. Entrance Dr., MS 2B, Cube 2130 Auburn Hills, MI 48326 Lab: 248-365-9187 Tel: 248-754-7917 Pg: 248-870-0306 pager Mail: <mailto:Doug.Delaney@xxxxxxx> Doug.Delaney@xxxxxxx Note: The information in this email is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited.