You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.

06: How do I make an Item Level Target for Server 2016 or Server 2019 (on-prem, MDM or PolicyPak Cloud?) ?

Depending on the editor you are using, your ILT editor may show one of EITHER these two:

In BOTH cases, they produce the same Item Level Targeting Filter in XML, like this:

In this way, there is no distinction between 2016 and 2019 servers. This is not a PolicyPak bug, because PolicyPak is using the underlying Group Policy Preferences Item Level Targeting editor and evaluation.

So you can have a SECOND item using Item Level Targeting to also check for the ReleaseID, which is the “major build number” in Windows server.

So.. the ILT would be:

– SERVER = 2016 / 2019
REGISTRY MATCH == Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ReleaseId

You would use 1809 to match for Server 2019 and
You would use 1607 to match for Server 2016.

Therefore you can match on Server 2016 when you make your ILT exactly like this…

And match on Server 2019 like this..

Additionally, if you wanted to limit your targeting, say, to only affect SERVER CORE installations, you can use this REGISTRY match.

hklm:/software/microsoft/windows nt/currentversion/installationtype =  "Server Core"

Note: If you prefer to target the CurrentBuild instead of the ReleaseID, you can use the following technique.

Locate the CurrentBuildNumber using the registry.

Then set your ILT to something similar to below:

"Windows 10" and BuildNumber <= 17704

  • 706
  • 27-Sep-2019