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:
- Build better pilot rings for Updates with MEM Intune - June 13, 2021
- Automatic Intune Documentation evolves to Automatic Microsoft 365 Documentation - May 25, 2021
- Build better pilot rings for Updates with MEMCM - March 14, 2021