none
Injected drivers for new build but not deploying image RRS feed

  • Question

  • I've had SCCM 2012 deploying an image to 2 different machines for a year now but I've just bought a new model. I've added the drivers, packaged them and added them to the boot image but when trying to apply the image to the new PC it gets to the WINPE splash screen then reboots. I've checked ipconfig and the machine doesn't look like it's picking up an IP address at this point. I must be missing a step but from what I can see it looks like the driver is available for the system.
    Tuesday, July 30, 2019 12:59 PM

Answers

  • Then the driver is not correct. 

    You need to make sure that the architecture matches as well; i.e., x86 and x64.

    Also, successfully loading the drvload for testing is only the first step. After doing so, did you run ipconfig to see if IP info is displayed? If not, it's not the correct driver for the NIC. 


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by danliddz Thursday, August 1, 2019 7:35 AM
    Wednesday, July 31, 2019 1:18 PM

All replies

  • First, note that you should only be adding NIC drivers (and sometimes storage drivers) if and only if they are necessary'; other driver types are not needed and could cause problems in the boot image. Additionally, WinPE boot images include many drivers by default so adding drivers is often not even necessary.

    Next, drivers in the boot image have nothing to do with drivers deployed and used by the Windows instance installed by the task sequence.

    Finally, you need to add drivers to a boot image that match the version of the boot image. WinPE boot images require Windows 10 drivers, WinPE 5.x boot image require Windows 8.x drivers, WinPE 4.x boot images require Windows 7 drivers, and WinPE 3.x boot images require Windows Vista drivers.

    What version exactly of ConfigMgr are you running, what boot image version are you running, and what OS are you deploying?

    Also, when you check ipconfig, is it showing an APIPA address or is it not showing any IP information at all?

    Finally, you can easily test drivers in WinPE by placing them on a USB stick/key and using the drvload.exe command to load them.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, July 30, 2019 3:47 PM
  • Thanks Jason, 

    I've added the network drivers in and I'm using the versions below

    Win 10 - Boot image 5.00.8634.1010 CCM version 1802.

    No IP address showing at all. The driver loads through drvload fine but still no further than the initial win pe splash screen then a reboot.

    Wednesday, July 31, 2019 1:03 PM
  • Then the driver is not correct. 

    You need to make sure that the architecture matches as well; i.e., x86 and x64.

    Also, successfully loading the drvload for testing is only the first step. After doing so, did you run ipconfig to see if IP info is displayed? If not, it's not the correct driver for the NIC. 


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by danliddz Thursday, August 1, 2019 7:35 AM
    Wednesday, July 31, 2019 1:18 PM
  • Thanks Jason, 

    The driver I was using wasn't correct as thought. The tool I was using to extract the driver didn't supply the right one and after a bit of digging for a better tool on tech net I found the right one.

    Thursday, August 1, 2019 7:36 AM
  • As a general rule, particularly for NIC drivers in boot images, always download and use the ones available from the vendor when necessary. That way, there's no ambiguity.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, August 1, 2019 2:12 PM