Following the excellent PowerShell script that Benoit wrote to, I decided to rethink it a bit to help classify collections and ease implementation when a different group of users accesses SCCM. On top of that, the way folders for collections are designed, it helps implement a naming convention to keep things clear all across the SCCM console.The overall idea is to keep collections on a per needs basis. Having a collection that receives client settings, 1-2 applications, OSD and Windows Updates can lead to unplanned/accidental deployment or misconfiguration.
Sccm Query File Does Not Exist
With one collection per need, everything is well targeted.I also prefer to have collection for inventory to feed my deployment collections, instead of always recreating the queries.I’ve been using the same methodology for years at multiple clients site. When I go back after a few years, I know exactly what is going on, as they were using the naming and structure for all that time.The script creates 17 folders and 36 collections. The collections are set to refresh on a 7 days schedule. If a collection already exists, the script will return an error but will continue.Some of the collections come from. (Thanks, Benoit!) SCCM Powershell Script Collections Folders DownloadThe script can be downloaded from my.Be sure to rate the submission if you are using it. Full list of foldersCollections under each sub-folder will keep the naming convention.