mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-21 13:23:36 +00:00
Merge branch 'master' into PubOps-repo-health
This commit is contained in:
Thomas Raya
GitHub
@ -273,7 +273,7 @@
|
||||
href: upgrade/windows-10-upgrade-paths.md
|
||||
- name: Deploy Windows 10 with Microsoft 365
|
||||
href: deploy-m365.md
|
||||
- name: Understanding the Unified Update Platform
|
||||
- name: Understand the Unified Update Platform
|
||||
href: update/windows-update-overview.md
|
||||
- name: Servicing stack updates
|
||||
href: update/servicing-stack-updates.md
|
||||
@ -321,57 +321,69 @@
|
||||
- name: Active Directory-Based Activation Overview
|
||||
href: volume-activation/active-directory-based-activation-overview.md
|
||||
- name: Install and Configure VAMT
|
||||
href: volume-activation/install-configure-vamt.md
|
||||
- name: VAMT Requirements
|
||||
href: volume-activation/vamt-requirements.md
|
||||
- name: Install VAMT
|
||||
href: volume-activation/install-vamt.md
|
||||
- name: Configure Client Computers
|
||||
href: volume-activation/configure-client-computers-vamt.md
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/install-configure-vamt.md
|
||||
- name: VAMT Requirements
|
||||
href: volume-activation/vamt-requirements.md
|
||||
- name: Install VAMT
|
||||
href: volume-activation/install-vamt.md
|
||||
- name: Configure Client Computers
|
||||
href: volume-activation/configure-client-computers-vamt.md
|
||||
- name: Add and Manage Products
|
||||
href: volume-activation/add-manage-products-vamt.md
|
||||
- name: Add and Remove Computers
|
||||
href: volume-activation/add-remove-computers-vamt.md
|
||||
- name: Update Product Status
|
||||
href: volume-activation/update-product-status-vamt.md
|
||||
- name: Remove Products
|
||||
href: volume-activation/remove-products-vamt.md
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/add-manage-products-vamt.md
|
||||
- name: Add and Remove Computers
|
||||
href: volume-activation/add-remove-computers-vamt.md
|
||||
- name: Update Product Status
|
||||
href: volume-activation/update-product-status-vamt.md
|
||||
- name: Remove Products
|
||||
href: volume-activation/remove-products-vamt.md
|
||||
- name: Manage Product Keys
|
||||
href: volume-activation/manage-product-keys-vamt.md
|
||||
- name: Add and Remove a Product Key
|
||||
href: volume-activation/add-remove-product-key-vamt.md
|
||||
- name: Install a Product Key
|
||||
href: volume-activation/install-product-key-vamt.md
|
||||
- name: Install a KMS Client Key
|
||||
href: volume-activation/install-kms-client-key-vamt.md
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/manage-product-keys-vamt.md
|
||||
- name: Add and Remove a Product Key
|
||||
href: volume-activation/add-remove-product-key-vamt.md
|
||||
- name: Install a Product Key
|
||||
href: volume-activation/install-product-key-vamt.md
|
||||
- name: Install a KMS Client Key
|
||||
href: volume-activation/install-kms-client-key-vamt.md
|
||||
- name: Manage Activations
|
||||
href: volume-activation/manage-activations-vamt.md
|
||||
- name: Perform Online Activation
|
||||
href: volume-activation/online-activation-vamt.md
|
||||
- name: Perform Proxy Activation
|
||||
href: volume-activation/proxy-activation-vamt.md
|
||||
- name: Perform KMS Activation
|
||||
href: volume-activation/kms-activation-vamt.md
|
||||
- name: Perform Local Reactivation
|
||||
href: volume-activation/local-reactivation-vamt.md
|
||||
- name: Activate an Active Directory Forest Online
|
||||
href: volume-activation/activate-forest-vamt.md
|
||||
- name: Activate by Proxy an Active Directory Forest
|
||||
href: volume-activation/activate-forest-by-proxy-vamt.md
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/manage-activations-vamt.md
|
||||
- name: Run Online Activation
|
||||
href: volume-activation/online-activation-vamt.md
|
||||
- name: Run Proxy Activation
|
||||
href: volume-activation/proxy-activation-vamt.md
|
||||
- name: Run KMS Activation
|
||||
href: volume-activation/kms-activation-vamt.md
|
||||
- name: Run Local Reactivation
|
||||
href: volume-activation/local-reactivation-vamt.md
|
||||
- name: Activate an Active Directory Forest Online
|
||||
href: volume-activation/activate-forest-vamt.md
|
||||
- name: Activate by Proxy an Active Directory Forest
|
||||
href: volume-activation/activate-forest-by-proxy-vamt.md
|
||||
- name: Manage VAMT Data
|
||||
href: volume-activation/manage-vamt-data.md
|
||||
- name: Import and Export VAMT Data
|
||||
href: volume-activation/import-export-vamt-data.md
|
||||
- name: Use VAMT in Windows PowerShell
|
||||
href: volume-activation/use-vamt-in-windows-powershell.md
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/manage-vamt-data.md
|
||||
- name: Import and Export VAMT Data
|
||||
href: volume-activation/import-export-vamt-data.md
|
||||
- name: Use VAMT in Windows PowerShell
|
||||
href: volume-activation/use-vamt-in-windows-powershell.md
|
||||
- name: VAMT Step-by-Step Scenarios
|
||||
href: volume-activation/vamt-step-by-step.md
|
||||
- name: "Scenario 1: Online Activation"
|
||||
href: volume-activation/scenario-online-activation-vamt.md
|
||||
- name: "Scenario 2: Proxy Activation"
|
||||
href: volume-activation/scenario-proxy-activation-vamt.md
|
||||
- name: "Scenario 3: KMS Client Activation"
|
||||
href: volume-activation/scenario-kms-activation-vamt.md
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/vamt-step-by-step.md
|
||||
- name: "Scenario 1: Online Activation"
|
||||
href: volume-activation/scenario-online-activation-vamt.md
|
||||
- name: "Scenario 2: Proxy Activation"
|
||||
href: volume-activation/scenario-proxy-activation-vamt.md
|
||||
- name: "Scenario 3: KMS Client Activation"
|
||||
href: volume-activation/scenario-kms-activation-vamt.md
|
||||
- name: VAMT Known Issues
|
||||
href: volume-activation/vamt-known-issues.md
|
||||
|
||||
@ -486,67 +498,75 @@
|
||||
- name: Application Compatibility Toolkit (ACT) Technical Reference
|
||||
items:
|
||||
- name: SUA User's Guide
|
||||
href: planning/sua-users-guide.md
|
||||
- name: Using the SUA Wizard
|
||||
href: planning/using-the-sua-wizard.md
|
||||
- name: Using the SUA Tool
|
||||
href: planning/using-the-sua-tool.md
|
||||
- name: Tabs on the SUA Tool Interface
|
||||
href: planning/tabs-on-the-sua-tool-interface.md
|
||||
- name: Showing Messages Generated by the SUA Tool
|
||||
href: planning/showing-messages-generated-by-the-sua-tool.md
|
||||
- name: Applying Filters to Data in the SUA Tool
|
||||
href: planning/applying-filters-to-data-in-the-sua-tool.md
|
||||
- name: Fixing Applications by Using the SUA Tool
|
||||
href: planning/fixing-applications-by-using-the-sua-tool.md
|
||||
items:
|
||||
- name: Overview
|
||||
href: planning/sua-users-guide.md
|
||||
- name: Use the SUA Wizard
|
||||
href: planning/using-the-sua-wizard.md
|
||||
- name: Use the SUA Tool
|
||||
href: planning/using-the-sua-tool.md
|
||||
- name: Tabs on the SUA Tool Interface
|
||||
href: planning/tabs-on-the-sua-tool-interface.md
|
||||
- name: Show Messages Generated by the SUA Tool
|
||||
href: planning/showing-messages-generated-by-the-sua-tool.md
|
||||
- name: Apply Filters to Data in the SUA Tool
|
||||
href: planning/applying-filters-to-data-in-the-sua-tool.md
|
||||
- name: Fix apps using the SUA Tool
|
||||
href: planning/fixing-applications-by-using-the-sua-tool.md
|
||||
- name: Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista
|
||||
href: planning/compatibility-fixes-for-windows-8-windows-7-and-windows-vista.md
|
||||
- name: Compatibility Administrator User's Guide
|
||||
href: planning/compatibility-administrator-users-guide.md
|
||||
- name: Using the Compatibility Administrator Tool
|
||||
href: planning/using-the-compatibility-administrator-tool.md
|
||||
- name: Available Data Types and Operators in Compatibility Administrator
|
||||
href: planning/available-data-types-and-operators-in-compatibility-administrator.md
|
||||
- name: Searching for Fixed Applications in Compatibility Administrator
|
||||
href: planning/searching-for-fixed-applications-in-compatibility-administrator.md
|
||||
- name: Searching for Installed Compatibility Fixes with the Query Tool in Compatibility Administrator
|
||||
href: planning/searching-for-installed-compatibility-fixes-with-the-query-tool-in-compatibility-administrator.md
|
||||
- name: Creating a Custom Compatibility Fix in Compatibility Administrator
|
||||
href: planning/creating-a-custom-compatibility-fix-in-compatibility-administrator.md
|
||||
- name: Creating a Custom Compatibility Mode in Compatibility Administrator
|
||||
href: planning/creating-a-custom-compatibility-mode-in-compatibility-administrator.md
|
||||
- name: Creating an AppHelp Message in Compatibility Administrator
|
||||
href: planning/creating-an-apphelp-message-in-compatibility-administrator.md
|
||||
- name: Viewing the Events Screen in Compatibility Administrator
|
||||
href: planning/viewing-the-events-screen-in-compatibility-administrator.md
|
||||
- name: Enabling and Disabling Compatibility Fixes in Compatibility Administrator
|
||||
href: planning/enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md
|
||||
- name: Installing and Uninstalling Custom Compatibility Databases in Compatibility Administrator
|
||||
href: planning/installing-and-uninstalling-custom-compatibility-databases-in-compatibility-administrator.md
|
||||
- name: Managing Application-Compatibility Fixes and Custom Fix Databases
|
||||
href: planning/managing-application-compatibility-fixes-and-custom-fix-databases.md
|
||||
- name: Understanding and Using Compatibility Fixes
|
||||
href: planning/understanding-and-using-compatibility-fixes.md
|
||||
- name: Compatibility Fix Database Management Strategies and Deployment
|
||||
href: planning/compatibility-fix-database-management-strategies-and-deployment.md
|
||||
- name: Testing Your Application Mitigation Packages
|
||||
href: planning/testing-your-application-mitigation-packages.md
|
||||
- name: Using the Sdbinst.exe Command-Line Tool
|
||||
href: planning/using-the-sdbinstexe-command-line-tool.md
|
||||
items:
|
||||
- name: Overview
|
||||
href: planning/compatibility-administrator-users-guide.md
|
||||
- name: Use the Compatibility Administrator Tool
|
||||
href: planning/using-the-compatibility-administrator-tool.md
|
||||
- name: Available Data Types and Operators in Compatibility Administrator
|
||||
href: planning/available-data-types-and-operators-in-compatibility-administrator.md
|
||||
- name: Search for Fixed Applications in Compatibility Administrator
|
||||
href: planning/searching-for-fixed-applications-in-compatibility-administrator.md
|
||||
- name: Search for Installed Compatibility Fixes with the Query Tool in Compatibility Administrator
|
||||
href: planning/searching-for-installed-compatibility-fixes-with-the-query-tool-in-compatibility-administrator.md
|
||||
- name: Create a Custom Compatibility Fix in Compatibility Administrator
|
||||
href: planning/creating-a-custom-compatibility-fix-in-compatibility-administrator.md
|
||||
- name: Create a Custom Compatibility Mode in Compatibility Administrator
|
||||
href: planning/creating-a-custom-compatibility-mode-in-compatibility-administrator.md
|
||||
- name: Create an AppHelp Message in Compatibility Administrator
|
||||
href: planning/creating-an-apphelp-message-in-compatibility-administrator.md
|
||||
- name: View the Events Screen in Compatibility Administrator
|
||||
href: planning/viewing-the-events-screen-in-compatibility-administrator.md
|
||||
- name: Enable and Disable Compatibility Fixes in Compatibility Administrator
|
||||
href: planning/enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md
|
||||
- name: Install and Uninstall Custom Compatibility Databases in Compatibility Administrator
|
||||
href: planning/installing-and-uninstalling-custom-compatibility-databases-in-compatibility-administrator.md
|
||||
- name: Manage Application-Compatibility Fixes and Custom Fix Databases
|
||||
items:
|
||||
- name: Overview
|
||||
href: planning/managing-application-compatibility-fixes-and-custom-fix-databases.md
|
||||
- name: Understand and Use Compatibility Fixes
|
||||
href: planning/understanding-and-using-compatibility-fixes.md
|
||||
- name: Compatibility Fix Database Management Strategies and Deployment
|
||||
href: planning/compatibility-fix-database-management-strategies-and-deployment.md
|
||||
- name: Test Your Application Mitigation Packages
|
||||
href: planning/testing-your-application-mitigation-packages.md
|
||||
- name: Use the Sdbinst.exe Command-Line Tool
|
||||
href: planning/using-the-sdbinstexe-command-line-tool.md
|
||||
- name: Volume Activation
|
||||
href: volume-activation/volume-activation-windows-10.md
|
||||
- name: Plan for volume activation
|
||||
href: volume-activation/plan-for-volume-activation-client.md
|
||||
- name: Activate using Key Management Service
|
||||
href: volume-activation/activate-using-key-management-service-vamt.md
|
||||
- name: Activate using Active Directory-based activation
|
||||
href: volume-activation/activate-using-active-directory-based-activation-client.md
|
||||
- name: Activate clients running Windows 10
|
||||
href: volume-activation/activate-windows-10-clients-vamt.md
|
||||
- name: Monitor activation
|
||||
href: volume-activation/monitor-activation-client.md
|
||||
- name: Use the Volume Activation Management Tool
|
||||
href: volume-activation/use-the-volume-activation-management-tool-client.md
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/volume-activation-windows-10.md
|
||||
- name: Plan for volume activation
|
||||
href: volume-activation/plan-for-volume-activation-client.md
|
||||
- name: Activate using Key Management Service
|
||||
href: volume-activation/activate-using-key-management-service-vamt.md
|
||||
- name: Activate using Active Directory-based activation
|
||||
href: volume-activation/activate-using-active-directory-based-activation-client.md
|
||||
- name: Activate clients running Windows 10
|
||||
href: volume-activation/activate-windows-10-clients-vamt.md
|
||||
- name: Monitor activation
|
||||
href: volume-activation/monitor-activation-client.md
|
||||
- name: Use the Volume Activation Management Tool
|
||||
href: volume-activation/use-the-volume-activation-management-tool-client.md
|
||||
- name: "Appendix: Information sent to Microsoft during activation "
|
||||
href: volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md
|
||||
|
||||
|
||||
@ -28,7 +28,11 @@ This topic provides an overview of new solutions and online content related to d
|
||||
|
||||
- For an all-up overview of new features in Windows 10, see [What's new in Windows 10](/windows/whats-new/index).
|
||||
|
||||
## Latest news
|
||||
## [Preview] Windows Autopilot diagnostics page
|
||||
|
||||
When you deploy Windows 11 with Autopilot, you can enable users to view additional information about the Autopilot provisioning process. A new **Windows Autopilot diagnostics Page** is available to provide IT admins and end users with a user-friendly view to troubleshoot Autopilot failures. For more information, see [Windows Autopilot: What's new](/mem/autopilot/windows-autopilot-whats-new#preview-windows-autopilot-diagnostics-page).
|
||||
|
||||
## Windows 11
|
||||
|
||||
Check out the following new articles about Windows 11:
|
||||
- [Overview of Windows 11](/windows/whats-new/windows-11)
|
||||
@ -37,7 +41,9 @@ Check out the following new articles about Windows 11:
|
||||
|
||||
The [Windows ADK for Windows 11](/windows-hardware/get-started/adk-install) is available.<br>
|
||||
|
||||
[SetupDiag](#setupdiag) is included with Windows 10, version 2004 and later.<br>
|
||||
## Deployment tools
|
||||
|
||||
[SetupDiag](#setupdiag) is included with Windows 10, version 2004 and later, and Windows 11.<br>
|
||||
New capabilities are available for [Delivery Optimization](#delivery-optimization) and [Windows Update for Business](#windows-update-for-business).<br>
|
||||
VPN support is added to [Windows Autopilot](#windows-autopilot)<br>
|
||||
An in-place upgrade wizard is available in [Configuration Manager](#microsoft-endpoint-configuration-manager).<br>
|
||||
|
||||
@ -72,7 +72,7 @@ To monitor the task sequence as it happens, right-click the **MDT Build Lab** de
|
||||
|
||||
### Configure permissions for the deployment share
|
||||
|
||||
In order to read files in the deployment share and write the reference image back to it, you need to assign NTSF and SMB permissions to the MDT Build Account (MDT\_BA) for the **D:\\MDTBuildLab** folder
|
||||
In order to read files in the deployment share and write the reference image back to it, you need to assign NTFS and SMB permissions to the MDT Build Account (MDT\_BA) for the **D:\\MDTBuildLab** folder
|
||||
|
||||
On **MDT01**:
|
||||
|
||||
@ -679,4 +679,4 @@ After some time, you will have a Windows 10 Enterprise x64 image that is fully
|
||||
[Build a distributed environment for Windows 10 deployment](build-a-distributed-environment-for-windows-10-deployment.md)<br>
|
||||
[Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md)<br>
|
||||
[Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md)<br>
|
||||
[Configure MDT settings](configure-mdt-settings.md)
|
||||
[Configure MDT settings](configure-mdt-settings.md)
|
||||
|
||||
@ -32,16 +32,16 @@ To configure your environment for BitLocker, you will need to do the following:
|
||||
4. Configure the rules (CustomSettings.ini) for BitLocker.
|
||||
|
||||
> [!NOTE]
|
||||
> Even though it is not a BitLocker requirement, we recommend configuring BitLocker to store the recovery password in Active Directory. For additional information about this feature, see [Backing Up BitLocker and TPM Recovery Information to AD DS](/windows/security/information-protection/tpm/backup-tpm-recovery-information-to-ad-ds).
|
||||
> Even though it is not a BitLocker requirement, we recommend configuring BitLocker to store the recovery password in Active Directory. For more information about this feature, see [Backing Up BitLocker and TPM Recovery Information to AD DS](/windows/security/information-protection/tpm/backup-tpm-recovery-information-to-ad-ds).
|
||||
If you have access to Microsoft BitLocker Administration and Monitoring (MBAM), which is part of Microsoft Desktop Optimization Pack (MDOP), you have additional management features for BitLocker.
|
||||
|
||||
> [!NOTE]
|
||||
> Backing up TPM to Active Directory was supported only on Windows 10 version 1507 and 1511.
|
||||
|
||||
>[!NOTE]
|
||||
>Even though it is not a BitLocker requirement, we recommend configuring BitLocker to store the recovery key and TPM owner information in Active Directory. For additional information about these features, see [Backing Up BitLocker and TPM Recovery Information to AD DS](/previous-versions/windows/it-pro/windows-7/dd875529(v=ws.10)). If you have access to Microsoft BitLocker Administration and Monitoring (MBAM), which is part of Microsoft Desktop Optimization Pack (MDOP), you have additional management features for BitLocker.
|
||||
>Even though it is not a BitLocker requirement, we recommend configuring BitLocker to store the recovery key and TPM owner information in Active Directory. For more information about these features, see [Backing Up BitLocker and TPM Recovery Information to AD DS](/previous-versions/windows/it-pro/windows-7/dd875529(v=ws.10)). If you have access to Microsoft BitLocker Administration and Monitoring (MBAM), which is part of Microsoft Desktop Optimization Pack (MDOP), you have additional management features for BitLocker.
|
||||
|
||||
For the purposes of this topic, we will use DC01, a domain controller that is a member of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](./prepare-for-windows-deployment-with-mdt.md).
|
||||
For the purposes of this topic, we will use DC01, a domain controller that is a member of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, see [Deploy Windows 10 with the Microsoft Deployment Toolkit](./prepare-for-windows-deployment-with-mdt.md).
|
||||
|
||||
## Configure Active Directory for BitLocker
|
||||
|
||||
@ -69,7 +69,7 @@ The BitLocker Drive Encryption Administration Utilities are added as features vi
|
||||
1. BitLocker Drive Encryption Administration Utilities
|
||||
2. BitLocker Drive Encryption Tools
|
||||
3. BitLocker Recovery Password Viewer
|
||||
7. On the **Confirm installation selections** page, click **Install** and then click **Close**.
|
||||
7. On the **Confirm installation selections** page, click **Install**, and then click **Close**.
|
||||
|
||||
|
||||
|
||||
@ -95,7 +95,7 @@ Following these steps, you enable the backup of BitLocker and TPM recovery infor
|
||||
|
||||
### Set permissions in Active Directory for BitLocker
|
||||
|
||||
In addition to the Group Policy created previously, you need to configure permissions in Active Directory to be able to store the TPM recovery information. In these steps, we assume you have downloaded the [Add-TPMSelfWriteACE.vbs script](https://gallery.technet.microsoft.com/ScriptCenter/b4dee016-053e-4aa3-a278-3cebf70d1191) from Microsoft to C:\\Setup\\Scripts on DC01.
|
||||
In addition to the Group Policy created previously, you need to configure permissions in Active Directory to be able to store the TPM recovery information. In these steps, we assume you have downloaded the [Add-TPMSelfWriteACE.vbs script](https://raw.githubusercontent.com/DeploymentArtist/DF4/master/BitLocker%20and%20TPM/Add-TPMSelfWriteACE.vbs) to C:\\Setup\\Scripts on DC01.
|
||||
|
||||
1. On DC01, start an elevated PowerShell prompt (run as Administrator).
|
||||
2. Configure the permissions by running the following command:
|
||||
@ -114,7 +114,7 @@ If you want to automate enabling the TPM chip as part of the deployment process,
|
||||
|
||||
### Add tools from Dell
|
||||
|
||||
[Dell Comnmand | Configure](https://www.dell.com/support/article/us/en/04/sln311302/dell-command-configure) provides a Command Line Interface and a Graphical User Interface.
|
||||
[Dell Command | Configure](https://www.dell.com/support/article/us/en/04/sln311302/dell-command-configure) provides a Command Line Interface and a Graphical User Interface.
|
||||
|
||||
### Add tools from HP
|
||||
|
||||
|
||||
@ -34,6 +34,7 @@
|
||||
"overwrite": [],
|
||||
"externalReference": [],
|
||||
"globalMetadata": {
|
||||
"recommendations": true,
|
||||
"breadcrumb_path": "/windows/windows-10/breadcrumb/toc.json",
|
||||
"uhfHeaderId": "MSDocsHeader-M365-IT",
|
||||
"ms.technology": "windows",
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Update Windows 10 media with Dynamic Update
|
||||
title: Update Windows installation media with Dynamic Update
|
||||
description: Learn how to deploy feature updates to your mission critical devices
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -14,17 +14,17 @@ ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Update Windows 10 media with Dynamic Update
|
||||
# Update Windows installation media with Dynamic Update
|
||||
|
||||
**Applies to**: Windows 10
|
||||
**Applies to**: Windows 10, Windows 11
|
||||
|
||||
This topic explains how to acquire and apply Dynamic Update packages to existing Windows 10 images *prior to deployment* and includes Windows PowerShell scripts you can use to automate this process.
|
||||
This topic explains how to acquire and apply Dynamic Update packages to existing Windows images *prior to deployment* and includes Windows PowerShell scripts you can use to automate this process.
|
||||
|
||||
Volume-licensed media is available for each release of Windows 10 in the Volume Licensing Service Center (VLSC) and other relevant channels such as Windows Update for Business, Windows Server Update Services (WSUS), and Visual Studio Subscriptions. You can use Dynamic Update to ensure that Windows 10 devices have the latest feature update packages as part of an in-place upgrade while preserving language pack and Features on Demand (FODs) that might have been previously installed. Dynamic Update also eliminates the need to install a separate quality update as part of the in-place upgrade process.
|
||||
Volume-licensed media is available for each release of Windows in the Volume Licensing Service Center (VLSC) and other relevant channels such as Windows Update for Business, Windows Server Update Services (WSUS), and Visual Studio Subscriptions. You can use Dynamic Update to ensure that Windows devices have the latest feature update packages as part of an in-place upgrade while preserving language pack and Features on Demand (FODs) that might have been previously installed. Dynamic Update also eliminates the need to install a separate quality update as part of the in-place upgrade process.
|
||||
|
||||
## Dynamic Update
|
||||
|
||||
Whenever installation of a feature update starts (whether from media or an environment connected to Windows Update), *Dynamic Update* is one of the first steps. Windows 10 Setup contacts a Microsoft endpoint to fetch Dynamic Update packages, and then applies those updates to your operating system installation media. The update packages include the following kinds of updates:
|
||||
Whenever installation of a feature update starts (whether from media or an environment connected to Windows Update), *Dynamic Update* is one of the first steps. Windows Setup contacts a Microsoft endpoint to fetch Dynamic Update packages, and then applies those updates to your operating system installation media. The update packages include the following kinds of updates:
|
||||
|
||||
- Updates to Setup.exe binaries or other files that Setup uses for feature updates
|
||||
- Updates for the "safe operating system" (SafeOS) that is used for the Windows recovery environment
|
||||
@ -53,14 +53,14 @@ The various Dynamic Update packages might not all be present in the results from
|
||||
|
||||
If you want to customize the image with additional languages or Features on Demand, download supplemental media ISO files from the [Volume Licensing Service Center](https://www.microsoft.com/licensing/servicecenter/default.aspx). For example, since Dynamic Update will be disabled for your devices, and if users require specific Features on Demand, you can preinstall these into the image.
|
||||
|
||||
## Update Windows 10 installation media
|
||||
## Update Windows installation media
|
||||
|
||||
Properly updating the installation media involves a large number of actions operating on several different targets (image files). Some actions are repeated on different targets. The target images files include:
|
||||
|
||||
- Windows Preinstallation Environment (WinPE): a small operating system used to install, deploy, and repair Windows operating systems
|
||||
- Windows Recovery Environment (WinRE): repairs common causes of unbootable operating systems. WinRE is based on WinPE and can be customized with additional drivers, languages, optional packages, and other troubleshooting or diagnostic tools.
|
||||
- Windows operating system: one or more editions of Windows 10 stored in \sources\install.wim
|
||||
- Windows installation media: the complete collection of files and folders in the Windows 10 installation media. For example, \sources folder, \boot folder, Setup.exe, and so on.
|
||||
- Windows operating system: one or more editions of Windows stored in \sources\install.wim
|
||||
- Windows installation media: the complete collection of files and folders in the Windows installation media. For example, \sources folder, \boot folder, Setup.exe, and so on.
|
||||
|
||||
This table shows the correct sequence for applying the various tasks to the files. For example, the full sequence starts with adding the servicing stack update to WinRE (1) and concludes with adding the Dynamic Update for Setup to the new media (26).
|
||||
|
||||
@ -89,7 +89,7 @@ This table shows the correct sequence for applying the various tasks to the file
|
||||
|
||||
### Multiple Windows editions
|
||||
|
||||
The main operating system file (install.wim) contains multiple editions of Windows 10. It’s possible that only an update for a given edition is required to deploy it, based on the index. Or, it might be that all editions need an update. Further, ensure that languages are installed before Features on Demand, and the latest cumulative update is always applied last.
|
||||
The main operating system file (install.wim) contains multiple editions of Windows. It’s possible that only an update for a given edition is required to deploy it, based on the index. Or, it might be that all editions need an update. Further, ensure that languages are installed before Features on Demand, and the latest cumulative update is always applied last.
|
||||
|
||||
### Additional languages and features
|
||||
|
||||
@ -178,8 +178,6 @@ The script assumes that only a single edition is being updated, indicated by Ind
|
||||
|
||||
It finishes by cleaning and exporting the image to reduce the image size.
|
||||
|
||||
> [!NOTE]
|
||||
> Skip adding the latest cumulative update to Winre.wim because it contains unnecessary components in the recovery environment. The components that are updated and applicable are contained in the safe operating system Dynamic Update package. This also helps to keep the image small.
|
||||
|
||||
```powershell
|
||||
# Mount the main operating system, used throughout the script
|
||||
@ -194,8 +192,33 @@ Write-Output "$(Get-TS): Mounting WinRE"
|
||||
Mount-WindowsImage -ImagePath $WORKING_PATH"\winre.wim" -Index 1 -Path $WINRE_MOUNT -ErrorAction stop | Out-Null
|
||||
|
||||
# Add servicing stack update
|
||||
|
||||
# Note: If you are using a combined cumulative update, there may be a prerequisite servicing stack update required
|
||||
# This is where you'd add the prerequisite SSU, before applying the latest combined cumulative update.
|
||||
|
||||
# Note: If you are applying a combined cumulative update to a previously updated image (e.g. an image you updated last month)
|
||||
# There is a known issue where the servicing stack update is installed, but the cumulative update will fail.
|
||||
# This error should be caught and ignored, as the last step will be to apply the cumulative update
|
||||
# (or in this case the combined cumulative update) and thus the image will be left with the correct packages installed.
|
||||
|
||||
Write-Output "$(Get-TS): Adding package $SSU_PATH"
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $SSU_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
try
|
||||
{
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
}
|
||||
Catch
|
||||
{
|
||||
$theError = $_
|
||||
Write-Output "$(Get-TS): $theError"
|
||||
|
||||
if ($theError.Exception -like "*0x8007007e*") {
|
||||
Write-Output "$(Get-TS): This failure is a known issue with combined cumulative update, we can ignore."
|
||||
}
|
||||
else {
|
||||
throw
|
||||
}
|
||||
}
|
||||
|
||||
#
|
||||
# Optional: Add the language to recovery environment
|
||||
@ -278,8 +301,33 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
Mount-WindowsImage -ImagePath $MEDIA_NEW_PATH"\sources\boot.wim" -Index $IMAGE.ImageIndex -Path $WINPE_MOUNT -ErrorAction stop | Out-Null
|
||||
|
||||
# Add SSU
|
||||
|
||||
# Note: If you are using a combined cumulative update, there may be a prerequisite servicing stack update required
|
||||
# This is where you'd add the prerequisite SSU, before applying the latest combined cumulative update.
|
||||
|
||||
# Note: If you are applying a combined cumulative update to a previously updated image (e.g. an image you updated last month)
|
||||
# There is a known issue where the servicing stack update is installed, but the cumulative update will fail.
|
||||
# This error should be caught and ignored, as the last step will be to apply the cumulative update
|
||||
# (or in this case the combined cumulative update) and thus the image will be left with the correct packages installed.
|
||||
|
||||
Write-Output "$(Get-TS): Adding package $SSU_PATH"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $SSU_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
try
|
||||
{
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
}
|
||||
Catch
|
||||
{
|
||||
$theError = $_
|
||||
Write-Output "$(Get-TS): $theError"
|
||||
|
||||
if ($theError.Exception -like "*0x8007007e*") {
|
||||
Write-Output "$(Get-TS): This failure is a known issue with combined cumulative update, we can ignore."
|
||||
}
|
||||
else {
|
||||
throw
|
||||
}
|
||||
}
|
||||
|
||||
# Install lp.cab cab
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_OC_LP_PATH"
|
||||
|
||||
Reference in New Issue
Block a user