Item level targeting is great and all, it works well for granular targeting. But with Item Level Targeting you are limited to only Active Directory components.
WMI or Windows Management Instrumentation consists of a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification.
What if I told you you could set up policies that that allow you to target specific users, specific user names, specific hardware, and specific software. Even specific hardware types. You could deploy hardware specific drivers on your domain using WMI flitering.
It’s actually pretty slick, and far superior to anything that SNMP can offer. It is a very powerful tool set for a Sys Aadmin. The level of control for WMI filtering is absolutely amazing and robust. But is it secure? Well that depends, it can be, if you follow best practices there is no reason it shouldn’t be.
WMI filters are similar to SQL queries, for example…
select Version, ProductType from Win32_OperatingSystem where ((Version like "10%") and (ProductType = 1))
The above version 10 followed by the wildcard character will select Windows 10 and Server 2016 operating system versions. ProductType = 1 means the desktop OS version, where as type of 3 would mean the server OS version. Finally ProductType = 2 means that the machine is a Domain Controller.
select Version, ProductType from Win32_OperatingSystem where ((Version like "6.1%") and (ProductType = 1))
The above is for Windows 7.
select Version, ProductType from Win32_OperatingSystem where ((Version like "6.3%") and (ProductType = 3))
Finally the last one is Server 2012 R2.
Note that the name space that this is available in, is root\CIMv2.
If you want to find and query WMI you can use the official tool available from Microsoft, it’s called The WMI Code Creator tool and it’s available here. If the link is dead just search for it. An alternative to this is the NirSoft SimpleWMIView available here, and Wmi Explorer available here.
WMI Code Creator looks something like the following. It allows you to browse all the WMI possibilities and search for property values of WMI classes. For obvious reasons you will need the .NET framework installed on your machine.
Creating a WMI Filter is simple. Open up your Group Policy Management application, expand your domain and at the bottom you should have a folder named WMI Filters. In this folder you can also see a collection of WMI Filters and which policies they are applied to.
Right click this folder and select New…
Give your Filter a name and Description, then click Add.
Finish by clicking OK and Save. You have now created a WMI Filter for Server 2016 all versions.
Now you need to apply the filter to a policy. Locate a policy in your Manager, and in the right pane on the bottom under WMI Filtering now you can select the filter you just created.
That’s pretty much it, you can play around with the WMI Code Creator and see that you can do some very granular filtering with this. You can create filters based on OS, CPU, Disk drives anything that you can think of. This is a very powerful tool and if you’re familiar with SQL queries you should have no trouble coming up with some complex filters.
Specific Host Name:
root\CIMV2 – Win32_ComputerSystem – DNSHostName = ‘YourHostname’
As a side note if you are a C# .NET developer you can also benefit from WMI using the Microsoft.Management.Infrastructure namespaces in Visual Studio. This allows you to query Microsoft Operating System hardware and retrieve statistics from said machine.