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.
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
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.