Package Filters
  • 20 Mar 2020
  • 6 Minutes To Read
  • Print
  • Share
  • Dark
    Light

Package Filters

  • Print
  • Share
  • Dark
    Light

Package filters are used in packages to filter entitlements, or determine conditions which need to be met to make the package available.

Agent deployment mode

Returns yes if the agent is in deployment mode, this is used when using deployments.

Value
Type Agent deployment mode
Enabled Yes,No
Agent required Yes

Agent version

The agent version can be used to filter based on the running agent on the device.

Value
Type Agent version
Compare Equal, Not equal, Greater than, Less than
Version 1.0.0.0
Agent required Yes

Context

Context can be used to filter based on any context the identity is currently in. You could use this to make a package available only to a specified context for example.

Value
Type Primary Context
Context MY_context
Primary If the context should be a primary context. Primary context is determined by the priority field on contexts.
Matches Yes, No
Agent required No

Device FQDN

Device Fully Qualified Domain Name (FQDN) can be used to filter devices based on domain name for example.

Value
Type Device FQDN
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value DEVICE.domain.net
Agent required Yes

Device name

Device name can be used to filter the collection to only include devices which start with a certain string for example. If your devices have names that start with a certain tag that identifies the department for example, you can easily use this filter to create a collection.

Value
Type Device name
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value DEVICE
Agent required Yes

Free disk space

With the free disk space filter, a check can preformed for example on an install or copy action so verify that the required disk space is available.

Value
Type Free disk space
Path The path where the check should be performed, this will also work on devices that are mounted as directory
Compare Equal, Not equal, Greater then, Less then
Size The size to check
Unit The unit of the size
Agent required Yes

System manufacturer

System manufacturer can be used to filter the system to only include devices manufacturer which start with a certain string for example. If your devices have names that start with a certain tag that identifies the manufacturer for example, you can easily use this filter to create a collection.

Value
Type System manufacturer
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against
Agent required Yes

System model

System model can be used to filter the collection to only include model which start with a certain string for example. If your devices have names that start with a certain tag that identifies the model for example, you can easily use this filter to create a collection.

Value
Type System model
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against
Agent required Yes

Directory exists

Directory exists can be used to only show this package when a certain directory does or does not exist on the device.

Value
Type Directory exists
Path C:\Program File\
Exists Yes, No
Agent required Yes

File exists

File exists can be used to only show this package when a certain file does or does not exist on the device.

Value
Type File exists
File C:\somefile.txt
Exists Yes, No
Agent required Yes

File size

File size can be used to only install a package for example if the installed version has a different size.

Value
Type File size
File C:\somefile.txt
Compare Equal, Not equal, Greater then, Less then
Size The size to check
Unit The unit of the size
Agent required Yes

File version

The file version can be used to filter based on the file version.

Value
Type File version
Compare Equal, Not equal, Greater than, Less than
Version 1.0.0.0
Agent required Yes

Path exists

Path exists can be used to only show this package when a certain path (file or directory) does or does not exist on the device.

Value
Type Path exists
Path C:\Program File\
Exists Yes, No
Agent required Yes

Environment variable exists

Environment variable exists can be used to determine if a certain environment variable does or does not exist on the device.

Value
Type Environment variable exists
Name MY_VAR
Exists Yes, No
Agent required Yes

Environment variable value

Environment variable value can be used to check on the value of a certain environment variable.

Value
Type Environment variable value
Name MY_VAR
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with, Greather than, Less than
Value My Value
Agent required Yes

Platform

Platform is a filter to catch all devices running on a certain platform. Based on the match value you can either include or exclude devices from the collection. This allows you to make your package available to only certain platforms.

Value
Type Platform
Value Windows
Matches Yes, No
Agent required Yes

Platform architecture

Platform architecture allows you to filter devices on their bitwise platform (32-bit, 64-bit).

Value
Type Platform architecture
Value x86, x64
Matches Yes, No
Agent required Yes

Platform version

Platform version allows you to filter devices based on the version of the operating system. This allows you to create packages that are only available on certain Windows versions.

Value
Type Platform version
Compare Equal, Not equal, Greater than, Less than
Platform Windows (Custom), Windows Server 2003, Windows Vista/Server 2008, Windows 7/Server 2008 R2, Windows 8/Server 2012, Windows 8.1/Server 2012 R2, Windows 10/Server 2016
Agent required Yes

MSI installed

Allows you to detect if a MSI is installed or not. Useful for MSI install actions to prevent unnecessarily install attempts.

Value
Type MSI installed
Product code The product code of the MSI
Exists Yes, No
Agent required Yes

Windows App installed

Allows you to detect if a Windows App is registered for the current user.

Value
Type Windows App installed
Package Family Name Package Family name that identifies the Windows App which is used for the detection
Exists Yes, No
Agent required Yes

Windows App installed version

Allows you to detect if a specific version of the Windows App is registered for the current user.

Value
Type Windows App installed version
Package Family Name Package Family name that identifies the Windows App which is used for the detection
Compare Equal, Not equal, Greather than, Less than
Version Version of the Windows App to compare against
Agent required Yes

Windows App staged

Allows you to detect if a Windows App is staged on the current device.

Value
Type Windows App staged
Package Family Name Package Family name that identifies the Windows App which is used for the detection
Exists Yes, No
Agent required Yes

Windows App staged version

Allows you to detect if a specific version of the Windows App is staged on the current device.

Value
Type Windows App staged version
Package Family Name Package Family name that identifies the Windows App which is used for the detection
Compare Equal, Not equal, Greather than, Less than
Version Version of the Windows App to compare against
Agent required Yes

Process exists

Process exists can be used to filter the entitlement based on the existence (or absence) of a process.

Value
Type Process exists
Name My_Process
Exists Yes, No
Agent required Yes

Registry key exists

Registry key exists can be used to filter based on the existence of a package based on the existence (or absence) of a registry key.

based on the existence

Value
Type Registry key exists
Key HKLM\My\Key
Exists Yes, No
Agent required Yes

Registry value

Registry value can be used to filter based on the value of a certain registry entry.

Value
Type Registry value
Key HKLM\My\Key
Name My_Value_Name
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with, Greather than, Less than
Value my value
Agent required Yes

Registry value exist

Registry value exist can be used to filter based on the existence of a value.

Value
Type Registry value exist
Key HKLM\My\Key
Name My_Value_Name
Exists Yes,No
Agent required Yes

Service exists

Service exists can be used to filter based on the existence (or absence) of a certain Windows service.

Value
Type Service exists
Service Windows Update
Exists Yes, No
Agent required Yes

Service state

Service state can be used to filter based on the current state of a Windows service.

Value
Type Service state
Service Windows Update
Compare Equal, Not Equal
State Running, Stopped, Paused
Agent required Yes
Was This Article Helpful?