Glad it helped.
dpinst.exe was last included with the Microsoft Windows Driver Kit 10.0.10586.0 (v1507) build 10.0.26639.
To install:
wdksetup.exe /quiet /features OptionId.WindowsDriverKitComplete
Then find the dpinst.exe files here:
C:\Program Files (x86)\Windows Kits\10\redist\DIFx\dpinst\EngMui\x64\dpinst.exe
C:\Program Files (x86)\Windows Kits\10\redist\DIFx\dpinst\EngMui\x86\dpinst.exe
One reason why I don’t let Windows decide when to install drivers.
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ExtendOSPartition>
<Extend>true</Extend>
</ExtendOSPartition>
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Description>Driver Installation Pass 1 of 3</Description>
<Path>"C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>2</Order>
<Description>Driver Installation Pass 2 of 3</Description>
<Path>"C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>3</Order>
<Description>Driver Installation Pass 3 of 3</Description>
<Path>"C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:c:/temp/v1709/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
ipxe.efi (1b67a) is the latest from the github repo linked above.
Results
#!ipxe
set fog-ip 10.12.40.14
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.12.40.14/fog/ consoleblank=0 rootfstype=ext4 mac=48:ba:4e:51:d9:e2 ftp=10.12.40.14 storage=10.12.40.14:/images/ storageip=10.12.40.14 osid=9 irqpoll hostname=48ba4e51d9e2 chkdsk=0 img=Win_10x64_C_20170314_UEFI imgType=n imgPartitionType=all imgid=77 imgFormat=0 PIGZ_COMP=-3 type=down
imgfetch init_32.xz
boot
Then I:
It IS an odd one.
In UEFI mode
a. Perform Full Host Registration and Inventory (init.xz… then returns to menu)
b. Quick Registration and Inventory (init.xz… then returns to menu)
c. Deploy Image ( see error above )
d. Join Multicast Session (same as Deploy Image)
e. Client System Information (init.xz… then returns to menu)
In Legacy mode
… waiting on other stuff right now… will edit this ina few minutes.
via FOG 1.4.4 and kernel
I can UEFI PXE (ipxe.efi) boot this laptop fine, but when it comes to actually doing any work with say, Deploy Image I wind up with:
http://10.12.40.14/fog/service/ipxe/boot.php... ok
bzImage... ok
init.xz... ok
Could not boot: No such device (http://ipxe.org/2c0408087)
Legacy PXE booting (undionly,kpxe) it will image fine.
I will have this laptop for just today so I don’t know if I’ll be able to do any troubleshooting.
When you mastered your 64bit PE did you master it for Legacy AND UEFI booting?
To Create Legacy Bootable x86 .ISO
----------------------------------
"oscdimg.exe -m -u2 -b"<path to source files>\boot\etfsboot.com" "<path to source files>" "C:\output\new86.iso"
To Create Legacy/UEFI Bootable x64 .ISO
---------------------------------------
"oscdimg.exe" -m -o -u2 -udfver102 -bootdata:2#p0,e,b"<path to source files>\boot\etfsboot.com"#pEF,e,b"<path to source files>\efi\microsoft\boot\efisys.bin" "<path to source files>" "C:\output\new64.iso"
I can now confirm that the Lenovo Mini-Ethernet Extension Adapter (p/n: sc10a39882bb, fru: 04x6435) also works in both UEFI and Legacy network boot.
No. Nothing changed on the laptop.
To get past the inits in UEFI network boot I had to use the Lenovo Mini-Ethernet Extension Adapter ( p/n: sc10a39882aa, fru: 04x6435 ) that I just acquired.
To get past the inits in Legacy network booting I can use the Lenovo ThinkPad USB 3.0 Ethernet Adapter ( p/n: SC10H30171/RTL8153 FRU: 03X6903 ) or the Lenovo Mini-Ethernet Extension Adapter ( p/n: sc10a39882aa, fru: 04x6435 ) that I just acquired.
All tests were conducted with BIOS 1.17 and fog server configuration (1.4.4 / 4.12.3).
I already tested the others (see above) with the same BIOS and fog server configuration (1.4.4 / 4.12.3).
That’s right. It works exactly as desired.
Alrighty then, I have successfully UEFI and Legacy network booted a Lenovo ThinkPad Yoga 370 (20JJS2F200) with BIOS 1.17 using a Lenovo Mini-Ethernet Extension Adapter (p/n: sc10a39882aa, fru: 04x6435)
Yay another proprietary interface! (here’s the modern version).
I’m a big fan of dpinst as well. Injecting for reals, into an OS for 30 different platforms prior to sysprep bloats the registry and can even poison an image in extreme cases.
I prefer to not leave Windows to install drivers as it wants, but where I want, when I want; I do this in the unattend.xml.
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ExtendOSPartition>
<Extend>true</Extend>
</ExtendOSPartition>
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Description>Driver Installation Pass 1 of 3</Description>
<Path>"C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>2</Order>
<Description>Driver Installation Pass 2 of 3</Description>
<Path>"C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>3</Order>
<Description>Driver Installation Pass 3 of 3</Description>
<Path>"C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
Where C:\temp\drivers\ contains every driver extracted from every system needed.
Alongside dpinst.exe in c:\temp\drivers I also place the dpinst.xml
<?xml version="1.0" ?>
<dpinst>
<!-- equivalent to /sa -->
<suppressAddRemovePrograms/>
<!-- The following search and subDirectory elements direct DPInst to search all subdirectories (under the DPInst working directory) to locate driver packages. -->
<search>
<subDirectory>*</subDirectory>
</search>
<!-- The following language element localizes its child elements for the English (Standard) language. The child elements customize the text that appears on the DPInst wizard pages. -->
<language code="0x0409">
<dpinstTitle>Device Driver Updater</dpinstTitle>
<welcomeTitle>Welcome to the Device Installer!</welcomeTitle>
<welcomeIntro>This wizard will walk you through updating the drivers for your device.</welcomeIntro>
<installHeaderTitle>Installing the software for your device...</installHeaderTitle>
<finishTitle>Congratulations! You finished installing your device drivers.</finishTitle>
</language>
<!-- equivalent to /sh -->
<scanHardware/>
</dpinst>
I run dpinst three times deliberately. First to grab primary devices, then to detect and load daughter devices, and then finally for those very few tertiary devices that can only be seen after two other parent devices are loaded.
I then leave it to setupcomplete.cmd to reclaim the disk space taken up by staging the drivers in the image.
@REM Place this file in C:\Windows\Setup\Scripts
@REM SetupComplete.cmd is executed as final step of coming out of Sysprep under SYSTEM account
@REM Cleanup
del /Q /F c:\windows\system32\sysprep\closer*.xml
del /Q /F c:\windows\system32\sysprep\default*.xml
del /Q /F c:\windows\panther\unattend.xml
rd /s /q C:\temp
rd /s /q C:\temp
This does not take care of any OEM software which I install through separate automated means.
My current driver pack for Windows 10 (64) is fully compatible with 30 different makes/models in our environment.
Dell Inc. Latitude 3379 <blank>
Dell Inc. OptiPlex 790 <blank>
Dell Inc. OptiPlex 7010 <blank>
Dell Inc. OptiPlex 7020 <blank>
Dell Inc. XPS One 2710 <blank>
LENOVO 7373BTU ThinkCentre M58
LENOVO 3548C1U ThinkCentre M72z
LENOVO 3548C8U ThinkCentre M72z
LENOVO 10BBS00Y00 ThinkCentre M73z
LENOVO 10BBS12Q00 ThinkCentre M73z
LENOVO 10EWS0B000 ThinkCentre M800z
LENOVO 10NY0010US ThinkCentre M810z
LENOVO 20GKS0A700 ThinkPad 13
LENOVO 20J2S0MJ00 ThinkPad 13 2nd Gen
LENOVO 20FES0VJ00 ThinkPad Yoga 260
LENOVO 20JJS2F200 ThinkPad Yoga 370
LENOVO 30ASS3NA0 ThinkStation P310
LENOVO 30BH002KUS ThinkStation P320
Toshiba PORTEGE R830 PT320C-0F502L
Toshiba PORTEGE R830 PT320C-01H018
Toshiba PORTEGE R830 PT320C-05L02L
Toshiba PORTEGE R930 PT330C-00v009
Toshiba PORTEGE R930 PT330C-05X039
Toshiba PORTEGE R930 PT330C-08S039
Toshiba PORTEGE Z930 PT235C-02H049
Toshiba PORTEGE R30-A PT341C-00W00T
Toshiba PORTEGE R30-A PT343C-0YP08W
Toshiba PORTEGE R30-A PT343C-01N01J
Toshiba PORTEGE Z30t-A PT24CC-05D02V
Toshiba TECRA R700 PT318C-00C001
Lenovo is shipping me a 4X90E51405 for testing. I hope to be back into testing it soon.
Was able to squeeze in a baseline observation before I go onto other things and I’ve informed Lenovo as well.
I have the following:
1.Lenovo ThinkPad OneLink+ to RJ45 Adapter ( p/n: SC10J34224BB FRU: 00JT801 )
2.Lenovo ThinkPad USB 3.0 Ethernet Adapter ( p/n: SC10H30171/RTL8153 FRU: 03X6903 )
3.Lenovo USB-C to Ethernet Adapter ( p/n: SC10L66919/RTL8153-04 FRU: 03X7205 )
All three work as desired on a Lenovo ThinkPad 13 (20GKSOA700 BIOS 1.24) for both Legacy and UEFI network boot. I also tested 1&2 on a Lenovo Yoga 260 (20FES0VJ00 BIOS 1.59) successfully.
Since there isn’t a OneLink+ connector on a Yoga 370 (1.17) here are my findings for the two USB models.
2a. Using the Lenovo ThinkPad USB 3.0 Ethernet Adapter ( p/n: SC10H30171/RTL8153 FRU: 03X6903 )
2b. Using the Lenovo ThinkPad USB 3.0 Ethernet Adapter ( p/n: SC10H30171/RTL8153 FRU: 03X6903 )
3a. Using the Lenovo USB-C to Ethernet Adapter ( p/n: SC10L66919/RTL8153-04 FRU: 03X7205 )
3b. Using the Lenovo USB-C to Ethernet Adapter ( p/n: SC10L66919/RTL8153-04 FRU: 03X7205 )
Gigabit 0.0.18-IPv4There is clearly something amiss with the 370’s code.
Lenovo says that the 4X90E51405 should work, but I don’t have one … yet 8).
I don’t have a lot of spare time just now for much testing; on the road; but I do have a USB-C adapter coming in and I have hooked Lenovo on the line to hopefully help out too.
Yay me. I’m on this ship now too. I just received a Yoga 370 ( 20JJS2F200 ) and I’m also unable to perform operations after a UEFI network boot.
I thought it may have been due to the new hardware this model has, Thunderbolt and WiGig but disabling them has no effect.