Hi - Anyone had any luck with this model with CM 2012 R2? The problem that we're experiencing is that after the WIM image is applied and after the machine reboots, it should begin the mini-setup phase. What happens instead though is it is in the process of updating the system settings and updating the registry, but never reaches the actual device enumeration phase (i.e. where shows the percentage complete during mini-setup). At this point, it gets a BSOD (stop 0x00000067 config initialization failed). In this scenario, we only have the LSI driver for the mass storage controller, the chipset driver and NIC driver as part of the package for testing purposes. If we remove NIC driver from the equation, this error does not occur and mini-setup runs, however, the NIC won’t be resolved in the device manager, so after mini-setup runs successfully and the machine reboots in preparation to install the SCCM client, it will run into a BITS 2.5 or later required message along with not being able to contact the AD site. We have tried the NIC driver for the “Intel(R) 82579LM” adapter from both HP’s site and Intel’s site and with different version releases, but they all run into the BSOD issue. Currently, we are utilizing an x86 WinPE 5 boot image, but will try an x64 WinPE 5 boot image today if time. These machines do not have a problem when deployed to from SCCM 2007 and they also worked in SCCM 2012 prior to the SCCM 2012 R2, ADK 8.1 and WinPE5 upgrade. If you need me to provide additional details, please let me know. Thanks,-S
