We have an sms infrastructure with 4 SMS sites. Each site having roughly 4000 each except the central site A which has 10,000.We are noticing that we have duplicate CCRs in the ccr.box of the central site. We have as mucha s 18,000 CCRs on a given day. Some clients have as much as 5 copies of the same CCR. We have a script that parses the ccr files for the machine name.HWinventory runs dailyHeartbeat discovery runs dailyAny thoughts on how to begin troubleshhoting this issue?Thanks

I would start by looking at my discovery settings and my mainteance task settings.

Correct, to me that would imply: * Active Directory System Discovery is being run way too frequently * You have Client Push Installation enabled * The site server is having issues pushing the agent out to systems For discovery, how often are you doing so? There should be no reason to run it more frequently that daily, though that may be too frequent anyway. I personally don't use automated client push, I prefer using the Client Push Installation Wizard. Check the ccm.log to see what the problems are with the site server pushing to clients. There are numerous posts in this and the Setup / Deployment forum on client push, and discussions on the issues and how to resolve them.

We have ADsysdisc running daily and we do have client push enabled. Is it by design that dupe ccrs are being generated? I thought sms would have a way to see that it already created a CCR for a system and won't bother creating another one. There are several issues in the ccm.log from machines not being connected to the network for a long time during the retry periods and once in a while access denied although we already have a GPO enforceing that the client push acct be in the local admin of all the machines in the domain.

We only look to see if the system is already a client, not whether or not a CCR is already created for that system. The reason being it normally does not take a long time to install the client (usually minutes), and if issues, the original CCR only is processed for up to one week, then we delete it.

What is recommended in terms of running AD system discovery in a multi-site hiererachy? Do we only have to enable it for the entire domain in the central site and leave it disabled for the child sites?The MS support guy gave a theory that since we have AD sys dis enabled on all sites for the same AD container, the ccrs are travelling up to the parentHow does SMS process ccrs from child sites? Are they sent up the tree and end up on the central sites' ccr.box?

I enable mine at all sites for the OU which holds machines for that site. There's no need to have more than one site discover the same container. You may want to review this flow chart for discovery: http://technet.microsoft.com/en-us/library/bb932137(TechNet.10).aspx ccr's are processed at the site where they are created. (I am assuming you are referring to primary sites) The location from which the install files are pulled depends on some different things explained in the chart. and these for client installs: http://technet.microsoft.com/en-us/library/bb694034(TechNet.10).aspx

Wally - This is a old post and I don't seem to see any posts on "millions of CCR files" files generated daily. Basically my D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\ccr.box directory on my CENTRAL site server only seem to contain millions (about 4 million) CCR files. They do not appear to be duplicates. We only have about 1500 PCs being managed and no SCCM clients on servers. We only have 2 sites with 1 as the CENTRAL site and the other as the Primary child. Where is the setting where i can see how often the CCR files are deleted? You said in your reply "the original CCR only is processed for up to one week, then we delete it." Where can I find the setting on the weekly deletion or is this just automatic by design? Thanks Nathan Bridges PGS Americas

The CCR deletion process is not configurable and is automatic. What is the purpose of 2 sites for only 1,500 systems? How often do you have your discoveries running? Do you have discovery running on both sites? What is the timestamp of the oldest CCR? Have you simply deleted all of the CCRs?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

What is the purpose of 2 sites for only 1,500 systems? I created 2 sites for political reasons within our company and because we have many WAN links that are highely used. I also, thought it would be best in the event of massive failure moving the clients to the other site would be quicker. How often do you have your discoveries running? Do you have discovery running on both sites? 1. AD System Group Discovery = 15 minutes - to speed up AD group based deployments. Helpdesk adds PCs to AD groups then the collection is based on AD group membership which also updates it's membership every 15 minutes. Although we don't have a SLA for install time I did not want it to take 1 day or 4 hours to install software. Maybe this is overkill now that Delta discovery is enabled with R3 installed and dynamic updates for collections? Thoughts? 2. Security Group Discovery = 4 hours 3. System Discovery = 4 hours 4. User Discovery = 4 hours What is the timestamp of the oldest CCR? 8/10.2010 Have you simply deleted all of the CCRs? I am currently deleting the files now. About 4 million.

Oh and Discovery is running on both sites BUT not for the same OUs. Each site discovers only the regional OUs.