[gptalk] Re: WMI filter on registry keys

Darren,
 
That is a possibility, but the reg method would have provide a
consistent flag to check.  The file method means hundreds of filters
would have to be used.  We are testing.
 
Thanks!
 

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: Doug.Delaney@xxxxxxx <mailto: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.

 


________________________________

        From: gptalk-bounce@xxxxxxxxxxxxx
[mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia
        Sent: Thursday, October 18, 2007 9:36 AM
        To: gptalk@xxxxxxxxxxxxx
        Subject: [gptalk] Re: WMI filter on registry keys
        
        

        Sadly, I just happened to be up late and still at the computer
J.  How about using a flag that WMI can handle without modification?
Like, the presence of a file on the system? What does the script do-does
it leave any other footprints that you could test for using WMI? 

         

        Darren

         

        From: gptalk-bounce@xxxxxxxxxxxxx
[mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Delaney, Doug
        Sent: Wednesday, October 17, 2007 10:05 PM
        To: gptalk@xxxxxxxxxxxxx
        Subject: [gptalk] Re: WMI filter on registry keys

         

        Darren,

         

        Wow, what a fast response.  I did find the .MOF method, and
already wrote that off, as I have to deploy something to be able to use
it.  We are currently writing a reg value and making the script
immediately read it and exit if complete, but the sheer volume of
scripts is introducing a 1-2 minute delay in boot up.  So, we are
looking for a creative solution that does not require a previous
deployment to enable it.  Adding a filter (or otherwise changing an
existing GPO), is a much faster solution than deploying something (which
may take months to reach all clients due to facts of life like travel,
vacation, VPN only connections where GPO's do not apply, etc.).

         

        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: Doug.Delaney@xxxxxxx <mailto: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.

         

                 

________________________________

                From: gptalk-bounce@xxxxxxxxxxxxx
[mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia
                Sent: Thursday, October 18, 2007 12:37 AM
                To: gptalk@xxxxxxxxxxxxx
                Subject: [gptalk] Re: WMI filter on registry keys

                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: Doug.Delaney@xxxxxxx <mailto: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.

Other related posts: