From 60267c8c55fec6b33de8890cb136401ea6913727 Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Fri, 1 Sep 2023 18:19:03 -0400 Subject: [PATCH 1/3] Fixing a few minor problems in article --- windows/deployment/customize-boot-image.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/windows/deployment/customize-boot-image.md b/windows/deployment/customize-boot-image.md index a72e0b1d1d..aa9abc46c2 100644 --- a/windows/deployment/customize-boot-image.md +++ b/windows/deployment/customize-boot-image.md @@ -840,7 +840,7 @@ For more information, see [Modify a Windows image using DISM: Unmounting an imag **Example**: ```powershell - Remove-Item - Path "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim" -Force + Remove-Item -Path "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim" -Force ``` For more information, see [Remove-Item](/powershell/module/microsoft.powershell.management/remove-item). @@ -1154,7 +1154,7 @@ then follow these steps to update the boot image in WDS: --- -2. Once the existing boot image in WDS has been replaced, restart the WDS service: +1. Once the existing boot image in WDS has been replaced, restart the WDS service: #### [:::image type="icon" source="images/icons/powershell-18.svg"::: **PowerShell**](#tab/powershell) @@ -1233,7 +1233,7 @@ then follow these steps to add the boot image in WDS: --- -2. Once the existing boot image in WDS has been replaced, restart the WDS service: +1. Once the existing boot image in WDS has been replaced, restart the WDS service: #### [:::image type="icon" source="images/icons/powershell-18.svg"::: **PowerShell**](#tab/powershell) @@ -1271,7 +1271,12 @@ The **boot.wim** that is part of Windows installation media isn't supported for ## Windows Server 2012 R2 -This walk-through isn't intended for use with Windows Server 2012 R2. Although the steps in this article may work with Windows Server 2012 R2 when using older versions of the Windows ADK. However it may have compatibility problems with versions of the Windows ADK that are newer than the [ADK for Windows 10, version 2004](/windows-hardware/get-started/adk-install#other-adk-downloads). For server OSes, it's recommended to use Windows Server 2016 or later for this walk-through. For more information, see [Windows Server 2012 R2 Lifecycle](/lifecycle/products/windows-server-2012-r2). +This walk-through isn't intended for use with Windows Server 2012 R2. The steps in this article may work with Windows Server 2012 R2 when using older versions of the Windows ADK. However, it may have compatibility problems with versions of the Windows ADK that are newer than the [ADK for Windows 10, version 2004](/windows-hardware/get-started/adk-install#other-adk-downloads). To resolve compatibility problems with newer ADKs and Windows Server 2012 R2: + +1. Upgrade Windows Server 2012 R2 to a newer version of Windows Server. +1. Perform the boot image customizations on a computer running a version of Windows that supports the newer ADKs, for example Windows 10 or Windows 11, and then transfer the modified boot image to the Windows Server 2012 R2 server. + +For more information, see [Windows Server 2012 R2 Lifecycle](/lifecycle/products/windows-server-2012-r2). ## Related articles From d6eeb9c80148e20f432371036a3e9e752d842fe0 Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Fri, 1 Sep 2023 18:19:27 -0400 Subject: [PATCH 2/3] Fixing a few minor problems in article 2 --- windows/deployment/customize-boot-image.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/customize-boot-image.md b/windows/deployment/customize-boot-image.md index aa9abc46c2..ea6d4877c9 100644 --- a/windows/deployment/customize-boot-image.md +++ b/windows/deployment/customize-boot-image.md @@ -7,7 +7,7 @@ author: frankroj manager: aaroncz ms.author: frankroj ms.topic: article -ms.date: 08/22/2023 +ms.date: 09/01/2023 ms.technology: itpro-deploy appliesto: - ✅ Windows 11 From f2ebc96adeea101063a97203cc853307178c2828 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Fri, 1 Sep 2023 16:29:18 -0700 Subject: [PATCH 3/3] Correct legitimate errors reported by Acrolinx https://microsoft-ce-csi.acrolinx.cloud/api/v1/checking/scorecards/58e283cf-bcab-45b4-b4f5-225500b0cda4#CORRECTNESS --- windows/deployment/customize-boot-image.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/customize-boot-image.md b/windows/deployment/customize-boot-image.md index ea6d4877c9..ddbe6a4d7d 100644 --- a/windows/deployment/customize-boot-image.md +++ b/windows/deployment/customize-boot-image.md @@ -108,7 +108,7 @@ Before modifying the desired boot image, make a backup copy of the boot image th Adjust the above paths for 32-bit boot images (only available with Windows 10 ADKs). -The following commands backs up the 64-bit boot image included with the **Windows PE add-on for the Windows ADK**: +The following command backs up the 64-bit boot image included with the **Windows PE add-on for the Windows ADK**: ### [:::image type="icon" source="images/icons/powershell-18.svg"::: **PowerShell**](#tab/powershell) From an elevated **PowerShell** command prompt, run the following command to create a backup copy of the 64-bit boot image included with the Windows ADK. If a backed-up boot image already exists, this command needs confirmation before it overwrites the existing backed up boot image: @@ -1019,7 +1019,7 @@ This process updates the boot image used by Configuration Manager. It also updat ### Updating Configuration Manager boot media -After completing the walkthrough, including updating boot images in Configuration Manager, update any Configuration Manager task sequence media. Updating any Configuration Manager task sequence media ensures that the task sequence media has both the updated boot image. If applicable, it will also updat bootmgr boot files on the media by extracting the latest versions from the boot image. For more information on creating Configuration Manager task sequence media, see [Create task sequence media](/mem/configmgr/osd/deploy-use/create-task-sequence-media). +After completing the walkthrough, including updating boot images in Configuration Manager, update any Configuration Manager task sequence media. Updating any Configuration Manager task sequence media ensures that the task sequence media has both the updated boot image. If applicable, it will also update bootmgr boot files on the media by extracting the latest versions from the boot image. For more information on creating Configuration Manager task sequence media, see [Create task sequence media](/mem/configmgr/osd/deploy-use/create-task-sequence-media). ## Microsoft Deployment Toolkit (MDT) considerations