Hi, Currently our AD data (computers) are not accurate and old and I want to delete all of the computers in "All Systems" Is it possible to delete all the data in there and have the Discovery run again and pull out all the data? I have modified the SQL maintenance to delete data that's 30 days old but I don't think this is working at all or not well enough. So is this possible?

if the computers are not discovered Via any other method and if they are not on the network for more than 30 days, site maintanance tasks that you have configured will delete the information . if you delete all the systems from SCCM database ? what happens to the existing data? you can wait until site maintanance tasks runs and deletes the non-avilable computers data from SCCM. To clean up the old systems from AD use oldcmp.exe and enable DNS scavenging or else you can create collection for the computers based on heartbeat discovery say for x days and remove the collection but again it might causes to remove the systems which are offline as well.//Eswar Koneti @ www.eskonr.com

Yes, you can delete. But the heartbeat discovery will get all the client records back. I would suggest you to do some clean up in AD or enable scavenging....Also, properly enable the maintenance tasks. More details on maintenance task http://technet.microsoft.com/en-us/library/bb632595.aspx To check whether the maintenance tasks are running ...go through the below link http://anoopmannur.wordpress.com/2010/12/06/reporting-of-maintenance-tasks-status-of-sccm-primary-server/Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

http://anoopmannur.wordpress.com/2010/12/06/reporting-of-maintenance-tasks-status-of-sccm-primary-server/ Looks very similar to Donnie's SQL query ... http://www.myitforum.com/absolutenm/templates/Articles.aspx?articleid=14230&zoneid=89, but that might be coincidence. Torsten Meringer | http://www.mssccmfaq.de

Yes, you can delete. But the heartbeat discovery will get all the client records back. Heartbeat Discovery will not discover new resources once they are deleted from SCCM and if the clients are heatly ,they will send the DDR to site server without any discovery methods. //Eswar Koneti @ www.eskonr.com

Ok let's focus on another issue. I have created a collection where it's looking computer accounts in a specific OU on AD. For some reason the computer accounts I see in this collection isn't the same as the computer accounts that are in AD. What could be the issue here?

shouldn't be the case.check the computers which you see are different are part of anyother OU or old computers ?//Eswar Koneti @ www.eskonr.com

Yes, you can delete. But the heartbeat discovery will get all the client records back. Heartbeat Discovery will not discover new resources once they are deleted from SCCM and if the clients are heatly ,they will send the DDR to site server without any discovery methods. //Eswar Koneti @ www.eskonr.com Hi Eswar - I think, here we are talking about deleting already discovered record :) Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

http://anoopmannur.wordpress.com/2010/12/06/reporting-of-maintenance-tasks-status-of-sccm-primary-server/ Looks very similar to Donnie's SQL query ... http://www.myitforum.com/absolutenm/templates/Articles.aspx?articleid=14230&zoneid=89, but that might be coincidence. Torsten Meringer | http://www.mssccmfaq.de Hi Torsten - Yes, I have seen this (orginal post from Donnie ) after creating this post long back in December 6, 2010. The orgin of my post was from the query which we used internally :) That is why I didn't mention the orginal post .....Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Ok so can we get a clear answer on this. Can I delete the computer accounts (already have been discovered) in "All Systems" and if new record of all computers will be re-discovered according to AD?

The computer accounts in OU on AD are accurate but the computer accounts in the collection created using query + criteria are accurate or not the same as what is in a specific OU on AD.

Ok so can we get a clear answer on this. Can I delete the computer accounts (already have been discovered) in "All Systems" and if new record of all computers will be re-discovered according to AD? Yes, you are correct !!!Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I just had a look at this particular SQL maintenance task "Delete inactive client discovery data" and the setting I have is delete data older than 2 days. Shouldn't this be deleting computer accounts that are not active in more than 2 days? This isn't the case because I have a lot of old data that's probably about 2 years old!!!! Our DNS also looks quite fresh. So SCCM isn't talking or updating data with AD? or its SQL maintenance tasks don't run properly?

it will delete computers that are not active(for inactive clients ,flag will be marked as Zero),please refer this artile when the flag will be marked as Zero http://myitforum.com/cs2/blogs/jgilbert/archive/2008/10/18/client-is-installed-flag-explained.aspx Clients are marked inactive in two ways for more info http://technet.microsoft.com/en-us/library/bb693646.aspx //Eswar Koneti @ www.eskonr.com

Why don't you enable "Delete Aged Discovery Data" task? That will clear these records ... See, more details http://technet.microsoft.com/en-us/library/bb693856.aspx http://social.technet.microsoft.com/Forums/en-US/configmgrinventory/thread/92a0bf19-42b7-496b-97a8-8e15adc1ccccAnoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Yes, you can delete. But the heartbeat discovery will get all the client records back. Heartbeat Discovery will not discover new resources once they are deleted from SCCM and if the clients are heatly ,they will send the DDR to site server without any discovery methods. //Eswar Koneti @ www.eskonr.com Hi Eswar - I think, here we are talking about deleting already discovered record :) just wonder how sccm(heartbeat discovery) knows if the client machines are removed from SCCM and they will be discovered automatically. Once they machines are not avilable in SCCM,they will be unknown to sccm until they appear. Havent tried it practically though.//Eswar Koneti @ www.eskonr.com

Yes, you can delete. But the heartbeat discovery will get all the client records back. Heartbeat Discovery will not discover new resources once they are deleted from SCCM and if the clients are heatly ,they will send the DDR to site server without any discovery methods. //Eswar Koneti @ www.eskonr.com Hi Eswar - I think, here we are talking about deleting already discovered record :) just wonder how sccm(heartbeat discovery) knows if the client machines are removed from SCCM and they will be discovered automatically. Once they machines are not avilable in SCCM,they will be unknown to sccm until they appear. Havent tried it practically though. //Eswar Koneti @ www.eskonr.com Please test. Just try deleting one record and initiate Discovery Data Cycle from client configmgr applet of wait for heatbeat discovery to happen.Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Eswar - More detailed discussion on http://social.technet.microsoft.com/Forums/en-US/configmgrinventory/thread/48b04a61-3d70-49c1-8a53-b0f7f6cba037Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Eswar - More detailed discussion on http://social.technet.microsoft.com/Forums/en-US/configmgrinventory/thread/48b04a61-3d70-49c1-8a53-b0f7f6cba037 Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Alrights,Thanks Anoop :)//Eswar Koneti @ www.eskonr.com

Okay I've just deleted all the computer accounts and I can see they are all now being discovered again. One major issue with this though. Some of the clients are being reported as "No Client". How do I fix this?

The status will get changed once Heartbeat discovery is done on those computers (If the clients are healthy). Also, see the other possibilities of client not reporting issues explained in the below blog? http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspx Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.