Close Menu
    Facebook X (Twitter) Instagram
    Sunday, May 18
    X (Twitter) LinkedIn
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»configmgr»Configuration Manager report for a list of clients missing boundaries

    Configuration Manager report for a list of clients missing boundaries

    Eswar KonetiBy Eswar KonetiMay 08, 11:04 pm2 Mins Read configmgr 7,236 Views
    Share
    Facebook Twitter LinkedIn Reddit

    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 extend the MOF inventory (client settings, hardware inventory) for getting the client boundary group details.

    With the release of the configuration manager current branch 2002, you no longer required to extend the MOF. Boundary group information is now available to help you troubleshoot the devices with site assignment/content location issues.

    With this release, we can now create a collection for a list of clients that fall into specific boundary groups and also create a collection for a list of clients that are missing the boundary groups.

    2020-05-08_20h25_02

    For the collections, you can refer these blog posts http://eskonr.com/2020/04/how-to-create-a-collection-based-on-boundary-group-for-client-assignment-and-content-troubleshooting/ and https://www.systemcenterdudes.com/sccm-powershell-collection-boundary-groups/

    Now, in this blog post, we will see how to create/get a report for you to identify the list of clients from specific collections that are missing the boundaries/boundary groups.

    I have created a report for you (this works only with configuration manager 2002 and later and also make sure your clients are upgraded to 2002 client) and is available in GitHub for your download.

    Download the report from GitHub, upload it to your SSRS, change the data source, and run the report.

    Clients missing boundaries: you need to go back and review your boundaries and boundary groups.

    If your clients are running lower than 2002 then you don't see the data in the report because the boundary group info is enabled only in clients 2002 and later.

    If your boundaries and boundary groups are configured perfect and all your clients running 2002 and later, you will see the following screen ( Don't look at the title as it has been changed later)

    I hope you find the post useful!

    The following are the few custom reports created for earlier versions of the configuration manager builds.

    http://eskonr.com/2019/12/how-to-find-configmgr-client-boundary-and-boundary-group-details-based-on-boundary-group-caching/

    http://eskonr.com/2017/09/sccm-configmgr-report-for-boundary-group-relationships-with-fallback-sites/

    http://eskonr.com/2013/12/sccm-2012-ssrs-report-site-servers-and-its-assigned-boundary-information/

    http://eskonr.com/2018/01/sccm-report-for-missing-boundaries-and-troubleshooting/

    For more information about boundary groups, please refer https://docs.microsoft.com/en-us/configmgr/core/servers/deploy/configure/boundary-groups#bkmk_show-boundary


    Boundaries Boundary Groups Collection configmgr content troubleshooting missing boundaries report SCCM sccm report SQL Report SSRS
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    Optimize Your Intune Workflow with a Powerful Browser Extension

    March 22, 10:39 am

    Migrate Microsoft 365 Updates from SCCM/MECM to Intune for Co-Managed Devices

    February 11, 9:50 pm

    How to detect the source of registry key modifications on windows devices – Intune

    November 21, 8:49 pm

    3 Comments

    1. Ali on July 31, 2020 2:17 AM

      Receiving this error when trying to upload this to “SQL Server Reporting Services 2017 Version 14.0.600.1453:

      An error has occurred.
      The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas. Details: Invalid character in the given encoding. Line 773, position 77.

      Schema is 2016 and looks like your report is configured for 2008. Any thoughts?

      Reply
    2. Tom on May 9, 2020 4:17 AM

      Hello when I try to open the report file from GitHub I get:

      DTD is prohibited in this XML document.

      Any ideas? Thanks.

      Reply
      • Eswar Koneti on May 10, 2020 2:44 AM

        Hi Tom,
        i can download the file by clicking on the file, on the right side you see raw, click on it and save the file as .rdl. You can follow this guide https://github.community/t5/How-to-use-Git-and-GitHub/How-can-I-checkout-or-download-single-file-from-GitHub-repo/td-p/8554
        I know that, downloading single file from Github is not easier if you compare with technet gallary or other download locations.

        Thanks,
        Eswar

        Reply

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2024 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.