Error E53:PXE bootfilename not recieved

I am using the Build n capture option while creating the Task Sequence.After advertising on the reference computer i recieve E53 error stating that bootfilename not received.

WDS and DHCP services are running fine.Something i need to look around to mare it work.
Please suggest.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: shweta_kar 12 years ago
Blue Belt
The WDS service had stopped, since i am doing R&D, my DC, Server, DHCP and WDS are on the same machine.

Whenever DHCP is configured after some times WDS service stops wrking, so i have to always stop DHCP server service and then restart WDS service and then DHCP(strange but after doign this both teh services works)

so now when i reboot my Reference computer , PXE starts the boot on the client and the deployment.
Posted by: bardol 12 years ago
Senior Yellow Belt
Is this on a 2008 server? Check the SCCM log files, there's likely a few hundred errors in one of them about not being able to delete a certain temporary directory. Server 2008 locks the temp directory down to only allow full access to TrustedInstaller, you need to manually adjust the permissions to give that to all Administrators.
Posted by: shweta_kar 12 years ago
Blue Belt
Yes, it is on server 2008. the problem was with WDS which is resolved now , so now when i reboot the client machine from network it download the boot image and after some time i recieve an error stating Press F12 for network service boot.
Also i am doing all these things on a vmware image so is there any settings to be taken care of on Vmware.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ