We've been using a TS on the Dell Latitude e7440. We recieved some new e7450s so I creating the corresponding driver package and add the necessary step for the drivers in the TS, but when we try to run the OSD on the new e7450 it gets to the SCCM 2012 splash screen and the last thing it says is loading network drivers then it reboots.

log files would help, specifically the SMSTS log file.  When the machine reboots, can you get to the file system?

It doesn't get that far in the boot process.

without any kind of log files it is going to be hard to diagnose.  It definitely seems like the driver package....

It seems that boot image has no proper NIC driver for that model. Right after WinPE starts, press F8, and type cmd.. see for IP adress. If the IP is missing, your boot image needs a nic driver for that spesific model.

When adding NIC driver to boot image, remember to add corresponding driver for the same OS as Boot image (probably Windows 8.1).

It seems that boot image has no proper NIC driver for that model. Right after WinPE starts, press F8, and type cmd.. see for IP adress. If the IP is missing, your boot image needs a nic driver for that spesific model.

When adding NIC driver to boot image, remember to add corresponding driver for the same OS as Boot image (probably Windows 8.1).

• Proposed as answer by d4rkcell 22 hours 42 minutes ago

It seems that boot image has no proper NIC driver for that model. Right after WinPE starts, press F8, and type cmd.. see for IP adress. If the IP is missing, your boot image needs a nic driver for that spesific model.

When adding NIC driver to boot image, remember to add corresponding driver for the same OS as Boot image (probably Windows 8.1).

• Proposed as answer by d4rkcell Thursday, June 25, 2015 9:03 AM

Here is a copy of the x:\windows\temp\smstslog\smsts.log

==============================[ TSBootShell.exe ]============================== TSBootShell 6/25/2015 11:22:47 AM 784 (0x0310)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSBootShell 6/25/2015 11:22:47 AM 784 (0x0310)
Debug shell is enabled TSBootShell 6/25/2015 11:22:47 AM 784 (0x0310)
Waiting for PNP initialization... TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
RAM Disk Boot Path: NET(0)\SMSIMAGES\CM10009A\BOOT-E7450.CM10009A.WIM TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
Booted from network (PXE) TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
Network(PXE) path: X:\sms\data\ TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
Found config path X:\sms\data\ TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
This is not a fixed non usb disk TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
Booting from removable media, not restoring bootloaders on hard drive TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
X:\sms\data\WinPE does not exist. TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
X:\_SmsTsWinPE\WinPE does not exist. TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
Executing command line: wpeinit.exe -winpe TSBootShell 6/25/2015 11:22:47 AM 788 (0x0314)
The command completed successfully. TSBootShell 6/25/2015 11:22:57 AM 788 (0x0314)
Starting DNS client service. TSBootShell 6/25/2015 11:22:57 AM 788 (0x0314)
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSBootShell 6/25/2015 11:22:58 AM 788 (0x0314)
The command completed successfully. TSBootShell 6/25/2015 11:22:58 AM 788 (0x0314)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 6/25/2015 11:22:58 AM 368 (0x0170)
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSMBootstrap 6/25/2015 11:22:58 AM 368 (0x0170)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 6/25/2015 11:22:58 AM 368 (0x0170)
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL' TSMBootstrap 6/25/2015 11:22:58 AM 368 (0x0170)
Current OS version is 6.2.9200.0 TSMBootstrap 6/25/2015 11:22:58 AM 368 (0x0170)
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH TSMBootstrap 6/25/2015 11:22:58 AM 368 (0x0170)
PXE Boot with Root = X:\ TSMBootstrap 6/25/2015 11:22:58 AM 368 (0x0170)
Executing from PXE in WinPE TSMBootstrap 6/25/2015 11:22:58 AM 368 (0x0170)
Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll TSMBootstrap 6/25/2015 11:22:58 AM 368 (0x0170)
TsPxe.dll loaded TSPxe 6/25/2015 11:22:58 AM 368 (0x0170)
Device has PXE booted TSPxe 6/25/2015 11:22:58 AM 368 (0x0170)
Variable Path: \SMSTemp\2015.06.25.11.05.04.0012.{7897CC59-4522-4FAE-92EF-1B602A5ACAC6}.boot.var TSPxe 6/25/2015 11:22:58 AM 368 (0x0170)
Succesfully added firewall rule for Tftp TSPxe 6/25/2015 11:22:58 AM 368 (0x0170)
Executing: X:\sms\bin\x64\smstftp.exe -i 192.168.100.9 get \SMSTemp\2015.06.25.11.05.04.0012.{7897CC59-4522-4FAE-92EF-1B602A5ACAC6}.boot.var X:\sms\data\variables.dat TSPxe 6/25/2015 11:22:58 AM 368 (0x0170)
Command line for extension .exe is "%1" %* TSPxe 6/25/2015 11:22:58 AM 368 (0x0170)
Set command line: "X:\sms\bin\x64\smstftp.exe" -i 192.168.100.9 get \SMSTemp\2015.06.25.11.05.04.0012.{7897CC59-4522-4FAE-92EF-1B602A5ACAC6}.boot.var X:\sms\data\variables.dat TSPxe 6/25/2015 11:22:58 AM 368 (0x0170)
Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 192.168.100.9 get \SMSTemp\2015.06.25.11.05.04.0012.{7897CC59-4522-4FAE-92EF-1B602A5ACAC6}.boot.var X:\sms\data\variables.dat TSPxe 6/25/2015 11:22:58 AM 368 (0x0170)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 6/25/2015 11:23:24 AM 784 (0x0310)
The command completed successfully. TSBootShell 6/25/2015 11:23:24 AM 784 (0x0310)
Successfully launched command shell. TSBootShell 6/25/2015 11:23:24 AM 784 (0x0310)
Process completed with exit code 1 TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
Succesfully removed firewall rule for Tftp TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185) TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
Failed to download pxe variable file. Code(0x00000001) TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
PxeGetPxeData failed with 0x80004005 TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1459) TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2665) TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078) TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1226) TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
Exiting with return code 0x80004005 TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493) TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335) TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553) TSPxe 6/25/2015 11:23:45 AM 368 (0x0170)
Execution complete. TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493) TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335) TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553) TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,809) TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
GetTsRegValue() is unsuccessful. 0x80070002. TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
End program: TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
Finalizing logging from process 780 TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
Finalizing logs to root of first available drive TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)
LOGGING: Setting log directory to "D:\SMSTSLog". TSBootShell 6/25/2015 11:23:45 AM 788 (0x0314)

Error "0x80004005 "

Check your BIOS and make sure the date/time isn't way off form the rest of the network and causing certificates to fail. You're failing to even download variables from PXE so that's going to be my guess.

BIOS time/date is correct. Could it be something with UEFI BIOS settings? I turned on UEFI for PXE and booted from that, but got to same place in PXE boot before it rebooted.

• Edited by Carltonw1 15 hours 3 minutes ago

Do you receive IP in WinPE or not?

If I wait until WinPE screen and hit F8 ipconfig comes back with "Windows IP Configuration" and nothing after that, but it does get an IP during the initial PXE boot in DOS.

BIOS time/date is correct. Could it be something with UEFI BIOS settings? I turned on UEFI for PXE and booted from that, but got to same place in PXE boot before it rebooted.

• Edited by Carltonw1 Thursday, June 25, 2015 4:43 PM

Okay, after doing some more google searching it looks like there are several people with the same issue. From the solutions it looks like the CAB driver that is provided by Dell has the wrong NIC included. (l2-17LM when it should be l2-18LM.)

I've downloaded the correct NIC driver from Intel's website. How do I inject it into the boot image?

l2-17LM and l2-18LM might use same driver. You are able to check this in Driver Catalogs Supported Model - page.

Before injecting driver to boot image, check that the driver is Windows 8.1 compatible. You inject driver the same way during the wizard, but instead of driver package, you select boot image. 

What a nightmare. I ended up building a new boot WIM from ADK and injecting the drivers using this post as a reference. (last reply at bottom of page)

http://en.community.dell.com/techcenter/enterprise-client/f/4448/t/19622333

That got my boot image working, but then my TS for the drivers wouldn't work. I've since downloaded the drivers from Dell's  support website and adding them to the driver package. I haven't had time to test it yet.