Build and Capture Task Sequence Failure
Posted by Jarvis on February 27, 2008
I have fought with this before and didn’t figure it out. Been fighting with it again and finally made an educated guess that has since been backed up by finding a thread to support my findings.
I created a Task Sequence in SCCM to “Build and capture a reference operating system image”. I am using the Vista SP1 DVD that I imported into Operating System Install Packages. It gets part of the way through the install, and then fails. By opening a command prompt on the machine running the Task Sequence (F8), I was able to look at the log files. In looking at the x:windowstempsmstslogsmsts.log log file, I saw an entry that stated “Windows Setup Failed, code 31″. That was followed by “Exiting with code 80004005“. Not a lot of help. Then I found the x:\windows\temp\smstslog\windowssetuplogs\setuperr.log log file. That contained the following lines:
Callback_Productkey_Validate: EditionID for product key was NULL.
Callback_Productkey_Validate: An error occurred writing the product key data to the blackboard.
Callback_Productkey_Validate_Unattend:Invalid product key; halting Setup.[gle=0x00000490]
Callback_Productkey_Validate_Unattend: An error occurred preventing setup from being able to validate the product key; hr = 0×80300006[gle=0x00000490]
Now…I know that my volume license product key is good. I’ve been using it for a long time. Just for grins I popped the Vista DVD in a spare computer and confirmed it. Why is it telling me the license key is invalid?
So here comes the educated guess. I modified the Task Sequence to not use a Product Key…just left that field blank. Hmmm…the install works perfectly fine. That led me to search on something different and find this thread. Basic gist is that if you are using a Task Sequence to install an OS using an Operating System Install Package, you should NOT specify a product key. Perhaps that is documented somewhere, but I haven’t seen it. It is however doggone frustrating to have wasted as much time as I have on this problem.
March 3, 2008 at 12:03 pm
Hey,
how did you solve your problem? when i leave the product key empty i get the question for it during the setup.
did you create a pid.txt? how does that file looks like ? any special syntax ? maybe you can help me.
thanks
March 3, 2008 at 12:33 pm
The Build and Capture task sequence is used to automate the build of a reference computer. What you are creating with the Build and Capture is an “image” that you will use another Task Sequence to deploy. The build and capture TS is using an “Operating System Install Package” (essentially an uploaded CD/DVD of the original install media) to build your reference computer and then uploading a WIM file. You actually won’t use this task sequence to directly deploy a computer.
After it is uploaded, you will go to the “Operating System Images” portion of OSD (directly above the “Operating System Install Packages” section). In there, you will click “Add Operating System Image” and point it to the WIM that you created with the Build and Capture TS.
You will use another TS to deploy that WIM file to hardware. That Task Sequence is where you put the product key. When it deploys, it will use that key, and you won’t get prompted for it.
March 19, 2008 at 6:22 am
Thank you Jarvis.
Your post saved me hours of searching.
I had this error 80004005 too.
It works now !
March 19, 2008 at 8:16 am
Glad it helped Hanna. The 80004005 code is always so helpful [sarcasm]. That’s why I loved Johan’s description of it!
March 27, 2008 at 9:02 am
Thank YOU! We’ve been looking for this error for almost two working days now. Thanks again!
April 11, 2008 at 2:31 pm
Had the same error…and this fixed it. So random :)
Thanks for the blog post, it saved the day.