I'm in the process of testing OSD in SCCM SP1. During the "Prepare OS" phase which uses Sysprep to capture the reference machine, the TS fails with error 0x00004005. From what I can find, the SMSTS.log file has little information surrounding this error. Specifics of interest are: 1.Running SCCM SP1 on VMWare in a virtual private network andattempting to build/capture a vmware virtual machine 2. Using 32-bit Windows XP SP3 for the OS Install Package 3. All prior tasks within the TS complete successfully 4. The sysprep package does have the XP SP3 version of sysprep 5. During the Install Software task, I copy the I386 folder to the root C:\ of the image being built Any troubleshooting help is much appreciated.

Hi there, I have created this guide "Building your Windows XP Reference Image on VMware ESX Step by Step" found here on my blog http://jensolekragh.spaces.live.com/blog/cns!805B93F8AD5DCF57!231.entry Hope it can help you.

While that is helpful, it hasn't resolved the problem The only thing I hadn't already done was define the Apply Drivers stuff. Other ideas?

Here's another question for anyone who can answer. What exactly is the Prepare OS task sequence doing? Just running C:\Sysprep\sysprep.exe -mini -quiet -reseal -activated? Maybe this problem has something to do with XP SP3? I know there is a hotfix for XP SP2 in order to use sysprep. Maybe it's the same type ofproblem. I'll have to check. * Update * - that hotfix (887816) is for default user functionality, nothing more.

Hi, Could you please check what the client reported back to ConfigMgr about the error. I suspect that the problem is about sysprep is not able to set the local administrator password to blank. I have this error my self, and have a workaround for the problem.

Thanks for your willingness to help. From another post I read recently, I would believe that you're right in that sysprep is unable to set the local administrator password. During TS "Apply Windows Settings", I enable the Administrator account and give it a generic password. Should I set the password field blank or randomize the password? Two errors returned to advertisement status as follows: The task sequence execution engine failed executing the action (Prepare OS) in the group (Capture the Reference Machine) with the error code 16389Action output: chine Certificates succeededExecuting 'C:\sysprep\sysprep.exe -reseal -mini -quiet -noreboot' ...Command line for extension .exe is "%1" %*Set command line: "C:\sysprep\sysprep.exe" -reseal -mini -quiet -norebootExecuting command line: "C:\sysprep\sysprep.exe" -reseal -mini -quiet -norebootFailed to show task sequence progress dialog. Error code 0x8001010eProcess completed with exit code 0The OS has not been generalized using sysprep.exe, or sysprep did not complete.bSysPreped, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\prepareos.cpp,522)RunSysprep(sCmdLine, bActivate, m_bDebug), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\prepareos.cpp,1326)pCmd->Sysprep(bActivate, bMsd), HRESULT=80004005(e:\nts_sms_fre\sms\client\osdeployment\prepareos\main.cpp,270)De-Initialization successfulExiting with error code 16389Sysprep did not complete successfullyUnable to sysprep the machine, hr=80004005Sysprep'ing the machine failed, hr=80004005. The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned.

To clarify, the local security policies are configured as such: "Password must meet complexity requirements" = disabled "Minimum pasword age" = 0 days "Minimum password length" = 0 characters

OK, this kills me, but I have "the answer". The password could not be reset (thus halting the process) because I had not installed any .NET Frameworks as part of the core image build. I installed 1.1 SP1, 2.0 SP1, and 3.0 SP1. At this point I'm out of energy to officially determine which component is necessary, but I highly suspect the 2.0 framework was a requirement. I wonder if there is a way for MS to add this into their documentation? Or maybe it is there but I completely overlooked it!!

Great info, I'll try to test it out at a customer site tomorrow (same problem), if time allows, and get back with the results.

Hi again, Sorry, but I didn't have the time to do the test at the customer site. Workaround: is to set the "default domain policy" to no complex passwords and password lenght = 0 while you do the build and capture, actually not very nice, but is works for now. Any one else expirencing this problem?

Well, my task sequence never joins the system to the domain, so it is not impacted by that policy.

This thread is getting old LOL. OK, as I've come to figure out, .NET is only a portion of the equation. If a TS is run to only build the OS and software installs AND another TS is used to do the capture, then .NET appreas to be necessary to do the capture. However, using a sole TS to the do the OS build, software installs, and capture, a problem still exists. Someone gave me a tip to inspect Sysprep more thoroughly....what I have found may be the problem I'm having. First, the administrator account is not created during the install of the OS. Or somehow is getting removed. Second, during the "Install Deployment Tools", Sysprep (for XPSP3) is copied to C:\_SMSTaskSequence\Packages\PkgID\ and not to C:\ - this is likely the primary cause for failure. I'm trying to understand how this "Install Deployment Tools" knows what to do with Sysprep package. I'm assuming something is going awry because, correct me if I'm wrong, XP requires the sysprep directory to be right on the root C:\ drive. This should probably be a new thread since it's adifferent error (0x0000107) but my problems are still occuring. Somehow it changed. Pffttttttttttt................

I also get this error (0x00004005) when doing a capture using capture media, during the sysprep part. I manually copied sysprep to c:\, the machine has every version of .net from 1.0 to 3.5, and the error still persists. I have also tried the default build and capture TS, with an error during the sysprep step on capture in winpe either 0x00000002 or0x00000032. Any new answers on this? Another 8 hour call with MS doesn't seem fun...

Sorry, I forgot to follow up with my resolution with this thread. I was able to resolve the problem by removing thefollowing from my sysprep.inf file. I don't quite understand the cause, but in reality with SCCM, it isn't necessary because of the enhanced driver injection. Hope this helps. [Sysprep] BuildMassStorageSection= Yes [SysprepMassStorage]

Hi, we encountered the same error "image capture wizard has failed with error code 0x00004005" while doing an image capture of xp sp3 during the sysprep part. This only happened to the desktop (Dell Optiplex 780), but we were able to use the same wizard on another hardware (laptop). there's only 1 active NTFS partition with the OS and another FAT EISA partition that's part of Dell standard config. any help is greatly appreciated, thanks!

I Had the same problem capturing a Windows 7 machine. After a while I found out you're only allowed to sysprep a machine for a maximum of 3 times.... (http://support.microsoft.com/kb/929828) I had to rebuild my capture machine from scretch....

Greetings! I'm having same error in TS advertisement log - The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned. So, the problem is that TS ends after or before completing sccm client installation, and none of advertised application start running installation, what should be done by TS. I have another model which runs similar TS and it goes all the way, but this no. Same sysprep is used and same application list. Password is not blank, but I think I will fail of I delete BuildMassStorageSection= Yes - section. Has anyone solved this for sure?

What you can do is update your base VM and when you are about to run the sysprep first make a copy then run the sysprep. Also update the copy that way it will have never been syspreped.