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.
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.
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!