Asked by:

Question

I have SCCM 2012 SP1 and use the integrated WinPE 4.0 boot image to create a Win7 master image.
I added the actual network driver for Intel 82579LM into the driver store and created a driver package, the driver inf is the same for Win7 x86 and Win8 x86.
When I create a new Win7 x86 master image the driver gets successfully injected in step "Apply Device Drivers" or "Apply Driver Package"(tried both) and the "DriversPath" will also be set in unattend.xml.
However after Reboot in Minisetup the driver fails effectively installing - see below sections from C:\Windows\Panther\setupact.log.
Of course my image can't get done and captured then. If I manually do pnputil -i -a in a dos box the driver can be installed without any issues and gets ip immediately.

All replies

patching the boot image is not the same as using the driver in an apply driver package step,

so i would suggest you have the wrong driver in your driver package, or you have an incorrect WMI query on the Apply Driver Package step itself (to identify the hardware) or the driver package is missing on your distribution points

seems not to be the issue, the boot image has the correct Win8 driver and the driver package has the correct Win7 driver.
Also if I add the failed driver manually with pnputil right after error - it works so the driver seems correct.

I also tried the newest driver directly from Intel site - same issue.

I did not yet create any WMI filters - only have one model currently - and the Task Sequence is out of the box SCCM SP1.

I have SCCM 2012 SP1 and use the integrated WinPE 4.0 boot image to create a
Win7 master image.

Does this issue only occur when you are running a task sequence that uses the original install.wim or source media files instead of a captured .wim image? Also, I am curious as to if you actually
need to inject your own version of the 82579 driver into WinPE 4.0 as I find network driver support is pretty good out of the box for WinPE 4.0.

Are you using the latest Intel ProWin64.exe (or ProWin32.exe) drivers and using the proper NDIS63 (Windows 8) driver for the WinPE 4.0 boot image and the NDIS62 (Windows 7) driver for the Win7 driver package?

I have found/observed that the Intel 82579LM driver when extracted and imported into the catalog has a SPECIFIC NDIS63 Windows 8 ONLY driver that is not tagged as being suitable for Windows 7 - so maybe it is that. I can say that I have no
problems with deploying/building systems using the right drivers for the 82579 based card.

When you boot in WinPE 4.0 your NIC is not missing and PnP enumeration doesn't apply any NIC driver. If you would use WinPE 3.0 (Win7) your NIC would be missing and PnP should find it in driver package and apply it to install process.

When you boot in WinPE 4.0 your NIC is not missing and PnP enumeration doesn't apply any NIC driver. If you would use WinPE 3.0 (Win7) your NIC would be missing and PnP should find it in driver package and apply it to install process.

My understanding is that as long as you are deploying a .wim file (and not using the install source media/setup.exe) then the "Apply Driver Package" step injects all drivers in the package regardless of PnP detection. When the "Setup Windows and ConfigMgr"
step runs, this is performed by the OS (not WinPE 4.0) and PnP will install whatever devices it can find matching drivers in the now populated DriverStore.

I think this is all just about getting the right network driver for the OS being deployed and making sure to use the install.wim. I personally use Virtualised Hardware for image creation - thus there are no driver requirements for getting my reference image
built.

Actually, in my case this is happenning not only for he network card driver, but all the other drivers I have tried (video, chipset, amt). The drivers have been downloaded a few days ago and apply to Windows 7.

The way I got around it so far, was to actually use dism to add the network card drivers to the base image install.wim. The rest of the drivers get installed as applications. This is not ideal, but is working until the solution is found.

Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.