Hi... I was wondering if someone could help me / point me in the direction on how to troubleshoot PXE-E53: No boot filename recieved error while trying to push out an operating system through SCCM 2007. The workstation that I'm currently testing with is in VLAN 62 (192.168.62.x). The DHCP Server is in VLAN 3 ( 192.168.3.1 ) and the PXE / WDS / SCCM 2007 server is also in VLAN 3 ( 192.168.3.49 ). IP Helper is configured on my 3Com 5500 layer 3 switch. I've tried setting it so that the first IP is the DHCP server and the second IP is the PXE / SCCM server with no luck. I've also tried it the other way around with the same results - same error. I've tried having option 66 in DHCP, with the name of the PXE / SCCM server with the same results - same error. Any help someone can give is greatly appreciated! :) Thanks... Frank

Hi, Make sure that Option 60,66 and 67 is not configured on the DHCP server. Check out this blog post with troubleshooting steps. http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx Regards, Jörgen-- My System Center blog ccmexec.com -- Twitter @ccmexec

Make sure you have distributed BOTH x86 and x64 boot images or you will get that error. Thanks to a half day of troubleshooting, It fixed it when I was getting that error. I did have option 66 set in dhcp and my IPhelpers setup on all other VLANS. ce

hi, The simple solution would be SCCM/PXE/WDS server on the same VLAN as the client. That should not be a problem. First 'IPhelper' IP is DHCP and the second is SCCM server. VLAN 62 (192.168.62.x). The DHCP Server is in VLAN 3 ( 192.168.3.1 ) and the PXE / WDS / SCCM 2007 server is also in VLAN 3 ( 192.168.3.49) check with your network team if this configuration can work and there is a connection between 2 vlans Regards George www.supportweblog.com

Jorgen and Lville... I will try both of those tomorrow. I dont believe that I have the x86 boot image set yet. Maybe thats my hold up?!?! Geroge - As I'm the network engineer for the network, communication between the VLANs is not an issue. But I appreciate your thoughts and suggestion(s)Thanks... Frank

Jorgen and Lville... Thank you VERY much for your instructions... Both helped! It appears that the PXE starts, it downloads the WinPE, it boots to the Config Mng 2007 screen, says that its initalizing. Then it reboots and never does the install of the O/S. Any ideas?Thanks... Frank

Have you added the Storage driver to the Boot image that is being used? Just because a system is x64 doesn't mean it is necessarily using that archetecture boot image. Anyway, add the storage driver to the boot image, update DP's and try again. Also, If I fixed your previous error, please mark as the answer:) Thanks ThePrep. -ce

Have you added the Storage driver to the Boot image that is being used? Just because a system is x64 doesn't mean it is necessarily using that archetecture boot image. Anyway, add the storage driver to the boot image, update DP's and try again. Also, If I fixed your previous error, please mark as the answer:) Thanks ThePrep. -ce Can you be a little more specific on adding the 'storage drivers'?? Not sure what you mean. Thanks... Frank

Yes, Under the drivers section of Configuration Manager, you import drivers and create driver packages, right? Of these drivers, you'll want to rightclick on the NIC and Storage drivers for your specific model and choose "Add Driver to Boot Image" or something similar. Depending upon the Drive mode (AHCI, SATA, RAID) you will need to add the associated driver. What Make and Model are you imaging at this point?