Obsolete objects - Reuse your ”Old” SCCM Client Objects in Mixed Mode
Got this from Kristian F. Thomsen's blog and look very handy for people dealing with re-imaging clients in a non-native environment.
http://kristianfthomsen.spaces.live.com/blog/cns!59A30145A64F8A9F!156.entry
***************************************************************************************************************************************************************************
When ConfigMgr is configured in Mixed mode and client computers are re-imaged/re-installed; by default a new ConfigMgr computer object is created and the “old” computer object will become “Obsolete”. Well, this is by design, but it might become a problem. If the client has many direct collection memberships, these direct memberships will not be preserved when a new computer object is created. Therefore, these have to be re-created.
When ConfigMgr is configured in “Native Mode”, the client identity is automatically migrated since we are using certificates.
Well, with ConfigMgr, this problem can be handled. However, it is a manually process. In the “Site properties” dialog, on the “Advanced” tab, there is a section called “Conflicting records”. From here it can be configured how ConfigMgr should handle conflicting records. That is, clients with duplicate hardware Id’s. By default, it is configured to “Automatically create new client records for duplicate hardware IDs” as shown in the picture below.
Click here to read the article