Trouble shooting PXE booting

Question

_{Monday, July 2, 2018 8:30 PM}

I have been trouble shooting PXE booting with my SCCM server without any indication as to where I am going wrong. All of the boxes are checked for PXE boot within SCCM, however I believe the issue may lie where the client is looking for the image to boot to. On my SCCM server I have my remoteinstall folder with the SMSBoot folder on my E: drive, also on my E: drive is everything related to my OSD (Sources folder/MDT folder).

My DHCP is on another server and option 66 is pointed to the IP of the SCCM server, and option 67 is set to smsboot\x64\pxeboot.com currently (it has been set to smsboot\x86\wdsnbp.com and smsboot\x64\wdsnbp.com). I am new to setting up PXE on SCCM and I am not sure if I have the remote folder set correctly (let alone how to set it), and if i am missing something else. Any help is appreciated. 

I do get a PXE-E23 TFTP error when I PXE boot from the client, however i believe that is because the client is not seeing any information that would cause it to properly PXe boot.

All replies (6)

_{Tuesday, September 25, 2018 9:38 PM ✅Answered}

I uninstalled and reinstalled the wds services and removing the remoteinstall folder. i reisntalled the wds serverice and it created a remoteinstall folder without the smsboot folder. i pointed option 67 to boot\x64\wdsnbp.com and it worked.

_{Monday, July 2, 2018 8:59 PM}

Hi,

I would remove the DHCP options and start using IP Helpers instead to point the client to the correct PXE Server. Devices that boot using UEFI needs another boot file than Legacy BIOS. IP helpers has always been the prefered and supported option. Could that be the problem? are you booting a UEFI computer or Legacy?

Regards

Jörgen

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

_{Monday, July 2, 2018 9:32 PM}

right now it is set for UEFI and legacy with UEFI being the priority.

I will look into the IP helpers.

_{Tuesday, July 3, 2018 8:50 AM}

Hi dbnumberiv,

If it's set for UEFI, the option 67 of your DHCP should set with "smsboot\x64\wdsmgfw.efi"

Please refer to this link for more details:
https://www.experts-exchange.com/articles/29394/Using-DHCP-to-Boot-WDS-to-BIOS-UEFI-with-SCCM.html 

Best regards,
Yuxiang

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

_{Tuesday, July 3, 2018 5:40 PM}

I am still waiting to to hear if we have IP helpers configured (i think we do, since I was told that in the past we have done PXE boot over a specific vlan).

i configured option 67 for the smsboot\x64\wdsmgfw.efi and followed the process mentioned in:

https://www.experts-exchange.com/articles/29394/Using-DHCP-to-Boot-WDS-to-BIOS-UEFI-with-SCCM.html 

However, the client is still not getting a response from the SCCM server for PXE boot.

_{Wednesday, September 12, 2018 6:03 PM}

I have come back to this issue now that there was a network admin in place to check the networking side of all of this. it appears to working correctly and currently i am getting an error that states that there is no communication from the server over port 4011. I can see that the port is open and being listen to from wds serverice. when i search issue i get articles saying the dhcp options are wrong. Currently i have 

option 60 set to pxeclient

option 66 set to the ip of the server

option 67 set to smsboot\x64\pxeboot.com

i also confirmed that the smsboot folder was shared (it wasn't before), and that there is a dns point for the server ip address to the server. as a side note this server has two NICs with active IPs on seperate vLANs (not sure if this will matter) to the DHCP scope.