[gptalk] Using a WMI Filter instead of Site Policies

  • From: "Peacock, Adrian " <Adrian.Peacock@xxxxxxxxxxxxxxxx>
  • To: <gptalk@xxxxxxxxxxxxx>
  • Date: Tue, 18 Mar 2008 12:32:46 -0000

Is there any way of applying a policy for a site by WMI Filtering rather
than using a policy at the site level? I have tried a few things without

1) WMI Filters using Win32_NetworkAdapterConfiguration attributes - all
the useful attributes (ip address, default gateway, etc) are in arrays
and WQL does not handle arrays.

2) Script to change the registry settings deployed by group policy using
ADSystemInfo.SiteName - the script required admin rights to make changes
to the registry, but this also resulted in setting that end up tattooed
(they don't go away)!. Also this variable could not be used for a WMI
filter as it is AD and not WMI.

3) WMI Filter on Win32_NTDomain.ClientSiteName - this is a collection of
attributes, which starts with the local computer, then domain and
finally all trusted domains. When the WMI Filter is parsed the filter
ONLY looks at the first ClientSiteName which is the local computer site
and so always is false.

This email and any attached files are confidential and copyright protected. If 
you are not the addressee, any dissemination of this communication is strictly 
prohibited. Unless otherwise expressly agreed in writing, nothing stated in 
this communication shall be legally binding.

The ultimate parent company of the Atkins Group is WS Atkins plc.  Registered 
in England No. 1885586.  Registered Office Woodcote Grove, Ashley Road, Epsom, 
Surrey KT18 5BW. A list of wholly owned Atkins Group companies registered in 
the United Kingdom can be found at 

Consider the environment. Please don't print this e-mail unless you really need 

Other related posts: