SCCM 2007 Best Practices On Removing Resources from Collections

Hello Everyone:

Any assistance from the knowledgable SCCM gurus would be most helpful and appreciated.

My company is new to removing resources from SCCM and we were looking to see what the Best Practice is on removing resources from Collections.  We have several desktops and laptops that are no longer on the network, but they are still showing up in the SCCM Collections.

1. Should the un-networked resources get removed from AD and then SCCM collection will list the resources correctly?

2. Or should they be manually deleted from the SCCM collection and also deleted from AD?

3. If a SCCM resource is not  on the network for a week, why would it still be reporting in AD?  Shouldn't the "Active" status of the resouce show up in SCCM as "NO"?


Our Discovery process is setup with the following:

Active Directory System Group Discovery - Enable Directory System Group Discovery

Distinguished Name: OU=Windows7 DESKTOPS, Recursive=Yes, Group=Excluded


Active Directory Security Group Discovery - Enable Active Directory Security Group Discovery

Distinguished Name: CN=SCCM SERVER CLIENT, Recursive=Yes, Group=Excluded


Active Directory System Discovery - Enable Active Directory System Discovery

Distinguished Name: OU=Windows7 DESKTOPS, Recursive=Yes, Group=Excluded


Active Directory User Discovery - NOT Enabled

Heartbeat Discovery - Enable Heartbeat Dicovery  (Send every 1 Weeks)

Network Discovery - NOT Enabled