Jump to content


  • 0
AllonsIT

Strange PXE-E53: No Boot Filename Received

Question

Quick question....

 

We have been deploying Win7 for a almost a year with no issues except for a few machines that dont seem to want to image. I'd say out of every 100 machines we image we will have 1 that fails with the PSE-E53 error. I've double checked the PXE boot settings and have updated the DP with both x64/x86 boot images with no success. The stranger part is that its mostly all of the same model machines and some have failed right out of the box.

 

Example: We un-box 25 Dell Optiplex 790's. 24 image while 1 fails with PXE-53 error.

 

We have collected 8 machines now that we are unable to image.

 

I'm out of ideas and any help would be appreciated.

  • Like 1

Share this post


Link to post
Share on other sites

2 answers to this question

Recommended Posts

  • 0

If you ever find out WTF is going on with these, please let me know. I have an Optiplex 790 that does this and it is my reference hardware for image verification.

 

I had a handful of 790's that have done it but I havent looked into it further. However, it hasn't happened in a while. I rebuilt the image with a spare Win7 machine i had and a capture disk and then rebuilt the boot image with the drivers. Im not sure of what the issue was because the boot image is nearly identical to the old one, but so far so good.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.