<div>
depneding on which programming language your script is executed in, this can be done in the script itself.<br />
Or alternatively, in Active Directory if you create OU's based on OS then put all the PC's with Windows 2000 in that OU and apply the GPO to only this OU.<br />
&nbsp;<br />

</div>


<div>
You can go through this, it has the details with example :<br />
<br />
<a href="http://computerperformance.co.uk/vbscript/wmi_filter.htm" rel="ugc">http://computerperformance.co.uk/vbscript/wmi_filter.htm</a><br />
<br />
However, as you mentioned that the script should run only if the OS is Windows 2000, for that below mentioned is the code.<br />
<br />
Root\CimV2; Select * from Win32_OperatingSystem where Caption = &quot;Microsoft Windows 2000 Server&quot;<br />
<br />
above mentioned script says that, Only target computers running Windows XP Professional will have this script running on it.<br />
<br />
Please let me know if you need further assistance on this.<br />
<br />
Regards,<br />
<br />
Vikas Shah
</div>


<div>
You can even go through this as well:<br />
<br />
<a href="http://technet.microsoft.com/en-us/library/cc779036.aspx" rel="ugc">http://technet.microsoft.com/en-us/library/cc779036.aspx</a><br />

</div>


<div>
Windows 2000 doesn't support WMI filters - it will ignore them and apply the GPO anyway. Do you have pre-2000 operating systems as well?<br />
<br />
If not, you could apply a filter such as:<br />
<br />
Namespace: root\CIMV2<br />
Select * from WIN32_OperatingSystem where Version&lt;5.1<br />
<br />
Version 5.1 is XP, so anything XP and beyond will not apply this GPO. The pre XP/2003 machines will ignore the filter and apply the GPO.<br />
<br />
You can create a WMI filter using GPMC (right click 'WMI Filters' | New)
</div>


<div>
For Windows 2000 the WMI filter is always ignored and the GPO is applied.<br />
So you could write a filter based on the build number, the build number of Windows 2000 is 2195 &nbsp;<a href="http://support.microsoft.com/kb/262255" rel="ugc nofollow">http://support.microsoft.c<wbr />om/kb/2622<wbr />55</a><br />
WMI filter would be <br />
SELECT * FROM Win32_OperatingSystem WHERE BuildNumber = 2195 <br />
The GPO will only apply if the WMI filter evaluates to TRUE. &nbsp;So for your XP, 2003, and Vista boxes it would be false and not apply.<br />
Thanks<br />
Mike<br />
&nbsp;<br />

</div>


<div>
Basically if you have pre-2000 operating systems as well as 2000 operating systems, WMI is not the way to go.<br />
<br />
If you only have a small number of machines, you could put them in a security group and apply security filtering to the GPO so that it only applies to this group on machines. Or if the current structure allows, you could segregate them into an OU and apply the GPO to this.
</div>


<div>
hmmm my filter should have come out as<br />
SELECT * FROM Win32_OperatingSystem WHERE BuildNumber = '2195'<br />

</div>


<div>
Don't get too complicated. &nbsp;Put all W2K computer in their own OU and apply the GPO to only that OU. &nbsp;Simple<br />
&nbsp;<br />

</div>


<div>
<div class="content wysiwyg-content">
I have a GPO that runs a script. &nbsp;The problem is I only want it to apply to Windows 2000 workstations or servers. &nbsp;Is there a way to createa WMI filter through GPMC to only apply if the OS is Windows 2000?
</div>
</div>


I have a GPO that runs a script.  The problem is I only want it to apply to Windows 2000 workstations or servers.  Is there a way to createa WMI filter through GPMC to only apply if the OS is Windows 2000?

WMI Filter for GPO

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.