PXE-E53 No bootfilename received - on one workstation only
Hi I appreciate this error is very heavily documented but I'm struggling to fathom why I'm getting this error and failed PXE OSD on a single workstation only. Most of the advice around this error seems to point to problems with the PXE point setup or DHCP and PXE booting being broken for all machines but I can PXE boot any other machine on the same subnet (same network cable) and OSD works fine but this workstation just throws error E53 every time. I've checked and double checked that there isn't a record with the same MAC address in the SCCM database. I import the PC from the Computer Association and it appears successfully and I can add it to my deployment collection. Still every time I get E53. Could anyone offer any suggestions as to what's causing this? Thanks in advance Stewart
July 13th, 2012 9:51am

This error usually occurs when the computer is not found in the database or there is no 'Unknown computers' advertisement. To resolve manually import the computer into the ConfigMgr database. Afterward, you may need to restart the WDS service to get the computer to boot. http://www.mockbox.net/configmgr-sccm/323-sccm-os-deployment-no-boot-filename-receivedMy blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2012 10:30am

What the does SMSPXE.log file say about the client machine that tries to PXE boot?
July 13th, 2012 2:15pm

Here is a good article about PXE troubleshooting: http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2012 2:50pm

Thanks for all your responses. The machine was definitely in the SCCM database as I was manually importing a record with the machine's MAC address. The machine's MAC address was not appearing in the SMSPXE.log and I was struggling to deceiver what was being written to the log that related to the PXE request from that specific machine due to the level of activity in the log. Annoyingly after spending the best part of a day trying to get it to work, it suddenly PXE booted successfully when I just gave it another random try later on having not changed anything. The last thing I'd done, which was some time previous to it working, was to delete the existing DHCP lease for the machine's PXE client. I tried PXE booting just after doing this and it failed so I'm not convinced this was the cause and there's plenty of addresses available on the scope. Thanks Stewart
July 18th, 2012 5:44am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics