Skip to content

Groups ​

Groups collect endpoints into reusable targets for jobs, variables, configuration profiles, alert rules, and reporting.

Open Groups from the top navigation.

Group Types ​

Ordyn supports groups that are scoped globally, to a tenant, or to a folder.

Groups can be:

  • static, where endpoints are assigned directly
  • dynamic, where endpoints match rules

Dynamic group rules can use endpoint properties and inventory fields. The query tab shows the configured rule logic.

Use collected inventory to match hardware, firmware, and security posture. An unknown value does not mean a setting is disabled; use null checks when looking for missing observations.

Intel AMT Rules ​

Use Intel AMT hardware support to build a stable group for assigning an AMT profile. Use provisioning and ownership state for operational views, such as devices requiring recovery.

Membership based on provisioning state changes during provisioning. Avoid assigning a required profile through a group whose rule removes the device as soon as provisioning succeeds.

Rules Based on Another Group ​

Use Endpoint group membership to include or exclude members of another group. Tenant groups can reference global groups or groups in the same tenant. A negative membership rule in a global group can also match devices from other tenants; add scope conditions when needed.

Group dependencies cannot form a cycle. Remove references before deleting a source group. If a source group's evaluation fails, dependent groups retain their membership until it can be evaluated successfully.

Operating System Rules ​

Choose Endpoint OS family for a broad operating-system group, OS name for a specific reported system, or Windows product type to distinguish clients from servers.

Network Rules ​

Network fields use the latest network configuration reported by the endpoint agent. IPv4 and IPv6 values share the same fields.

  • IP address matches an exact address assigned to any interface.
  • Subnet uses is in subnet and is not in subnet with CIDR input such as 192.168.10.0/24 or 2001:db8::/64.
  • Default gateway matches a default-route gateway reported for any interface.
  • DNS server matches a resolver address reported by a Windows endpoint. Linux endpoints do not report DNS servers for this rule.

IP address and subnet rules exclude loopback, unspecified, and multicast addresses. Link-local addresses can match. The is null operator matches endpoints without a valid reported value. Negative operators also match endpoints without a valid reported value; combine a negative rule with is not null when the endpoint must report the field.

Uptime Rules ​

Use Uptime with a duration to find devices that may need a restart. For disconnected endpoints, uptime reflects the last observation. Threshold-based membership can take approximately ten minutes to update.

Use Refresh dynamic group memberships in a job only when subsequent work needs updated membership immediately.

Use groups as targets ​

Assign jobs, configuration profiles, alert rules, or variable overrides to a group when its members should receive the same treatment. Review the group's endpoints before assigning disruptive work.

Exporting And Importing Dynamic Groups ​

Use Export JSON on a dynamic group or group folder, then Import in the destination environment. Map external references during review. Folder exports include nested dynamic groups and map references between those groups automatically.

Exports carry definitions, not membership history or assignments. Static groups are excluded. Configure assignments and environment-specific values after import.

An AI agent can retrieve the portable group and group collection formats through its configuration documentation tools.