RELATED IDEAS
Device Collections based on Application, files and registry keys
Adding additional options for Device Collections such as Applications, files and registry keys can help administrators create more dynamic groups. Being able to quickly create a group based on a file found or registry key can help Admins and even security if needed.
-
-
-
-
-
-
- +1
1
MERGED
Filter on installed software
I would like to create device collections based on installed software. Therefore the Liquit agent has to gather information about installed software on the devices from time to time. With this feature we could deploy software update packages only ...
On Product backlog
Device Collections Based on WMI Queries / System Inventory
To support targeted deployments, we need the ability to build dynamic device collections based on system data collected via WMI queries.
This requires:
A central data warehouse storing device inventory
Regular sync of system properties (installed software, versions, OS build, hardware state, etc.)
Ability to create collections such as:
“All systems with Notepad++ installed”
“All devices running version X of software Y”
“All laptops with battery health < 40%”
This enables highly accurate and safe deployments.
Use Case 1: Targeted Software Updates (e.g., Notepad++)
We want to deploy a Notepad++ update only to systems where Notepad++ is installed.
Without WMI-based collections or inventory data, we must rely on workaround filters like “file exists”, which is functional but:
Not as reliable
Less scalable
Harder to manage at scale
Requires IT to force-install patches rather than offering controlled rollout