I am trying to deploy to a Dell 7010 using provisiong and HII. Everything goes well until you get to the HII part. It will install all the drivers and then get to the end and say it failed. Does anyone have any clue what would be causing this?

Looks like it is trying to install an unsigned boot critical driver. A boot critical driver would be something like a hard drive controller that obviously Windows can't run without. Can you find a signed driver to use instead of the unsigned one for whatever hardware is the problem? In that log you attached you can just search for unsigned to find the affected drivers.

I still contuine to have the same problem. I just delete all of my dirvers and rebuild my driver store and it seems to fix it. I am wokring with LANDesk support to get a better answer of to why it is happening but if you find out any more that would be great.

2014-01-03 11:27:39, Info IsDriverPackageSigned: File [j:\Windows\LDDriverStore\E5520_Win864\IntelManagementEngine\HECI.inf] is signed by a catalog [j:\Windows\LDDriverStore\E5520_Win864\IntelManagementEngine\HECI.cat]

2014-01-03 11:27:39, Info IsDriverPackageSigned: File [j:\Windows\LDDriverStore\E5520_Win864\STMicroFreefallSensor\accelern.inf] is signed by a catalog [j:\Windows\LDDriverStore\E5520_Win864\STMicroFreefallSensor\accelern.cat]

This log indicates that the O2MDRw8x64.INF driver package is unsigned. x64 Windows after Vista and some x86 Windows have the requirement that the driver be signed. There are some ways to try and bypass that. Because of the strict recommendation that Microsoft gave to not allow unsigned drivers the decision was made to not run the /forceunsigned switch with DISM when we run the driver install process.

A quick workaround that should be valid after 9.5 SP1 (and possibly 9.5) would be to set that action as not required (ie, uncheck the box that says "Fail template if action fails" or whatever the wording is) and add an action immediately after that runs

(where C: is the drive Windows is installed to). We are discussing options such as making this configurable. I would like to know from those on this thread what you would think of having that option back vs. the severe security warnings given by Microsoft about the use of unsigned drivers. Would you like the option to take on that risk or do you believe that a hardware manufacturer should provide the signed driver for all circumstances?