Share via


SCCM fails to Initialize Windows PE during PXE boot sequence

Question

Monday, November 20, 2017 6:00 PM

Last week I finished imaging a system and prepared another system. Both systems are the same make and model, same bios version, and the system fails. It initially connected via PXE with SCCM downloaded the boot image file, but then when it attempts to Initialize Windows PE, it will sit there and then time out. Once this happens, I am unable to PXE boot the system to SCCM. It will just time out with failure code: PXE-E51: No DHCP or ProxyDHCP offers were received. I can look in the SMSPXE.Log file on the server and I do not see anything unusual.  Below is a snippet of what it logged for a system this morning that fails:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 11/20/2017 9:16:52 AM 3372 (0x0D2C)
70:5A:0F:45:60:F1, 0695DF5C-DE8D-11E6-9C43-BC0000600000: device is not in the database. SMSPXE 11/20/2017 9:16:52 AM 3372 (0x0D2C)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 11/20/2017 9:16:53 AM 3372 (0x0D2C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>8ac0add1-e649-45b6-8489-b4bef4782330</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="DAV200C0" OfferIDTime="10/6/2017 4:04:00 PM" PkgID="DAV0004F" PackageVersion="" PackagePath="http://XXXXXSCCM.rac.local/SMS_DP_SMSPKG$/DAV00004" BootImageID="DAV00004" Mandatory="0"/></ClientIDReply>
 SMSPXE 11/20/2017 9:16:53 AM 3372 (0x0D2C)
70:5A:0F:45:60:F1, 0695DF5C-DE8D-11E6-9C43-BC0000600000: found optional advertisement DAV200C0 SMSPXE 11/20/2017 9:16:53 AM 3372 (0x0D2C)
Looking for bootImage DAV00004 SMSPXE 11/20/2017 9:16:53 AM 3372 (0x0D2C)
BootImage DAV00004 needs to be updated (new packageID=DAV00004) VersionUpdate=true SMSPXE 11/20/2017 9:16:53 AM 3372 (0x0D2C)
PXE::CBootImageInfo::CBootImageInfo: key=DAV00004 SMSPXE 11/20/2017 9:16:53 AM 3372 (0x0D2C)
Saving Media Variables to "E:\RemoteInstall\SMSTemp\2017.11.20.09.16.54.0001.{36A86711-AAEF-435E-879C-117F2C9A6E92}.boot.var" SMSPXE 11/20/2017 9:16:54 AM 3372 (0x0D2C)

I went back and looked at systems that were successful and do not see a difference.  I am not sure what other log I can look at that would give me information about what is happening from the initial file download to when it fails Initializing Windows PE. 

I Did find 3 unknown systems listed in Devices and they had the MAC address for 3 of the systems that failed, so I deleted them, but that still has not resolved the issue.  When I take a system right from the box and plug it in and PXE boot it is successful connecting and then downloading the boot.wim file but then like stated above fails to initialize.

What other logs on the server can I look at that would give me a clue as to what the system is attempting to do.

Mark Reny

All replies (1)

Tuesday, November 21, 2017 9:51 AM

Hi,

Please refer to the links below:

Troubleshooting PXE in SCCM OSD Part 1

http://adventuresinosd.blogspot.sg/2011/02/troubleshooting-pxe-in-sccm-osd-part-1.html

Troubleshooting SCCM Part VII ………. OSD …. Part I

https://blogs.technet.microsoft.com/sudheesn/2013/09/20/troubleshooting-sccm-part-vii-osd-part-i/

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].