From 4ba3085c2a915dd0979a01f91e59ccda3f261436 Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Fri, 11 Aug 2023 17:37:16 -0400 Subject: [PATCH] Update Boot Image with CU Article 59 --- windows/deployment/TOC.yml | 2 ++ windows/deployment/customize-boot-image.md | 13 +++++++------ 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index 20d9752fdf..b8da7a6027 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -591,3 +591,5 @@ - name: Install fonts in Windows client href: windows-10-missing-fonts.md + - name: Customize Windows PE boot images + href: customize-boot-image.md diff --git a/windows/deployment/customize-boot-image.md b/windows/deployment/customize-boot-image.md index 64a27ccf8e..deed6bd549 100644 --- a/windows/deployment/customize-boot-image.md +++ b/windows/deployment/customize-boot-image.md @@ -663,7 +663,7 @@ In particular, this step is needed when addressing the BlackLotus UEFI bootkit v > [!NOTE] > -> **Microsoft Configuration Manager** automatically extracts these bootmgr boot files from the boot images as needed. No additional steps are needed for **Microsoft Configuration Manager**. +> **Microsoft Configuration Manager** and **Windows Deployment Services (WDS)** automatically extract the bootmgr boot files from the boot images when the boot images are updated in these products. They don't use the bootmgr boot files from the Windows ADK. ## Step 9: Perform component cleanup @@ -906,6 +906,9 @@ After the default `winpe.wim` boot image from the Windows ADK has been updated, - [Microsoft Configuration Manager](#updating-the-boot-image-in-configuration-manager) - [Microsoft Deployment Toolkit (MDT)](#updating-the-boot-image-and-boot-media-in-mdt) - Windows Deployment Services + - [Original WDS boot image is updated](#original-wds-boot-image-is-updated) + - [WDS boot image is replaced with new updated boot image](#wds-boot-image-is-replaced-with-new-updated-boot-image) + - [Add updated boot image as a new boot image in WDS](#add-updated-boot-image-as-a-new-boot-image-in-wds) For any other products that utilize boot images, consult the product's documentation on updating the boot image. @@ -1070,9 +1073,7 @@ These steps also update the MDT boot media in the MDT Deployment Share. After fo ## Windows Deployment Services (WDS) considerations -### Update boot image and boot files in WDS - -### Boot image in WDS is updated +### Original WDS boot image is updated If the WDS boot image modified was the original WDS boot image in the `` folder, then the only additional step to take is to restart `Windows Deployment Services Server` service. WDS can be restarted by using the following command lines: @@ -1106,7 +1107,7 @@ For more information, see [wdsutil stop-server](/windows-server/administration/w --- -### Existing boot image in WDS is updated with a new update boot image +### WDS boot image is replaced with new updated boot image In the following boot image replacement scenario for WDS: @@ -1185,7 +1186,7 @@ then follow these steps to update the boot image in WDS: --- -### Updated boot image is added as a new boot image in WDS +### Add updated boot image as a new boot image in WDS In the following boot image scenario for WDS: