A network administrator is deploying a standardized Windows 11 Enterprise image across new workstations using Preboot Execution Environment (PXE) through Windows Deployment Services (WDS). During initial testing, UEFI-based workstations successfully obtain an IP address from the DHCP server and locate the WDS server, but fail during the initial boot loader download with an architecture mismatch error. Legacy BIOS-based workstations on the same network subnet complete the PXE boot process without any issues. Which of the following configuration changes on the network deployment services should the administrator make to resolve this boot failure for the UEFI endpoints?
- Configure DHCP vendor class identifier options to specify bootmgfw.efi as the Network Boot Program (NBP) for UEFI clients instead of pxeboot.n12Cevap
- BPerform an in-place architecture upgrade on the WDS server operating system from 32-bit to 64-bit to support 64-bit PXE client requests
- CExecute sfc /scannow on the WDS server to repair corrupted System State files in the TFTP boot root folder
- DGrant administrator elevated application execution permissions to the default network installation user account
Cevap
Configure DHCP vendor class identifier options to specify bootmgfw.efi as the Network Boot Program (NBP) for UEFI clients instead of pxeboot.n12.
Preboot Execution Environment (PXE) booting relies on the target machine downloading a Network Boot Program (NBP) via TFTP. Legacy BIOS systems use NBP files designed for x86/x64 legacy boot (such as pxeboot.n12 or wdsnbp.com). Modern UEFI machines require EFI binaries (such as bootmgfw.efi or wdsmgfw.efi). Configuring the network DHCP server or WDS deployment scope with proper vendor class policies ensures UEFI endpoints receive the correct .efi boot loader file.
Adım Adım Çözüm
Anahtar Kavram
PXE Deployment and UEFI vs. Legacy BIOS Network Boot Programs