Home / server / Questions / 281507
In Process
Andy May
Asked: 2011-06-18 05:37:52 +0800 CST

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

  • 772

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!

windows-server-2003 deployment windows-xp wds mdt-2010

3 Answers

  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.

    • 2

  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.

    • 1

  3. If you are unable to connect to the share and no DHCP lease, then your problem starts with the Network. Don't take for granted that everything works. Check out more than 2 of the laptops as I have seen those specifically having board problems with the network. Load the OS manually and verify a few of the devices.

    If you have updated the WIM already, copy the windows image to usb and load it that way, once you get the image loaded on the device, you can see that either the driver worked or it didn't. I would guess that it didn't.

    Finally, make sure you are not mixing 32/64 drivers.

    Dan

    • 0