Originally Posted by
SuperJdynamite
The typical way of presenting the end user with a "tweaked" image is to use sysprep.
With sysprep you install the OS, install software, make tweaks, and so on, then you "reseal" it with sysprep. During "sealing" you can remove the license key that was there or keep it (likewise for Windows "activation"). During initial boot of a sysprepped image the end user runs through an abbreviated setup to re-enter a license key (if necessary). When the mini-setup is complete the end user has a machine with software and settings pre-installed.
There's probably a way to do a custom one-time configuration operation during the sysprep mini-setup that the end user runs through, but I've never done it so I can't offer any advice there. I've seen vendors add their own custom setup routines which is why I'm guessing it's doable.
Your other solution -- messing with registry hives -- is a tricky proposition. You may run afoul of code in the core OS that monitors the hives for tampering (MS added this because various products are different only by a few registry settings). There are also other issues you'll likely encounter when trying to manipulate hives directly.