deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 10:53:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

added to TOC

Browse Source
This commit is contained in:
Greg Lindsay
2016-06-01 16:29:39 -07:00
parent 60ad78e71f
commit 707e682be8
2 changed files with 71 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
windows/deploy/TOC.md
View File

@ -34,6 +34,7 @@
### [Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
## [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md)
## [Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md)
## [Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md)
## [Windows 10 edition upgrade](windows-10-edition-upgrades.md)
## [Deploy Windows To Go in your organization](deploy-windows-to-go.md)
## [Update Windows 10 images with provisioning packages](update-windows-10-images-with-provisioning-packages.md)

140
windows/deploy/configure-a-pxe-server-to-load-windows-pe.md
View File

@ -1,5 +1,5 @@
---
title: Walkthrough: Configure a PXE server to load Windows PE
title: Walkthrough: Configure a PXE server to load Windows PE (Windows 10)
description: 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.
keywords: windows pe, windows 10, upgrade, deploy, image
ms.prod: w10
@ -19,115 +19,115 @@ This topic describes how to configure a PXE server to load Windows PE so that
## Prerequisites
- Deployment computer: A computer with the Windows Assessment and Deployment Kit (Windows ADK) installed (<https://www.microsoft.com/en-us/download/details.aspx?id=39982>).
- DHCP server: A DHCP server or DHCP proxy configured to respond to PXE client requests.
- PXE server: A server running the TFTP server service.
- File server: A server hosting a network file share.
- A deployment computer: A computer with the [Windows Assessment and Deployment Kit](https://www.microsoft.com/en-us/download/details.aspx?id=39982) (Windows 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 if desired, but this is not required.
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 to the PXE server
## Step 1: Copy Windows PE source files from the deployment computer to the PXE server
### To copy source files to your PXE server:
### To copy source files to the PXE server:
1. On the deployment computer, click **Start**, and type **deployment**.
2. 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.
3. 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.
```
copype.cmd <arch> <destination>
```
```
copype.cmd <arch> <destination>
```
The value of &lt;arch&gt; can be **x86**, **amd64**, or **arm** and &lt;destination&gt; is a path to a local directory. If the directory does not already exist, it will be created. For example:
The value of **&lt;arch&gt;** can be **x86**, **amd64**, or **arm** and **&lt;destination&gt;** is a path to a local directory. If the directory does not already exist, it will be created. For example, the following command copies **amd64** architecture files to the **C:\winpe_amd64** directory:
```
copype.cmd amd64 C:\\winpe\_amd64
```
```
copype.cmd amd64 C:\winpe_amd64
```
The script creates the destination directory structure and copies all the necessary files for that architecture. For example:
The 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
C:\\winpe\_amd64
C:\\winpe\_amd64\\fwfiles
C:\\winpe\_amd64\\media
C:\\winpe\_amd64\\mount
4. 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. To mount the image file, run the following command. Replace the directory names with the directory name that you used in the previous step.
4. 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\mount
```
```
Dism /mount-image /imagefile:c:\winpe_amd64\media\sources\boot.wim /index:1 /mountdir:C:\winpe_amd64\mount
```
5.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, enable sharing 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. See the following example:
5. 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
```
```
net use y: \\PXE-1\TFTPRoot
y:
md boot
```
6. Copy the PXE boot files from the mounted directory to the \\Boot folder. For example,
6. 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 c:\winpe_amd64\mount\windows\boot\pxe\*.* y:\boot
```
7. Copy the boot.sdi file to the PXE/TFTP server.
```
copy C:\winpe_amd64\media\boot\boot.sdi y:\boot
```
```
copy C:\winpe_amd64\media\boot\boot.sdi y:\boot
```
8. Copy the bootable Windows PE image (boot.wim) to the \\Boot folder.
8. Copy the bootable Windows PE image (boot.wim) to the \Boot folder.
```
copy C:\winpe_amd64\media\sources\boot.wim y:\boot
```
```
copy C:\winpe_amd64\media\sources\boot.wim y:\boot
```
## Step 2: Configure boot settings and copy the BCD file
### To configure boot settings:
1. Create a BCD store using bcdedit.exe. For example:
1. Create a BCD store using bcdedit.exe:
```
bcdedit /createstore c:\BCD
```
```
bcdedit /createstore c:\BCD
```
2. Configure RAMDISK settings. See the following example:
2. Configure RAMDISK settings:
```
bcdedit /store c:\BCD /create {ramdiskoptions} /d "Ramdisk options"
bcdedit /store c:\BCD /set {ramdiskoptions} ramdisksdidevice partition=C:
bcdedit /store c:\BCD /set {ramdiskoptions} ramdisksdipath \winpe_amd64\media\boot\boot.sdi
```
```
bcdedit /store c:\BCD /create {ramdiskoptions} /d "Ramdisk options"
bcdedit /store c:\BCD /set {ramdiskoptions} ramdisksdidevice partition=C:
bcdedit /store c:\BCD /set {ramdiskoptions} ramdisksdipath \winpe_amd64\media\boot\boot.sdi
```
3. Create a new boot application entry for the Windows PE image. See the following example:
3. Create a new boot application entry for the Windows PE image:
```
bcdedit /store c:\BCD /set {GUID1} device ramdisk=[c:]\winpe_amd64\media\sources\boot.wim,{ramdiskoptions}
bcdedit /store c:\BCD /set {GUID1} path \windows\system32\winload.exe
bcdedit /store c:\BCD /set {GUID1} osdevice ramdisk=[c:]\winpe_amd64\media\sources\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
```
```
bcdedit /store c:\BCD /set {GUID1} device ramdisk=[c:]\winpe_amd64\media\sources\boot.wim,{ramdiskoptions}
bcdedit /store c:\BCD /set {GUID1} path \windows\system32\winload.exe
bcdedit /store c:\BCD /set {GUID1} osdevice ramdisk=[c:]\winpe_amd64\media\sources\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
```
4. Configure BOOTMGR settings. See the following example:
4. Configure BOOTMGR settings:
```
bcdedit /store c:\BCD /set {bootmgr} timeout 30
bcdedit /store c:\BCD -displayorder {GUID1} -addlast
```
```
bcdedit /store c:\BCD /set {bootmgr} timeout 30
bcdedit /store c:\BCD -displayorder {GUID1} -addlast
```
5. Copy the BCD file to your TFTP server. For example,
5. Copy the BCD file to your TFTP server:
```
copy c:\BCD \\PXE-1\TFTPRoot\Boot
```
```
copy c:\BCD \\PXE-1\TFTPRoot\Boot
```
Your PXE/TFTP server is now configured.
Note: You can view the BCD settings that have been configured using the command “bcdedit /store &lt;BCD file location&gt; /enum all. See the following example:
Note: You can view the BCD settings that have been configured using the command **“bcdedit /store &lt;BCD file location&gt; /enum all**:
```
C:\>bcdedit /store C:\BCD /enum all