Solved

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

Posted on 2009-07-13
4
649 Views
Last Modified: 2013-11-21
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.
0
Comment
Question by:WNottsC
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 22

Expert Comment

by:Adam Leinss
ID: 24842184
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
 

Author Comment

by:WNottsC
ID: 24844147
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
 
LVL 22

Expert Comment

by:Adam Leinss
ID: 24844342
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
 
LVL 10

Accepted Solution

by:
JonLambert earned 500 total points
ID: 24844968
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

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

1. Boot PC and press F10, select storage options and change the compatibility from “AHCI” to “IDE”, save and exit 2. Boot PC and press F12 3. Upon PXE display of searching for DHCP server, press Pause break to obtain MAC address 3. Open Configu…
Remote Apps is a feature in server 2008 which allows users to run applications off Remote Desktop Servers without having to log into them to run the applications.  The user can either have a desktop shortcut installed or go through the web portal to…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question