OS Deployment 7.1.1.20.311.45 - MDT Bundle 3.11.14 - WinPE - UEFI without Secure Boot - Direct Boot Disabled - Network / Storage Drivers not recognized
Wanted to use the Automatic Driver Binding
Model:
Dell Latitude 5420
What I’ve done:
Uploaded all of the latest Dell WinPE10 Drivers PCI
I did not assigned Labels or Model Bound
On Driver Library, Binding - WinPEx64 and the specific model - There are drivers showing in “Driver Bound” and there are not on “Current Manual Binding”
I’ve Full Synced the Server - Successfully without Errors
On PXE Boot
The machine is being started, I’m getting to the Binding Menu.
After selecting the Profile, it will download the boot.wim file and will start the procedure - at first it does not find and driver, it will restart and search applicable drivers and then will download again the boot.wim and will recreate the procedure again.
It does not find any driver in the end and return back to the Binding Menu.
Does the Automatic Driver Binding works well?
How I can troubleshoot it much easier?
Is it better to use the Direct Boot option and bound the Driver per module?
Hello.
Did you check if, editing the network/storage devices, more than one driver is displayed? Maybe a driver that is seen as compatible (PCI ids matches) but not actually working could have been bound at bare metal server level.
I suggest to manually bound the correct driver to the network/storage device in the mentioned biding grid, waiting for the triggered sync to be completed and retry the deployment (no need to pass to WinPE direct boot for UEFI targets).
If this does not solve, I suggest to open a case to the support team for the investigation.
Thanks.
Sergio
L3 BigFix OSD support
Hello. Did you verify if binding the specific model to the working driver that you want to use, among the compatible ones, makes the automatic driver injection to work?
This should help the bare metal server to identify the right driver among the ones that are seen as compatible (because PCI ids match) where some of them could not work, even if PCI ids match, and this could cause the device not to work even if a driver is auto injected.
Thanks.
Yea, before I’ve manually bounded the driver I’ve assigned it to the specific model - after the sync action, the driver was not bounded to the device while PXE boot although it was showing on the binding grid.