We have a few lines of script in SetupComplete.cmd we set up befoere a sysprep in a Build task sequence that creates a wim. We point to said wim in a deploy task sequence that we use to add specific drivers and a couple of app sthat need to be installed after a sysprep. All seems good, but the scripts we have in SetupComplete are not written, and in fact SetupComplete.cmd all of a sudden is replaced with a SetupComlete.cmd that has one line: %windir%\system32\osdsetuphook.exe /execute Where does this get pushed from? As far as we can tell, we don't.

Yes, OSD does use this facility (only XP to my knowledge) so using it is not going to work for you. However, why wouldn't you just put the actions captured in SetupComplete.cmd into the deployment task sequence as run command-line tasks or Install Software tasks?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

One step is to apply a language pack, which needs to be done in the build TS. I've actually moved it there... The others we will move to run as command-line is the deploy TS. Thanks!