ConfigMgr 2012, UEFI and PXE Boot Support

This is a topic that is discussed in many forums and almost with every customer I meet, how can we do PXE boot on out UEFI devices. This is new technology to many of us and driven by the new Windows 8 tablet’s like the HP Elitepad 900 and the Dell Latitude 10.
Configuration Manager 2012 SP1 supports UEFI and PXE boot of these devices, however there are some dependencies to which version of Windows Deployment Services (WDS) that is used on the PXE-enabled Distribution Point as well.
To support PXE boot of 32-bit UEFI devices Configuration Manager 2012 Cumulative Update 1 needs to be installed as well, KB2817245

A Windows Server 2008 R2 WDS supports PXE boot of 64-bit EFI devices:

From Technet: “Provides support for network booting x64-based computers with EFI, including support for the Auto-Add policy and the ability to deploy boot images using multicasting.” Reference:

A Windows Server 2012 WDS supports the PXE Boot of both 32 and 64 bit EFI Devices:

From Technet: “Support x86 clients (32-bit processors) with Unified Extensible Firmware Interface (UEFI) to network boot and complete an end-to-end deployment by using WDS.” Reference:

This means that yes you can use Configuration Manager 2012 to deploy Windows 8 to your Windows 8 tablet using Windows 8, as long as you are using Server 2012 as the operating System for the PXE-enabled DP and if the Firmware from the vendor supports it as well.

If we look at the file structure in the RemoteInstall directory on a Windows 2008 R2 server running Configuration Manager 2012 sp1 DP it looks like this, where the .efi file doesn’t exist in the x86 folder:



On a Server 2012 DP we can see that the x86 folder includes the files needed to boot .UEFI based devices.

Conclusion, yes, you can PXE boot your UEFI devices depending on which version of  Windows Server the DP is running and which architecture the UEFI device you are trying to boot uses and as long as you are using Configuration Manager 2012 SP1


Add a Comment

Your email address will not be published. Required fields are marked *