Maintaining the SMS Resource ID of a machine when redeploying the OS on it..possible?
Here's one I'm trying to work out (and there has to be a way....it may just be a matter of finding it hehe)....
When we rebuild a computer with a OS via SCCM, it creates a new resource ID during the process and the result is two computer resource objects in SCCM.
You may think, whats the big deal? just get the old ones deleted automatically with that maintainance setting to remove obsolete (and other) resource objects.
And you'd be right, however, thats fine when you dont need to / dont use SCCM to keep a inventory of your computers, but alas, we kind of need this system to do that, so I've got to find some decent way on how its possible.
I've seen that in SMS 2003, there was a tool in their toolkit called "Transfer SMS ID", although I've not used it, the description says "Transfers SMS client ID (GUID) from one computer image to another. You can use this tool to help support asset management and to avoid data loss during re-imaging."
The latter part of that sounds perfect, however, im just wonderings whether any of you good good people using SCCM have managed to figure out a way to do it, before I spent potentially countless hours figuring it out.
Also using the Deployment Web Service too in order (very handy, and maybe if i dig, theres a way to do it via that).
As normal, thoughts/ideas/complete noob guides welcome :)