This error has been round the forums a few times. I have sccm sp1 on server 2008, pxe role is set up, wds installed. I have checked every pre req on the Ms SCCM site and its all spot on as far as I can see.
when I F12 a client I get
PXE-E53: No boot filename received
PXE_MOF: Exiting HP PXE ROM
I have done the steps mentioned in a few posts of
5. Add boot images (both of course) to PXE DP
I have upgraded my WAIK to 1.1 and exported the boot images from that and imported them into SCCM
I found a post that said
Has anyone (Wally?) got a definite answer to this pxe issue. I didnt have any problems with my test lab and when I saw all the posts about this in the forums I assumed/hoped it was a bug that would be fixed in SP1
Answers
In case anyone is interested. My PXE is now working.
The issue is definitely to do with our VLAN setup. I created a new site server with the PXE role on the same VLAN as my desktops and it started working straight away. One day I’ll have to research ip helper addresses and find out if I can get it going that way
All replies
Grief, this gets worse.
I have tried everything I can find written on the net about PXE issues with SCCM. Now when I try to advertise a Task Sequence the ‘Make this task sequence available to boot media and PXE» option is greyed out.
Does anyone have a defintive checklist/set up guide for PXE I can go through?
Is this a fresh install or have you upgraded from an earlier version? I don’t want to send you on a wild goose chase.
This posting is provided “AS IS” with no warranties and confers no rights.
This is a clean install. I have fixed the second issue, during all my add/remove WDS and PXE role the task sequence ‘lost’ contact with its boot image. I removed the boot image from the TS properties page, and added it back in again and then the tick box became available once more. Just the PXE-E53 issue to go
The setup is a clean install of Server 2008 following the MS how to configure Server 2008 step by step. SQL is on our main SQL server runing on Server 2003. Everything is fully patched. SCCM was installed with a full SP1 installer from the eval, then reinstalled from the CD once we received it on our SA. I think I have read every page found by google listed from a SCCM/PXE search. I have done every listed fix, most of which seem to be around removing and reinstalling PXE and WDS.
I have not configured WDS at any point as directed by MS, nor have I set the port info in DHCP. The only things I have read about that I havent tried is ip helpder addresses, which I plan to discuss with our network guy this morning. We do run a VLAN setup, and I believe the server is on a seperate subnet to the client, need to confirm that this morning. I’ve seen this suggested on various forums but never mentioned by MS. I have also resisted the full site reinstall, so far. If I do this, do I simply use the same site code to have it reuse my database info or do I have to back everything up?
any suggestions greatly appreciated.
I got the same problem in my test lab. I also got an error in pxecontrol.log that said:
What I finally figured out was that I forgot to add my site server to the Administrators group in AD. After I added the computer to the Administrators group I reinstalled my PXE site server roll on the site server. After that everything works ok.
If you are using a different account than the site server check that the account is able to connect to the site database.
Andy Tuke wrote:
My SCCM setup is working fine with everything, just not PXE. I’m pretty sure that its because the site server is running on a VLAN with a different subnet to the workstations. I am going to knock up another server in the PC subnet and install the PXE role on that and see how that works
The PXE Service Point service that is running on the WDS server(s) reports it’s status to the adult primary Configuration Manager 2007 server and the results can be viewed in the component status messages on the adult primary Configuration Manager 2007 console.
These messages will report specific errors or events that have occurred with the PXE service point.
Basic PXE log files contain information about the configuration and setup of the PXE service point.
PXESetup.log will contain the installation logging for the PXE Service Point role that is added by the Configuration Manager 2007 console. Many installation and configuration errors can be seen in this log.
Log file location: \sms\logs
PXEMsi.log Provides information about the PXE service point and is generated when the PXE service point site server has been created.
Log file location: \sms\logs
PXEControl.log provides information about the PXE Control Manager.
Log file location: \sms\logs\
Advanced Log Files
To enable WDS Logging set the following registry key:
The log file generated from this setting will appear in %Windir%\Tracing\WDSServer.log
To add additional logging features to the PXE Filter Script add the following style of code to the script: PXE.LogTrace «My log file comment»
Problem solved. Had a problem with the WDS PXE Filter that I installed.
Thanks for your help!
In case anyone is interested. My PXE is now working.
The issue is definitely to do with our VLAN setup. I created a new site server with the PXE role on the same VLAN as my desktops and it started working straight away. One day I’ll have to research ip helper addresses and find out if I can get it going that way
hi i installed sccm 2007 sp2 on server 2003 sp2 and installed dhcp on it after that i installed wds without any configuration during setup
after installiong wds i add pxe point role to this server all role and wds and dhcp are assigned to same box when client wants to boot from pxe it gets NO BOOT FILENAME recived
Make sure the DNS name is resolvable and also make sure your test machines have at least 512Mb RAM to boot PE and give PE some ram. Memory should be at a minimum [Size of PE image] + 128Mb.
try setting it to Respond to All known and unknown computers
My step by step SCCM Guides Follow me on Twitter
I had exactly the same problem «PXE-E53: No boot filename received».
I fixed it by the re-updating the distribution points with my boot image, Boot Image (x86) in my case.
I gathered that the problem was not with DHCP, as the DHCP allocation happens prior to the boot image being loaded. It just doesn’t actually recieve an IP address because it doesn’t boot.
1. So just launched Config Manager Console.
2. Selected Computer Management, Operating System Deployment, Boot Images.
3. Right clicked my boot image that should have been booting my client machine and clicked «Update Distribution Points».
When you get the no boot filename received error in SCCM 2007 it generally will only happen in a test environment. I had been doing some testing for a client and experienced the issue lots and lots of times and now can fix it every time.
To fix this issue you have to be patient depending how many clients machines you have in your active directory, this particular client had 14,00 plus so it can take some time to refresh and update the collection membership. Follow the following steps to resolve.
1. In the SCCM Management utility, from the «Computer Management» node, right click All Systems and click «Update Collection Membership».
2. When this is complete the hourglass icon will disappear and you then should search for the machine in question in the «All Systems collection».
3. When the search finishes (if you have this problem) you will see duplicate records for the same machine, one being obsolete. (Scroll a bit to the right to see the obselete field).
4. Delete the Obsolete machine record.
5. Re-advertise your Task sequence.
6. Reboot your Client machine and it now will PXE boot.
