Forgive me if this quesation has been posed under another thread, I've not seen any questions posed with this same issue. In SCCM 2007 Version: 4.00.6487.2000, I've created some new collections (dynamic membership) for both physical and virtual servers and each type of server has it's own OU. I've configured both Active Directory System Discovery and Active directory System Group Discovery to see each of these OU's. In each of the two collections I've created, I've specified which OU the collection is to pull in new members from, but for some reason each of the collections pulls in all servers (both physical and virtual) into each collection. In the case, there's one main OU (physical servers) and it has three child OU's (containing only VM's) under it. I've tried a number of Query Rule Criteria statements to try to get each collection to see physical and virtual servers seperately, but to no avail. Why would SCCM look at and pull in servers from other OU's when they're not even specified in the collection membership criteria? Is there a way to ensure that SCCM will only look the specified OU and not pull in all members from both parent and child OU's? Thanks for any advice you may have!

That's a regular SQL query, you can throw that in a report in the console and run it, or run it using SQL Server Management Studio.Scott Gill SCCM Consultant

I threw that query into SQL Manangement Studio, but got the following error: Msg 208, Level 16, State 1, Line 1 Invalid object name 'dbo.v_R_System Apparently that DB object doesn't exist on my server. Where is that object called from? Perhaps I can locate it and get this query to work. Thank you for the explanation above. I can why I'm running into this issue, but I'm unclear as to how I can get past it. Is there any way to get SCCM to look only at a specific OU and ignore the child OU if you only need a collection from the Parent, or also ignoring the Parent OU if you only need a collection from the Child OU? Perhaps the only way around this is to just un-nest the Child OU's from the Parent so they're completely unassociated? I've been grappling with this for a few weeks now, and have used a multitude of LIKE, NOT LIKE, EQUAL TO statements within my SCCM Collection query citeria properties in order to force SCCM to look only at a specific OU, but nothing seems to work.

Let's take this scenario: OU structure like this Computers\Birmingham\Laptops\Accounting with a machine named MyLaptop You will see seperate entries in SQL for MyLaptop like Computers Computers\Birmingham Computers\Birmingham\Laptops Computers\Birmingham\Laptops\Accounting If you want a collection of all the machines in Accounting that's no big deal you can do that. However if you want a collection of all machines in Laptops then you have a problem because anything in Accounting is also in Laptops. I don't have an OU structure to test this with except at home so if I have some spare time this weekend I will give it a shot, you may be able to do a subselect and fix this. So basically you'd say show me all the computers that are in Laptops (subselet not in accounting). Does that make sense? John Marcum | http://myitforum.com/cs2/blogs/jmarcum |