deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-29 05:37:22 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

minor fixes

Browse Source
This commit is contained in:
Greg Lindsay 2016-06-01 17:18:18 -07:00
parent 002c324c72
commit 0638414cca
1 changed files with 5 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -47,18 +47,18 @@ All four of the roles specified above can be hosted on the same computer or each
``` ```
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: 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
C:\\winpe\_amd64\\fwfiles C:\\winpe\_amd64\\fwfiles
C:\\winpe\_amd64\\media C:\\winpe\_amd64\\media
C:\\winpe\_amd64\\mount 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. See the following example. 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, 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: 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:
``` ```
@ -66,19 +66,16 @@ All four of the roles specified above can be hosted on the same computer or each
y: y:
md boot 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. 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.
``` ```
@ -92,7 +89,6 @@ All four of the roles specified above can be hosted on the same computer or each
``` ```
bcdedit /createstore c:\BCD bcdedit /createstore c:\BCD
``` ```
2. Configure RAMDISK settings: 2. Configure RAMDISK settings:
``` ```
@ -100,7 +96,6 @@ All four of the roles specified above can be hosted on the same computer or each
bcdedit /store c:\BCD /set {ramdiskoptions} ramdisksdidevice partition=C: 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 /set {ramdiskoptions} ramdisksdipath \winpe_amd64\media\boot\boot.sdi
``` ```
3. Create a new boot application entry for the Windows PE image: 3. Create a new boot application entry for the Windows PE image:
``` ```
@ -111,21 +106,19 @@ All four of the roles specified above can be hosted on the same computer or each
bcdedit /store c:\BCD /set {GUID1} detecthal Yes bcdedit /store c:\BCD /set {GUID1} detecthal Yes
bcdedit /store c:\BCD /set {GUID1} winpe Yes bcdedit /store c:\BCD /set {GUID1} winpe Yes
``` ```
4. Configure BOOTMGR settings: 4. Configure BOOTMGR settings:
``` ```
bcdedit /store c:\BCD /set {bootmgr} timeout 30 bcdedit /store c:\BCD /set {bootmgr} timeout 30
bcdedit /store c:\BCD -displayorder {GUID1} -addlast bcdedit /store c:\BCD -displayorder {GUID1} -addlast
``` ```
5. Copy the BCD file to your TFTP server: 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. You can view the BCD settings that have been configured using the command “bcdedit /store <BCD file location> /enum all. See the following example: 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. The GUID displayed below is an example and your GUID will be different:
``` ```
C:\>bcdedit /store C:\BCD /enum all C:\>bcdedit /store C:\BCD /enum all
@ -154,7 +147,7 @@ ramdisksdidevice boot
ramdisksdipath \boot\boot.sdi ramdisksdipath \boot\boot.sdi
``` ```
#### The deployment process ## PXE boot summary
The following summarizes the PXE client boot process. The following summarizes the PXE client boot process.