none
SCCM 2012 SP1 - WinPE 4.0 - Win7x86 image creation network driver fails

    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.

    thanks for any tipps

    ...
    2013-01-28 09:11:22, Info                         PnPIBS: Finished building list of drivers in the path C:\_SMSTaskSequence\drivers.
    2013-01-28 09:11:22, Info                         PnPIBS: Driver C:\_SMSTaskSequence\drivers\1\E1C6232.inf is being queued up for addition to the offline image.
    2013-01-28 09:11:22, Info                  IBS    Callback_Compliance_GatherDeviceIDs:Driver package is [C:\_SMSTaskSequence\drivers\1\E1C6232.inf]
    2013-01-28 09:11:22, Info                  IBS    GatherDeviceIDsInDriverPackage:Driver package path is [C:\_SMSTaskSequence\drivers\1\E1C6232.inf]
    2013-01-28 09:11:22, Info                         GetModelSectionNameEx:Using section name [Intel.NTx86.6.1.1]
    2013-01-28 09:11:22, Info                  IBS    AddDeviceIDsToInjectedDriverNodeHelper:Model section name is [Intel.NTx86.6.1.1]
    2013-01-28 09:11:22, Info                  IBS    GatherDeviceIDsInDriverPackage:Successfully gathered device ID's from [C:\_SMSTaskSequence\drivers\1\E1C6232.inf]
    2013-01-28 09:11:22, Info                         PnPIBS: Successfully gathered device ID's from [C:\_SMSTaskSequence\drivers\1\E1C6232.inf]
    ...

    ...
    2013-01-28 09:14:27, Info                  IBS    Callback_Unattend_InitiatePass: Initiating unattend CBS pass [offlineServicing]
    2013-01-28 09:14:27, Info                  IBS    InstantiateCBSUnattendPass: Calling dism.exe to initiate CBS unattend pass...
    2013-01-28 09:14:27, Info                  IBS    LaunchPackageManager: Using local folder [C:\$WINDOWS.~LS\PackageTemp\78fab6e0-0b47-4240-a2d0-7213f2d7821d] for temporary package storage.
    2013-01-28 09:14:27, Info                  IBS    LaunchPackageManager: Launching [C:\_SMSTaskSequence\Packages\K920000A\SOURCES\dism.exe  /logpath:C:\$WINDOWS.~BT\Sources\Panther\cbs_unattend.log /scratchdir:C:\$WINDOWS.~LS\PackageTemp\78fab6e0-0b47-4240-a2d0-7213f2d7821d /image:C:\ /sysdrivedir:S:\ /windir:Windows /apply-unattend:C:\$WINDOWS.~BT\Sources\Panther\unattend_cbs_copy.xml].
    2013-01-28 09:14:40, Info                  IBS    InstantiateCBSUnattendPass: dism.exe returned with exit code 0.
    2013-01-28 09:14:40, Info       [0x0a0024] UI     progress task ProgressInfo\CBSServicing : EndProgress
    2013-01-28 09:14:40, Info       [0x0602a4] IBS    CallBack_AddDriverPackageIntoDriverStore:Driver package path is [C:\_SMSTaskSequence\drivers\1\E1C6232.inf]
    2013-01-28 09:14:40, Info       [0x0602b2] IBS    CallBack_AddDriverPackageIntoDriverStore:Driver package is [NOT critical]
    2013-01-28 09:14:40, Info                  IBS    AddDriverPackageIntoDriverStore:Driver package path is [C:\_SMSTaskSequence\drivers\1\E1C6232.inf]
    2013-01-28 09:14:40, Info                  IBS    AddDriverPackageIntoDriverStore:Image architecture is [0x0]
    2013-01-28 09:14:40, Info                  IBS    AddDriverPackageIntoDriverStore:System root is [C:\Windows]
    2013-01-28 09:14:40, Info                  IBS    AddDriverPackageIntoDriverStore:System drive is [C:\]
    2013-01-28 09:15:01, Warning    [0x0602b1] IBS    AddDriverPackageIntoDriverStore:Failed to add the driver package [C:\_SMSTaskSequence\drivers\1\E1C6232.inf] into driver store. Error code is [0x80070032]
    2013-01-28 09:15:01, Warning    [0x0602a9] IBS    CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [C:\_SMSTaskSequence\drivers\1\E1C6232.inf]. Driver package is [Non Critical]. Error code is [0x32]
    ...

    Monday, January 28, 2013 9:08 AM

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



    Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady

    Monday, January 28, 2013 9:59 AM
  • Hi Niall

    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.

    Monday, January 28, 2013 12:41 PM
  • Hello Niall,

    Did you solve the problem?

    We have the same after updating to SP1 Windows 7 Deployment is not working anymore.


    Andre van den Berg

    Wednesday, February 13, 2013 1:05 PM
  • 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.

    Andy


    My Personal Blog: http://madluka.wordpress.com

    Wednesday, February 13, 2013 2:40 PM
  • Same problem here after upgrading to SCCM 2012 sp1....
    Friday, February 15, 2013 3:00 PM
  • 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.

    Andy


    My Personal Blog: http://madluka.wordpress.com

    Monday, February 18, 2013 5:56 PM
  • Hi,

    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.

    So my suggestion is to create custom Boot image based on Windows 7.

    Regards,

    Grega

    Tuesday, February 19, 2013 3:37 PM
  • Hi,

    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.

    So my suggestion is to create custom Boot image based on Windows 7.

    Regards,

    Grega

    A good suggestion, however WinPE 3.0 boot images cannot be imported into ConfigMgr 2012 SP1 - only WinPE 4.0 is supported.

    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.


    My Personal Blog: http://madluka.wordpress.com

    Wednesday, February 20, 2013 10:01 AM
  • I concur with MadLuka.

    Jason | http://blog.configmgrftw.com

    Sunday, February 24, 2013 9:25 PM
  • I am getting the same error after upgrading to SP1. 

    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.

    Tuesday, February 26, 2013 5:06 PM
  • Hi, I'm having the same issue

    If you use the originall installation source you get the problem. If using apply WIM file though then there's no issue.

    I manually installed the network driver with the vendor exe just after mini setup to get my image captured because i can deploy the imgae without issue.

    I'm using the same Windows 7 driver in both the WinPE boot image and in the apply device driver task.

    Cheers,

    Rus

    Friday, March 08, 2013 7:50 AM