I've recently moved to a small-medium sized business that uses HP desktops and has always used various forms of Ghost-style cloning before to image its PCs. The clones images were built using an HP-supplied Win7 Pro OEM disc, and when the clone was applied to another HP computer, Windows would automatically activate.
I set up an MDT 2013 server, and built task sequences using the same HP OEM Windows 7 Pro .iso.
However when I deploy to our HP PC's using MDT, Windows fails to activate - saying the activation key is incorrect. I suspect that this is something to do with the autounattend built into the task sequence? Not all of our PC's still have the Windows OEM sticker with a key on it, so I'd really like to find a way out of this fix.... any help greatly appreciated.