I was contacted last week by a former colleague who is just getting into MDT. He was missing drivers on one model and received this common error page during his boot sequence. Naturally, I had loads of resources to share but sadly the final part was missing from my blog. The error is:
A connection to the deployment share (\\Server\DeploymentShare$)
could not be made.
The following networking device did not have a driver installed.
PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01
Here’s how to resolve this issue.
This error is very helpful in that it shows the hardware ID of the missing network driver. A quick Google search or visit to Microsoft Update Catalog should find the missing drivers.
Create a Driver Store
After you locate and download the correct driver, create an organised driver store on a local or network drive. I posted a script to do this a few months back. MDT Powershell: Creating a Driverstore folder structure
Import Drivers
Next, import the drivers into the desired Windows PE folder and run the script to import the drivers into the deployment workbench. Again, I created another script to do this a few months back. MDT Powershell: Importing device drivers from organised folders My script will not only creates the driver folders but the selection profiles also.
Check the hardware ID of the imported driver and ensure that it matches the error from earlier.
Apply Selection Profiles
We now need to use selection profiles to ensure that only the Windows PE network drivers get copied to the boot disk, otherwise the boot image can take longer to load.
To do this, right-click the deployment share and select properties. Select the correct platform then the WinPE selection profile.
Recreate the Boot Image
Finally, recreate the boot image by updating the deployment share.
Update your boot media with the newly updated LiteTouchPE_x64.wim file and reboot your client.
I recommend implementing selection profiles like this to isolate your boot drivers and ensure that the boot process runs as fast as possible.
I have been getting this same error message in my TS, but I have dug into my driver selection profiles and I still cannot rectify this. I have even used drivers from similar models. I am using the Dell Driver deployment .cab files which has all of the required drivers bundle for certain models. I have had to resort to installing the drivers manually at the point where it fails. This is only happening on the Dell Latitude E6430 laptops
If you require any further information before you can assist, please do not hesitate to ask.
Any help you can offer is greatly appreciated.
Many thanks
Scott
Hi Scott,
Have you followed all the steps above?
Ensure that the hardware ID matches in the deployment workbench (as above)
The driver may be wrong so send me the hardware ID and I’ll search to try and find a match for you.
/Andrew
Hi Andrew,
Thanks for replying. When running through the TS, it fails after the partition C, and just after installing the OS, it drops to a CMD and I have to type “exit” so that it reboots and continues. Once the TS continues and reaches the first stage of ‘inject drivers’, I can see it skip my selection profile for Win7 – E6430 Drivers without injecting them (this does not happen on any other models we have). I thought that this might be due to MDT not detecting the model during the Gather stage, but after checking the logs, this was not the case.
I noticed in your post that you have a Win PE drivers folder, which I do not have. Is this strictly necessary or is it fine to have all of the selection profile drivers add themselves to the Win PE image?
The particular driver which is failing is this:
PCI\VEN_8086&DEV_1502&SUBSYS_05341028&REV_04
I have checked through the drivers folders I have created in my workbench and I was able to find drivers matching that particular device ID, which is also why it seems strange.
Apologies for the long winded reply.
Thanks
Scott