SCCM Obsolete records


Ever wondered why your SCCM client records become obsolete and you can no longer find some reports about the OSD task sequence that was executed ?

I have created a small table listing the possible scenarios :

Deployment type Bare-metal PXE boot Refresh PXE boot Refresh Advertisement
Record obsolete X
Record Merged X X
Comment Newly imported record is merged with SCCM record

So any added variables to manual import will still exist.

Old record becomes obsolete. Old record and new record are merged. Any variables stay.

So your newly imported record will be merged and will keep all the created custom properties but once you refresh this machine using PXE boot the record will become obsolete and a new record will be created so your custom properties will disappear.

Alternative would be to use MDT database integration for adding custom properties and advertise your task sequence to the unknown computer collection in SCCM or update your deployment process so the existing record always gets deleted in SCCM and a new computerrecord is imported.

Or you could set your site to “manually resolve conflicting records” and let a custom script merge the existing records.

Personally I like the MDT integration but this will be covered in more detail in one of the next posts…


One Response to SCCM Obsolete records

  1. I like the helpful info you supply for your articles. I will bookmark your blog and test once more here frequently. I’m slightly certain I will be told lots of new stuff proper here! Best of luck for the next!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s