Not sure what was broken, but I built another captured image with MDT 2013 and the Precisions started imaging without issue.

The differences between the captured images were:

• inclusion on 32-bit Java installation
• change in the licensing model on the Office installation (from MAK to KMS)
• software updates since last build - which would have been January and February patches.

Again, I don't think the above differences would have corrected the problem - but nevertheless, I am now building Precision systems without issue.

Hey ByronTodd - we've run into a similar issue at our company, except only with newer Inspiron 7010 series.  I've already built a new base image (suspecting corruption) but I didn't make any changes to the included applications.  I also built new driver packages and boot images (suspecting an issue there as well) and made some progress, but still see failures every 1 in 5 images or so.

Anyways, I'm thinking that a combination of boot image / base image are at fault, but I was hoping you could elaborate on the differences in your captured images?  Does the newly capture image include or not include Java?  My guess is that Java is at fault in our image as well - but I wanted to confirm before I go through the hassle of rebuilding the base image yet again.

Having the same problem since starting to use MDT 2013 to build master images vs. SCCM.  The problem only impact Precision M4800.  Latitude and Optiplex models have no issue. Has anyone found a solution to this problem?

Similar issue in our environment with only the Precisions (M4800,M6800,T1700) facing this issue, all other models (OptiPlex, Latitude) image without issue. After the Precision driver package applies the computer reboots and blue screens.

If we use an earlier captured WIM then we have more success with the driver pack applying successfully but there wasn't much added to the new WIM apart from Windows Updates.

Anyone else seeing this issue with Precisions or know where to start looking to diagnose what's going on?

I opened a case with Microsoft and solved the issue by making a shim to the WinPE 32-bit boot image as described in this post:

http://blogs.technet.com/b/dip/archive/2015/01/21/win2008r2-win7-stop-0xf4-during-task-sequence-os-deployment.aspx

This basically tells WinPE not to try to compress the registry.  My guess is that the issue is related to this model having a large amount of memory.  In my case, the M4800 is my only hardware model with 16GB of RAM.  All other models have 4GB or 8GB and none of them have this issue.

Hi All,

Could someone share the winpe cab and driver cab details which is  used ?

Thanks,

Hema_client

Thanks very much for that. It could definitely be the same issue for us as the Precisions are the only ones with > 16Gb of RAM.

How did you apply the shim to the WinPE boot image? Did you mount the WIM and then edit the registry or just use 'reg add' as one of the first steps in the task sequence to add in the registry key.

Thanks for your help!

I mounted the boot.wim and added the reg value set to 999. Then, just updated the boot image in SCCM.

Got the same with Optiplex 3040 (Win 7 x64)

Using the same image/TS/boot image on many other models & never fails.

Just OP 3040. Sometimes it will finish fine, mostly will fail on drivers apply dism install step

Dism /add-drivers /recurse works fine, no no issue with drivers

I get "very" descriptive error in smsts.log:

Failed to create temporary package manager directory C:\_SMSTaskSequence\PkgMgrTemp. Code 0x800700b7

Failed to provision driver. Code 0x800700b7

Kind of like that (but only for this one model):

blogs.technet.microsoft.com/.../

Gave up on trying to find out why, went with simple dism as per this

Got myself TS variables as per this and run as per ie this

dism /image=%OSDTargetSystemDrive%\ /add-driver /driver:. /recurse /logpath:"C:\temp\dism3040.log"