I am trying to understand how Delete Aged Discovery Data, Delete Obsolete Client Discovery Data, and Delete Inactive Client Discovery Data tasks work. I created a flow chart according to how I understand it here: http://mayurkirti.files.wordpress.com/2006/11/client_lifecycle_flow_chart.jpg It will be great if folks could help me correct it. Thanks.Mayur

I'm not sure a flowchart is the best way to represent what's going on, but here are a few comments anyway. - Resources are only marked Obsolete if another resource is created with the same HW ID - A resource deleted by the Delete Aged Discovery Data task will be recreated by AD Discovery if the object still exists in AD. - A resource will be marked Inactive it it is marked obsolete (this usually doesn't matter though because the delete obsolete time is usually less than the delete inactive time) - A resource will be only marked Inactive by R2 client health, if it is newly discovered, or is obsolete. Looking back at previous answers of my own (on this and other forums), I've stated that a lack of heartbeat will also cause a resource to be marked inactive. Based upon the documentation which I've just reviewed, I don't think that this is true.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

- A resource will be only marked Inactive by R2 client health, if it is newly discovered, or is obsolete. Looking back at previous answers of my own (on this and other forums), I've stated that a lack of heartbeat will also cause a resource to be marked inactive. Based upon the documentation which I've just reviewed, I don't think that this is true. Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys That's what confuses me too. An answer on this thread says lack of heartbeat discovery can mark a resource inactive: http://social.technet.microsoft.com/Forums/en/configmgrgeneral/thread/83d34e85-2193-4c6a-ab8e-6d16b0ae2eef but it's not mentioned anywhere in the documentation.Mayur

Only if CSR is implemented: "Now the lack of a heartbeat discovery ddr is one of the things that could mark a client inactive if you implemented the client status reporting feature" After digging through the documentation, I've come to the conclusion that the Delete Inactive task is useless unless you have CSR implemnted.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys