deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update Boot Image with CU Article 59

Browse Source
This commit is contained in:
Frank Rojas 2023-08-11 17:37:16 -04:00
parent 6c7ffadf0a
commit 4ba3085c2a
2 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
windows/deployment/TOC.yml
View File

@ -591,3 +591,5 @@
- name: Install fonts in Windows client - name: Install fonts in Windows client
href: windows-10-missing-fonts.md href: windows-10-missing-fonts.md
- name: Customize Windows PE boot images
href: customize-boot-image.md

13
windows/deployment/customize-boot-image.md
View File

@ -663,7 +663,7 @@ In particular, this step is needed when addressing the BlackLotus UEFI bootkit v
> [!NOTE] > [!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 ## 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 Configuration Manager](#updating-the-boot-image-in-configuration-manager)
- [Microsoft Deployment Toolkit (MDT)](#updating-the-boot-image-and-boot-media-in-mdt) - [Microsoft Deployment Toolkit (MDT)](#updating-the-boot-image-and-boot-media-in-mdt)
- Windows Deployment Services - 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. 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 ## Windows Deployment Services (WDS) considerations
### Update boot image and boot files in WDS ### Original WDS boot image is updated
### Boot image in WDS is updated
If the WDS boot image modified was the original WDS boot image in the `<RemoteInstall>` 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: If the WDS boot image modified was the original WDS boot image in the `<RemoteInstall>` 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: 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: In the following boot image scenario for WDS: