I have just taken delivery of a new eval PC (Intel DQ67SW) from our suppliers and I can't get the thing to build Windows 7 Ent x86 or XP. I have added a apply driver step to the task sequence to inject the "(intel) ESB2 SATA AHCI controller" and "Intel Desktop/Workstation/Server Express Chipset SATA AHCI controller" Driver I think its something to do with the SATA driver not loading. here is the log file from the smsts.log Error Milestone LIV 11/05/2011 10:31:06 BUILDCAPTUREA Task Sequence Engine The task sequence execution engine failed executing the action (Setup Windows and ConfigMgr) in the group (PostInstall) with the error code 2147500037 Action output: ce\unattend.xml Successfully initialized driver information Command line for extension .EXE is "%1" %* Set command line: "C:\_SMSTaskSequence\Packages\LIV001B8\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot Executing commandline: "C:\_SMSTaskSequence\Packages\LIV001B8\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot Process completed with exit code 31 Windows Setup completed with exit code 31 Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\LIV001B8 reference count 1 for the source C:\_SMSTaskSequence\Packages\LIV001B8 before releasing Delete source directory C:\_SMSTaskSequence\Packages\LIV001B8 Released the resolved source C:\_SMSTaskSequence\Packages\LIV001B8 exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440) setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707) Exiting with code 0x80004005 Windows setup failed, code 31. The operating system reported error 2147500037: Unspecified error 11135 Do I have to do anything else because when Windows boots for the first time I get error "BOOTMGR is Misssing"

When choosing the "Apply driver package" step instead of "auto apply drivers" the SATA AHCI driver and model can be selected. Just try some different types of drivers and models if they are available. When building a new image from source files, put the auto-apply drivers or apply driver package step before the "Apply Operating System" step. Otherwise specific drivers (SATA AHCI disks for example) will not be functional when booting from disk. When distributing a Windows image (WIM file), put the auto-apply drivers or driver package step after the "Apply Operating System" step.My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

OK I sorted the issue. the logs above are erroneous, this was caused be a incorrectly set role in MDT which was picking up a XP licence key. here are the correct steps/settings •make sure that the correct Device is configured in the Bios (in my case AHCI controller) •download the SATA driver from intel •import the drivers into SCCM and create and deploy package •add a task sequence step "Apply Drivers" in options add a condition "SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%DQ67SW%"" •in properties check the "select the mass storage driver....". •Select the Intel ESB2 SATA AHCI Controller •Select Model "Intel Desktop/Workstation/Server Express Chipset SATA AHCI controller" •Select "Do Unattended installation........"