Attempting to capture a Windows XP Sp2 image using a custom task sequence. The referencecomputer has had the ConfigMgr client installed, the local administrator account is blank,and it has been sysprepped. It immediately failes during the "Prepare OS" step with the 0x00000032 error. The capture TS is as follows: 1. Prepare ConfigMgr Client 2. Prepare OS 3. Capture the reference machine Idea's?

Hi Jeff, The image capture process for ConfigMgr needs to sysprep the machine itself (e.g. the machine should not be sysprepped before you capture the image) so that it can gather some information about the operating system before rebooting into WinPE. A custom task sequence would need to start in the Full OS and contain the following steps: 1. Install Deploy Tools (to copy sysprep to the local machine) 2. Prepare ConfigMgr Client (to wipe the client identity and prepare it for deployment) 3. Prepare OS (to run sysprep and reboot the machine) 4. Capture System Image (to capture the image) You can also create a capture CD to automate these steps and/or use the new task sequence wizard to create a task sequence to do a scripted install and capture of Windows. -- Brett

Thanks Brett for the input. Following the exact TS steps above, the issue persists. Would it be helpful if I were to either send you, or post a log from the installation attempt?

Hi Jeff, Yes - please post the part of the smsts.log file that contains the error (see http://blogs.technet.com/inside_osd/archive/2007/12/13/troubleshooting-tips.aspxfor information on how to get the log). Thanks, -- Brett

Sorry to dig this thread up, but I found it on Google when I was searching for a solution of a very similar problem and I think other might find it the same way. I found that it was due to a "Restart" in my task sequence being set to "The boot image assigned..." rather than being set to "The currently installed default..." Once I set it to the currently installed OS the error went away. Alex

Hi Jeff, The image capture process for ConfigMgr needs to sysprep the machine itself (e.g. the machine should not be sysprepped before you capture the image) so that it can gather some information about the operating system before rebooting into WinPE. A custom task sequence would need to start in the Full OS and contain the following steps: 1. Install Deploy Tools (to copy sysprep to the local machine) 2. Prepare ConfigMgr Client (to wipe the client identity and prepare it for deployment) 3. Prepare OS (to run sysprep and reboot the machine) 4. Capture System Image (to capture the image) You can also create a capture CD to automate these steps and/or use the new task sequence wizard to create a task sequence to do a scripted install and capture of Windows. -- Brett Hi Brett,Several questions about this process:- Where are the Drivers? Do I need another task "Apply Driver Package"?- When you said "Copy Sysprep" is it just a script which copy sysprep.exe, sysprep.xml etc... or the command line itself "sysprep /generalize /oobe /shutdown /unattend:sysprep.xml' which is passed in the command line box(e.g. the machine should not be sysprepped before you capture the image)?Thanks,- DomAltiris Support / System Center Configuration Manager Support

If you are using the "New Task Sequence Wizard" to "Build and capture a reference operating system image" it includes "Apply device drivers"Quote of the day: "We're gonna wait for Windows 7"

hi did u solve this error 000000032 ?

Hi, I have sama problem when capture windows xp sp3 with task sequence ( sccm ) error 0x00000032, please help me. Thanks, Arisg