SMS Query not showing correct results

[HanSolo111]

Hi all,

I have an issue with multiple collections that are based on an AD query. They do not show the same results as Active Directory. For instance: a workstation collection in AD contains 284 PC's, but the SMS collection will only return 269 Pc's.

This is the query that i'm using:

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System where SystemOUName = "test.CORP/test/WORKSTATIONS"

Now the weird part is, that it DOES work correctly for some OU's.

Does anybody have an idea as why SMS is 'out of sync' with the AD OU's?

Thanks!

 

[ncotton]

First question that must always be asked when you are diagnosing ANY problem where some are working and some are failing, is :

"Are there any similarities in the systems that are failing?"

After you establish any similarities.

"Are there machines that have the above similarities that AVE worked?"

Neil J Cotton
Technical Consultant
Anix Group Ltd

 

[HanSolo111]

Hey,

The thing is that the 'missing' machines in my AD based collection, do show up in the default "All Systems" collection.
However, viewing their properties result in a similarity:
the properties "Active", "ADSiteName" is <null>. And also there is no "Systemgroup" name or "SystemOU" name.

Looks like SMS is not finding these pc's in the Right OU's?

Also, I checked the ADSysgrp.log on the sms server, and there, the pc's that are not showing up in the AD based collection share this message: "pcname" is not in the list of assigned systems.

In the sms console most pc's that don't show up in the AD based collections are not assigned, others are....

 

[ncotton]

if they are showing as inctive, what does the "Client" property say. Is the client installed on these troubled machines? If it is reporting Client : YES, can you remote to the client and check the Systems Management control from Control Panel and see what happens when you press "Auto Discover Site"

Neil J Cotton
Technical Consultant
Anix Group Ltd

 

[HanSolo111]

No the clients aren't installed on those machines. I can't seem to push em out to them.
On the other hand I've had some PC's that HAD the client, and would be active, and sms would tell me that there wasn't a client installed...

But to return to my first problem.... Since I'm using the AD SiteNames as boundries, I went and took a look at Sites and Services and discovered that many Sites either didn't have a subnet defined, were missing subnets, or held subnets other than their own local ones ! (I don't administer the AD).

So that might be the problem why the discovery agent says ' xxx is not in the list of assigned systems" and hence doesn't show it in an AD based query...

I've asked to get this Sites and Services thing sorted out. Once that's done, I'll see if SMS shows me the 'missing' pc's .

 

[ncotton]

That is one major problem, and is probably the cause of YOUR issues.

Let us know if this doesn't fix the problem. You will have to wait for 2 automatic/or manually forces hardware inventory cycles before you start seing the data come through with the newly assigned site codes and installed client data. Remeber UPDATE and REFRESH are different. People always forget the REFRESH button. Do both.

Neil J Cotton
Technical Consultant
Anix Group Ltd

 

[HanSolo111]

Well, we've sorted out the Sites and Services issue.

But SMS is still not showing certain PC's from the Active Directory OU's. Most of them still get a '...not assigned to any site system" message in the adgrpdis.log.

When I try to ping these systems, I get no response. (Ping request could not find host xxxx).
So these systems seems to have dropped from DNS.
Migth this be the reason sms is not showing these systems in the SMS collections?

 

[tbrennans]

yes