In many networks, subnets and IP address information reflect organizational distinctions, such as geographical location or job function. If IP address organization coincides with your needs, consider using this information to create and maintain parts or all of your System Tree structure by setting IP address sorting criteria for such groups.
This functionality has changed in this version of ePolicy Orchestrator, which now allows for setting of IP sorting criteria randomly through the tree — you no longer need to ensure that the child group’s IP address sorting criteria is a subset of the parent’s (as long as the parent has no assigned criteria).
Once configured, you can sort systems at agent-server communication, or only when a sort action is
manually initiated.
Please know that IP address sorting criteria should not overlap between different groups. Each IP range or subnet mask in a group’s sorting criteria should cover a unique set of IP addresses.
If criteria does overlap, which group those systems end up in depends on the order of the subgroups on the Groups tab.
Tag-based sorting criteria
In addition to using IP address information to sort systems into the appropriate group, you can define sorting criteria based on the tags assigned to systems.
Tag-based criteria can be used with IP address-based criteria for sorting. Group order and sorting
To provide additional flexibility with System Tree management, you can configure the order of a group’s subgroups, and therefore the order by which they are considered for a system’s placement during sorting. When multiple subgroups have matching criteria, changing this order can change where a system ends up in the System Tree.
Additionally, if you are using catch-all groups, they must be the last subgroup in the list.
Tag-based sorting criteria
In addition to using IP address information to sort systems into the appropriate group, you can define sorting criteria based on the tags assigned to systems. Tag-based criteria can be used with IP address-based criteria for sorting.
Group order and sorting
To provide additional flexibility with System Tree management, you can configure the order of a group’s subgroups, and therefore the order by which they are considered for a system’s placement during sorting. When multiple subgroups have matching criteria, changing this order can change where a system ends up in the System Tree.
Catch-all groups
Catch-all groups are groups whose sorting criteria is set to All others on the Sorting Criteria page of the group. Only subgroups at the last position of the sort order can be catch-all groups.
These groups receive all systems that sorted into the parent group, but did not sort into any of the catch-all’s peers.
Additionally, if you are using catch-all groups, they must be the last subgroup in the list.