SCCM - PXE Boot Aborted. Booting to next device

Benjamin Hagen 121 Reputation points
2021-10-26T20:27:21.493+00:00

Afternoon All,

I have been working on getting Imaging setup in our environment for about two - three weeks now. I followed the blog by this site. I am attaching pictures. SCCM version: 2107 ADK: 10.0.19041.1 Host OS: Server 2019

  • PXE boot is enabled
  • x86 and x64 boot images are deployed to my db
  • WDS service is running
  • From my Hyper-V test box I get Clinet IP, Mask, and DHCP, Gateway. Configuration Manger is looking for policy and then then right after contacting Server PXE Boot aborted. Booting to next device.
  • SMS PXE and SMS TS logs attached. Please let me know any other Logs you would like see.
  • Pictures of desired settings also attached. Please let me know if there are any settings that you would like to see.!
  • List item143944-wds-running.png143951-windows-10.png143790-x64-boot-image.png143945-x86-boot-image.png

143907-dhcp-options.png143908-sms-pxe-log.txt143934-pxe-hyper-v-host.png143943-pxe-enabled.png

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,261 questions
0 comments
Accepted answer
  1. Benjamin Hagen 121 Reputation points
    2021-11-19T20:43:13.377+00:00

    Thank you to everyone that helped with this issue. I am proud to say my issue is now resolved. Granted this may be the nuclear option of fixes but damn it worked.

    1. Triple-checked Boundary groups. deleted boundary groups and re-created, ensuring IP ranges DID NOT over lap
    2. deleted DHCP scope options especially on the VLAN where the SCCM Server is hosted. Spoke with my networking team and had IP helpers placed on VLANs outside where SCCM is hosted.
    3. Uninstalled ADK
    4. Reinstalled ADK
    5. Re-created Boot images (x86 and x64)
    6. Uninstalled PXE and rebooted
    7. Uninstalled WDS Service and rebooted
    8. Removed Distribution Point
    9. Deleted the RemoteInstall folder
    10. Rebooted
    11. Re-created Distribution point
    12. While building DP enabled PXE, enabled PXE Support for all unknown computers.
    13. went to each boot image and from properties went to Datasource
    • Ensured Update DP on a schedule was enabled ( once every month)
    • Enabled Binary Differential Replication
    • Deploy from PXE enabled DP
    1. from my task sequence ensured my x64 boot image was the selected Boot Image.
    2. Distributed connect (OS, Boot images (x64 and x86), Client package to the Distribution point
    3. Went out to my back porch and smoked two cigarettes.
    4. Went to Hyper-V VM and power cycled
    5. Successfully UEFI PXE boot!
    0 comments

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pavel yannara Mirochnitchenko 11,716 Reputation points MVP
    2021-10-27T08:23:09.54+00:00

    In PXE aborted, 99% cases are that device exists in CM already and the TS is not applied to it. Sometime you don't know the machine hostname or have wrong info about it, so use MAC query to track the device. You also see in smspxe.log the event with what MAC adress the device has skipped the PXE process to start TS.

    1 person found this answer helpful.
  2. AllenLiu-MSFT 40,881 Reputation points Microsoft Vendor
    2021-10-27T08:15:40.41+00:00

    Hi, @Benjamin Hagen
    Thank you for posting in Microsoft Q&A forum.

    We may check have we make the task sequence available for media and PXE?
    144154-1.jpg

    And have we deploy the task sequence to "All Unknown Computers"?

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.

  3. Pavel yannara Mirochnitchenko 11,716 Reputation points MVP
    2021-11-01T07:00:42.023+00:00

    How about physical machine, can you boot it up? Your Hyper VM is Gen1 legacy bios, try switching it / create new one with Gen2 which will be UEFI device.

  4. Benjamin Hagen 121 Reputation points
    2021-11-04T02:52:10.57+00:00

    I did just find this artical

    https://learn.microsoft.com/en-US/troubleshoot/mem/configmgr/troubleshoot-pxe-boot-issues#solution-2-reinstall-pxe-use-only-if-solution-1-didnt-resolve-the-issue

    IT appears there is a step that I was missing:

    Locate and delete the RemoteInstall folder.

    Change the date on the self-signed certificate in the properties of PXE DP. Wait for the new certificate to be created. It isn't applicable if the DP is HTTPS.

    I will try this in the morning and update the thread

    0 comments