Objective
To troubleshoot why selecting "Preview Impacted Devices" returns zero devices or fewer endpoints than expected when using Device Targeting Filters across any policy type in Automox.
Overview
Device Targeting Filters are available across all policy types in Automox—including Patch Policies, Worklets, and Required Software Policies. This feature allows administrators to refine which endpoints execute a policy based on attributes such as hostname, operating system version, IP address, device tags, or Active Directory OUs.
Problem / Symptoms
While configuring or editing a policy, Worklet, or Required Software Policy:
Device targeting filters are configured.
Clicking Preview Impacted Devices displays no matching devices or omits expected target devices.
Root Cause
Device Targeting Filters evaluate as a secondary filter scoped strictly to the Device Groups associated with the policy.
If the policy is not associated with any Device Group, or if it is associated with a group that does not contain the intended endpoints, the targeting filters evaluate against an empty or incomplete set of systems. This results in no matching devices during the preview regardless of policy type.
[ All Managed Devices ] ➔ [ Associated Device Group Scope ] ➔ [ Device Targeting Filters ] ➔ [ Preview Impacted Devices ]Resolution Steps
To resolve this issue and accurately target your endpoints:
Open the affected Patching Policy, Worklet, or Required Software Policy in the Automox console.
Navigate to the Scope / Associate Groups section.
Ensure the policy is associated with the Device Group(s) that contain your target endpoints.
Verify that your Device Targeting rules and conditions (e.g., Hostname Contains, Tag Equals) match your intended attributes.
Click Preview Impacted Devices again to confirm that the expected endpoints are now displayed.