all_experts
asked on
Microsoft Configuration Manager 2007 Discovery Best practice
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/e52b568f-2da5-45a6-a9d5-c33592937871
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.
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.
ASKER
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.
Thanks.