Tech Community Live: Endpoint Manager edition
Jul 21 2022, 08:00 AM - 12:00 PM (PDT)

Management Insight - "Collections limited to All Systems or All Users"

%3CLINGO-SUB%20id%3D%22lingo-sub-2859415%22%20slang%3D%22en-US%22%3EManagement%20Insight%20-%20%22Collections%20limited%20to%20All%20Systems%20or%20All%20Users%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2859415%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fservices-hub%2Fhealth%2Fremediation-steps-configmgr%23collections-limited-to-all-systems-or-all-users%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERemediation%20steps%20for%20Configuration%20Manager%20management%20insights%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3CP%3EThe%20section%20mentioned%20in%20my%20subject%20doesn't%20make%20sense%20to%20me%2C%20is%20anyone%20able%20to%20clarify%3F%20As%20all%20collections%20must%20have%20a%20limiting%20collection%20and%20%22all%20systems%22%20is%20the%20only%20built%20in%20collection%20for%20devices%2C%20any%20collection%20you%20create%20must%20be%20limited%20to%20%22all%20systems%22%20whether%20directly%20or%20indirectly%20so%20if%20the%20data%20is%20inaccurate%20at%20that%20point%2C%20all%20collection%20data%20will%20be%20inaccurate.%3C%2FP%3E%3CP%3EIf%20this%20is%20not%20correct%2C%20give%20an%20example%20of%20a%20collection%20that%20you%20would%20not%20limit%20to%20All%20systems%20at%20some%20point.%3CBR%20%2F%3EEven%20if%20you%20create%20a%20collection%20to%20limit%20all%20future%20collections%20to%2C%20this%20initial%20collection%20must%20be%20limited%20to%20%22All%20Systems%22%20which%20as%20stated%20may%20not%20contain%20valid%20client%20information%20meaning%20all%20collections%20will%20contain%20invalid%20information.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2859415%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApp%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECM%20current%20branch%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGeneral%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

Remediation steps for Configuration Manager management insights | Microsoft Docs

The section mentioned in my subject doesn't make sense to me, is anyone able to clarify? As all collections must have a limiting collection and "all systems" is the only built in collection for devices, any collection you create must be limited to "all systems" whether directly or indirectly so if the data is inaccurate at that point, all collection data will be inaccurate.

If this is not correct, give an example of a collection that you would not limit to All systems at some point.
Even if you create a collection to limit all future collections to, this initial collection must be limited to "All Systems" which as stated may not contain valid client information meaning all collections will contain invalid information.


EDIT - my statement that "all systems" was the only built in collection was incorrect, "All Desktop and Server Clients" is also built in, so I have restricted most collections to this.  The only issue there is that any machine that doesn't show as having a client is now no longer included in any collection.  Fine for deployment collections, however where we had collections used for maintenance as in identifying pingable machines that had broken clients etc, I have had to create an "all devices without a client" limited to All Systems to use as a limiting collection for any of these type of collections.  It means the insight will never be clear, but at least there will only be one collection showing now.  

0 Replies