I had built a Windows 7 x64 image and set up a task sequence to deploy it. Some of the steps in my task sequence added or changed keys in the registry with a command line. It used to work great... I recently switched my image to SP1 (still Win7 x64) and now I notice some registry keys work and some don't. The command lines run in the task sequence and I get a success status message in my advertisement status, but the registry keys are not created/changed in the registry. Here is an example of one of the command lines I am running to try to change the AutoAdminLogon key: reg add “HKLM\Software\Microsoft\Windows NT\Currentversion\Winlogon” /v AutoAdminLogon /d 1 /f This task runs and reports a success status message. But after the task sequence finishes the AutoAdminLogon key is still set to zero instead of 1. I have 64 bit file system redirection disabled (checked) and I have tried changing the "Start In" line to C:\WINDOWS\SYSTEM32. Each time everything looks good in my SMSTS.LOG and my status messages say the step completed successfully, but the key is set zero... I searched the entire registry to see if another "autoadminlogon" key was being created and set to 1 someplace else but its not. Furthermore, I know the command line works because after the PC is built I can open a command prompt and manually run it and the key value will change to 1. It just won't work inside my task sequence anymore. This used to work great before I switched to SP1. Does anybody have a possible explanation??? Thanks, Jan

I have no explanation, but you could test something: create a new custom task sequence that contains just one step (run command line including all settingsetc) as you mentioned above and advertise it to a Win7x64SP1 machine. I am curious about the results then ...Torsten Meringer | http://www.mssccmfaq.de