PXE not work in Configuration Management

MuddyMayor-5788 240 Reputation points
2024-05-30T16:06:50.6766667+00:00

We are using MDT to image clients for years and going to deploy Windows 11, as we know that Microsoft MDT is not officially supported Windows 11, so we decide to migrate from MDT to SCCM. We have enabled PXE and checked PXE responder option. But we just get "PXE boot aborted" error, can't load boot image. What should I do to make PXE work?

Microsoft Configuration Manager
0 comments
Accepted answer
  1. Pavel yannara Mirochnitchenko 12,396 Reputation points MVP
    2024-05-30T21:13:57.2833333+00:00

    I remember from old days that PXE boot aborted usually means that the Task Sequence assiment is not propertly assigned to a boot image or you have a SCCM computer record for that device and it is not assigned that Task Sequence (delete account or assign TS to collection where that record is).

    But there might be other reasons as well. At you DP server there is smspxe.log which should reveal the reason for you. There will be new entities same time you are trying PXE boot.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Simon Ren-MSFT 31,831 Reputation points Microsoft Vendor
    2024-05-31T02:01:39.66+00:00

    Hi,

    Thanks for posting in Microsoft MECM Q&A forum.

    1,Please verify that the computer that you try to restart exists in a collection that's targeted for a Task Sequence deployment.

    2,Make sure that you've checked the Enable unknown computer support PXE setting on the DP.

    3,If you are deploying the Task Sequence to unknown computers, verify that the computers don't already exist in the database.

    4,Please check the smspxe.log on the server side to see if there is any error.

    Hope it helps. Thanks for your time.

    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.

    0 comments