From a60787240326ce3167979755b65de681db40bb07 Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Wed, 1 Jun 2016 11:02:07 -0700 Subject: [PATCH 1/7] editing change history --- .../manage/change-history-for-manage-and-update-windows-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index df398cfd27..3035b4bb6c 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -17,7 +17,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in | New or changed topic | Description | | ---|---| | [Group Policies that apply only to Windows 10 Enterprise and Education Editions](group-policies-for-enterprise-and-education-editions.md) | New | -| [Configure Windows 10 devices to stop data flow to Microsoft](configure-windows-10-devices-to-stop-data-flow-to-microsoft.md) | Added section on how to turn off Live Tiles | +| [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md) | Added section on how to turn off Live Tiles | | [Configure Windows telemetry in your organization](configure-windows-telemetry-in-your-organization.md) | New telemetry content | | [Manage Wi-Fi Sense in your company](manage-wifi-sense-in-enterprise.md) |Removed info about sharing wi-fi network access with contacts, since it's been deprecated. | | [Set up a kiosk on Windows 10 Pro, Enterprise, or Education](set-up-a-kiosk-for-windows-10-for-desktop-editions.md) | Corrected script for setting a custom shell using Shell Launcher | From e0e1891fdde9bb3324d29d8f14b0739402ccfb37 Mon Sep 17 00:00:00 2001 From: Trudy Hakala Date: Wed, 1 Jun 2016 12:51:18 -0700 Subject: [PATCH 2/7] space error --- devices/surface-hub/use-room-control-system-with-surface-hub.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/surface-hub/use-room-control-system-with-surface-hub.md b/devices/surface-hub/use-room-control-system-with-surface-hub.md index e3971aa2c6..447edd18aa 100644 --- a/devices/surface-hub/use-room-control-system-with-surface-hub.md +++ b/devices/surface-hub/use-room-control-system-with-surface-hub.md @@ -62,7 +62,7 @@ To connect to a room control system control panel, you don't need to configure a You can use a standard RJ-11 (6P6C) connector to connect the Surface Hub serial port to a room control system. This is the recommended method. You can also use an RJ-11 4-conductor cable, but we do not recommend this method. -This diagram shows the correct pinout usedfor an RJ-11 (6P6C) to DB9 cable. +This diagram shows the correct pinout used for an RJ-11 (6P6C) to DB9 cable. ![image showing the wiring diagram.](images/room-control-wiring-diagram.png) From 0d7d697908da8a424fccd21a958def0662b41342 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 1 Jun 2016 13:56:33 -0700 Subject: [PATCH 3/7] minor edits --- windows/deploy/upgrade-windows-phone-8-1-to-10.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deploy/upgrade-windows-phone-8-1-to-10.md b/windows/deploy/upgrade-windows-phone-8-1-to-10.md index 4a59de5fa9..c2e678923a 100644 --- a/windows/deploy/upgrade-windows-phone-8-1-to-10.md +++ b/windows/deploy/upgrade-windows-phone-8-1-to-10.md @@ -55,7 +55,7 @@ SyncML xmlns="SYNCML:SYNCML1.1"> 250 - ./Vendor/MSFT/Registry/HKLM/SOFTWARE/Microsoft/Provisioning/OMADM/ EnterpriseUpgrade + ./Vendor/MSFT/Registry/HKLM/SOFTWARE/Microsoft/Provisioning/OMADM/EnterpriseUpgrade chr @@ -91,7 +91,7 @@ Note: The availability of Windows 10 Mobile as an update for existing Windows Ph ### How to blacklist the Upgrade Advisor app -Some enterprises may want to block their users from installing the Windows 10 Mobile Upgrade Advisor app. With Windows Phone 8.1, you can allow or deny individual apps by adding specific app publishers or the app globally unique identifier (GUID) from the Window Phone Store to an allow or deny XML list. The GUID for a particular application can be found in the URL for the app in the phone store. For example, the GUID to the Windows Phone Upgrade Adviser (fbe47e4f-7769-4103-910e-dca8c43e0b07) is displayed in the following URL: +Some enterprises may want to block their users from installing the Windows 10 Mobile Upgrade Advisor app. With Windows Phone 8.1, you can allow or deny individual apps by adding specific app publishers or the app globally unique identifier (GUID) from the Window Phone Store to an allow or deny XML list. The GUID for a particular application can be found in the URL for the app in the phone store. For example, the GUID to the Windows 10 Mobile Upgrade Adviser (fbe47e4f-7769-4103-910e-dca8c43e0b07) is displayed in the following URL: http://windowsphone.com/s?appid=fbe47e4f-7769-4103-910e-dca8c43e0b07 From 60ad78e71f336e6071e309ffd2a511c1a1c25edc Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 1 Jun 2016 15:37:35 -0700 Subject: [PATCH 4/7] checking new topic --- ...nfigure-a-pxe-server-to-load-windows-pe.md | 177 ++++++++++++++++++ 1 file changed, 177 insertions(+) create mode 100644 windows/deploy/configure-a-pxe-server-to-load-windows-pe.md diff --git a/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md b/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md new file mode 100644 index 0000000000..e174209ece --- /dev/null +++ b/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md @@ -0,0 +1,177 @@ +--- +title: Walkthrough: Configure a PXE server to load Windows PE +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 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.pagetype: deployment +author: greg-lindsay +--- + +# Walkthrough: Configure a PXE server to load Windows PE + +**Applies to** + +- 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. + +## Prerequisites + +- Deployment computer: A computer with the Windows Assessment and Deployment Kit (Windows ADK) installed (). +- 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. + +All four of the roles specified above can be hosted on the same computer if desired, but this is not required. + +## Step 1: Copy Windows PE source files to the PXE server + +### To copy source files to your 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 +``` + +The value of <arch> can be **x86**, **amd64**, or **arm** and <destination> is a path to a local directory. If the directory does not already exist, it will be created. For example: + +``` +copype.cmd amd64 C:\\winpe\_amd64 +``` + +The script creates the destination directory structure and copies all the necessary files for that architecture. For example: + +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. + +``` +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: + +``` +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, + +``` +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 +``` + +8. Copy the bootable Windows PE image (boot.wim) to the \\Boot folder. + +``` +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: + +``` +bcdedit /createstore c:\BCD +``` + +2. Configure RAMDISK settings. See the following example: + +``` +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: + +``` +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: + +``` +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, + +``` +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 <BCD file location> /enum all. See the following example: + +``` +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 +``` + +#### The deployment process + +The following summarizes the PXE client boot process. + +1. A client is directed by DHCP options 066 and 067 to download boot\\wdsnbp.com from the TFTP server. +2. Wdsnbp.com validates the DHCP/PXE response packet and then the client downloads boot\\pxeboot.com. +3. Pxeboot.com requires the client to press the F12 key to initiate a PXE boot. +4. 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. +5. 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. +6. Bootmgr.exe starts Windows PE by calling winload.exe within the Windows PE image. +7. Windows PE loads, a command prompt opens and wpeinit.exe is run to initialize Windows PE. +8. The Windows PE client provides access to tools like imagex, diskpart, and bcdboot using the Windows PE command prompt. Using these tools together with a Windows 10 image file, the destination computer can be formatted properly to load a full Windows 10 operating system. + +See Also +--------- + +#### Concepts + +[Windows PE Walkthroughs](https://technet.microsoft.com/en-us/library/cc748899.aspx) \ No newline at end of file From 707e682be8307696804ce89d2a5f57e4b27c96a9 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 1 Jun 2016 16:29:39 -0700 Subject: [PATCH 5/7] added to TOC --- windows/deploy/TOC.md | 1 + ...nfigure-a-pxe-server-to-load-windows-pe.md | 140 +++++++++--------- 2 files changed, 71 insertions(+), 70 deletions(-) diff --git a/windows/deploy/TOC.md b/windows/deploy/TOC.md index d0819639d7..cc0388e935 100644 --- a/windows/deploy/TOC.md +++ b/windows/deploy/TOC.md @@ -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) diff --git a/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md b/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md index e174209ece..0d9b9332db 100644 --- a/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md +++ b/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md @@ -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 (). -- 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 -``` + ``` + copype.cmd + ``` -The value of <arch> can be **x86**, **amd64**, or **arm** and <destination> is a path to a local directory. If the directory does not already exist, it will be created. For example: + The value of **<arch>** can be **x86**, **amd64**, or **arm** and **<destination>** 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 <BCD file location> /enum all. See the following example: +Note: You can view the BCD settings that have been configured using the command **“bcdedit /store <BCD file location> /enum all**: ``` C:\>bcdedit /store C:\BCD /enum all From 002c324c72820439ed945e405db99dbec5990c21 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 1 Jun 2016 17:00:00 -0700 Subject: [PATCH 6/7] several edits --- .../change-history-for-deploy-windows-10.md | 10 +++++++ ...nfigure-a-pxe-server-to-load-windows-pe.md | 30 +++++++++---------- .../deploy/upgrade-windows-phone-8-1-to-10.md | 2 +- 3 files changed, 25 insertions(+), 17 deletions(-) diff --git a/windows/deploy/change-history-for-deploy-windows-10.md b/windows/deploy/change-history-for-deploy-windows-10.md index 00404f4def..ef6b329f37 100644 --- a/windows/deploy/change-history-for-deploy-windows-10.md +++ b/windows/deploy/change-history-for-deploy-windows-10.md @@ -11,6 +11,16 @@ author: greg-lindsay # Change history for Deploy Windows 10 This topic lists new and updated topics in the [Deploy Windows 10](index.md) documentation for [Windows 10 and Windows 10 Mobile](../index.md). +## June 2016 +| New or changed topic | Description | +|----------------------|-------------| +| [Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md) | New | + +## May 2016 +| New or changed topic | Description | +|----------------------|-------------| +| [Upgrade a Windows Phone 8.1 to Windows 10 Mobile with Mobile Device Management](upgrade-windows-phone-8-1-to-10.md) | New | + ## December 2015 | New or changed topic | Description | |----------------------|-------------| diff --git a/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md b/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md index 0d9b9332db..3c8d7acd2a 100644 --- a/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md +++ b/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md @@ -1,21 +1,23 @@ --- -title: Walkthrough: Configure a PXE server to load Windows PE (Windows 10) +title: 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 +keywords: upgrade, update, windows, windows 10, pxe, WinPE, image, wim ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library -ms.pagetype: deployment +ms.pagetype: deploy author: greg-lindsay --- -# Walkthrough: Configure a PXE server to load Windows PE +# Configure a PXE server to load Windows PE **Applies to** - 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. +## Summary + +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 @@ -26,19 +28,19 @@ This topic describes how to configure a PXE server to load Windows PE so that 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 from the deployment computer to the PXE server - -### To copy source files to the PXE server: +## Step 1: Copy Windows PE source files 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. + +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. The value of **<architecture>** can be **x86**, **amd64**, or **arm** and **<destination>** is a path to a local directory. If the directory does not already exist, it will be created. ``` - copype.cmd + copype.cmd ``` - The value of **<arch>** can be **x86**, **amd64**, or **arm** and **<destination>** 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: + For example, the following command copies **amd64** architecture files to the **C:\winpe_amd64** directory: ``` copype.cmd amd64 C:\winpe_amd64 @@ -85,8 +87,6 @@ All four of the roles specified above can be hosted on the same computer or each ## Step 2: Configure boot settings and copy the BCD file -### To configure boot settings: - 1. Create a BCD store using bcdedit.exe: ``` @@ -125,9 +125,7 @@ All four of the roles specified above can be hosted on the same computer or each 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 <BCD file location> /enum all**: +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: ``` C:\>bcdedit /store C:\BCD /enum all diff --git a/windows/deploy/upgrade-windows-phone-8-1-to-10.md b/windows/deploy/upgrade-windows-phone-8-1-to-10.md index c2e678923a..f79c20d4ba 100644 --- a/windows/deploy/upgrade-windows-phone-8-1-to-10.md +++ b/windows/deploy/upgrade-windows-phone-8-1-to-10.md @@ -6,7 +6,7 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: mdt -author: greg-lindsay +author: Jamiejdt --- # Upgrade a Windows Phone 8.1 to Windows 10 Mobile with Mobile Device Management (MDM) From 0638414cca87e1f45f62e9b6fe1fa1c8482cecd0 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 1 Jun 2016 17:18:18 -0700 Subject: [PATCH 7/7] minor fixes --- ...configure-a-pxe-server-to-load-windows-pe.md | 17 +++++------------ 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md b/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md index 3c8d7acd2a..164be99f99 100644 --- a/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md +++ b/windows/deploy/configure-a-pxe-server-to-load-windows-pe.md @@ -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: - + + ``` 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. See the following example. ``` 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: ``` @@ -66,19 +66,16 @@ All four of the roles specified above can be hosted on the same computer or each y: md boot ``` - 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 ``` - 7. Copy the boot.sdi file to the PXE/TFTP server. ``` copy C:\winpe_amd64\media\boot\boot.sdi y:\boot ``` - 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 ``` - 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} ramdisksdipath \winpe_amd64\media\boot\boot.sdi ``` - 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} winpe Yes ``` - 4. Configure BOOTMGR settings: ``` bcdedit /store c:\BCD /set {bootmgr} timeout 30 bcdedit /store c:\BCD -displayorder {GUID1} -addlast ``` - 5. Copy the BCD file to your TFTP server: ``` 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 @@ -154,7 +147,7 @@ ramdisksdidevice boot ramdisksdipath \boot\boot.sdi ``` -#### The deployment process +## PXE boot summary The following summarizes the PXE client boot process.