This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 1%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMA%3C/text%3E%3C/svg%3E)
Hello, We have the Boundaries created with IP Subnets and the Range is added to AD Site and the Boundaries are mapped to Boundary Group and BG's are mapped to Site System. For example, if we have 100 devices, 70 are getting Boundary Groups and rest 30 are showing empty. Client is healthy on those devices. Please help in this case. We need to get the Boundary Group for the rest of the devices as well.
First only use IP ranged. Convert everything else to them. that will ensure that all clients talk correctly to ConfigMgr.
But it is not feasible in a environment with approx. 50K devices. Usually Network team creates IP subnets and it will be synced in AD. This is where SCCM pulls the data. So, it there any other way?
It's not recommended to use IP Subnets, check this article for details: https://home.memftw.com/ip-subnet-boundaries-still-evil/
@Manoj Anukonda Environments much larger than 50k use IP ranges. IP Ranges are the only boundary type that will be 100% correct all of the time. All others relay on outside items to be correct. Namely IP subnet masks to be correct.