Selected boot device failed - SCCM PXE

Question

_{Wednesday, February 1, 2017 5:59 PM}

Hi Folks,

I have an issue for OSD in my current organization. Once i have added a registry key RamDiskTFTPBlockSize in my primary server. under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP. Post adding this key i have started getting issues for OSD in my environment then i had done some workaround and restored OSD by disabling and enabling DP again. My primary site started working again without issues. But my secondary servers are not restored with OSD. Anyhow i have managed to disable PXE and enable PXE again but of no luck. Any suggestions to mitigate the issue? 

All replies (6)

_{Wednesday, April 26, 2017 7:05 PM ✅Answered}

Below are the things i have done to resolve this issue.

PXE reinstallation module
1.untick the enable PXE checkbox on the distribution point. Answer yes that you want to remove the Windows Deployment service.
2.remove your boot images from your distribution point
3.After 5 minutes. Delete %windir%\temp
4.check with server manager if you can add/remove roles on the server. If WDS is done uninstalling there is a pending boot.Reboot!!!
5.check if the remoteinstall folder is located on your system. If it is delete it.
reboot
6.Add the PXE point again by checking the box on the distribution point properties. Check the distrmgr.log and see if the remoteinstall folder reappers..
7.Send the boot images to the distribution points again

Command to remove WDS role:

Import-Module ServerManager; Get-WindowsFeature WDS; Remove-WindowsFeature WDS

Cheers! G Praveen

_{Wednesday, February 1, 2017 9:54 PM}

On the PXE points not working, what is in the smspxe.log?

_{Wednesday, February 1, 2017 10:03 PM}

Images are in place of SMSBoot folder. SMSPXE log doesn't show any error's

_{Wednesday, February 1, 2017 10:05 PM}

When a client tries to PXE boot, can you post the smspxe.log from a DP that is having the issue?

_{Thursday, February 2, 2017 5:04 AM}

Hi,

removing the RamdiskTFTPBlocksize value and to make sure restart the WDS service should restore it to the state before. Modifying he RamDiskTFTPBlocksize value will if you set it to a to  high value fail on certain models. It is basically depending on which NIC, BIOS, firmware and so on the test client.

I did some tests with RamdiskTFTBlocksize and the new setting for windows size and some models will fail with to agressive values.

Regards,
Jörgen

-- My System Center blog ccmexec.com -- Twitter @ccmexec

_{Tuesday, February 7, 2017 2:50 AM}

Hi,

     Just want to confirm the current situations.

  Did you find the correct smspxe.log and search some clues for this issue?

Best Regards,

Ray

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].