hi Just received a new system to integrate (Dell E6410). Winpe boots and installs the os. Installing the packages fails during windows setup. Error 80004005. I see that the network driver are not recognized in windows but in windows pe. any idea how to "give" the nic drivers for that operating system install package? Thx

It is a little strange, winpe detect the nic driver and the windows dont. Do you already tried to add the specific nic driver to the Configmgr before run the task sequence. Normally DELL provides all drivers online.

nope. Newbie question: should I also add the cab files for my client during the TS build? For the deployment of the captured image, I use the cab files in a Apply Driver Package filtered by WMI & model.

There are a handful of drivers issues going with the E6410/6510s: http://www.myitforum.com/forums/tm.aspx?high=&m=218556&mpage=1#218648 and http://www.delltechcenter.com/thread/3938139/SCCM+2007+XP-SP3+OSD+for+new+6510+and+6410+problems....Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

hi that's xp. I have problem under win7 cheers

Hi Oli, This issue sounds like a known bug. If separate NIC drivers are offered by an OEM manufacturer for use in Windows PE vs. the full Windows OS, the Task Sequence may fail if the Windows OS being deployed is Windows Vista or newer (Vista, Windows 7, 2008, 2008 R2) and if it is being deployed from an "Operating System Install Packages" (Windows installation source files). Did you upgrade your SCCM to SP2? If so, could you please check SMSTS.log and post some useful informaiton? Thanks.

Hi Yes, running 2007 SP2 / R2. I'll post that log as soon as I have another E6410. working workaroung: creating a reference capture from another computer type (e.g. E6400). cheers

Hi I'm experiencing exactly the same issue. Did this ever get resolved? properly - not work around as per Oli's suggestion. Cheers KA.

does this help ? 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/ My step by step SCCM Guides I'm on Twitter > ncbrady

Hi Niall, Unfortunately, No. I have SCCM 2007 SP2 R2. The SCCM OSD uses one Task Sequence for all Win7 builds (on many different H/W Models). Tried Frank Rojas resolution no 1 (download and run TS locally) with no luck. Suggestions no 2 through to 4 are not practical enough for me. Anyway, have escalated the issue to DELL. Will update the forum the outcome later. Cheers Kornelius Asikin.

Small update on the issue. It's been two weeks now - since I raised the issue with Dell. So far, I only got the smoke screen answers .. yeah we're looking into this etc. No solution or even useful hints whatsoever. Anyone has better luck? Cheers KA. Sorry pressed the Proposed for answer on this one by mistake. Will enter the answer soon.

Hi Everyone, Good News. I finally nailed it! Here’s what I did: 1. In SCCM, got rid of all the 4 copies of INTEL 82567LM-3 Gigabit Network Connection NIC drivers (downloaded from DELL WEB Site). Note: This includes the one added into the boot image. 2. Downloaded the latest INTEL NIC drivers for INTEL ® 82577LM from INTEL WEB Site. Relevant Notes: o Must extract the file first and ended up with close to hundred drivers (for all OS). o Re the 82567LM-3 Gigabit Network Connection driver for Win7 x64, the DELL driver version is 11.6.92.0. INTEL Driver version is 11.8.75.0. 3. Added the INTEL 82567LM-3 Gigabit Network Connection NIC driver into the boot image (x64). 4. Created a NIC driver package for the INTEL 82567LM-3 Gigabit Network Connection NIC driver only and applied it in Task sequence – before installing OS – and WMI filtered it to apply only to E6410 and E6510. 5. In Task sequence, I also added 2 restarts (one straight after the Setup Windows and ConfiMgr and the other straight after I applied the E6410 and E6510 drivers packages (containing all DELL Drivers except the INTEL 82567LM-3 Gigabit Network Connection NIC driver). Note: These restart are mandatory as otherwise you’ll end up with the usual and misleading TS 0x80040005, 0x00000032 and 0x00000001 errors. 6. OSD completed successfully. 7. In the OS, I noticed that the Video driver is an MS Standard VGA (as the result of PnP), but this is a different issue. BTW, in case you are wondering, DELL did not help much. Cheers Kornelius Asikin

Kornelius, I'm experiencing a similar problem with SCCM 2012 and these Dell NIC drivers. It's been having me pull my hair out for the past two weeks now, I'm going to try your fix and see if I meet with any success. As for Dell (whom I have a support contract with), yeah they're pretty much completely useless all of the time unless you need a piece of hardware shipped to you. Hope to report back with success (I know there's a two year gap, but this is the first post that seems to have found any workaround). Cheers.

Hi, can you please provide me the PE driver for INTEL 82567LM-3 for 64 bit win7. i am unable to get the driver from anywhere.Thanks Chandan