Configuration Manager report for a list of clients missing boundaries

I did a few blog posts on the client's boundary and boundary groups for configuration manager build versions lower than 2002. In one of the blog posts, I talked about, how to identify the clients that are missing boundaries/boundary groups. For more information, please refer http://eskonr.com/2018/01/sccm-report-for-missing-boundaries-and-troubleshooting/ In all these blog posts, you would need to…
SCCM ConfigMgr Current Branch 2002 is available as in-console and baseline version

Microsoft releases the configuration manager production builds 3 times a year. The first production build for this year,which is configuration manager 2002 is released today and is available as an in-console update (fastring only for now) and baseline version. You can apply this update on sites that run version  1806,1810, 1906 or 1910 from the…
How to find ConfigMgr client boundary and boundary group details based on boundary group caching

Use boundary groups in Configuration Manager to logically organize related network locations (boundaries) to make it easier to manage your infrastructure. You must Assign boundaries to boundary groups before using the boundary group. Clients use a boundary group for: Automatic site assignment To find a site system server that can provide a service, including: Distribution…
SCCM Configmgr Report for Boundary group relationships with Fallback Sites

Beginning with configuration manager version 1702, clients use boundary groups to find a new software update point. You can add individual software update points to different boundary groups to control which site servers, a client can find the content or update scan. More information about boundary groups and its relationship with¬† software update point changes…