You will have seen the button in the console: Manage the drivers in the Windows PE image. Using that button to add a network driver is entirely straightforward. Much less so in the case of a mass storage driver, however. As you can read in http://community.landesk.com/support/docs/DOC-1157, if you just click your way through the wizard and do everything right, chances are things won't work for you. You need to edit one of the driver files (txtsetup.oem) to reflect the relevant hardware ID for your target machine. If you have multiple target machine types, you may need to import the same driver multiple times, each time with a different txtsetup.oem.

 

This article describes an alternative approach that avoids the need to customise any files, or to inject the driver multiple times.

 

But first, let's make an observation about SATA drivers. Most of today's desktop and laptop machines are using intel SATA chipsets. If the processor is intel, then usually the SATA controller is intel. In general (there may be a few older machines that break this rule), all these machines can use the same SATA driver. The PC manufacturers simply pass through the original intel driver with no customisations (except a new wrapper for licensing reasons). If there is a difference, it will be that the manufacturer's driver is an earlier version that doesn't support some of the newer hardware. If you want a WinPE image that runs on as many machines as possible, your best bet is to use the latest intel driver. Chances are it will work on all your SATA desktops and laptops. One driver fits all.

 

The recipe is as follows:

  1. download intel SATA driver (aka "matrix storage manager"): http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=17412
  2. create folder on your core server, e.g. c:\intelsata
  3. unpack driver (without installing it): iata88enu.exe -a -p c:\intelsata
  4. wpeaddmsd /inf=c:\intelsata\winall\driver\iaahci.inf


The program used in step 4 (wpeaddmsd) is included in the attachment. It's a compiled autoit script (source included). Also in the attachment is a document that describes both the GUI method and the alternative method in detail.

 

Note: this article has effectively been superseded by this new article, which automates things further (downloads and unpacks the intel driver for you) and also imports a comprehensive NIC driver pack.