WMI Filtering

[FN-GM]

Hi,

 

I am trying to get a user policy called "Windows XP" to only apply to windows XP.

 

I am using this code on the WMI attached to the policy.

 

select * from Win32_OperatingSystem where Version like "5.1%" and ProductType = "1"

 

But the policy doesn't apply when i log onto a Windows XP machine, can anyone tell me why please? I am in work first thing tomorrow so need to know by then

 

Thanks

Edited February 5, 2010 by FN-GM

[SYNACK]

http://www.edugeek.net/forums/windows-7/48318-lockdown-windows-7-a.html#post443702

http://www.edugeek.net/forums/windows-7/47474-windows-7-0-gpo-new-policy-scratch-customise-old.html#post435441

http://www.edugeek.net/forums/windows-server-2008/23961-roaming-profiles-2008-how-do-you-do.html#post231122

[FN-GM]

Root\CimV2; Select * from Win32_OperatingSystem where Caption = "Microsoft Windows XP Professional"

 

Im sure i tried that and it still didnt apply.

 

EDIT:

 

Do you need Root\CimV2; in front of it?

 

If it does work what code will i need for a policy to apply to a terminal session on Server 2008?

 

Thanks

Edited February 5, 2010 by FN-GM

[Kitkatninja]

I've uploaded a screen shot of the wmi filter that we use and where we've applied it. The GPO that the WMI filter is applied to is attached to one of our user OU's and not the OU where the PC is (not sure if that makes any difference, but that's the way we're using them).

 

-Ken

[Kitkatninja]

This is a good site for WMI Filters.

 

-Ken

[FN-GM]

I've uploaded a screen shot of the wmi filter that we use and where we've applied it. The GPO that the WMI filter is applied to is attached to one of our user OU's and not the OU where the PC is (not sure if that makes any difference, but that's the way we're using them).

 

-Ken

 

Thats the same code as above isnt it? That simply failed to work.

[SYNACK]

Are you sure that the policy itself is setup correctly and not locked off by permissions or inheritance or something as that WMI query works for us. Are you sure that the "Windows Management Instrumentation" service is running on the clients and that the policies have all been updated via a gpupdate /force

[FN-GM]

I found what the problem was. It was the Mandatory profile causing the policies not to apply.