SOLVED PXE Boot Failure after upgrading to Configuration Manger 2403

[k towle]

We recently upgraded to Configuration Manger 2403

PXE boot is working on the main SCCM server, but not on the remote site distribution point servers
This is the message that appears when attempting to PXE boot …

Checking Media Presence …..
Media Present ….
Start PXE over IPv4.
Station IP address is x.x.x.x (valid ip address)

Then briefly the following pops up …

Server IP address is x.x.x.x (correct sccm dp)
NBP filename is smsboot\x64\wdsmgfw.efi
NBP filesize is 0 Bytes
PXE-E99: Unexpected network error.

And then failure

• We use DHCP options 066 Boot Server Host Name and 067 Bootfile Name for pxe booting and have never had issues with this method in the past.
• The pxe tab setting are consistent for all sites including the main Site Server
• Content is being distributed from the main DP to remote servers

Has anyone seen this problem - Thanks

 

[Prajwal Desai]

What I can suggest is to uninstall PXE on the DP and rename the current RemoteInstall folder to .old and let it rebuild your RemoteInstall folder. Let me know if that works.

 

[k towle]

What I can suggest is to uninstall PXE on the DP and rename the current RemoteInstall folder to .old and let it rebuild your RemoteInstall folder. Let me know if that works.

Thank you for your reply - in addition to unchecking 'Enable PXE support for clients' do I also need to uninstall the Windows Deployment Services role ?

 

[Prajwal Desai]

Thank you for your reply - in addition to unchecking 'Enable PXE support for clients' do I also need to uninstall the Windows Deployment Services role ?

No, keep the WDS role as it is. Only remove the PXE and enable it back. I also read in online forums that this issue could be due to the DHCP working inconsistently. Many have suggested creating a new DHCP scope and testing the PXE boot.

 

[k towle]

No, keep the WDS role as it is. Only remove the PXE and enable it back. I also read in online forums that this issue could be due to the DHCP working inconsistently. Many have suggested creating a new DHCP scope and testing the PXE boot.

Hi Prajwal - I removed the pxe role but when I go to rename the RemoteInstall folder I get a windows message indicating that the folder or File is open in another program. I can't reboot this server until after work hours. Any other suggestions for the renaming ? Thanks

 

[Prajwal Desai]

Hi Prajwal - I removed the pxe role but when I go to rename the RemoteInstall folder I get a windows message indicating that the folder or File is open in another program. I can't reboot this server until after work hours. Any other suggestions for the renaming ? Thanks

Can you stop the WDS service and rename the RemoteInstall folder and see if that works.

 

[k towle]

Can you stop the WDS service and rename the RemoteInstall folder and see if that works.

After a server reboot that evening, I was able to rename the folder. Re-enabled and configured PXE but after 2 days the new RemoteInstall folder has not been created. The WDS Server service is set to Automatic but fails to stay running. Does WDS need to be running for the RemoteInstall folder to be created ? Thank you

 

[k towle]

Updating the boot image and re-starting the DHCP service at each site has fixed this problem. Thank you for your input this post can be closed.