DHCP, WDS, PXE Boot and Common Issues

Hi Guys,

Again i am back with very common information about DHCP,WDS & PXE and issues troubleshooting and their solutions.

DHCP, WDS, and PXE are the main and needed components which plays very important role in SCCM OSD. They function and provide a very cool and automatize the OS installations (Network based).

So why is the Need?

DHCP: DHCP offers automatic ip address assigning functionality to machines at both booting state and online state.

DHCP Scope options are one main key component.

WDS: WDS offers the PXE functionality (Not SCCM) for network based OS installation (boots machine in to windows installation mode from network)

So when we install the SCCM PXE service Point on WDS Server, It just overrides the settings of WDS PXE.

Now Common PXE Boot Issues:

·        PXE-E53: No boot filename received 

·        PXE-T01: File not found

·        PXE-E3B: TFTP Error - File not Found 

·        PXE-E55 Proxy DHCP Service did not reply to request on port 4011 

·        PXE-T04: Access Violation 
PXE-E36: Error Received from TFTP Server 
PXE-M-F Exiting PXE Rom

PXE-E53: No boot filename received 

"PXE-E53" error indicates that the PXE client received a reply to its DHCPDISCOVER message, but the "boot filename" information was missing in this reply.

PXE-T01: File not found

This Error indicates that WDS service is not able to access or cannot found any PXE images

Solution

1: Stop the WDS service.
2: Delete C:\WINDOWS\TEMP\PXEBootFiles\Windows
3: Start the WDS service.
4: Check smspxe.log again and see if <![LOG[Unable to delete directory... exists.

PXE-E3B: TFTP Error - File not Found 

This Error comes when WDS role installation does not go well.

RemoteInstall folder gets corrupted

SMSBoot folders under the RemoteInstall which should have the following files:

x64\abortpxe.com
x64\bootmgfw.efi
x64\bootmgr.exe
x64\pxeboot.com
x64\pxeboot.n12
x64\wdsnbp.com
x86\abortpxe.com
x86\bootmgr.exe
x86\pxeboot.com
x86\pxeboot.n12
x86\wdsnbp.com

PXE-E55 Proxy DHCP Service did not reply to request on port 4011 

The "PXE-E55" error indicates that the PXE client has sent a request to the proxy DHCP server on port 4011, but did not receive a reply. This problem can only occur when the DHCP Class Identifier Option #60 is set on the DHCP server, but there is no proxy DHCP service running on port 4011 on the same machine.

SOLUTION

If you are operating DHCP and proxyDHCP services on different machines, do not set the DHCP Class Identifier Option #60 in the DHCP configuration, and let both services run on port 67/udp (bootps).

If you are operating DHCP and proxyDHCP services on the same machine, set the DHCP Class Identifier Option #60 in the DHCP configuration. Let the DHCP service run on port 67/udp, and the proxyDHCP service on port 4011/udp.

PXE-T04: Access Violation 

PXE-E36: Error Received from TFTP Server 
PXE-M-F Exiting PXE Rom

Above three errors can occur because of wrong DHCP configuration.

Solution

You may need to configure IP helper (BOOTP) settings on the routers OR configure DHCP scope options in case you have Cisco DHCP instead of Microsoft DHCP.

To Configure DHCP Scope on Cisco Routers, add the following to DHCP Scope:

next-server ‘IP Address of PXE Service Point’

filename \boot\x86\wdsnbp.com

hope this will be helpful.

cheers..