WMI Filter Best Practice

are there any do`s and dont`s? when to use and when not?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

In what context?  Group Policy?
WMI Filters are best used by Group Policies
U can define if particular condition is True, apply GPO else skip.

WMI filters are best suited when you have single OU containing multiple objects (Say WinXP\ win 7 \win8 computers) underneath multiple OUs, in that case it is easy to put GPO on top level OU and apply WMI filter on GPO to apply specific policy to specific objects
For Ex: specific registry you want to apply on to windows XP machines only you can apply policy with registry settings which will apply to WinXP machines only based on WMI query

Do not use multiple WMI filters \ queries in single GPO, it will hamper performance because every WMI filter will be evaluated against condition and if it proved to be true, then only GPO will apply and this may increase startup \ logon time

As far as possible you should keep your GPO structure simple and use WMI filters only when it is really required, there are other options also available which you can explore like security filtering.

There are some tools available to test WMI filters before you deploy it in production which will help you to make WMI query accurate

finally when you cannot segregate your AD objects in separate OUs due to some limitations and you want to apply specific policy to specific objects based on matching criteria, WMI filters are best friend.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
There aren't really best practice processes for WMI, but there are some gotchas that can prevent them working the way you expect, which are described here:
Gotcha #1: What does that value look like?
Gotcha #2: What’s the property name I need?
Gotcha #3: What does the operator look like?

The one don't I try to avoid is using the Win32_Product class to query installed software
How to NOT Use Win32_Product in Group Policy Filtering

Try and always use the forward only enumerator, as it is a bit faster

I also don't use CIM_DataFile as it can be very slow, and the syntax is very confusing to get right.

And lastly I would say test, test, test with as many scenarios you can.


One more thing with GP preferences you can use item level targeting more effectively rather than WMI filters.
GP preferences item level targeting use WMI queries only but with more control.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.