Error 0×80004005 - Hyper-V driver issue?

[gramoscscs]

Hi, folks,

 

New to the forums, but a long time fan. Great stuff! Not sure if this is simple or not (probably is and I just messed up --- I hope), but I'm using Microsoft's Solution Accelerator for integrating MDT 2010 Update 1 with SCCM 2007 SP2 and I'm able to create a bootable task sequence and PXE boot a Hyper-V virtual machine and actually get it to start blowing down an image, but it dies with a 0x80004005 error. When I look at the SMSTS.log, it seems like it's driver related (I attached the log). But the errors that caught my eye were:

 

Failed to resolve content for driver "Storage miniport driver (not supported)". Code 0x80040102

Failed to resolve content for driver "Hyper-V Heartbeat". Code 0x80040102

Failed to resolve content for driver "Virtual Machine Bus". Code 0x80040102

 

There were also a couple of warnings in the BDD.log:

 

The TaskSequenceID is blank, possibly a misconfigured customsettings.ini or task sequence

Merge specified, but C:\_SMSTaskSequence\WDPackage\Control\\Unattend.xml wasn't found, unable to merge

 

(The customsettings.ini was modified to include a "DoCapture=Yes" parameter per the MS doc, but I don't recall specifying an unattend setting.) Other than that, the other logs were clean when I nabbed them from the WinPE environment before the VM rebooted following the failure.

 

Anyway, I tried extracting the drivers from the Hyper-V Integration Components *.cab files and then creating a driver package to be included in the task sequence, but that just renders the subsequent ISO unbootable (I get an error like, "Corrupt vmbus.sys" or something).

 

It's weird because I thought for Hyper-V vm's you didn't need to inject drivers. (Unless the issue is something else. I'm kinda lost at this point.) Is anyone using MDT 2010 with SCCM 2007 SP2 integration to create task sequences and bootable media, and then using the resulting ISO to PXE boot and install a reference image in a Hyper-V virtual machine?

 

The Solution Accelerator I'm using is the one found here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&=tm&id=25175

 

Sorry if this is a silly question! I kept all the other logs if they're of any use, but any help anyone could offer would be greatly appreciated!

 

G

smsts.log

[gramoscscs]

Just an FYI, decided to just rebuild from scratch just to eliminate any confounding variables, and that appears to have cleared those driver errors. Getting a new one regarding IIS in 2008, but at least this is documented (http://support.microsoft.com/kb/2508665). Will work the issue from here. Appears to be related to the 2008 IIS version disallowing *.config files to pass through.

 

Thanks to everyone for listening, though! For anyone who was having this issue, I have to confess I did screw up the inital build by installing SCCM 2007 and then integrating MDT before upgrading to SP2. Screw up on my part, but I was too lazy to go back and redo it. This time, I installed SCCM, upgraded to SP2, then went so far as to put on R3 (figured I'd go all in), then after rebooting and letting the dust settle, I installed MDT and ran the integration script.

 

Now, back to this IIS error...