Context Filters
  • 26 Oct 2021
  • 7 Minutes to read
  • Dark
    Light
  • PDF

Context Filters

  • Dark
    Light
  • PDF

Context filters are applied to contexts of user and/or device data to provision the dynamic membership of a context.

Agent available

Check if a compatible agent is running, allowing local actions to be executed on the device.

Value
Type Agent available
Available Yes, No
Agent required Yes

Agent version

The agent version can be used to filter based on the running agent on the device. You could use this for rolling out a new agent automatically when the reported agent version on the device is not the latest for example.
Another example could be to create a collection where you specifically want all devices that are running an out of date version.

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

Context

Check if the target is part of a context.

Value
Type Context
Compare Contains, Doesn’t contain
Context Select the targeted context

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

Device membership

Check whether or not the device is part of device collection.

Value
Type Device membership
Compare Contains, Doesn’t contain
Device collection Select the targeted device collection

HTTP header exists

This let's you filter based on the existence (or absence) of a named HTTP header. This can be used when a known proxy sets a unique header and you want to filter based on it.

Value
Type HTTP header exists
Name Name of header
Exists Yes, No
Agent required No

HTTP header value

Not unlike the 'HTTP header exists' filter, this goes one step further and lets you filter based on it's value.

Value
Type HTTP header value
Name Name of header
Compare Equal, Not Equal, Contains, Doesn't contain, Starts with, Ends with
Value Value to check for
Agent required No

Subnet

The subnet filter is pretty powerful. It doesn't require an agent, this can be used for every device. The source setting allows you to specify which reported IP address is taken into account.

Value
Type Subnet
Network IP address
Subnet Subnetmask
Source
  • Forwarded
    This takes the forwarded IP address (in case of a proxy) that has been set in the X-Forwarded-For header
  • Direct
    Direct takes the IP address that is actually communicating with the Liquit backend. This could be a proxy
  • Agent
    This always takes the agent IP address
  • Remote client
    Use the IP address of the remote client in case of remote desktop session
Matches Yes, No
Agent required No

System manufacturer

The ​System manufacturer allows you to select on the manufacturer value of the device.

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

System model

The model of the connected device.

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

User city

Compares the city attribute of the user logging in.

Value
Type User city
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User company

Compares the company attribute of the user logging in.

Value
Type User company
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User country

Compares the country attribute of the user logging in.

Value
Type User country
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User department

Compares the department attribute of the user logging in.

Value
Type ​User department
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User description

Compares the description attribute of the user logging in.

Value
Type ​​User description
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User display name

Compares the display name attribute of the user logging in.

Value
Type ​​User display name
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User fax

Compares the fax name attribute of the user logging in.

Value
Type ​​User fax
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User job title

Compares the job title attribute of the user logging in.

Value
Type ​​User job title
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User mail

Compares the mail attribute of the user logging in.

Value
Type ​​User mail
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User membership

Checks if the user is a member of a group.

Value
Type User membership
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Identity Let's you select a group

User mobile

Compares the mobile attribute of the user logging in.

Value
Type User mobile
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value Mobile

User name

Compares the name attribute of the user logging in.

Value
Type ​​User name
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User postal code

Compares the postal code attribute of the user logging in.

Value
Type ​​User postal code
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User street

Compares the street attribute of the user logging in.

Value
Type ​​User street
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

User telephone

Compares the telephone attribute of the user logging in.

Value
Type ​​User telephone
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value The value matched against

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 capture all Windows devices or, based on the Matches setting, all Non-Windows devices.

Value
Type Platform
Value Windows, macOs, Linux, Android, iOs, Windows Phone, Unkown
Matches Yes, No
Agent required No

Platform language

Check if the platform of the device is installed/configured with the specified language. Language of the platform can be checked within device diagnostics for the local device or viewed within an inventory view on the device.

Value
Type Platform language
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value ISO 639-1 Language code identified by the platform for example: en-US for English (United States)
Agent required Yes

Platform type

Platform is a filter to catch all devices running on a certain platform type. Based on the match value you can either include or exclude devices from the collection. This allows you to capture all Workstations or Servers.

Value
Type Platform type
Value Workstation, Server
Matches Yes, No
Agent required Yes

Platform user language

Check if the platform of the currently logged on user is installed/configured with the specified language. Language of the platform can be checked within user diagnostics for the local device.

Value
Type Platform language
Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with
Value ISO 639-1 Language code identified by the platform for example: en-US for English (United States)
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 separate contexts based on the Windows version that the devices are running.

Value
Type Platform version
Compare Equal, Not equal, Greater than, Less than
Platform Windows (custom), Windows Client, Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10, Windows 11, Windows Server, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022
Agent required Yes

Was this article helpful?

What's Next