PXE boot image on new DP

Oilers93 1 Reputation point
2022-10-12T22:16:41.737+00:00

Hello,

We've been running into some issues in the last 2-3 weeks when PXE'ing existing and unknown computers. The computers will grab an IP Address with no problem but aren't able to grab the boot image.

After receiving the IP it reads:

TFTP.
PXE-M0F: Existing Intel Boot Agent
Selected boot device failed. Press any key to reboot.

Looking at the SMSPXE logs it seems to be trying to grab a boot image that isn't deployed to the server and one that isn't used on a task sequence that I can find.

TFTP: 10.x.x.x connected
TFTP: 10.x.x.x request for smsboot\<packageid100130>\x86\wdsnbp.com

I've removed it from all other DP's in the domain so I'm hoping that fixes it but I'm wondering why would the client choose to grab that one, when there are other boot images on the server it could have used?

DHCP and PXE responder live on the same server
Client and DHCP/DP are in different VLANS
Using IP Helpers and the PXE Responder Service

Thanks for any info you can provide.

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
920 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Gideoney 446 Reputation points
    2022-10-14T09:15:34.47+00:00

    As you know, client download wdsnbp.com to download pxeboot.com and then download other files.

    You can view blow article to know usual boot process:
    troubleshooting-sccm-part-vii-osd-part-i

    The wdsnbp.com file is the file on the DP after we enable PXE on DP. The file path is: C:\RemoteInstall\SMSBoot\x64 or C:\RemoteInstall\SMSBoot\x86. Although we don't configure wdsnbp.com in the task sequence, this is what the boot process needs.

    On your question, It seems that the wdsnbp.com file could not be found.

    You can check the following to try to resolve the issue:

    1). The boundary group is configured correctly. Make sure DHCP-scoped boundaries, mp servers, and DP server(DP for PXE is enabled) in a boundary group.

    2). WDS is not configured successfully. If WDS is not configured successfully, there will be no wdsnbp.com file.

    3). IP Helper was unable to locate the pxe-related file.

    If the response is helpful, please click "Accept Answer" and upvote it.

    1 person found this answer helpful.
    0 comments No comments

  2. Simon Ren-MSFT 30,906 Reputation points Microsoft Vendor
    2022-10-13T09:14:24.897+00:00

    Hi @Oilers93 ,

    1,==>I've removed it from all other DP's in the domain so I'm hoping that fixes it.
    May we know if the issue is fixed by removing the boot image from DPs?

    2,==>but I'm wondering why would the client choose to grab that one, when there are other boot images on the server it could have used?
    Here is an awesome article that detailed explains which boot image will be delivered to a PXE booted client at PXE time.
    https://home.memftw.com/boot-image-selection-configmgr/
    In short, the last boot image associated with the last TS deployed will be the one used.

    Hope it helps. Have a nice day!

    Best regards,
    Simon


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.