PXE boot stuck on “Start PXE over IPv4” and not working after this message

Question

I am beginner of SCCM and checking PXE functionality on my organisation but it failed with error below with SMSPXE log screenshot. Please assist as soon as possible. Importantly let me know that how to make sure that ip helperconfigured & PXE enabled for specific site. Do we have any exe file or any trick to check that?.   Kindly be noted that we have only standalone DP (NOT in site server) and we have many DP servers across all d region.

Error on Client machine while booting:

Checking Media Presence,Media Presence and Start PXE over ipv4

Error Log from SMSPXE.Log under DP server

Log smspxe - How To Manage Devices Community Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - PXE boot stuck on "Start PXE over IPv4" and not working after this message

 

Text version of Log:

If you think screenshot is not viewable , pls use the text version of log beloClient lookup reply: <ClientIDReply><Identification Unknown=”0″ DuplicateSMBIOS=”0″ DuplicateMACAddress=”0″ ItemKey=”0″ ServerName=””><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 17-Aug-20 2:31:36 PM 9380 (0x24A4)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 17-Aug-20 2:31:36 PM 9380 (0x24A4)
Adding SMSPXE 17-Aug-20 2:31:36 PM 9380 (0x24A4)
Found new image SMSPXE 17-Aug-20 2:31:39 PM 9380 (0x24A4)
Unable to open registry key ‘SoftwareWow6432NodeMicrosoftWindows KitsInstalled Roots’, cannot find location of ADK SMSPXE 17-Aug-20 2:31:39 PM 9380 (0x24A4)
Loaded Windows Imaging API DLL (version ‘6.3.9600.19467’) from location ‘C:Windowssystem32wimgapi.dll’ SMSPXE 17-Aug-20 2:31:39 PM 9380 (0x24A4)
Opening image file D:RemoteInstallSMSImages1.8_Boot.wim SMSPXE 17-Aug-20 2:31:39 PM 9380 (0x24A4)
Found Image file: D:RemoteInstallSMSImages1.8_Boot.wim
PackageID:
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 17-Aug-20 2:31:39 PM 9380 (0x24A4)
Closing image file D:RemoteInstallSMSImagesHGC1.8_Boot..wim SMSPXE 17-Aug-20 2:31:39 PM 9380 (0x24A4)
Begin validation of Certificate [Thumbprint 32498E5D7C49DAD5F5B55D30D84477231A9DE118] issued to ‘876dabe6-eddd-4a9f-a984-bfac8752da8c’ SMSPXE 17-Aug-20 2:31:40 PM 9380 (0x24A4)
Completed validation of Certificate [Thumbprint 32498E5D7C49DAD5F5B55D30D84477231A9DE118] issued to ‘876dabe6-eddd-4a9f-a984-bfac8752da8c’ SMSPXE 17-Aug-20 2:31:40 PM 9380 (0x24A4)
PXE Provider finished loading. SMSPXE 17-Aug-20 2:31:40 PM 9380 (0x24A4)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 17-Aug-20 2:54:49 PM 7888 (0x1ED0)
MAC Ignore List Filename in registry is empty SMSPXE 17-Aug-20 2:54:49 PM 7888 (0x1ED0)
Begin validation of Certificate [Thumbprint 32498E5D7C49DAD5F5B55D30D84477231A9DE118] issued to ‘876dabe6-eddd-4a9f-a984-bfac8752da8c’ SMSPXE 17-Aug-20 3:31:40 PM 16536 (0x4098)
Completed validation of Certificate [Thumbprint 32498E5D7C49DAD5F5B55D30D84477231A9DE118] issued to ‘876dabe6-eddd-4a9f-a984-bfac8752da8c’ SMSPXE 17-Aug-20 3:31:40 PM 16536 (0x4098)
Error opening file: D:RemoteInstallSMSImagesHGC1.8_Boot..wim. Win32=32 SMSPXE 17-Aug-20 3:36:30 PM 16432 (0x4030)
Retrying D:RemoteInstallSMSImagesHAN0011EHGC1.8_Boot.wim SMSPXE 17-Aug-20 3:36:30 PM 16432 (0x4030)
Boot image —– has changed since added SMSPXE 17-Aug-20 3:36:33 PM 16432 (0x4030)

solved 0
nanda kumar 4 months 10 Answers 101 views Beginner 0

Answers ( 10 )

  1. Hope this thread can be closed now. Open a new question if required.

  2. I meant that i request you to shortly describe only below points from MS link, so that i can exactly advise our internal team to do that.

    When you configure a single PXE-enabled distribution point to support multiple subnets, it’s not supported to use DHCP options. To allow the network to forward client PXE requests to PXE-enabled distribution points, configure IP helpers on the routers.

    In version 1810, it’s not supported to use the PXE responder without WDS on servers that are also running a DHCP server.

    Starting in version 1902, when you enable a PXE responder on a distribution point without Windows Deployment Service, it can now be on the same server as the DHCP service. Add the following settings to support this configuration:

    · Set the DWord value DoNotListenOnDhcpPort to 1 in the following registry key: HKLMSoftwareMicrosoftSMSDP.

    · Set DHCP option 60 to PXEClient.

    Restart the SCCMPXE and DHCP services on the server.

    • Havent came across this scenario because not using IPHelper. It would be better to do some google on it and if articles says that by changing the above settings it works then you should try.

      Best answer
  3. I think you need to involve network team, network team can trace that when you boot the machine in PXE whether broadcast packets are reaching to PXEmachine or not.

  4. I can’t find any specific errors in the above log snippet.

    The best approach to resolve the issue is to understand the process.

    You can check the video tutorial of Vishal. He explains end to end troubleshooting scenario SMS PXE –
    https://www.youtube.com/watch?v=U5L8wbJemb8&list=PL67vGzo-INWODJeLSun9N7lPWTqDckDxB&index=2&t=0s

    https://www.anoopcnair.com/sccm-osd-task-sequence-ultimate-guide/

    • Hi Anoop,

      Thank you for the response.

      I could see that the above video and contents are very much helpful for me after PXE works on my environment.

      But my point is that PXE boot itself not started at all on any AD site on our organisation.

      Any input/help is much appreciated :).

      While starting F12 (network boot), it stays on same page with “Starting PXE over IPV4” nothing else… 🙁

Leave an answer

Sorry, you do not have a permission to answer to this question .