[mdt] Windows PE - Missing Driver but injected in to MDT Image

[robyholmes]

Hi All,

 

I have a problem imaging a new machine, and not just any machine either. My brand new workstation I've been waiting for for ages!

 

I've downloaded all the drivers for the motherboard (This is a custom build from @VeryPC) and imported them in to MDT. I've then re-built my MDT boot image so the network drivers are injected and imported that in to WDS. However when I boot the image from PXE on the PC itself I get a driver missing error for the network adapter.

 

I've checked the driver INF file and the device ID shown including revision is listed as supported. MDT shows the driver is injected in to the boot image as well. I've checked there's no duplicate driver with the same name in MDT (We put drivers in to make and model folders).

 

So I'm a bit at a lost, I've re-built the MDT boot image as well just to be sure it's injecting the driver correctly rather than simply adding it later.

 

Is there anyway in Windows PE to get a list of drivers MDT has? Or see why it didn't load the driver? I'm a bit at a lost as to what to try next.

 

Thanks, Rob

[DaveTheTech]

I presume that the make and model that you are using is added to the DriverSet001 variable?

Double to check that the Make and Model vars are correct. I take mine from 'wmic csproduct list brief'.

 

Its been over a year since I have used MDT.

But after the drive import, I refresh the deployment and update the boot file.

Then import that to WDS, then restart the service.

[robyholmes]

I presume that the make and model that you are using is added to the DriverSet001 variable?

Double to check that the Make and Model vars are correct. I take mine from 'wmic csproduct list brief'.

 

Its been over a year since I have used MDT.

But after the drive import, I refresh the deployment and update the boot file.

Then import that to WDS, then restart the service.

 

I'm not even getting to install the image, just booting the MDT WinPE environment it's failing on. MDT is set to import all network drivers to the boot image. You are right, I've using the DriverSet001 variable for the install itself.

 

The only thing I've not tried is restarting the WDS service, so I'll give that a try now.

[robyholmes]

Well restarting the WDS service didn't work. Damn

[robyholmes]

So I tried exporting the LAN driver from the pre-installed VeryPC image and replacing the new driver I downloaded in MDT. Re-built the image and tried again...same result. Hmmm, this really stumping me now.

[kjadams]

Don’t you need to import the NIC driver into the WinPE drivers folder and not any general or machine specific folder set?

 

I needed to add a WinPE driver for a Dell laptop just this week. On the Dell website there were drivers specifically for WinPE.

[robyholmes]

Don’t you need to import the NIC driver into the WinPE drivers folder and not any general or machine specific folder set?

 

I needed to add a WinPE driver for a Dell laptop just this week. On the Dell website there were drivers specifically for WinPE.

 

I'm pretty sure it's injecting any network or storage driver from any folder with how I have it setup. However I'll do a test by importing it in to the root and re-building the MDT boot image.

[robyholmes]

Put the driver in the MDT Drivers root, re-built the image but still no luck.

 

Does anyone know of a way of seeing what drivers are in the boot image? To confirm it's injected it correctly?

[snagrat]

Put the driver in the MDT Drivers root, re-built the image but still no luck.

 

Does anyone know of a way of seeing what drivers are in the boot image? To confirm it's injected it correctly?

 

When you build the boot image it tells you what it is doing and confirms at the end. Does it say it is injecting it?

 

So when you PXE boot it loads into WinPE then says the network card is missing?

[robyholmes]

When you build the boot image it tells you what it is doing and confirms at the end. Does it say it is injecting it?

 

So when you PXE boot it loads into WinPE then says the network card is missing?

Yer shows the GUID of the driver and says its injected it.

 

Then you PXE boot it and it says the network driver is missing. The Vendor, Device and Revision numbers shown match those listed in the driver INF file.

[robyholmes]

SOLVED

 

Turns out the issue was with the Windows PE version in MDT. I was still running the ADK from 1803. I removed that and installed 2004 (With the Windows PE addon installer) and updated the deployment share. New boot file imported to WDS and it's worked! So I guess the driver didn't support something in Windows 1803, but does in 2004 which is the latest ADK you can get.

[fiza]

Sorry to ressurect this old thread but I have a similar issue. Our MDT process starts building the image, boots into windows and gets to around 55% and then we get an error;

 

Wizard Error

A Connection the Deployment share (\\pathtoDeploymentshare$) could not be made. The following networking device did not have a driver installed.

PCI\VEN_8086&DEV_1A1D&SUBSYS_86721043&REV_11"

 

 

We know the driver is an Intel_I219 driver and we have ensured it is injected in the WinPE and the Out of Box Drivers section.

 

When we get the error we can then manually install the driver using the same files we injected and then the imaging continues and completes successfully.

 

We are using MDT version 6.3.8456.1000 and ADK version 10.1.19041.1 including the WinPE addon Installer. Which I believe are the latest.

 

Any ideas please?

[robyholmes]

I seem to think I ran in to this again and found I was injecting to many drivers in to the boot image. So it would try and use the wrong one. Maybe try a fresh boot image without any injected if you've not done that already, the latest version might not need it.