Clients in Collections
Home  » Config Manager  » Clients in Collections

Clients in Collections
Posted: Fri, Jan 29, 2010 7:05 AM :: Rank: 44
Author
Points: 510
Level: System Center Hero

Hello,

 

What is difference between Total Number of Clients In Collection and Total Number of Non-Obsolete Clients In Collections?

If I have 100 clients "Total Number of Clients In Collection" and 90 "Total Number of Non-Obsolete Clients In Collections"? what does it mean??

 

its quite confusing and didnt find any references any where.

 

 

 

   Report Abuse
RE: Clients in Collections
Posted: Sat, Jan 30, 2010 1:31 PM :: Rank: 49
Author
Points: 11589
Level: System Center Expert

Hey MrSharique, As I understand it, "obsoletion" is a concept that was introduced specifically to deal with duplicate records. When SCCM processes the DDR, it checks to see if it mactches an existing record. If it does, it marks the existing record as obsolete. And since their is a waiting period before those records are deleted, you can have obsolete and active records in the same collection.

These can be cleaned up (Source: This TechNet Article)

The Delete Obsolete Client Discovery Data task deletes obsolete client records from the Configuration Manager 2007 site database. A record that is marked obsolete typically was superseded by a newer record for the same client. The newer record becomes the client's current record, and the older record becomes obsolete.

When you enable this task, you should configure the schedule to run at an interval greater than the heartbeat discovery schedule. This allows clients to send Discovery Data Records (DDRs) so that the obsolete bit is set correctly.'

Defaults   Deletes obsolete client discovery data older than seven days; runs on Saturday. This task is not enabled by default.

 

   Report Abuse
RE: Clients in Collections
Posted: Sat, Jan 30, 2010 8:42 PM :: Rank: 55
Author
Points: 65502
Level: System Center Expert

Well said, Kitty. To  add to this, you want to  take steps to keep things clean in this respect, not only in ConfigMgr, but in your Active Directory. You can use the mainanance tasks for deleting records that are inactive and obsolete. I tend to set the value from the 90 day default to something a bit less, but what works well in one environment may be too agressive for another.

Bear in mind if you have a stale machine account in AD for that system that represents an obsolete record (deleted manually or by a maintenance task),a new record would be generated from AD System Discovery I believe. To avoid this, you could move the computer account to an OU that is not discovered or just disable the computer account. 

   Report Abuse
RE: Clients in Collections
Posted: Fri, Feb 05, 2010 8:59 AM :: Rank: 85
Author
Points: 510
Level: System Center Hero

no doubt that i have stale computer account in AD. therefore, they account for large discrepancies in total number of clients installed and total number of resources in collections...etc..

can  "Delete Aged Discovery Data" remove stale computers accounts from AD or not since it removes stale computers accounts from SCCM Site server database?

 

or any other way to remove stale computers accounts from AD.

 

 

 

   Report Abuse
RE: Clients in Collections
Posted: Fri, Feb 05, 2010 9:20 AM :: Rank: 49
Author
Points: 42718
Level: System Center Expert

Safest and best way I know of is OLDCMP from joeware.net. Tool has rich reporting, options and safety features. Works on Windows 2008 as well!

http://www.joeware.net/freetools/tools/oldcmp/index.htm

Be careful of the home grown PowerShell scripts out there for stale acct grooming. The two I've tested don't hold a candle to OLDCMP.

   Report Abuse

Home  » Config Manager  » Clients in Collections
Top Contributors
Featured Members
Pete Zerger
Points: 65502
Level: System Center Expert
Tommy Gunn
Points: 42718
Level: System Center Expert
Simon Skinner
Points: 40744
Level: System Center Expert
Stefan Koell
Points: 28999
Level: System Center Expert
Andreas Zuckerhut
Points: 27584
Level: System Center Expert