PENDING Creating collections based on boundary membership

[Harshit Pandey]

I have a requirement to use boundary or boundary group membership to automatically move devices into collections. While our Active Directory (AD) sites are configured correctly, creating collections based on specific AD sites would require constant updates to the queries whenever sites are added or modified. For instance, adding or changing an AD site would typically necessitate updating the boundaries to ensure proper coverage. However, this approach also requires manually editing related collections to reflect these changes. Instead, by creating collections based on boundary groups or boundaries, we can ensure that they are automatically updated whenever boundaries are modified, eliminating the need for manual adjustments to the collections.

 

[Garth]

I have a requirement to use boundary or boundary group membership to automatically move devices into collections. While our Active Directory (AD) sites are configured correctly, creating collections based on specific AD sites would require constant updates to the queries whenever sites are added or modified. For instance, adding or changing an AD site would typically necessitate updating the boundaries to ensure proper coverage. However, this approach also requires manually editing related collections to reflect these changes. Instead, by creating collections based on boundary groups or boundaries, we can ensure that they are automatically updated whenever boundaries are modified, eliminating the need for manual adjustments to the collections.

It is generally recommended to use IP ranges and not AD site for Boundaries.

Are you trying to use the collection for reporting purposes???