Best Practice: Collection Structure and Naming Convention for ConfigMgr (with Poster)

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.


Download Poster

Download Script

Other Best Practice Blog Posts:

Follow me

Thomas Kurth

Principal Workplace Consultant at baseVISION AG
I’m a consultant, trainer and architect for workplace management and enterprise mobility projects with Microsoft Technologies in the past eight years. I love to push and design the modern workplace based on Windows 10, EM&S and O365 for my customers which is the only answer for the current security threats, agile world and the fast-changing business requirements of my customers. Important for me is to simplify and automate the operational processes, because there are the highest costs.

Thomas Kurth
Follow me

Latest posts by Thomas Kurth (see all)