Jump to content


infinite-loop

Failed to download PXE variable file

By infinite-loop, in Configuration Manager 2012

Recommended Posts

infinite-loop Newbie

infinite-loop

Posted
Posted

Hello, I'm trying to deploy a Windows 7 task sequence to a Latitude E6540. After it downloads the files, it says "Windows is starting up..." and "Preparing network connections..." then hangs on a blank SCCM screen then reboots. The problem seems to be limited to this model because the task sequence works for other Dell models.

I have tried re-creating the boot image and injecting only the E6540 storage and network drivers to no avail.

 

Here are the contents of smsts.log:

 

LOGGING: Finalize process ID set to 772 TSBootShell 12/27/2013 3:58:25 PM 776 (0x0308)
==============================[ TSBootShell.exe ]============================== TSBootShell 12/27/2013 3:58:25 PM 776 (0x0308)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSBootShell 12/27/2013 3:58:25 PM 776 (0x0308)
Debug shell is enabled TSBootShell 12/27/2013 3:58:25 PM 776 (0x0308)
Waiting for PNP initialization... TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
RAM Disk Boot Path: NET(0)\SMSIMAGES\ABC0003F\BOOT.ABC0003F.WIM TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Booted from network (PXE) TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Network(PXE) path: X:\sms\data\ TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Found config path X:\sms\data\ TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Booting from removable media, not restoring bootloaders on hard drive TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
X:\sms\data\WinPE does not exist. TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
X:\_SmsTsWinPE\WinPE does not exist. TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Executing command line: wpeinit.exe -winpe TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
The command completed successfully. TSBootShell 12/27/2013 3:58:34 PM 788 (0x0314)
Starting DNS client service. TSBootShell 12/27/2013 3:58:34 PM 788 (0x0314)
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSBootShell 12/27/2013 3:58:34 PM 788 (0x0314)
The command completed successfully. TSBootShell 12/27/2013 3:58:34 PM 788 (0x0314)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL' TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
PXE Boot with Root = X:\ TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Executing from PXE in WinPE TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
TsPxe.dll loaded TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Device has PXE booted TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Variable Path: \SMSTemp\2013.12.27.15.56.29.0007.{51782B5D-AFFC-413F-B21B-093D5073DA42}.boot.var TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Succesfully added firewall rule for Tftp TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Executing: X:\sms\bin\x64\smstftp.exe -i 10.16.64.79 get \SMSTemp\2013.12.27.15.56.29.0007.{51782B5D-AFFC-413F-B21B-093D5073DA42}.boot.var X:\sms\data\variables.dat TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Command line for extension .exe is "%1" %* TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Set command line: "X:\sms\bin\x64\smstftp.exe" -i 10.16.64.79 get \SMSTemp\2013.12.27.15.56.29.0007.{51782B5D-AFFC-413F-B21B-093D5073DA42}.boot.var X:\sms\data\variables.dat TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 10.16.64.79 get \SMSTemp\2013.12.27.15.56.29.0007.{51782B5D-AFFC-413F-B21B-093D5073DA42}.boot.var X:\sms\data\variables.dat TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Process completed with exit code 1 TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Succesfully removed firewall rule for Tftp TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Failed to download pxe variable file. Code(0x00000001) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
PxeGetPxeData failed with 0x80004005 TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1416) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2623) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1183) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Exiting with return code 0x80004005 TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Execution complete. TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
::RegOpenKeyExW (HKEY_LOCAL_MACHINE, c_szSMSTSKey, 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,258) TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
GetTsRegValue() failed. 0x80070002. TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
End program: TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
Finalizing logging from process 772 TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
Finalizing logs to root of first available drive TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
Successfully finalized logs to D:\SMSTSLog TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
Cleaning up task sequencing logging configuration. TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)

 

LOGGING: Finalize process ID set to 772 TSBootShell 12/27/2013 3:58:25 PM 776 (0x0308)
==============================[ TSBootShell.exe ]============================== TSBootShell 12/27/2013 3:58:25 PM 776 (0x0308)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSBootShell 12/27/2013 3:58:25 PM 776 (0x0308)
Debug shell is enabled TSBootShell 12/27/2013 3:58:25 PM 776 (0x0308)
Waiting for PNP initialization... TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
RAM Disk Boot Path: NET(0)\SMSIMAGES\GLT0003F\BOOT.GLT0003F.WIM TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Booted from network (PXE) TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Network(PXE) path: X:\sms\data\ TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Found config path X:\sms\data\ TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Booting from removable media, not restoring bootloaders on hard drive TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
X:\sms\data\WinPE does not exist. TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
X:\_SmsTsWinPE\WinPE does not exist. TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
Executing command line: wpeinit.exe -winpe TSBootShell 12/27/2013 3:58:25 PM 788 (0x0314)
The command completed successfully. TSBootShell 12/27/2013 3:58:34 PM 788 (0x0314)
Starting DNS client service. TSBootShell 12/27/2013 3:58:34 PM 788 (0x0314)
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSBootShell 12/27/2013 3:58:34 PM 788 (0x0314)
The command completed successfully. TSBootShell 12/27/2013 3:58:34 PM 788 (0x0314)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL' TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
PXE Boot with Root = X:\ TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Executing from PXE in WinPE TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll TSMBootstrap 12/27/2013 3:58:34 PM 672 (0x02A0)
TsPxe.dll loaded TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Device has PXE booted TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Variable Path: \SMSTemp\2013.12.27.15.56.29.0007.{51782B5D-AFFC-413F-B21B-093D5073DA42}.boot.var TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Succesfully added firewall rule for Tftp TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Executing: X:\sms\bin\x64\smstftp.exe -i 10.16.64.79 get \SMSTemp\2013.12.27.15.56.29.0007.{51782B5D-AFFC-413F-B21B-093D5073DA42}.boot.var X:\sms\data\variables.dat TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Command line for extension .exe is "%1" %* TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Set command line: "X:\sms\bin\x64\smstftp.exe" -i 10.16.64.79 get \SMSTemp\2013.12.27.15.56.29.0007.{51782B5D-AFFC-413F-B21B-093D5073DA42}.boot.var X:\sms\data\variables.dat TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 10.16.64.79 get \SMSTemp\2013.12.27.15.56.29.0007.{51782B5D-AFFC-413F-B21B-093D5073DA42}.boot.var X:\sms\data\variables.dat TSPxe 12/27/2013 3:58:34 PM 672 (0x02A0)
Process completed with exit code 1 TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Succesfully removed firewall rule for Tftp TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Failed to download pxe variable file. Code(0x00000001) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
PxeGetPxeData failed with 0x80004005 TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1416) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2623) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1183) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Exiting with return code 0x80004005 TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSPxe 12/27/2013 3:59:21 PM 672 (0x02A0)
Execution complete. TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
::RegOpenKeyExW (HKEY_LOCAL_MACHINE, c_szSMSTSKey, 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,258) TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
GetTsRegValue() failed. 0x80070002. TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
End program: TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
Finalizing logging from process 772 TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
Finalizing logs to root of first available drive TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
Successfully finalized logs to D:\SMSTSLog TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)
Cleaning up task sequencing logging configuration. TSBootShell 12/27/2013 3:59:21 PM 788 (0x0314)

 

Here are the contents of smspxe.log:

 

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 12/27/2013 4:09:54 PM 2928 (0x0B70)
F0:1F:AF:4C:51:57, 4C4C4544-0050-3210-8036-C2C04F585931: device is not in the database. SMSPXE 12/27/2013 4:09:54 PM 2928 (0x0B70)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 12/27/2013 4:09:54 PM 2928 (0x0B70)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName="" ServerRemoteName=""><Machine><ClientID>7390270b-5a29-4729-9569-98986d38acfa</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="ABC20019" OfferIDTime="12/27/2013 4:09:00 PM" PkgID="ABC00025" PackageVersion="" PackagePath="http://<name omitted>/SMS_DP_SMSPKG$/ABC0003F" BootImageID="ABC0003F" Mandatory="0"/></ClientIDReply>
SMSPXE 12/27/2013 4:09:55 PM 2928 (0x0B70)
F0:1F:AF:4C:51:57, 4C4C4544-0050-3210-8036-C2C04F585931: found optional advertisement ABC20019 SMSPXE 12/27/2013 4:09:55 PM 2928 (0x0B70)
Looking for bootImage ABC0003F SMSPXE 12/27/2013 4:09:55 PM 2928 (0x0B70)

 

Any help or guidance would be appreciated as I've been stuck on this issue for a couple of weeks. Thank you.

Share this post

Link to post
Share on other sites
Rocket Man Newbie

Rocket Man

Posted
Posted

If it is only on 1 system you could check if the BIOS date/time is accurate on this particular device?

Also check if the BIOS can be updated to newer version.

There are winPE3.0 and 4.0 drivers for this model to inject into boot.wim on the dell website.

Share this post

Link to post
Share on other sites
infinite-loop Newbie

infinite-loop

Posted
Posted

Thanks for your reply. The BIOS is at the latest version and the date/time is accurate. I injected the WinPE 3.0 drivers, updated the DP, and am unfortunately getting the same result. Any other ideas?

 

Here is the log of the driver import. Should I be concerned with the first entry?

 

Creating Wim
Source WIM file parameter was invalid.

Wim not created.

Injected drivers into boot image successfully.
Injected drivers into boot image successfully.

Details of created Dell Client WinPE Boot Image:
Name: Dell Client WinPE Boot Image (A12) x64
Path: \\abc-sccm\SMS_ABC\OSD\boot\x64\boot.ABC0003F.wim
Version: 6.2.9200.16384
Driver Version: A12

Details of Source Boot Image:
Name: Boot image (x64) clean
Path: \\abc-sccm\SMS_ABC\OSD\boot\x64\boot.ABC0003F.wim
Version: 6.2.9200.16384

Drivers imported into Boot Image:
Release ID Device Description Inf File Version
---------- ------------------ -------- -------
WYF38_A00-00 9271-8I Storage Controller for Precision Work... megasas2.inf 6.504.5.0
WYF38_A00-00 9271-8I Storage Controller for Precision Work... nodev.inf 6.504.5.0
WYF38_A00-00 9271-8I Storage Controller for Precision Work... dcdbas32.inf 6.504.5.0
WYF38_A00-00 9271-8I Storage Controller for Precision Work... dcdbas64.inf 6.504.5.0
NNGMH_A08-00 Intel Ethernet controller;Intel Ethernet Cont... e1r62x64.inf 18.1.0.0
NNGMH_A08-00 Intel Ethernet controller;Intel Ethernet Cont... e1q62x64.inf 18.1.0.0
NNGMH_A08-00 Intel Ethernet controller;Intel Ethernet Cont... e1c62x64.inf 18.1.0.0
0TM0H_A00-00 PERC H710P Adapter for Precision Workstations... nodev.inf 5.2.222.64
0TM0H_A00-00 PERC H710P Adapter for Precision Workstations... percsas2.inf 5.2.222.64
R235484 825xx Gigabit Platform LAN Network Device e1y62x64.inf 10.0.6.0
NJKX3_A00-00 LAN7500 NDIS Driver v1.1.9.0 for Windows (32 ... net7500-x64-n620f.inf v1.1.9.0
6DNDD_A00-00 LSI SAS2308 integrated RAID for Precision Wor... lsinodrv.inf 2.0.60.0
6DNDD_A00-00 LSI SAS2308 integrated RAID for Precision Wor... lsi_sas2.inf 2.0.60.0
6DNDD_A00-00 LSI SAS2308 integrated RAID for Precision Wor... dcdbas32.inf 2.0.60.0
6DNDD_A00-00 LSI SAS2308 integrated RAID for Precision Wor... dcdbas64.inf 2.0.60.0
R291722 Rapid Storage Technology iaahci.inf 10.1.0.1008
R291722 Rapid Storage Technology iastor.inf 10.1.0.1008
7R4RM_A00-00 Broadcom 57XX Driver/BACS;BCM95722 PCI-E NIC ... b57nd60a.inf 17.4.2
7R4RM_A00-00 Broadcom 57XX Driver/BACS;BCM95722 PCI-E NIC ... k57nd60a.inf 17.4.2
9PW7M_A00-00 Realtek RTL8111G Ethernet Controller rt64win7.inf 7.71.327.2013
32V81_A00-00 Fresco Logic xHCI (USB3) Host Controller FL10... flxhcih.inf 3.5.36.0
32V81_A00-00 Fresco Logic xHCI (USB3) Host Controller FL10... flxhcic.inf 3.5.36.0
VCDGN_A00-00 Intel 825xx Gigabit Platform LAN Network Devi... e1d62x64.inf 18.1.0.0
C8Y1T_A00-00 Intel Rapid Storage Technology Management Con... iaahcic.cat 12.7.1.1000
C8Y1T_A00-00 Intel Rapid Storage Technology Management Con... iaahcic.inf 12.7.1.1000
C8Y1T_A00-00 Intel Rapid Storage Technology Management Con... iastora.sys 12.7.1.1000
C8Y1T_A00-00 Intel Rapid Storage Technology Management Con... iastorac.cat 12.7.1.1000
C8Y1T_A00-00 Intel Rapid Storage Technology Management Con... iastorac.inf 12.7.1.1000
C8Y1T_A00-00 Intel Rapid Storage Technology Management Con... iastorf.sys 12.7.1.1000
C8Y1T_A00-00 Intel Rapid Storage Technology Management Con... release.dat 12.7.1.1000
V76GK_A00-00 Ethernet 10G Base-T Adapter X520-T2 Driver;In... ixn62x64.inf 17.2.0.0
9F51R_A00-00 Intel T3600 IRST;Intel T5000 IRST;Intel C600 ... iastors.inf 3.7.4.1004
9F51R_A00-00 Intel T3600 IRST;Intel T5000 IRST;Intel C600 ... iaahci.inf 3.7.4.1004
9F51R_A00-00 Intel T3600 IRST;Intel T5000 IRST;Intel C600 ... iastora.inf 3.7.4.1004
R267025 825xx Gigabit Platform LAN Network Device e1k62x64.inf 11.5.10.0

 

 


Share this post

Link to post
Share on other sites
Rocket Man Newbie

Rocket Man

Posted
Posted

It does sound like a driver issue. Have you verified that you are actually getting an IP address on the system prior to the reboot?

You will have to enable F8 command support on boot images to test this..

 

If you are getting an IP address and can ping the FQDN of the site server/MP then you may want to take a look at this as it may very well be your problem if you have managed switches with spanning tree enabled on your network.

 

Had a similar problem in my current setup but the problem occurred immediately with all HP machines. The spanning tree time frame was decreased from I think 15 seconds default (I think) to 5 seconds possibly. If it is the problem I would'nt recommend disabling the feature completely as it checks for loops on the network and automatically isolates the problematic ports.

 

Other than this Im afraid I have nothing more to add as unfortunately I do not have any of these models in the enterprise so do not know if it is a common SCCM/Latitude E6540 problem or just a HW problem with the device you have at present.

Share this post

Link to post
Share on other sites
Rocket Man Newbie

Rocket Man

Posted
Posted

 

 

Are you running SCCM 2012 RTM, SP1 or R2?

 

 

 

Version: 6.2.9200.16384

Driver Version: A12

 

 

This is SCCM SP1 looking at the boot.wim version. So the Dell WinPE4.0 should work, the winPE3.0 has been injected according to the driver version A12?

 

Here is where the source of the winPE drivers are.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
Go to topic listing
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.