Microsoft Configuration Manager 2007 Discovery Best practice

all_experts used Ask the Experts™
I have a single site set up with Microsoft Configuration Manager 2007. I am trying to come up with the best practice for discovery. Right now I have Heartbeat discovery and Network Discovery enabled.
Heartbeat is setup to send every 1 day
Network Discovery turns on at 12pm and goes for an hour.
I didnt want to use Active Directory discovery because sometimes it contains obsolete computers.

My problem is the following:
-Some computers dont get discovered for some reason.
-Some computers get discovered twice and get stored as two PCs.

Please advise what's the best approach.

Thank you.
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I would recommend using AD discovery as it is the most common and easy to setup discovery method.

Heartbeat discovery should remain enabled all times.

SCCM will pick obsolete computers from AD, only if there are computer objects present in AD + SCCM is able to resolve there names to IP.
I would recommend enabling scavenging in DNS, so that stale records get deleted. In this way you would not get obsolete computers in SCCM.

Once you enable scavenging after that you have run dnscmd /ageallrecords command because scavenging deletes only those records by default which have been created after the scavenging got enabled.

As far as your duplicate entries query in SCCM.
I believe you have "Automatically create new client records for duplicate hardware IDs" selected in SCCM
You could select "Manually resolve conflicting records "


Interesting. I think that would work.
We already have scavenging set up in DNS and it's 7 days.

Let me ask you this. How do i configure SCCM to get rid of old PCs so that is not done manually?
I was trying to find Site Maintenance -> Task to do that, but it's a bit confusing.


The Delete Aged Discovery Task will only delete resources that have not been updated by any discovery method for the designated period (14 days in your example). So they'd remain there until that task runs, assuming nothing else has discovered them.

This is normal behavior. It's not a dynamic process so normal that if you delete a earlier discovered resource in Active Directory it remains in SCCM.

 To have your environment more up to date, configure the Delete Aged Discovery Task. This task deletes aged client discovery data from the database. On the task you can specify the age of discovered data that must be deleted.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial