8.8 KiB
title, description, ms.prod, ms.localizationpriority, author, manager, ms.author, ms.topic, ms.custom, ms.collection
| title | description | ms.prod | ms.localizationpriority | author | manager | ms.author | ms.topic | ms.custom | ms.collection |
|---|---|---|---|---|---|---|---|---|---|
| Configure a PXE server to load Windows PE (Windows 10) | This topic describes how to configure a PXE server to load Windows PE so that it can be used with an image file to install Windows 10 from the network. | w10 | medium | aczechowski | dougeby | aaroncz | article | seo-marvel-apr2020 | highpri |
Configure a PXE server to load Windows PE
Applies to
- Windows 10
This walkthrough describes how to configure a PXE server to load Windows PE by booting a client computer from the network. Using the Windows PE tools and a Windows 10 image file, you can install Windows 10 from the network.
Prerequisites
- A deployment computer: A computer with the Windows Assessment and Deployment Kit (Windows ADK) and the Windows PE add-on with ADK installed.
- A DHCP server: A DHCP server or DHCP proxy configured to respond to PXE client requests is required.
- A PXE server: A server running the TFTP service that can host Windows PE boot files that the client will download.
- A file server: A server hosting a network file share.
All four of the roles specified above can be hosted on the same computer or each can be on a separate computer.
Step 1: Copy Windows PE source files
-
On the deployment computer, click Start, and type deployment.
-
Right-click Deployment and Imaging Tools Environment and then click Run as administrator. The Deployment and Imaging Tools Environment shortcut opens a Command Prompt window and automatically sets environment variables to point to all the necessary tools.
-
Run the following command to copy the base Windows PE files into a new folder. The script requires two arguments: hardware architecture and destination location. The value of <architecture> can be x86, amd64, or arm and <destination> is a path to a local directory. If the directory doesn't already exist, it will be created.
copype.cmd <architecture> <destination>For example, the following command copies amd64 architecture files to the C:\winpe_amd64 directory:
copype.cmd amd64 C:\winpe_amd64The script creates the destination directory structure and copies all the necessary files for that architecture. In the previous example, the following directories are created:
C:\winpe_amd64 C:\winpe_amd64\fwfiles C:\winpe_amd64\media C:\winpe_amd64\mount -
Mount the base Windows PE image (winpe.wim) to the \mount directory using the DISM tool. Mounting an image file unpacks the file contents into a folder so that you can make changes directly or by using tools such as DISM. See the following example.
Dism /mount-image /imagefile:c:\winpe_amd64\media\sources\boot.wim /index:1 /mountdir:C:\winpe_amd64\mountVerify that "The operation completed successfully" is displayed. Note: To view currently mounted images, type dism /get-MountedWiminfo.
-
Map a network share to the root TFTP directory on the PXE/TFTP server and create a \Boot folder. Consult your TFTP server documentation to determine the root TFTP server directory, then enable sharing for this directory, and verify it can be accessed on the network. In the following example, the PXE server name is PXE-1 and the TFTP root directory is shared using a network path of \\PXE-1\TFTPRoot:
net use y: \\PXE-1\TFTPRoot y: md Boot -
Copy the PXE boot files from the mounted directory to the \boot folder. For example:
copy c:\winpe_amd64\mount\windows\boot\pxe\*.* y:\Boot -
Copy the boot.sdi file to the PXE/TFTP server.
copy C:\winpe_amd64\media\boot\boot.sdi y:\Boot -
Copy the bootable Windows PE image (boot.wim) to the \boot folder.
copy C:\winpe_amd64\media\sources\boot.wim y:\Boot -
(Optional) Copy true type fonts to the \boot folder
copy C:\winpe_amd64\media\Boot\Fonts y:\Boot\Fonts
Step 2: Configure boot settings and copy the BCD file
-
Create a BCD store using bcdedit.exe:
bcdedit /createstore c:\BCD -
Configure RAMDISK settings:
bcdedit /store c:\BCD /create {ramdiskoptions} /d "Ramdisk options" bcdedit /store c:\BCD /set {ramdiskoptions} ramdisksdidevice boot bcdedit /store c:\BCD /set {ramdiskoptions} ramdisksdipath \Boot\boot.sdi bcdedit /store c:\BCD /create /d "winpe boot image" /application osloaderThe last command will return a GUID, for example:
The entry {a4f89c62-2142-11e6-80b6-00155da04110} was successfully created.Copy this GUID for use in the next set of commands. In each command shown, replace "GUID1" with your GUID.
-
Create a new boot application entry for the Windows PE image:
bcdedit /store c:\BCD /set {GUID1} device ramdisk=[boot]\Boot\boot.wim,{ramdiskoptions} bcdedit /store c:\BCD /set {GUID1} path \windows\system32\winload.exe bcdedit /store c:\BCD /set {GUID1} osdevice ramdisk=[boot]\Boot\boot.wim,{ramdiskoptions} bcdedit /store c:\BCD /set {GUID1} systemroot \windows bcdedit /store c:\BCD /set {GUID1} detecthal Yes bcdedit /store c:\BCD /set {GUID1} winpe Yes -
Configure BOOTMGR settings (remember to replace GUID1 in the third command with your GUID):
bcdedit /store c:\BCD /create {bootmgr} /d "boot manager" bcdedit /store c:\BCD /set {bootmgr} timeout 30 bcdedit /store c:\BCD -displayorder {GUID1} -addlast -
Copy the BCD file to your TFTP server:
copy c:\BCD \\PXE-1\TFTPRoot\Boot\BCD
Your PXE/TFTP server is now configured. You can view the BCD settings that have been configured using the command bcdedit /store <BCD file location> /enum all. See the following example. Note: Your GUID will be different than the one shown below.
C:\>bcdedit /store C:\BCD /enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
description boot manager
displayorder {a4f89c62-2142-11e6-80b6-00155da04110}
timeout 30
Windows Boot Loader
-------------------
identifier {a4f89c62-2142-11e6-80b6-00155da04110}
device ramdisk=[boot]\Boot\boot.wim,{ramdiskoptions}
description winpe boot image
osdevice ramdisk=[boot]\Boot\boot.wim,{ramdiskoptions}
systemroot \Windows
detecthal Yes
winpe Yes
Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description ramdisk options
ramdisksdidevice boot
ramdisksdipath \Boot\boot.sdi
Tip
If you start the PXE boot process, but receive the error that "The boot configuration data for your PC is missing or contains errors" then verify that \boot directory is installed under the correct TFTP server root directory. In the example used here the name of this directory is TFTPRoot, but your TFTP server might be different.
PXE boot process summary
The following process summarizes the PXE client boot.
The following assumes that you have configured DHCP option 67 (Bootfile Name) to "boot\PXEboot.n12" which enables direct boot to PXE with no user interaction. For more information about DHCP options for network boot, see Managing Network Boot Programs.
- A client is directed by DHCP options 066 and 067 to download boot\PXEboot.n12 from the TFTP server.
- PXEboot.n12 immediately begins a network boot.
- The client downloads boot\bootmgr.exe and the boot\BCD file from the TFTP server. Note: The BCD store must reside in the \boot directory on the TFTP server and must be named BCD.
- Bootmgr.exe reads the BCD operating system entries and downloads boot\boot.sdi and the Windows PE image (boot\boot.wim). Optional files that can also be downloaded include true type fonts (boot\Fonts\wgl4_boot.ttf) and the hibernation state file (\hiberfil.sys) if these files are present.
- Bootmgr.exe starts Windows PE by calling winload.exe within the Windows PE image.
- Windows PE loads, a command prompt opens and wpeinit.exe is run to initialize Windows PE.
- The Windows PE client provides access to tools like imagex, diskpart, and bcdboot using the Windows PE command prompt. With the help of these tools accompanied by a Windows 10 image file, the destination computer can be formatted properly to load a full Windows 10 operating system.