Collection Filters

Collection filters are applied to collections of devices to provision the dynamic membership of the collection.
Therefore, all filters here are device related.

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

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

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 in a collection.

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 separate collections 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 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

Subnet

The subnet filter is pretty powerful. It doesn't require an agent, thus 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, Direct, Agent, Remote
Matches Yes, No
Agent required No
  • 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
    Used the Remote-IP header.