Windows 10 Deployment

First off, I apologize for my ignorance.

We deployed Windows 7 images three years ago without issue. This year we will be deploying Windows 10 64-bit images on our new hardware. I believe I have the creation of separate partitions nailed down (for bitlocker) as well as creating the sysprep file. My issue right now is booting from the NIC.

We have Dell Latitude E5570 and Optiplex 3040 machines. The only way I have been able to successfully boot from the NIC is to disable secure boot and change the Boot List Option to Legacy. I was under the impression that it is best practice to not do this. 

I have been scouring the forums for an answer and have not been able to find one yet. Any help would be greatly appreciated.


1 Comment   [ + ] Show comment
  • We do not UEFI boot here we still Legacy boot and have had no problems installing windows 10 on our systems. - jboling 3 years ago

Answers (1)

Posted by: CTRL+ALT+DEL 3 years ago
White Belt

If I got it right then you're trying to UEFI PXE Boot to the KBE and then install Windows 10.

For UEFI PXE-booting you need to configure your DHCP scope options properly, what are you using as your DHCP server? A Windows Server, the Kbox built-in DHCP server or something else?

  • We're using a Windows server for DHCP (server 2012). - shane.stecher 3 years ago
    • That's good. There's a KKE video about how to configure the Windows DHCP server properly in order to use both, UEFI and Legacy PXE boot. You can find this video here: https://support.quest.com/kace-systems-deployment-appliance/kb/215635 - CTRL+ALT+DEL 3 years ago
      • Thanks a million! I will check it out. - shane.stecher 3 years ago
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