E7450 SCCM Build

I too have been experiencing similar issues to DMK1 with regards to the Dynamic Platform & Thermal Framework (DPTF) drivers.

I am using SCCM 2012 R2 attempting to build both a Dell Latitude E7250 & Dell Latitude E5450 with a Windows 7 Task Sequence.

As DMK1 mentions the DPFT drivers won't apply during the Apply Driver stages of the Task Sequence. Not only does it not apply the appropriate drivers the machine will then fail to boot during initial system setup. 

Kernel Mode User Framework is already applied and active within the .WIM file that is applied during the task sequence so this suggestion didn't help me much. 

I then contacted Dell who sent me a link to the the Dell Family Driver Packs site.

http://en.community.dell.com/techcenter/enterprise-client/w/wiki/11438.dell-imageassist-driver-cab-files

Dell advised me NOT to use model specific .CAB files to compile driver packages within SCCM and to use the Family Driver pack instead. I have previously been going onto the Dell Support site, entering the service tag of the device and then downloading the model specific CAB. Dell advised me that the Family Driver packs a vigorously tested for use within numerous deployment tools including SCCM. In addition to this they are also update more frequently than the model specific CAB files. 

I then downloaded the E6 Family pack which covers both models of laptops I am having difficulties with, imported the drivers into SCCM and created a Driver Package. Please note, each driver package needs to be architecture specific to the OS you're trying to apply. i.e you will need 2 driver packages one x86 one x64. 

Once the Driver Packages were created I then removed the DPTF drivers, 4/5 from each. If these drivers aren't removed from the driver package you will be back to square one when the machine fails to boot after applying drivers. 

I then created an Application to install the drivers using the .EXE provided by Dell. Link below. 

http://www.dell.com/support/home/uk/en/ukbsdt1/Drivers/DriversDetails?driverId=66P3R

The installation syntax I used is below.

Chipset_Driver_66P3R_WN_8.0.10002.14_A00.exe /s /f /l=C:\Temp\DFTPD.log 

You will also need to add in a return code (Soft Reboot) with the value 2 to stop the application flagging up as a failure as there is no switch to force a reboot. I then added the reboot command to the deployment. 

I then added this Install Application stage shortly after the Apply Drivers step and this worked a treat! 

For Microsoft Deployment Toolkit (MDT), which I believe works similar to SCCM, I had to import the drivers for Windows 8 and Windows 8.1 even though I'm imaging Windows 7 x64 PCs.  I suspect that the WinPE driver included in the Windows 7 files was older than what was required.  Once I imported the Windows 8 and Windows 8.1 drivers WinPE, then rebuilt and imported my boot image, it connected fine.

1. Download the file from here: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=0J8HP&fileId=3493709081&osCode=WT64A&productCode=latitude-e7450-ultrabook&languageCode=EN&categoryId=NI
2. Run the downloaded .EXE file and select Extract (give the program a temp folder to use)
3. We're only imaging 64bit so I open the "\Drivers\production" sub-folder in the temp folder and delete any "-x86" folders
4. Import the remaining drivers and rebuild your boot image

Thank you Rick,  I had this issue using SCCM 2007 R2 to image a Dell Latitude E7250.

OS: Win7x64

PE: WinPE 3.0

Deleted the files you suggested and configured the UMDF 1.11 to install via Task Sequence.  Worked like a charm!

Thanks again

JTPort,

I faced similar issues with all I217 and I218 drivers and eventually resolved these by using the following set up.  This is tested on E7450, E7250, E7440, E7240, OptiPlex 9020, OptiPlex 9030

WinPE 5.0 x64 - imported Intel I217/I218-LM 12.12.80.19  I pulled the driver set apart and only include the files that I needed for the driver import process when I imported them into SCCM.  This keeps things from adding in support for cards I did not intend.  If you download the Dell or Intel version, they give you support for multiple networking cards.

* e1d64x64.cat

* e1d64x64.din

* e1d64x64.inf

* e1d64x64.sys

* e1dmsg.dll

* NicCo36.dll

* NicInstD.dll

* ProUnstl.exe

I integrated the KMDF 1.11 update into my Windows 7 x64 SP1 install.wim offline (along with most patches)

I then imported the NDIS 6.2 version of the drivers listed above, but specifically version 12.11.96.1.  I created a Driver Category for this, and used WMI queries on the make and model to deploy these drivers to the applicable systems using the auto apply drivers step in the task sequence

* e1d62x64.cat

* e1d62x64.din

* e1d62x64.inf

* e1d62x64.sys

* e1dmsg.dll

* NicCo36.dll

* NicInstD.dll

* ProUnstl.exe

This has worked for me across multiple models for the Intel I217 and I218 NICs, I do not have a version of this tested for the newer Intel I219 version.

Please ensure that you are not using version 12.6.47.0 of the Intel I217 driver, which has been known in special cases to cause multicast packet storms when two OptiPlex 9020s running Windows 7 x64 SP1 have IPv6 enabled and are in sleep mode in the same subnet.

Thanks,

Tim

TDanzer, Nice post dude! :)

Just received E7470, and it has the I219-LM, same issue.