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(144, 11%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELD%3C/text%3E%3C/svg%3E)
Hi,
Can someone confirm how the below configuration is expected to work, as far as clients are concerned:
approx. 200 IP subnets exist in the environment - however these are not listed in AD Sites and Services - Subnets
approx. 50 of those have been added as SCCM boundaries
1 AD Site exists in AD. This has been added as SCCM boundary
Sample client is in the same AD Site as the AD Site boundary
AD Forest Discovery is configured only to sync Sites, not Subnets
We have a client that has an IP that is NOT in any of the manually added IP Range boundaries. CMtrace and LocationServices.log is reporting it is not in a boundary group and Config. Mgr is not managing it anymore.
So my question is, if a device has an IP who's subnet is not added as a Boundary, but is in the same AD Site as the AD Site Boundary, why is it reporting that it's not in a Boundary Group? Is the AD Site Boundary a catch-all, or a discard-all?
Both the IP ranges and AD Site that are Boundaries do belong to a Boundary Group.
Thanks
PS: Because of this we believe devices are either;
going to the internet for updates if the "go to internet if no boundary group" option is enabled
not installing any updates if the "go to internet if no boundary group" option is disabled
First is is recommend that you only use IP Ranges for all of your boundaries.
Next you say that not all subnets are listed within AD, what makes you think that this computers' subnet is within that AD sites?
Thanks for the quick reply.
There's only one site listed in AD
No subnets have been added to AD
Some subnets have been manually added as SCCM Boundaries (as IP ranges)
I know SCCM has the concept of an actual 'Subnet' for a Boundary, this isn't what I mean.
In this particular environment, they have loads of subnets across the LAN, and the ones that are added in SCCM are as individual /24 IP ranges, even contiguous ones. This is what I've inherited!
No subnets have been added to AD
This is the key detail here. If your AD site has no subnets added to it, then nothing falls within the scope of that AD site and thus no ConfigMgr clients will be detected as part of a boundary based on this AD site either.
Hi,
Hope everything goes well. May we know the current status of the question?
Are Garth and Jason's answer helpful to you? If it is helpful, please accept answer. It will make someone who has the similar issue easily find the answer. If you have any other issues, please don't hesitate to let us know.
Thanks and have a nice day.
Thanks and regards,
Amanda