I tried using local paths without credentials too (and putting the drivers in $OEM$\$1) to no avail. it would integrate my drivers in the offlineServicing pass) but it appears not. I thought this would have broadly the same effect as OEMPnpDriverPaths in XP/2003 (i.e. In 2000/XP/2003 this was a simple as a few registry tweaks to specify the path and copying drivers into said path.
It looks like I may be able to use pnputil to do import the drivers into the driver store, not sure if this is the best way though and also not sure how I force a full rescan to update all drivers afterwards? Run a first logon command to install these new drivers from the local hard drive - this isn't ideal as it would mean video drivers would not be installed until a good way through the setup sequence.Īt the moment in the unattend.xml I have setup in Offline Servicing the path to the drivers (c:\drivers) but this is not processed from this directory since the machine is not in an offline state by the time I'm deploying the image. Provide some way in the tell the unattend.xml / Win7 to use the new drivers on the local hardrive (C:\drivers) early during windows setup.Ģ. So my options now are (in order of preference that I can think of.):ġ.
I have an automated reference image task sequence and a separate deploy image task sequence.In an ideal world I would use DISM to inject the drivers into the offline image after it has been applied - however I'm not able to do this as DISM will not run in a Windows PE 2.1 environment (and WinPE3.0 is not an option right now). I don't want to include all drivers into the reference image as this will slow the deployment time as additional support for hardware is provided. I'm currently working on a hardware independent Windows 7 image using HTA/vbscript to control process of deployment and perform hardware identification then apply a specific driver set depending on the detected hardware.