One thing I dislike about ConfigMgr is that there isn\u2019t a SQL view I can easily reference to determine what boundary or boundaries my clients are part of. IP subnet and AD site boundaries are easy to do, but what about those IP range based boundaries.<\/p>\n
With the help of our Microsoft PFE, I now have a solution. He sent me a query that used two views\/tables I was not aware of and I was able to modify his query and use it to build out a custom table.<\/p>\n
In order to determine if a system falls within a boundary, you need to takes its IP address and see if it falls within the boundary\u2019s range. This is done using numerical value of the IP address and the numerical values of the start and stop IP address of the range. Luckily, this data can be found in the ConfigMgr database so you do not have to manually calculate these values. System_IP_Address_ARR stores the IP address numerical value and BoundaryEx stores the numerical value of the start and stop IP addresses of the IP range.<\/p>\n
Again, with the help of our Microsoft PFE, I was able to create a query the lists out all the ResourceIDs and their associated BoundaryIDs regardless of type of boundary. I have taken this query, changed it to dump into a table and then used a schedule job to refresh the data on a daily basis.<\/p>\n