MDT Windows 10 on Dell Optiplex 5060 - No bootable device found on restart

[bicky]

Dear all,

I am not sure if anyone has come across this issue and knows the solution.

 

We just got 20 x Dell Optiplex 5060 which are trying to install Windows 10 via MDT. Computer successfully does PXE boot and goes through the task sequence/OS/App selection, then goes through the installation, but when it reboots after the OS install completion the POST screen shows "No bootable devices found".

 

All drivers for this model has been installed on the MDT & WDS.

BIOS has been configured to Disable SecureBoot, Enable Legacy Option, Disable UEFI, Disable Deep Sleep Control, Enable WOL with PXE Support and Boot Sequence with internal HD & Onboard NIC selected.

 

This is the first time we have across this issue and in the past we had no problem MDT Win 10 on Dell Optiplex 3040/5040/Surface Pro/HP Desktops.

 

 

Any help on this will be much appreciated, thank you.

[minimoo]

This doesn't answer your question - but have you tried with UEFI on; and doing a uefi network boot - and using uefi all the way through?

[bicky]

When I enable the UEFI on the Bios, there are no boot options like PXE or Windows Boot Manager, resetting BIOS to defaults is not helping either.

[bicky]

Just found out that I have "Enable UEFI Network Stack" for the UEFI PXE to work.

thank you Minimoo.

[minimoo]

the next question is whether you can get it to pick up the pxe server under uefi, and whether it works or you hit the same issue?

 

But if the laptops are going out to staff, using tpm+bitlocker+uefi would seem to be a more sensible setup

[drdos256]

We were using MDT 2013 for Window 7 installs but we are now we are using it for Windows 10 - if it helps anyone we had the UEFI rollout challenge on some new Dell Latitudes and needed a quick solution, we had to disable secure boot, enable the UEFI stack and boot off the network with the UEFI IP4 option in the boot menu.

In DHCP we changed option 67 from Bootfile=boot\x86\wdsnbp.com to Bootfile=boot\x64\bootmgfw.efi and Windows 10 installed ok.

[FN-GM]

In DHCP we changed option 67 from Bootfile=boot\x86\wdsnbp.com to Bootfile=boot\x64\bootmgfw.efi and Windows 10 installed ok.

 

If you use IP Helpers on your core switch instead it will work interchangeably between BIOS and UEFI.

[Mujja]

Not sure how getting PXE booting is going to help bicky. He\She doesn't have a problem booting the computer and connecting to the DeploymentShare.

 

Bicky, boot the computer in to WinPE, you can use the same bootmedia for MDT and press F8. Check the HDD is partitioning correctly as in the TS partition step. Run the BCDboot command.

 

It seems like you don't have a bootable partition.

[strawberry]

are you installing a custom wim or the factory wim?

[FishCustard]

If you use IP Helpers on your core switch instead it will work interchangeably between BIOS and UEFI.

This - do this. Makes your life so much easier.

[Arthur]

It seems like you don't have a bootable partition.

The error message @bicky is seeing is what you get when you partition a disk with GPT partitions on a BIOS-based computer.

 

@FN-GM's suggestion is the best way to avoid issues like this, although it is also possible to create policy rules on your DHCP server to make it support both BIOS & UEFI-based PCs when PXE booting.