question

PeterSmithKentCommunityHealth-6383 avatar image
0 Votes"
PeterSmithKentCommunityHealth-6383 asked SimonRenMSFT-3639 answered

MDT Build Issue

Hi All Having an issue with Latitude 5410's recently, I posted on here about the driver repository being copied in its entirety to the local machine and was given some good advice to change the preinstall section of inject drivers to use the selection profile = 'Nothing' with the option 'install all drivers from the selection profile' as well.

This has worked fine for all other devices except the 5410 & 5400 I use the variable for %make%%model% with structured driver repos for each model and this is working ok as mentioned apart from 5410's. & 5400's. The task starts off ok and gets to the desktop and then I get the error to say that the connection to the deployment share could not be found as DHCP cannot assign an ip address due to no physical adapter.

I know it's a driver issue as I extracted the drivers from a Dell oem build and pointed the nic card to the drivers and it installed the relevant driver, clicked on the option to retry and the connection was restored. I have just created a selection profile just for the 5410 driver repository in the preinstallation inject drivers and it built. Forgot to add I copied the oem drivers to the driver repo as well, what's happening guys any ideas?

From the BDD.Log this is the error shown Unable to connect to the deployment share \\xyz123\Win10. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection.


I've recreated the driver repository for that device from new, added Intel drivers directly from Intel, added that device nic drivers to WinPE etc but they simply refuse to build unless I create a selection profile pointing to the driver repository for that device. Checking the bdd.log I see that it sets the Setting variable DriverGroup001 to value Dell Inc.\Latitude 5410 & Property DriverGroup001 is now = Dell Inc.\Latitude 5410 Any ideas at all ?

Forgot to add using the same task from the same share with the same image on other models does not cause any issues. I have ensured that the return from the model using wmic cs product get name is correct as well....! At a loss with this guys

mem-mdt
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SimonRenMSFT-3639 avatar image
0 Votes"
SimonRenMSFT-3639 answered

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

1.Please go to the OEM's/Network Card manufacturer’s web site to track down a current driver.

2.Please try to add a delay in the Litetouch script for the DHCP.

Here is a similar thread for your reference:
Resolving "A connection to the deployment share could not be made"errors in MDT

Best regards,
Simon


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.