Puppet or cfengine could be used to manage these sort of changes in a policy-driven manne. They are both a high level configuration management framework that can wrap around powershell, batch files, installers, and registry patch files, and other deployment techniques. It's a bear to set it up, but if you are going to be frequently deploying systems with similar changes, it's worth doing, since it helps you do these changes not just with the initial setup, but on an ongoing basis. I'd say it's overkill for under half a dozen systems (unless you are reinstalling them on a weekly basis), but starts to become absolutely necessary to have that sort of framework the more systems you add beyond that.