I would like to make sure that our configmgr environment keeps fairly clean and doesn't get out of control in the future.  We have a pretty new install.  What I would like to do is optimize the cleanup settings.  I've come across settings for Delete Aged Discovery Data and Delete Inactive Client Discovery Data as well as discovering computers within the last xx days but am not sure what to set them to.

So in our network we have users who are only here on our local network from January to May. They either take their laptops home or they give them to us to put in storage until they return in January.  We also have training laptops that are typically only in use starting in late November and stop being in use after the first couple weeks in January.

What would be the best settings to keep sccm clean of old computers that have either been removed from the domain or old computers that should be removed from the domain but aren't because people don't seem to keep it clean type of situation.

Thanks

Hi,

Please keep the heartbeat discovery method enabled all the time and make sure the value is always less than the value of the task Delete Aged Discovery Data and Delete Inactive Client Discovery Data.

There is a Important Note in the official article.

"For example, at the central administration site, you might configure Discovery to run one time per month to identify non-client computers, and plan to install the Configuration Manager client to these computers within two weeks of their discovery. However, at one site in the hierarchy, an administrator configures the Delete Aged Discovery Data task to run every seven days with a result that seven days after non-client computers are discovered, they are deleted from the Configuration Manager database. Back at the central administration site, you prepare to push install the Configuration Manager client to these new computers on day 10. However, because the Delete Aged Discovery Data task has recently run and deleted data that is seven days or older, the recently discovered computers are no longer available in the database."

Reference:https://technet.microsoft.com/en-us/library/gg712686.aspx?f=255&MSPPError=-2147217396#BKMK_PlanMaintenanceTasks

Best Regards,

Joyce

My heartbeat discovery has always been enabled and is currently set for 1 week.  My delete aged discovery data is set to 90 days.  My delete inactive client discovery data seems to be set to not enabled, must have been set that way by default.  I only have one site, no CAS.  I was kind of wanting to know what I should set these to for my environment based on the fact we have laptops that will be in use from January to May and not any other time except for maybe a few random ones on occasion who may come back randomly to do some work as well as the training laptops we have which are only used for a few weeks out of the year.

Anyone have an optimum setting for this for my environment?

anyone?

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Actually no, not really.  I'm kind of wanting some suggestions as to what I should set mine to based off of the info I gave about our setup.

Actually no, not really.  I'm kind of wanting some suggestions as to what I should set mine to based off of the info I gave about our setup.

There is no right answer to this.

But I would make the clean up a semi-manually process to clean up old computers. Or look at BOTH WOL and DirectAccess, to endure that your computers are updated at least monthly. Ultimately why do you care of a PC gets removed form the CM12 DB, they will automatically get added back then next time they connect to your network.