SOLVED PXE installation stop and reboot before entring task sequence

[NAB1919]

Hello Everyone, We changed the Mother Bord and reinstall the server(our DP and PXE server) , i added back the role WDS, done the configuration like the others servers, but when we try to install a device, we face 2 type of problem:
1st case: when the boot image folder is empty in WDS , the device cannot enter the installation and in the logs it says no boot image found ( Strange cause in E:\Remoteinstall we have everything and its working for the other servers)
2nd case: when i add the boot image into the WDS folder, image.WIM load and after that it stop, and then reboot, so i cannt get the task sequence screen.

ANy help please ? i compare all configuration with the other servers , i dont see what ive miss
network team said that nothing has change on their side
PS: i noticed that we cannot distribute content on this DP since the reinstallation
thanks in advance

 

[Harshit Pandey]

I think you must repair the PXE once. And use PXE responder instead of WDS as it works correctly.

 

[NAB1919]

I think you must repair the PXE once. And use PXE responder instead of WDS as it works correctly.

thanks for replaying, i Can not change the way the company work, i'm external and they want to keep things as they are, maybe i'll try to convince them . But i dont get repair pxe, while i just installed it

 

[Prajwal Desai]

Does repairing the PXE helps? have you already tried it?

 

[NAB1919]

Does repairing the PXE helps? have you already tried it?

thanks for answering , i didn't try it cause device able to boot and load .WIM, beside it's a new WDS installation so i didn't thought of that, ( at least i didn't understant well the term "repair pxe")

 

[Harshit Pandey]

repair PXE means go to the DP properties and on the PXE tab uncheck the options and enable them back.

 

[NAB1919]

i'm back to give news , so this can help others if they face the same issue.
First Thanks for replying.
The solution was to delete DP form SCCM, re create it again cause it seems that some links between DP and SCCM was Broken when the DP crashed and reinstalled again. So after that we have to re create the DP in SCCM so the links or Synchronization get back.