Question about WinPE Drivers in OSD 3.2

Usage and Config
1

(imported topic written by mctivy2)

We have several computer systems that are failing on reimage because they are missing drivers. This is because the drivers are not in the WinPE image. Previous version of IEM let you inject the drivers from the install screen (see option :
http://pic.dhe.ibm.com/infocenter/tivihelp/v26r1/index.jsp?topic=%2Fcom.ibm.tem.doc_8.2%2FLifecycle_Man%2FOSD_Users_Guide%2Fc_additional_winpe_drivers__opti.html&lang%3Dzh_CN
). However, this appears to be removed in the new version. So the question is: do we inject the drivers into WinPE with a Microsoft tool like DISM or are the drivers automatically added to WinPE during deploy if they are selected as part of the OS Image?

2

(imported comment written by francesco.latino)

Hi,

during the Reimage we automatically inject compatible drivers from Driver Library (Win7 x86 drivers are used for WinPE3 x86, Win7 x64 for WinPE3 x64,…) into the WinPE being booted and next reboot.

So what happens is:

  • prior to boot WinPE

  • we download from Driver Library compatbile drivers and add into WinPE (not with a DISM command installing it offline, just adding to the WIM)

  • at WinPE starts, added drivers are expanded and started with drvload command (so runtime driver load procedure)

What you experienced was WinPE booting and not able to find NIC or Disk ?

You may stop with CTRL+C the WinPE dos shell (just before the failure), take control over the shell and test your driver with drvload <driverfile.inf> (from a USB key).

If the driver is correct, check in the Driver Library its compatible OSes are correct (e.g.: Win7x64 if you are using WinPE3x64)

Some useful runtime logs are at c:\Deploy\Boot*.log where the computation is performed.

You may attach some pictures (of driver library drivers) and logs if you want.

Thanks

Francesco

3

(imported comment written by mctivy2)

Thanks- it was because the driver had to be specific, even though it was back a few revisions. We manually bound the specific driver and it worked. This was for the hard drives -