I'm trying to add in some automation for customizing a reference build so I can just run a TS with these steps and it does build, customize and capture. There are a couple things I am trying to do like customize wallpapers, configure some user settings ect which require registry changes and copying in some files. I've made a couple .reg's and .cmd's to perform these. I've created a folder on SCCM share and put all the required files inside, created a package, distributed and inside the single package created a program for each of the tasks. Then on the TS install each program individually. This seems to work but I'm wondering if there is a better way to do this? Also outside of OSD how should a .reg or .cmd be deployed? The .cmd commands are pretty long so probably not going to be suitable for a "run command line" step in TS. Do you do all these customizations manually on your reference machine then capture or have it automated? If so, how?

Many tasks in ConfigMgr can be done in multiple ways -- at te end of the day, whatever works for you is the best solution. I'm not sure of the exact details of what you are doing, but it does sound similar to what I typically do though for customizing profiles and Windows in general. Doing it using an automated method like scripts that you have just define lowers your overhead and ensures that you have a repeatable process in and out of OSD which I highly recommend. I never do things manually because that limits repeatability and introduces the possibility of human error. As for the long commands in your batch files, you can just run the batch file from the run command-line task.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

As for the long commands in your batch files, you can just run the batch file from the run command-line task. Jason | http://blog.configmgrftw.com | Twitter @JasonSandys Thanks Jason! I think I'll change over most of them to run command line task. If the command requires .reg or .jpeg ect files (small stuff), do you just point it to a central source or replicate the content as a package and then somehow point to a local source? eg: copy "\\sccm-server\sourcefiles\customizations\backgroundDefault.jpg" "%windir%\system32\oobe\info\backgrounds\backgroundDefault.jpg" or regedit.exe /s "\\sccm-server\sourcefiles\customizations\OEMBackground-Enable.reg" Thanks again!