WMI is a great addition to Group Policy and adds to the almost non-existant
targeting mechanism. Unfortunately it is all or nothing. You can put a
filter on the GPO but not the individual settings in the GPO. This level of
targeting you really need to take a look at third party solutions providing
extensions to Group Policy.
Kevin
AutoProf
http://www.autoprof.com/policy
"Len Nally" <anon...@discussions.microsoft.com> wrote in message
news:33fc01c4a506$3f203a40$a301...@phx.gbl...
Namespace: root\RSOP\Computer
Query: select * from RSOP_GPO where guidName = "{XXXXXXXXXXXXXX}"
Just put the GUID of the GP object in the query in place of the XX's.
The only problem with this method is that it was bandwidth intensive and
caused logon delays when the client and DC were seperated over a slow
link.
Also, I have just updated the Wiki page on WMI Filters to make an important
point about how and when they should be considered for us. See the "When To
Use (And Not Use) WMI Filters" section here:
http://grouppolicy.editme.com/WMIFilters
I hope this helps.
--
Mark Williams
Program Manager, Group Policy
http://www.microsoft.com/technet/grouppolicy
Play a Role - Contribute To The Group Policy Wiki
http://www.grouppolicywiki.com
This posting is provided "AS IS" with no warranties, and confers no rights.
"lnally" <len....@nospam.bendigobank.com.au> wrote in message
news:c6639b6e871d3045...@localhost.talkaboutsoftware.com...