You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Home > 120: Getting Started with PolicyPak (Misc) > Knowledge Base > 02: Tips, Tricks and FAQs > 04: How can I use Item Level Targeting to specify a specific Windows 10 build and/or LTSC/LTSB?
04: How can I use Item Level Targeting to specify a specific Windows 10 build and/or LTSC/LTSB?
print icon

To target a specific Windows 10 BUILD, you would start out by using the Operating System item and selecting Windows 10.
Then you would also immediately select EITHER:

  1. WMI Query or
  2. Registry match.

 

If you choose WMI Query to detect the build number…

Then you would enter the following in the Query field

SELECT * FROM Win32_OperatingSystem WHERE BuildNumber = "15063"

This would select Windows 1703 which is that build number.

 

Warning: Note that you want to place a WHOLE number and not a number with decimal places. The BUILDNUMBER field is actually NOT a numeric value, but a STRING value and must match exactly.

If you choose REGISTRY Query to detect the build number…

Search for the following item in the Registry..

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion | CurrentBuildNumber

 

Then use the Registry Match item as follows for a specific BUILD number.

 

Other build numbers you can use are:

10586 Windows 10, version 1511
14393 Windows 10, version 1607
15063 Windows 10, version 1703
16299 Windows 10, version 1709
17134 Windows 10, version 1803
17763 Windows 10, version 1809

How to Query for Minor Build Numbers…

From time to time, you might want to target a machine with an unusual build number.

For instance, Windows 1809 had two revisions.. with the same build ID of 17763.
The original shipping version (which was pulled from Microsoft due to quality concerns) and then the final build which was broadly deployed.

Each of these Windows 1809 builds has the BUILD number of 17763, but has a “minor version” of .1 for the first release and .253 for the second release.
You can see examples of the first and second Windows 1809 releases in these two screenshots.

First release of Windows 1809 build 17763…

 

Second release of Windows 1809 build 17763….

The Value you want to match with an ILT Registry Match is…

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion | UBR 
UBR stands for Update Build Revision.

This Item Level Target expresses:

When Machine is Windows 10 AND

  • When build is 17763 (Windows 1809) AND
  • When build’s UBR is .1 (first version of 1809).

 

How to Query for CB/CBB vs. LTSB/LTSC …

Additionally, if you wanted to be specific and target LTSB/LTSC builds of Windows 10, you use a WMI query filter which would specify

SELECT OperatingSystemSKU FROM Win32_OperatingSystem WHERE OperatingSystemSKU = 125

Or, if you want to target CB/CBB builds…

SELECT OperatingSystemSKU FROM Win32_OperatingSystem WHERE OperatingSystemSKU = 4

Example…

 

Feedback
4 out of 5 found this helpful

scroll to top icon