The last best practice post was last February and contains information about a file and folder structure, which was tested and very useful for my clients. In this post I will explain the structure and naming convention we use for SCCM collections.
The important thing is, that a single collection should only have one function. This means it should be only, for example, for endpoint protection, client settings or application assignment. Then we should use a prefix which describes this functionality. That allows us to have a Pilot collection for windows updates(SUM Pilot) and one for application patch days(DSWP Pilot), because every name could only be used once.
Now we have created a Poster to print out and a PowerShell script to create the required folders.
Other Best Practice Blog Posts:
- Microsoft Purview Information protect predefined permission groups demystified - February 28, 2023
- Extending Microsoft Sentinel with important device data - January 30, 2023
- SOC Monitor wall – Develop your Video Wall Application (Part 2) - August 22, 2022
Ollon · October 22, 2019 at 16:28
What program did you use to create your poster or document with the icons of folders and etc…
Thomas Kurth · October 22, 2019 at 16:29
Very uncool…. just Word …
Best Practice: File and Folder Structure and Naming Convention for SCCM 2012 (with Poster) - Workplace Management Blog · February 12, 2016 at 12:53
[…] Configuration Manager Collection […]