I am running into the following scenario, and not sure what the easiest way is around it.
Home office users who's hard drives completely die, we usually image up a new hard drive, join to domain, etc and mail it out to the user. The hard drive's are imaged usually in one of a couple machines that we have for this purpose. The problem I am seeing is with imaging multiple drives in the same laptop as they will have the same MAC/SMBIOS in SCCM.
I currently have my team re-importing the imaging laptop into SCCM, by specifying the MAC and new machine name. The problem I see is it basically just rename's any machine that has the same MAC address to the new machine name to prevent duplicate records. It will show all the information, like last user logon, etc of the machine that had the duplicate MAC, but with the new machine name.
Once AD Discovery completes, I see it will re-detect the machine it had re-named, but show as no client installed.
I need to know what the best way of dealing with this is.
1. Should I have my team re-run the ccmsetup on the hard drive once the end user receives it (didn’t seem to work right when we tried it on a test machine, came up with information from another machine??)
2. Should I uninstall the Client before shipping, if so what is the command line?
3. Will it just resolve its self after time?
4. other...