Duplicate records after re-image
I have imported one computer in SCCM so that it picks up the computer name and MAC address. I put this in the unknown computer collectuion. When I imaged it with the task sequence it imaged it and picked up the right name and put it in the right OU. I have a custom collection that scans that OU. Everything worked fine but then when I re-imaged the PC from PXE - the custom collection picked up a new entry for the PC with the same - now had 2 computer on the same name and software distribution stopped working. How can I solve this? What is the best approcah because if re-image any other machine I will have double entry once again
December 8th, 2010 7:33pm

why did you import the computer into the Unknown Computer collection, that doesnt make sense, you could import it to a deploy collection or just NOT import it and pxe boot and have an advertisement advertised to the unknown computers collection, which would target this 'unknown' computer... and thereby image it. The duplicate record is the old and now obsolete record for the computer, simply delete the obsolete record as it is no longer required or useful. You can configure this via Site Maintenance tasks , delete obsolete client discovery data My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
December 9th, 2010 1:20am

One of the 2 duplicate records is marked as obsolete - but then I tried to schedule to run the task which is supposed to run already a few times. However the old record is still there thanks
December 13th, 2010 7:28pm

Hi, You might also just delete the record marked as obsolete. Make sure to refresh collections and then retry. If you have your site configured for manual resolving conflicting records, check under the conflicting records node to merge the two records.Miguel Rodriguez MCTS - ConfigMgr ~~elmunjo.blogspot.com~~
Free Windows Admin Tool Kit Click here and download it now
December 14th, 2010 7:26am

It took a while for the SCCM server to clear the obsolete data (atleast a week I guess) how ever it worked at the end Thanks
January 4th, 2011 11:19pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics