/build/static/layout/Breadcrumb_cap_w.png

problem pxe booting only vm's will pxe boot and other computers, will not boot new dells

It talks to the server and downloads the NBP file.

Then no error, just will go no further.

CXgi1FD1TwIAAAAASUVORK5CYII=

im working on a dells Precision 3650 desktop

what am i missing?


0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Posted by: TheAustinDave 1 year ago
Third Degree Brown Belt
0

Top Answer

The system is showing that it is attempting to PXE boot into the undionly.pxe file which is a Legacy/BIOS boot mode. This comes from the DHCP setting for OPTION 67, the file name that would need to be loaded on this UEFI system is ipxe.efi. Images which are captured as Legacy can be adapted to run and install as UEFI. There are a couple of articles on Quest support site which may help.
https://support.quest.com/kb/4306577/capturing-and-deploying-multiple-partitions-for-windows-7-and-later
https://support.quest.com/kb/4243138/dhcp-configuration-for-bios-and-uefi-pxe

Posted by: TheAustinDave 1 year ago
Third Degree Brown Belt
0

Hello -

Is it intended to boot into the Legacy mode for image deployments?  Check with the new dell system and see if it has the Legacy mode to enable or they might just be UEFI only.


Posted by: pitt 1 year ago
White Belt
0

I know longer see Legacy mode in the dell bios

infact i see a note in the bios that says

"Note: Legacy boot mode is not supported on this Plateform."

and i think that started with a bios update some time in the last 6 months

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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