Hi guys, I'm aware that SCCM no longer discovers disabled machines but unfortunately there isnt a task to delete disabled machines that have already been discovered (i.e were discovered when they were enabled, they were then disabled and although not rediscovered, they are still in the DB until deleted). Firstly, is there any way you can use SCCM to identify machines that have been discovered but have since been disabled without using System Discovery? Secondly, if not, what is the best way of identifying machines that are now disabled in SCCM? Thirdly, is there any way of deleting machines that have been discovered but have since been disabled, preferably on a schedule? Any help would be appreciated Cheers Nivor

There is indeed a task that removes them automatically.http://technet.microsoft.com/en-us/library/bb693646.aspxhttp://technet.microsoft.com/en-us/library/bb694040.aspxJohn Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

There's no way that I am aware of to do what you are asking in a supported manner. The only thing you can do is be more aggressive with your built-in tasks. What's the drivign factor for this request? John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

Honestly I think people make too big of a deal of this scenario. How often are you retiring machines? How often are you runnining these compliancy reports? Using the built-in maintenance tasks will handle getting these computers out of the db is a couple of days in an automated fashion. How much more accuracy do you need? You could as a manual method use oldcmp to generate a list of all the disabled computers, put that into a text file, import those computers from the textt file into a collection then use delete special to remove them from the database. But I think that's overkill personally. I would simply rely on the built-in tasks and be aggressive with the schedules if you feel that is required.John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

BTW, You could write a vb scritp to disable the computer and delete the PC from the ConfigMgr db too. Make sure that you use the SDK to do this.http://www.enhansoft.com/