Greetings,

I have a SCCM 2012R2 Task Sequence for my Windows Servers (OS: 2012R2) that has been working on one model of server (IBM x3650 M4) but now with the new model (Lenovo x3650 M5) it is not working anymore. The step it fails on is right after the image gets applied, and Windows Setup kicks off, after the automatic reboot that Windows Setup initiates it fails upon the setup of windows. The error message is: "Windows Setup could not configure Windows on this computer's hardware" and is explained in this link.

One thought I had was that this could be Storage driver related. All that I've added to the boot image are NIC drivers, I have not added any storage related drivers. I'm not sure if they are needed however. My Task Sequence correctly kicks off with WinPE, formats and partitions the hard drive, and copies down my custom .wim successfully. I can run diskpart and see my disk. So is a storage driver actually needed?

Unfortunately when the error is encountered it is not during the Task Sequence so I can't get any logs. I also can't get to a command prompt with shift+f10 to see what exactly might be causing the error.

Any insight as to when storage drivers are actually needed in the boot image?

If the TS gets past partitioning the disk, then the boot image has successfully already has accessed the disk and thus the drivers included in the boot image are sufficient.

To get to the Windows setup logs, boot back into WinPE via a boot image and drop to a command-prompt -- don't kick off a task sequence. 

Thanks Jason - never thought of using the boot image to get to a command prompt. Now I can begin troubleshooting these sysprep errors in the setupact.log