We are presently deploying SCCM in our environment. Our system count is around 11K+. and are using one single primary site. We are using IP subnets as boundaries. We have two discovery methods enabled and are still not collecting all our clients systems. Using AD System Discovery once a day. and Heartbeat Discovery once a week. We are missing around 45 servers that are not discovered . The query criteria is for any server "%Server% and in OU which contains all these servers. These are all win 2003 svrs. mixture of service packs. The odd part is that if we make a query by name which looks for the servers OS like above but inbstead of OU we use a name with wildcards i.e. "%FS%", we get all the servers we are looking for plus others that have same letters in name "FS" Also we are not seeing over 3k client systems across 390 subnets. Our networking team has ensured no other firewall is on the subnets. Our group policy has the windows firewall off while on LAN. Any help on discovery would be greatly appreaciated.

Based on your description, AD System Discovery is working fine--you can see the servers when you query for %fs% by name. but in the first query, you are asking to limit to a specific OU in that collection query. OU Discovery relies on two things: 1) that you have Active Directory System Group discovery enabled. 2) that the Systems for which you are attempting to get OU information are clients in the database.It could be I've misunderstood what you mean by query criteria vs. discovery agents enabled vs by OU vs. by name. So perhaps I'm giving bad advice; so take it skeptically.Standardize. Simplify. Automate.

Thanks all. Your feedback is quite helpful in my trying to understand "how it works".Would like more clarification. Yes All systems collections has over 11k+.In reference to our server collections, this is what I see.1st collection - collects servers from an AD OU that has all servers we are looking for. Results are 189 assigned to site with 7 not having client even after many attempts to install.2nd collection - collects servers without client installed but have%FS% in there name (FS = file server in our naming convention) Results are 92 servers found and 4 assigned to site the others are not assigned.Here is where I am at a lost in why aren't the 2d collection members havenot been assigned.Also since I am here what is a "DDR". See DDR being written in adsysdis.log.Thanks

DDR = data discovery record. ConfigMgr uses .ddr files (internally) to update/create client records in the database. What's wrong now? Are you concerned about the number of servers in each collection? If so: post the WQL statement for each collection. Or are you concerned about "assigned = no"? If so: what boundaries have you set up (AD site? IP subnet?) and what would be the IP and subnet mask of a server?

So the AD guys screwed up again, what else is new :-)"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm