Why do some machines not appear in the SCCM All Systems Collection

I am having a problem with SCCM in that it does not seem to see all the machines on my network.

Can anyone enlighten me on how it discovers these machines, it is before it even attempts to put on the client.
WNottsCAsked:
Who is Participating?
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.

Adam LeinssServer SpecialistCommented:
Check Site Database>Site management>YOUR DATABASE>Site Settings>Discovery Methods
You can have it search by Active Directory OUs or Network discovery or both.
I believe these run every 24 hours, but you can go into each discovery method>polling schedule and checkmark "Run discovery as soon as possible" to do it on demand.
0
WNottsCAuthor Commented:
what about heartbeat discovery?  Will the machines only show in the collections if they have the Site assigned to them?

Currently it search heartbeat discovery and DHCP network discovery.  The machines it can not find have been on for a whole day now and I have checked that they are in both DNS and DHCP but still not being picked up.
0
Adam LeinssServer SpecialistCommented:
Heartbeat Discovery just verifies the SCCM client is still alive and functioning as a SCCM client.  If a SCCM client doesn't respond to a heartbeat discovery after a certain period of time, SCCM sets "Client Installed" from Yes to No, even though the client may still be installed.
Yes, clients need to be assigned to site to be discovered and within the site's boundaries.  Did you define site boundaries under Site Database>Site Management>YOUR DATABASE>Site Settings>Boundaries?
0
JonLambertCommented:
Actually thats not quite correct, discovery methods such as AD System discovery does not rely on site boundaries.  All that is required for a client to be discovered (an thus a Data Discovery Record created) is to have a computer object in AD, and also be resolvable in DNS.

Could it be that the clients you are discovering in AD for some reason are not also in DNS?
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
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.