Hi,
Thank you for posting in Microsoft Q&A forum.
Per my experience, this issue may be because the client is recognized as a known client and no optional advertisement for it. We can check this in the smspxe.log on the server.
When the WDS server receives the PXE request, it (the WDS server, not the client itself) interacts the client's MAC address and SMSBIOS with the MP to see if the client is in the ConfigMgr Database. If it isn't in the database, the client will be recognized as an unknown computer. So that the WDS server decides if there is a suitable deployment and optional advertisement for the unknown\known client. Here is an example of SMSPXE.log in my lab to show the details:
When an unknown computer is started, Configuration Manager recognizes the computer as an unprovisioned computer rather than an unknown computer. This means that the computer can now receive the task sequences that were deployed to the unknown computer object. The deployed task sequence then installs an operating system image that must include the Configuration Manager client.
Similar thread for your reference, we can also try to clear PXE flag to have a try.
SCCM PXE Boot - always have to delete existing client for it to work?
Thanks for your time. 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.