I have a collection (departments), which is basically a folder/group for a bunch of sub-collections(finance, hr, etc). I use the departments collection as a way to target all departments for org wide software deployment. This works great for advertisements. Since the actual departments collection contains no clients, only sub collections, I can't always target this collection for other purposes. For example, I want to create a laptop collection which is limited to all the departments. However, if I simply limit it to the Departments collection it will contain nothing because it dosn't pick up the sub-collections. Do I need to have a collection wmi queries everywhere with a where clause pointing to a particular parentid collection or parent collection linking to a list of sub-colleciton id's? I'm hoping this isn't the case just because I wouldn't want to have maintain this query whenever new sub-collections are added. What is the best way to handle collections/sub collections? Thank you.

Why don't you just add a WQL query to the departments collection (that's currently empty) so that it contains all members of all subcollections?Torsten Meringer | http://www.mssccmfaq.de

So kind of like I mentioned where you have a query linking to all collections that have a particular parent collection id?

Let's say the child collections are using OU criteria ... Coll1 -> like %HR%, Coll2 -> like %Fi% etc So you could use the following WQL criteria for the departments collection: is like %HR% or is like %Fi% or ... etc. You get the idea.Torsten Meringer | http://www.mssccmfaq.de

I think this is what you are after: http://blog.configmgrftw.com/?p=76.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

I think this is what you are after: http://blog.configmgrftw.com/?p=76. Jason | http://blog.configmgrftw.com | Twitter @JasonSandys That works yep! Thanks to both of you