"Has anyone been successful with this? First, I had to inject the NIC drivers into the boot image for it to PXE boot. It goes through the steps of capturing and when it reboots after the preinstall, boom, no more IP address. I've tried capturing with MDT and SCCM 07. "

I've had a lot of issues with the E6510 and MDT (Windows Deployment Server) - it goes way beyond adding the drivers into the deployment share.

Tell me about it. These things don't PXE boot out of the box. C'mon Dell! It took me a week to fix the pxe boot issue and now it's taking me just as long to capture a custom image.

Mike,

Is your capture task sequence configured to use the boot media with the updated NIC driver?

Hi Warren,

I've already watched a few of your videos and no luck unfortunately.

My capture sequence is configured ot use the boot media witht he updated nic driver. Which is the baffling part. It goes through the whole process, it gets to the Prepare OS stage and craps out on me.

Forget about adding a driver package. I have no problem creating the driver package. When it tries to push them to the image it craps out.

Right now I have a working Windows 7 image I captured off of a Dell D630 machine. It doesn't load the NIC drivers for the E4310. Currently in the process of trying the Dell driver package to be deployed as a software package included with the deployment. Hopefully this works.

No dice with software package w/ NIC drivers. Even though it installs the package at the end of OS deployment. Was really hoping that would work.

We are a school district and run a variety of hardware from Dell and others. We have Dell Latitude 2110, Optiplex 755, Optiplex GX620, Optiplex 980, Latitude E6510 ... as well as some other netbook models from HP. We also install our same Windows 7 image onto Apple products via BootCamp. The ONLY devices that are giving us fits are the newer Latitudes with the i5 and i7 processors. We were able to image a couple in the summer/fall ... but the newer ones aren't taking an image at all.

I follow the same procedure with all new models - add the drivers to the deployment server.

I can get an imagine onto the E4310. I can also install the dell CAB driver package with that image. It will install the video, the sound, the wireless, the bluetooth. But it will not install the network adapters. Talk about odd.

Finally I was able to figure it out. It took some time but this method is what finally got it working.

http://www.windows-noob.com/forums/index.php?/topic/1688-nic-devices-that-require-a-special-driver-for-winpe-may-cause-a-configmgr-task-sequence-to-fail/

So can you give the specific details of the root cause of your issue? Was it because you aren't on SCCM SP2/WinPE 3.0? Were you applying the driver package too late in your task sequence?

I'm just trying to capture the specifics for anyone else that runs into this issue. The article you referenced shows many scenarios that can cause this issue along with many resolutions.

Creating the unattend.xml file and all the steps that went with that is what did the trick.