SCCM 2007 - Computers Absent From "All Systems" Collection

We're running System Center Configuration Manager 2007 on a Windows Server 2008 R2 Standard server.  It polls Active Directory for our workstations.  For some reason, it finds all but four of our workstations.  All these workstations (both the ones that are discovered and those that are mysteriously skipped) exist in the same OU in AD.  All machines are of the same configuration (identical hardware, OS, software installations, etc).  Can anyone here please provide a suggestion as to why SCCM 2007 might not add these four machines to it's collections while all the other machines are added?  

Thanks!
pedroelbeeAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Glen KnightCommented:
Have you checked the client? Is it installed properly?

If you execute the Machine Retrieval policy from the client manually does it work?

Have you updated the collection (right click All Systems and select update collection)
0
NJComputerNetworksCommented:
Are these machine account disabled? or can you confirm that these machine account actually exist on the network?
0
pedroelbeeAuthor Commented:
The client isn't installed on any of the missing machines as far as I'm aware, but they should still be able to appear on the All Systems collection in SCCM, correct?  We have a couple other machines which are currently inactive and report a "No" in the client column of the All Systems collection.. but they show up in there :-)

I performed an update of collection membership just to be sure, and they're still not listed.

My understanding is that SCCM polls active directory for machines.  
Under the Site Database > Site Management > (site name) > Site Settings > Discovery Methods, "Active Directory System Discovery" is enabled and configured to check the appropriate OU - doing this added the majority of the machines, just seems to not like those remaining couple ;-)  Other settings are "Recursive" = "Yes" and "Group" = "Included".  I tried "Run discovery as soon as possible", waited a couple minutes then updated the collections again... and still no dice.

It's a chin-scratcher, eh?
0
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Glen KnightCommented:
What have you got the time poll on the discovery set as? Change it to 15 minutes.
0
pedroelbeeAuthor Commented:
NJComputerNetworks - I can confirm the computer accounts exist and are enabled.  They're laptops and currently roaming, but they do enter the office regularly as well as join via VPN.  Would a computer being away from the office prevent it from being discovered by AD System Discovery?
0
pedroelbeeAuthor Commented:
demazter - it was set to 2 hours, but I'll happily switch it to 15 minutes for the time being.
0
NJComputerNetworksCommented:
I believe disabled accounts are not discoved...  being off the network is Ok... but if there is something wrong with the accounts they won't get discovered...

http://allfaq.org/forums/p/153799/307963.aspx#307963
http://social.technet.microsoft.com/Forums/ko-KR/configmgrgeneral/thread/af79c5b0-a19c-4dc9-ae53-1c01df88ee64
0
Glen KnightCommented:
Set it ti 15 minutes and then force a manual discovery.

Then leave it for about 30 minutes and update the collection membership.

I have all my SCCM servers set for 15 minute discovery during deployment periods.
0
NJComputerNetworksCommented:
also check you rdiscover logs for more details why this isnt getting discovered.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ExemplarCommented:
If none of the previously mentioned comments seem to be the fix, you could have a duplicate GUID or a lack of registering the GUID.

I would try the following:
* uninstall the client, ccmsetup /uninstall
* delete the smscfg.ini file
* reinstall the ConfigMgr client.

This issues a new GUID and could resolve your problems on those four clients.

Cheers
0
pedroelbeeAuthor Commented:
NJComputerNetworks led me to browse the adsysdis log file.  I came across these lines:

INFO: discovered object with ADsPath = 'LDAP://<domain_controller>.<domain>.ORG/CN=<FAULTY_MACHINE_NAME>,OU=Reinstalled,OU=Workstations,DC=<domain>,DC=ORG'~  $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Wed Apr 28 14:00:07.346 2010 Eastern Daylight Time><thread=5068 (0x13CC)>

WARN: Could not get property (domain) for system (0x80005010)~  $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Wed Apr 28 14:00:07.346 2010 Eastern Daylight Time><thread=5068 (0x13CC)>

ERROR: GetIPAddr - getaddrinfo() for '<FAULTY_MACHINE_NAME>.<domain>.ORG' failed with error code 11004.  $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Wed Apr 28 14:00:07.348 2010 Eastern Daylight Time><thread=5068 (0x13CC)>

ERROR: Machine <FAULTY_MACHINE_NAME> is offline or invalid.~  $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Wed Apr 28 14:00:07.410 2010 Eastern Daylight Time><thread=5068 (0x13CC)>

WARN: CADSource::ProcessSystemInfo: Failed to get IP Address for the system.~  $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Wed Apr 28 14:00:07.453 2010 Eastern Daylight Time><thread=5068 (0x13CC)>

-- -- -- --

These errors seem to indicate that it's failing to find an IP address for this machine... which makes sense, because it's not on the network right now (it's out roaming the vast wonders of the world).
0
NJComputerNetworksCommented:
nice
0
pedroelbeeAuthor Commented:
demazter - Thanks for the tip.  I've set the discovery to 15 minutes, then forced a start, then waited an additional ~45 minutes... still no improvement - doh!

NJComputerNetworks - I checked the adsysdis log file, but could find nothing other than the above-posted errors pertaining to the inability to discover an IP address (which makes sense, since the PC is off the network at the moment).  Where else can I look for possible related issues?

Exemplar - Thank you for the suggestion.  Unfortunately, at the moment the laptops do not have the client installed on them (which shouldn't stop them from being discovered by SCCM system discovery and added to the collections, right?)  Do you think manually installing the client on these four machines would fix the problem?  Is there a way I can manually check the GUID information against something in order to verify it may be duplicate or otherwise erroneous?  Thanks!
0
pedroelbeeAuthor Commented:
According to a post in this link shared by NJComputerNetworks, a possible cause may be that SCCM is failing to resolve the name of the discovered resource (because it's on an adventure?).

So:

1. SCCM polls AD
2. SCCM discovers one of the trouble PCs
3. SCCM attempts to resolve the PC name, but fails because PC is out and about
4. SCCM does not add resource to any collections due to step 3.

Is this a possible reason for the issue at hand?

Thanks to everyone who's been following this!
0
ExemplarCommented:
Have you verified that your Boundaries are set to protect for the four workstations?

Which type of boundary are you using Active Directory Site, IP address range, IP Subnet, etc?  Have you verified that the four computers are protected appropriately?

Thanks,
Ex
0
Adam LeinssServer SpecialistCommented:
Is there a DNS record for these laptops?  If not, the AD discovery will fail:
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/f52563d7-e773-43de-90f3-4fb98027a105
 
0
pedroelbeeAuthor Commented:
Sorry for the delay in updating this thread!

We finally have one of the missing computers return from it's adventures abroad.  Once it was connected to the LAN, I forced a System Discovery and then updated collection membership.  Lo and behold: the system appeared on our All Systems list.  

So it seems that, in this case, the only problem was that the laptops were not connected to the network during previous discovery attempts, so SCCM was never able to verify it's existence and add it to any collections.

Thank you to everyone who participated, it's been very much appreciated!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.