WDS Error: A connection to the deployment share could not be made

5,307

Solution 1

Sounds like you need to add the drivers for the NIC into the Boot.WIM. I know you said you use MDT to add drivers to your WIMs but are you sure you're adding the correct ones?

Dell provides a WinPE Driver pack. I created a folder under the Out-of-Box drivers called WinPE and a selection profile called WinPE that only selects that folder. For the Boot.WIM setup in MDT I have it set to only use the WinPE profile for the Boot.WIMs.

Solution 2

WDS is interesting in that it grabs one DHCP address at PXE boot, and then grabs another one right after that after WinPE has started. What happens on some networks is that the DHCP server can't respond quickly enough to support this behavior.

I have been able to remedy this exact problem on some networks by enabling portfast on the switches/switch ports involved.

Share:
5,307

Related videos on Youtube

Andy May
Author by

Andy May

Updated on September 18, 2022

Comments

  • Andy May
    Andy May over 1 year

    We currently have a WDS server that we use for imaging both Windows XP and Windows 7 machines. We use MDT 2010 to add drivers to the WIM files. It works for all of our existing hardware, but we recently got in some Dell E6420 machines that we can't get to image (we're trying to install XP). After the machine downloads the WIM it throws an error:

    A connection to the deployment share (\\servername\DeploymentShare) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Abort - Abort Litetouch and cleanup (No Recovery). Retry - Retry network operation. Ignore - Cancel out of Litetouch (Retry later).

    I don't think this is a network or DHCP issue, since all other models work. I think it's a driver issue, but I added the network driver from Dell's site to the WIM using MDT so I'm not sure why it isn't working. Any suggestions would be greatly appreciated!

  • Andy May
    Andy May almost 13 years
    This model has the same issue in multiple offices using different WDS servers and many different laptops of the same model. I will try the straight WIM file and post my results. Thanks for the suggestion.