mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge branch 'main' into vp-sec-mdag
This commit is contained in:
Gary Moore
GitHub
commit
fea4bfefa0
@ -11487,7 +11487,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/plan/windows-10-compatibility.md",
|
||||
"redirect_url": "/windows/deployment/planning/windows-10-compatibility",
|
||||
"redirect_url": "/windows/compatibility/",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
|
||||
@ -37,7 +37,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/enhanced-diagnostic-data-windows-analytics-events-and-fields.md",
|
||||
"redirect_url": "/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields",
|
||||
"redirect_url": "https://techcommunity.microsoft.com/t5/windows-it-pro-blog/preview-app-and-driver-compatibility-insights-in-endpoint/ba-p/3482136",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
|
||||
@ -1179,6 +1179,16 @@
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-and-feature-update-reports-overview",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/planning/windows-10-compatibility.md",
|
||||
"redirect_url": "/windows/compatibility/",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/plan-determine-app-readiness.md",
|
||||
"redirect_url": "/windows/compatibility/windows-11/testing-guidelines",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -54,6 +54,11 @@
|
||||
"source_path": "windows/privacy/windows-personal-data-services-configuration.md",
|
||||
"redirect_url": "/windows/privacy/windows-10-and-privacy-compliance",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields.md",
|
||||
"redirect_url": "https://techcommunity.microsoft.com/t5/windows-it-pro-blog/preview-app-and-driver-compatibility-insights-in-endpoint/ba-p/3482136",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -9,7 +9,6 @@ metadata:
|
||||
ms.collection:
|
||||
- education
|
||||
- tier1
|
||||
- essentials-navigation
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
manager: aaroncz
|
||||
|
||||
@ -5,7 +5,7 @@ author: aczechowski
|
||||
ms.author: aaroncz
|
||||
manager: aaroncz
|
||||
ms.date: 10/03/2017
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-apps
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -5,7 +5,7 @@ author: aczechowski
|
||||
ms.author: aaroncz
|
||||
manager: aaroncz
|
||||
ms.date: 04/04/2023
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-apps
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -4,6 +4,8 @@ description: The folders for Windows Tools and Administrative Tools are folders
|
||||
ms.date: 07/01/2024
|
||||
ms.topic: conceptual
|
||||
zone_pivot_groups: windows-versions-11-10
|
||||
ms.collection:
|
||||
- essentials-manage
|
||||
---
|
||||
|
||||
# Windows Tools
|
||||
|
||||
@ -10,6 +10,7 @@ metadata:
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier1
|
||||
- essentials-manage
|
||||
author: vinaypamnani-msft
|
||||
ms.author: vinpa
|
||||
manager: aaroncz
|
||||
|
||||
@ -7,6 +7,7 @@ ms.localizationpriority: medium
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier2
|
||||
- essentials-manage
|
||||
---
|
||||
|
||||
# Mobile Device Management overview
|
||||
|
||||
@ -429,6 +429,10 @@ Specifies whether device lock is enabled.
|
||||
> - DevicePasswordHistory
|
||||
> - MaxDevicePasswordFailedAttempts
|
||||
> - MaxInactivityTimeDeviceLock
|
||||
|
||||
> [!NOTE]
|
||||
> DevicePasswordExpiration isn't supported through MDMWinsOverGP.
|
||||
|
||||
<!-- DevicePasswordEnabled-Editable-End -->
|
||||
|
||||
<!-- DevicePasswordEnabled-DFProperties-Begin -->
|
||||
|
||||
@ -17,6 +17,13 @@ The table below shows the applicability of Windows:
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Windows 11 Home devices that have been upgraded to one of the below mentioned applicable editions might require you to run the following command before onboarding:
|
||||
>
|
||||
> `DISM /online /Add-Capability /CapabilityName:Microsoft.Windows.Sense.Client~~~~`
|
||||
>
|
||||
> For more information about edition upgrades and features, see [Customize Windows features](/windows-hardware/manufacture/desktop/windows-features?view=windows-11&preserve-view=true).
|
||||
|
||||
The Windows Defender Advanced Threat Protection (WDATP) configuration service provider (CSP) allows IT Admins to onboard, determine configuration and health status, and offboard endpoints for WDATP.
|
||||
|
||||
The following example shows the WDATP configuration service provider in tree format as used by the Open Mobile Alliance (OMA) Device Management (DM).
|
||||
|
||||
@ -4,6 +4,8 @@ description: Learn how to configure the Windows Start menu to provide quick acce
|
||||
ms.topic: overview
|
||||
ms.date: 04/10/2024
|
||||
zone_pivot_groups: windows-versions-11-10
|
||||
ms.collection:
|
||||
- essentials-manage
|
||||
appliesto:
|
||||
---
|
||||
|
||||
|
||||
@ -3,6 +3,8 @@ title: Configure the Windows taskbar
|
||||
description: Learn how to configure the Windows taskbar to provide quick access to the tools and applications that users need most.
|
||||
ms.topic: how-to
|
||||
ms.date: 04/17/2024
|
||||
ms.collection:
|
||||
- essentials-manage
|
||||
appliesto:
|
||||
zone_pivot_groups: windows-versions-11-10
|
||||
---
|
||||
|
||||
@ -455,7 +455,7 @@ ConfigureTelemetryOptInSettingsUx | This policy setting determines whether peopl
|
||||
| DisableDeviceDelete | Specify whether the delete diagnostic data is enabled in the Diagnostic & Feedback Settings page. | ✅ | | | |
|
||||
| DisableDataDiagnosticViewer | Configure whether users can enable and launch the Diagnostic Data Viewer from the Diagnostic & Feedback Settings page. | ✅ | | | |
|
||||
| [DisableOneDriveFileSync](/windows/client-management/mdm/policy-configuration-service-provider#system-disableonedrivefilesync) | Prevent apps and features from working with files on OneDrive. | ✅ | | | |
|
||||
| [LimitEnhancedDiagnosticDataWindowsAnalytics](/windows/client-management/mdm/policy-csp-system#system-limitenhanceddiagnosticdatawindowsanalytics) | This policy setting, in combination with the System/AllowTelemetry policy setting, enables organizations to send Microsoft a specific set of diagnostic data for IT insights via Windows Analytics services. To enable this behavior you must enable this policy setting, and set Allow Telemetry to level 2 (Enhanced). When you configure these policy settings, a basic level of diagnostic data plus other events that are required for Windows Analytics are sent to Microsoft. These events are documented in [Windows 10, version 1703 basic level Windows diagnostic events and fields](/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields). Enabling enhanced diagnostic data in the System/AllowTelemetry policy in combination with not configuring this policy will also send the required events for Windows Analytics, plus other enhanced level diagnostic data. This setting has no effect on computers configured to send full, basic or security level diagnostic data to Microsoft. If you disable or don't configure this policy setting, then the level of diagnostic data sent to Microsoft is determined by the System/AllowTelemetry policy. | ✅ | | | |
|
||||
| [LimitEnhancedDiagnosticDataWindowsAnalytics](/windows/client-management/mdm/policy-csp-system#limitenhanceddiagnosticdatawindowsanalytics) | This policy setting, in combination with the System/AllowTelemetry policy setting, enables organizations to send Microsoft a specific set of diagnostic data for IT insights via Windows Analytics services. To enable this behavior you must enable this policy setting, and set Allow Telemetry to level 2 (Enhanced). When you configure these policy settings, a basic level of diagnostic data plus other events that are required for Windows Analytics are sent to Microsoft. Enabling enhanced diagnostic data in the System/AllowTelemetry policy in combination with not configuring this policy will also send the required events for Windows Analytics, plus other enhanced level diagnostic data. This setting has no effect on computers configured to send full, basic or security level diagnostic data to Microsoft. If you disable or don't configure this policy setting, then the level of diagnostic data sent to Microsoft is determined by the System/AllowTelemetry policy. | ✅ | | | |
|
||||
|
||||
## TextInput
|
||||
|
||||
|
||||
@ -36,8 +36,6 @@
|
||||
href: update/plan-define-readiness.md
|
||||
- name: Evaluate infrastructure and tools
|
||||
href: update/eval-infra-tools.md
|
||||
- name: Determine application readiness
|
||||
href: update/plan-determine-app-readiness.md
|
||||
- name: Define your servicing strategy
|
||||
href: update/plan-define-strategy.md
|
||||
- name: Delivery Optimization for Windows client updates
|
||||
@ -53,6 +51,8 @@
|
||||
href: planning/windows-10-infrastructure-requirements.md
|
||||
- name: Plan for volume activation
|
||||
href: volume-activation/plan-for-volume-activation-client.md
|
||||
- name: Windows compatibility cookbook
|
||||
href: /windows/compatibility/
|
||||
- name: Features removed or planned for replacement
|
||||
items:
|
||||
- name: Windows client features lifecycle
|
||||
|
||||
@ -6,7 +6,7 @@ ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.date: 11/23/2022
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.date: 05/09/2024
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
|
||||
@ -6,7 +6,7 @@ description: Learn about deploying Windows with Microsoft 365 and how to use a f
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.date: 02/13/2024
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/27/2022
|
||||
---
|
||||
|
||||
@ -8,15 +8,13 @@ author: cmknox
|
||||
ms.author: carmenf
|
||||
manager: aaroncz
|
||||
ms.reviewer: mstewart
|
||||
ms.collection:
|
||||
ms.collection:
|
||||
- tier3
|
||||
- essentials-privacy
|
||||
- essentials-security
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 05/23/2024
|
||||
---
|
||||
|
||||
@ -30,7 +28,7 @@ Delivery Optimization can't be used to download or send personal content. Delive
|
||||
|
||||
Delivery Optimization downloads the same updates and apps that you would get through [Windows Update](../update/windows-update-security.md), Microsoft Store apps, and other Microsoft updates using the same security measures. To make sure you're getting authentic updates, Delivery Optimization gets information securely from Microsoft to check the authenticity of each part of an update or app that it downloads from other PCs. The authenticity of the downloads is checked again before installing it. <!--8658744-->
|
||||
|
||||
## Download request workflow
|
||||
## Download request workflow
|
||||
|
||||
This workflow allows Delivery Optimization to securely and efficiently deliver requested content to the calling device and explains client-service communication. Delivery Optimization uses content metadata to verify the content and to determine all available locations to pull content from.
|
||||
|
||||
@ -50,4 +48,4 @@ This workflow allows Delivery Optimization to securely and efficiently deliver r
|
||||
| cp\*.prod.do.dsp.mp.microsoft.com <br> | 443 | Content Policy | Provides content specific policies and as content metadata URLs. | **Profile**: The device type (for example, PC or Xbox) <br> **ContentId**: The content identifier <br> **doClientVersion**: The version of the DoSvc client <br> **countryCode**: The country the client is connected from <br> **altCatalogID**: If ContentID isn't available, use the download URL instead <br> **eID**: Client grouping ID <br> **CacheHost**: Cache host ID |
|
||||
| disc\*.prod.do.dsp.mp.microsoft.com | 443 | Discovery | Directs clients to a particular instance of the peer matching service (Array), ensuing that clients are collocated by factors, such as content, groupID and external IP. | **Profile**: The device type (for example, PC or Xbox) <br> **ContentID**: The content identifier <br> **doClientVersion**: The version of the DoSvc client <br> **partitionID**: Client partitioning hint <br> **altCatalogID**: If ContentID isn't available, use the download URL instead <br> **eID**: Client grouping ID |
|
||||
| array\*.prod.do.dsp.mp.microsoft.com | 443 | Arrays | Provides the client with list of peers that have the same content and belong to the same peer group. | **Profile**: The device type (for example, PC or Xbox) <br> **ContentID**: The content identifier <br> **doClientVersion**: The version of the DoSvc client <br> **altCatalogID**: If ContentID isn't available, use the download URL instead <br> **PeerID**: Identity of the device running DO client <br> **ReportedIp**: The internal / private IP Address <br> **IsBackground**: Is the download interactive or background <br> **Uploaded**: Total bytes uploaded to peers <br> **Downloaded**: Total bytes downloaded from peers <br> **DownloadedCdn**: Total bytes downloaded from CDN <br> **Left**: Bytes left to download <br> **Peers Wanted**: Total number of peers wanted <br> **Group ID**: Group the device belongs to (set via DownloadMode 2 + Group ID GP / MDM policies) <br> **Scope**: The Download mode <br> **UploadedBPS**: The upload speed in bytes per second <br> **DownloadBPS**: The download speed in Bytes per second <br> **eID**: Client grouping ID |
|
||||
| dl.delivery.mp.microsoft.com <br> download.windowsupdate.com | 80 | Delivery Optimization metadata file hosting | CDN hostnames for Delivery Optimization content metadata files | Metadata download can come from different hostnames, but it's required for peer to peer. |
|
||||
| dl.delivery.mp.microsoft.com <br> download.windowsupdate.com | 80 | Delivery Optimization metadata file hosting | CDN hostnames for Delivery Optimization content metadata files | Metadata download can come from different hostnames, but it's required for peer to peer. |
|
||||
|
||||
@ -5,7 +5,7 @@ description: Elixir images read me file
|
||||
ms.service: windows-client
|
||||
author: nidos
|
||||
ms.author: nidos
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.date: 12/31/2017
|
||||
ms.subservice: itpro-updates
|
||||
robots: noindex
|
||||
|
||||
@ -12,13 +12,12 @@ metadata:
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier3
|
||||
- essentials-navigation
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
manager: aaroncz
|
||||
ms.date: 12/22/2023 #Required; mm/dd/yyyy format.
|
||||
localization_priority: medium
|
||||
|
||||
|
||||
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
|
||||
|
||||
landingContent:
|
||||
@ -61,8 +60,8 @@ landingContent:
|
||||
- text: Optimize Windows 10 or later update delivery with Configuration Manager
|
||||
url: /mem/configmgr/sum/deploy-use/optimize-windows-10-update-delivery#windows-delivery-optimization
|
||||
- text: Delivery Optimization settings in Microsoft Intune
|
||||
url: /mem/intune/configuration/delivery-optimization-windows
|
||||
|
||||
url: /mem/intune/configuration/delivery-optimization-windows
|
||||
|
||||
# Card
|
||||
- title: Microsoft Connected Cache (MCC) for Enterprise and Education
|
||||
linkLists:
|
||||
@ -71,7 +70,7 @@ landingContent:
|
||||
- text: MCC for Enterprise and Education (early preview)
|
||||
url: waas-microsoft-connected-cache.md
|
||||
- text: Sign up
|
||||
url: https://aka.ms/MSConnectedCacheSignup
|
||||
url: https://aka.ms/MSConnectedCacheSignup
|
||||
|
||||
# Card
|
||||
- title: Microsoft Connected Cache (MCC) for Internet Service Providers (ISPs)
|
||||
@ -84,7 +83,7 @@ landingContent:
|
||||
url: https://aka.ms/MCCForISPSurvey
|
||||
- text: MCC for ISPs (early preview)
|
||||
url: mcc-isp.md
|
||||
|
||||
|
||||
|
||||
# Card (optional)
|
||||
- title: Resources
|
||||
|
||||
@ -10,11 +10,10 @@ manager: aaroncz
|
||||
ms.reviewer: mstewart
|
||||
ms.collection:
|
||||
- tier3
|
||||
- essentials-manage
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 05/23/2024
|
||||
---
|
||||
|
||||
@ -87,8 +87,8 @@ All cached files have to be above a set minimum size. This size is automatically
|
||||
More options available that control the impact Delivery Optimization has on your network include the following settings:
|
||||
|
||||
- [Minimum Background QoS](#minimum-background-qos) lets administrators guarantee a minimum download speed for Windows updates. This setting adjusts the amount of data downloaded directly from HTTP sources, rather than other peers in the network.
|
||||
- [Maximum Foreground Download Bandwidth](#maximum-foreground-download-bandwidth) specifies the maximum foreground download bandwidth*hat Delivery Optimization uses, across all concurrent download activities, as a percentage of available download bandwidth.
|
||||
- [Maximum Background Download Bandwidth](#maximum-background-download-bandwidth) specifies the **maximum background download bandwidth** that Delivery Optimization uses, across all concurrent download activities, as a percentage of available download bandwidth.
|
||||
- [Maximum Foreground Download Bandwidth](#maximum-foreground-download-bandwidth) specifies the maximum foreground download bandwidth that Delivery Optimization uses, across all concurrent download activities, as a percentage of available download bandwidth.
|
||||
- [Maximum Background Download Bandwidth](#maximum-background-download-bandwidth) specifies the maximum background download bandwidth that Delivery Optimization uses, across all concurrent download activities, as a percentage of available download bandwidth.
|
||||
- [Set Business Hours to Limit Background Download Bandwidth](#set-business-hours-to-limit-background-download-bandwidth) specifies the maximum background download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth.
|
||||
- [Set Business Hours to Limit Foreground Download Bandwidth](#set-business-hours-to-limit-foreground-download-bandwidth) specifies the maximum foreground download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth.
|
||||
- [Select a method to restrict Peer Selection](#select-a-method-to-restrict-peer-selection) restricts peer selection by the options you select.
|
||||
|
||||
@ -10,7 +10,6 @@ ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier3
|
||||
- essentials-get-started
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
|
||||
@ -11,11 +11,10 @@ ms.reviewer: mstewart
|
||||
ms.collection:
|
||||
- tier3
|
||||
- highpri
|
||||
- essentials-overview
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 05/23/2024
|
||||
---
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ metadata:
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
manager: aaroncz
|
||||
ms.date: 04/01/2024
|
||||
ms.date: 07/12/2024
|
||||
localization_priority: medium
|
||||
|
||||
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
|
||||
@ -34,10 +34,10 @@ landingContent:
|
||||
url: update/plan-define-readiness.md
|
||||
- text: Define your servicing strategy
|
||||
url: update/plan-define-strategy.md
|
||||
- text: Determine application readiness
|
||||
url: update/plan-determine-app-readiness.md
|
||||
- text: Plan for volume activation
|
||||
url: volume-activation/plan-for-volume-activation-client.md
|
||||
- text: Windows compatibility cookbook
|
||||
url: /windows/compatibility/
|
||||
|
||||
- title: Prepare
|
||||
linkLists:
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ ms.author: frankroj
|
||||
description: The Compatibility Administrator tool helps you resolve potential application-compatibility issues before deploying a new version of Windows.
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ description: Learn how to deploy your compatibility fixes into an application-in
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 10/28/2022
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
|
||||
@ -1,45 +0,0 @@
|
||||
---
|
||||
title: Windows 10 compatibility (Windows 10)
|
||||
description: Windows 10 will be compatible with most existing PC hardware; most devices running Windows 7, Windows 8, or Windows 8.1 will meet the requirements for Windows 10.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
|
||||
# Windows 10 compatibility
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
Windows 10 will be compatible with most existing PC hardware; most devices running Windows 7, Windows 8, or Windows 8.1 will meet the requirements for Windows 10.
|
||||
|
||||
For full system requirements, see [Windows 10 specifications](https://go.microsoft.com/fwlink/p/?LinkId=625077). Some driver updates may be required for Windows 10.
|
||||
|
||||
Existing desktop (Win32) application compatibility is also expected to be strong, with most existing applications working without any changes. Those applications that interface with Windows at a low level, those applications that use undocumented APIs, or those that do not follow recommended coding practices could experience issues.
|
||||
|
||||
Existing Windows Store (WinRT) apps created for Windows 8 and Windows 8.1 should also continue to work, because compatibility can be validated against all the apps that have been submitted to the Windows Store.
|
||||
|
||||
For web apps and sites, modern HTML5-based sites should also have a high degree of compatibility and excellent performance through the new Microsoft Edge browser, while older web apps and sites can continue to use Internet Explorer 11 and the Enterprise Mode features that were first introduced in Windows 7 and Windows 8.1 and are still present in Windows 10. For more information about Internet Explorer and Enterprise Mode, see the [Internet Explorer 11 Deployment Guide for IT Pros.](/internet-explorer/ie11-deploy-guide/)
|
||||
|
||||
## Recommended application testing process
|
||||
|
||||
Historically, organizations have performed extensive, and often exhaustive, testing of the applications they use before deployment of a new Windows version, service pack, or any other significant update. With Windows 10, organizations are encouraged to use more optimized testing processes, which reflect the higher levels of compatibility that are expected. At a high level:
|
||||
|
||||
- Identify mission-critical applications and websites, those applications and websites that are essential to the organization's operations. Focus testing efforts on this subset of applications, early in the Windows development cycle (for example, with Windows Insider Program builds) to identify potential issues. Report any issues you encounter with the Windows Feedback tool, so that these issues can be addressed prior to the next Windows release.
|
||||
|
||||
- For less critical applications, apply an "internal flighting" or pilot-based approach, by deploying new Windows upgrades to groups of machines, growing gradually in size and potential impact, to verify compatibility with hardware and software. Reactively address issues before you expand the pilot to more machines.
|
||||
|
||||
## Related articles
|
||||
|
||||
|
||||
[Windows 10 servicing options](../update/waas-servicing-strategy-windows-10-updates.md)
|
||||
|
||||
[Windows 10 deployment considerations](windows-10-deployment-considerations.md)
|
||||
|
||||
[Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md)
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
@ -69,7 +69,7 @@ In either of these scenarios, you can make various configuration changes to the
|
||||
For computers using the [General Availability Channel](../update/waas-overview.md#general-availability-channel), you can deploy these upgrades by using various methods:
|
||||
|
||||
- Windows Update or Windows Update for Business, for devices where you want to receive updates directly from the Internet.
|
||||
- Windows Server Update Services (WSUS), for devices configured to pull updates from internal servers after they're approved (deploying like an update).
|
||||
- Windows Server Update Services (WSUS), for devices configured to pull updates from internal servers after they're approved (deploying like an update).
|
||||
- Configuration Manager task sequences.
|
||||
- Configuration Manager software update capabilities (deploying like an update).
|
||||
|
||||
@ -79,5 +79,4 @@ The upgrade process is also optimized to reduce the overall time and network ban
|
||||
|
||||
## Related articles
|
||||
|
||||
[Windows 10 compatibility](windows-10-compatibility.md)<br>
|
||||
[Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md)
|
||||
|
||||
@ -61,11 +61,6 @@ sections:
|
||||
answer: |
|
||||
Many existing Win32 and Win64 applications already run reliably on Windows 10 without any changes. You can also expect strong compatibility and support for Web apps and devices.
|
||||
|
||||
- question: |
|
||||
Is there an easy way to assess if my organization's devices are ready to upgrade to Windows 10?
|
||||
answer: |
|
||||
[Desktop Analytics](/mem/configmgr/desktop-analytics/overview) provides powerful insights and recommendations about the computers, applications, and drivers in your organization, at no extra cost and without other infrastructure requirements. This service guides you through your upgrade and feature update projects using a workflow based on Microsoft recommended practices. Up-to-date inventory data allows you to balance cost and risk in your upgrade projects.
|
||||
|
||||
- name: Administration and deployment
|
||||
questions:
|
||||
- question: |
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
@ -97,4 +97,3 @@ Windows 10 Enterprise and Windows 10 Enterprise LTSC installations use different
|
||||
|
||||
[Windows 10 servicing options](../update/waas-servicing-strategy-windows-10-updates.md)<br>
|
||||
[Windows 10 deployment considerations](windows-10-deployment-considerations.md)<br>
|
||||
[Windows 10 compatibility](windows-10-compatibility.md)<br>
|
||||
@ -3,7 +3,7 @@ title: Evaluate infrastructure and tools
|
||||
description: Review the steps to ensure your infrastructure is ready to deploy updates to clients in your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -13,7 +13,7 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Windows Server</a>
|
||||
ms.date: 12/05/2023
|
||||
ms.date: 07/10/2024
|
||||
---
|
||||
|
||||
# Update Windows installation media with Dynamic Update
|
||||
@ -38,10 +38,10 @@ Devices must be able to connect to the internet to obtain Dynamic Updates. In so
|
||||
|
||||
## Acquire Dynamic Update packages
|
||||
|
||||
You can obtain Dynamic Update packages from the [Microsoft Update Catalog](https://catalog.update.microsoft.com). At that site, use the search bar in the upper right to find the Dynamic Update packages for a particular release. The various Dynamic Update packages might not all be present in the results from a single search, so you might have to search with different keywords to find all of the updates. Check various parts of the results to be sure you've identified the needed files. The following tables show the key values to search for or look for in the results.
|
||||
You can obtain Dynamic Update packages from the [Microsoft Update Catalog](https://catalog.update.microsoft.com). At that site, use the search bar in the upper right to find the Dynamic Update packages for a particular release. The various Dynamic Update packages might not all be present in the results from a single search, so you might have to search with different keywords to find all of the updates. Check various parts of the results to be sure you've identified the files needed. The following tables show the key values to search for or look for in the results.
|
||||
|
||||
### Windows 11, version 22H2 Dynamic Update packages
|
||||
**Title** can distinguish each Dynamic Package. Cumulative updates have the servicing stack embedded. The servicing stack is published only if necessary for a given cumulative update.
|
||||
### Windows 11, version 22H2 and later Dynamic Update packages
|
||||
**Title** can distinguish each Dynamic Package. Latest cumulative updates have the servicing stack embedded. The servicing stack is published only if necessary for a given cumulative update.Titles below are for Windows 11, version 22H2. Windows 11, version 23H2 and 24H2 have a similar format.
|
||||
|
||||
| Update packages |Title |
|
||||
|-----------------------------------|---------------------------------------------------------------|
|
||||
@ -61,7 +61,7 @@ You can obtain Dynamic Update packages from the [Microsoft Update Catalog](https
|
||||
|Latest cumulative update | YYYY-MM Cumulative Update for Windows 11 | | |
|
||||
|Servicing stack Dynamic Update | YYYY-MM Servicing Stack Update for Windows 11 Version 21H2 | | |
|
||||
|
||||
### For Windows 10, version 22H2 Dynamic Update packages
|
||||
### Windows 10, version 22H2 Dynamic Update packages
|
||||
**Title**, **Product** and **Description** are required to distinguish each Dynamic Package. Latest cumulative update has the servicing stack embedded. Servicing stack published separately only if necessary as a prerequisite for a given cumulative update.
|
||||
|
||||
| Update packages |Title |Product |Description |
|
||||
@ -75,7 +75,7 @@ If you want to customize the image with additional languages or Features on Dema
|
||||
|
||||
## 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:
|
||||
Properly updating the installation media involves many 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.
|
||||
@ -86,7 +86,7 @@ This table shows the correct sequence for applying the various tasks to the file
|
||||
|
||||
|Task |WinRE (winre.wim) |Operating system (install.wim) | WinPE (boot.wim) | New media |
|
||||
|-----------------------------------|-------------------|--------------------------------|------------------|-----------|
|
||||
|Add servicing stack Dynamic Update | 1 | 9 | 17 | |
|
||||
|Add servicing stack Dynamic Update | 1 | 9 | 17 | |
|
||||
|Add language pack | 2 | 10 | 18 | |
|
||||
|Add localized optional packages | 3 | | 19 | |
|
||||
|Add font support | 4 | | 20 | |
|
||||
@ -119,6 +119,13 @@ You don't have to add more languages and features to the image to accomplish the
|
||||
|
||||
Optional Components, along with the .NET feature, can be installed offline, however doing so creates pending operations that require the device to restart. As a result, the call to perform image cleanup would fail. There are two options to avoid the cleanup failure. One option is to skip the image cleanup step, though that results in a larger install.wim. Another option is to install the .NET and Optional Components in a step after cleanup but before export. This is the option in the sample script. By doing this, you'll have to start with the original install.wim (with no pending actions) when you maintain or update the image the next time (for example, the next month).
|
||||
|
||||
|
||||
### Checkpoint cumulative updates
|
||||
Starting with Windows 11, version 24H2, the latest cumulative update may have a prerequisite cumulative update that is required to be installed first. These are known as checkpoint cumulative updates. In these cases, the cumulative update file level differentials are based on a previous cumulative update instead of the Windows RTM release. The benefit is a smaller update package and faster installation. When you obtain the latest cumulative update from the [Microsoft Update Catalog](https://catalog.update.microsoft.com), checkpoint cumulative updates will be available from the download button. In addition, the knowledge base article for the cumulative update will provide additional information.
|
||||
|
||||
To install the checkpoint(s) when servicing the Windows OS (steps 9 & 12) and WinPE (steps 17 & 23), call `Add-WindowsPackage` with the target cumulative update. The folder from `-PackagePath` will be used to discover and install one or more checkpoints as needed. Only the target cumulative update and checkpoint cumulative updates should be in the `-PackagePath` folder. Cumulative update packages with a revision <= the target cumulative update will be processed. If you are not customizing the image with additional languages and/or optional features, then separate calls to `Add-WindowsPackage` (checkpoint cumulative updates first) can be used for steps 9 & 17 above. Separate calls cannot be used for steps 12 and 23.
|
||||
|
||||
|
||||
## Windows PowerShell scripts to apply Dynamic Updates to an existing image
|
||||
|
||||
These examples are for illustration only, and therefore lack error handling. The script assumes that the following packages are stored locally in this folder structure:
|
||||
@ -150,12 +157,13 @@ $LANG_FONT_CAPABILITY = "jpan"
|
||||
# If you are using this script for Windows 10, modify to mount and use the LANGPACK ISO.
|
||||
$FOD_ISO_PATH = "C:\mediaRefresh\packages\FOD-PACKAGES_OEM_PT1_amd64fre_MULTI.iso"
|
||||
|
||||
# Declare Dynamic Update packages
|
||||
$LCU_PATH = "C:\mediaRefresh\packages\LCU.msu"
|
||||
$SSU_PATH = "C:\mediaRefresh\packages\SSU_DU.msu"
|
||||
$SETUP_DU_PATH = "C:\mediaRefresh\packages\Setup_DU.cab"
|
||||
$SAFE_OS_DU_PATH = "C:\mediaRefresh\packages\SafeOS_DU.cab"
|
||||
$DOTNET_CU_PATH = "C:\mediaRefresh\packages\DotNet_CU.msu"
|
||||
# Declare Dynamic Update packages. A dedicated folder is used for the latest cumulative update, and as needed
|
||||
# checkpoint cumulative updates.
|
||||
$LCU_PATH = "C:\mediaRefresh\packages\CU\LCU.msu"
|
||||
$SSU_PATH = "C:\mediaRefresh\packages\Other\SSU_DU.msu"
|
||||
$SETUP_DU_PATH = "C:\mediaRefresh\packages\Other\Setup_DU.cab"
|
||||
$SAFE_OS_DU_PATH = "C:\mediaRefresh\packages\Other\SafeOS_DU.cab"
|
||||
$DOTNET_CU_PATH = "C:\mediaRefresh\packages\Other\DotNet_CU.msu"
|
||||
|
||||
# Declare folders for mounted images and temp files
|
||||
$MEDIA_OLD_PATH = "C:\mediaRefresh\oldMedia"
|
||||
@ -211,14 +219,14 @@ This process is repeated for each edition of Windows within the main operating s
|
||||
# Update each main OS Windows image including the Windows Recovery Environment (WinRE)
|
||||
#
|
||||
|
||||
# Get the list of images contained within WinPE
|
||||
# Get the list of images contained within the main OS
|
||||
$WINOS_IMAGES = Get-WindowsImage -ImagePath $MEDIA_NEW_PATH"\sources\install.wim"
|
||||
|
||||
Foreach ($IMAGE in $WINOS_IMAGES) {
|
||||
|
||||
# first mount the main OS image
|
||||
Write-Output "$(Get-TS): Mounting main OS, image index $($IMAGE.ImageIndex)"
|
||||
Mount-WindowsImage -ImagePath $MEDIA_NEW_PATH"\sources\install.wim" -Index $IMAGE.ImageIndex -Path $MAIN_OS_MOUNT -ErrorAction stop| Out-Null
|
||||
Mount-WindowsImage -ImagePath $MEDIA_NEW_PATH"\sources\install.wim" -Index $IMAGE.ImageIndex -Path $MAIN_OS_MOUNT -ErrorAction stop| Out-Null
|
||||
|
||||
if ($IMAGE.ImageIndex -eq "1") {
|
||||
|
||||
@ -237,19 +245,22 @@ Foreach ($IMAGE in $WINOS_IMAGES) {
|
||||
# Windows 11, version 22H2 are examples. In these cases, the servicing stack update is not published seperately; the combined
|
||||
# cumulative update should be used for this step. However, in hopefully rare cases, there may breaking change in the combined
|
||||
# cumulative update format, that requires a standalone servicing stack update to be published, and installed first before the
|
||||
# combined cumulative update can be installed.
|
||||
# combined cumulative update can be installed.
|
||||
|
||||
# This is the code to handle the rare case that the SSU is published and required for the combined cumulative update
|
||||
# Write-Output "$(Get-TS): Adding package $SSU_PATH"
|
||||
# Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
# Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
|
||||
# Now, attempt the combined cumulative update.
|
||||
# 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 Safe OS update and thus the image will be left with the correct
|
||||
# packages installed.
|
||||
|
||||
|
||||
Write-Output "$(Get-TS): Adding package $LCU_PATH to WinRE"
|
||||
try
|
||||
{
|
||||
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $LCU_PATH | Out-Null
|
||||
}
|
||||
Catch
|
||||
@ -270,29 +281,27 @@ Foreach ($IMAGE in $WINOS_IMAGES) {
|
||||
# update. This second approach is commented out below.
|
||||
|
||||
# Write-Output "$(Get-TS): Adding package $SSU_PATH"
|
||||
# Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
# Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
|
||||
#
|
||||
# Optional: Add the language to recovery environment
|
||||
#
|
||||
# Install lp.cab cab
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_OC_LP_PATH"
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $WINPE_OC_LP_PATH -ErrorAction stop | Out-Null
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_OC_LP_PATH to WinRE"
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $WINPE_OC_LP_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
# Install language cabs for each optional package installed
|
||||
$WINRE_INSTALLED_OC = Get-WindowsPackage -Path $WINRE_MOUNT
|
||||
Foreach ($PACKAGE in $WINRE_INSTALLED_OC) {
|
||||
|
||||
if ( ($PACKAGE.PackageState -eq "Installed") `
|
||||
-and ($PACKAGE.PackageName.startsWith("WinPE-")) `
|
||||
-and ($PACKAGE.ReleaseType -eq "FeaturePack") ) {
|
||||
if ( ($PACKAGE.PackageState -eq "Installed") -and ($PACKAGE.PackageName.startsWith("WinPE-")) -and ($PACKAGE.ReleaseType -eq "FeaturePack") ) {
|
||||
|
||||
$INDEX = $PACKAGE.PackageName.IndexOf("-Package")
|
||||
if ($INDEX -ge 0) {
|
||||
$OC_CAB = $PACKAGE.PackageName.Substring(0, $INDEX) + "_" + $LANG + ".cab"
|
||||
if ($WINPE_OC_LANG_CABS.Contains($OC_CAB)) {
|
||||
$OC_CAB_PATH = Join-Path $WINPE_OC_LANG_PATH $OC_CAB
|
||||
Write-Output "$(Get-TS): Adding package $OC_CAB_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $OC_CAB_PATH to WinRE"
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $OC_CAB_PATH -ErrorAction stop | Out-Null
|
||||
}
|
||||
}
|
||||
@ -301,7 +310,7 @@ Foreach ($IMAGE in $WINOS_IMAGES) {
|
||||
|
||||
# Add font support for the new language
|
||||
if ( (Test-Path -Path $WINPE_FONT_SUPPORT_PATH) ) {
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_FONT_SUPPORT_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_FONT_SUPPORT_PATH to WinRE"
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $WINPE_FONT_SUPPORT_PATH -ErrorAction stop | Out-Null
|
||||
}
|
||||
|
||||
@ -309,16 +318,16 @@ Foreach ($IMAGE in $WINOS_IMAGES) {
|
||||
if (Test-Path -Path $WINPE_SPEECH_TTS_PATH) {
|
||||
if ( (Test-Path -Path $WINPE_SPEECH_TTS_LANG_PATH) ) {
|
||||
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_SPEECH_TTS_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_SPEECH_TTS_PATH to WinRE"
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $WINPE_SPEECH_TTS_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_SPEECH_TTS_LANG_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_SPEECH_TTS_LANG_PATH to WinRE"
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $WINPE_SPEECH_TTS_LANG_PATH -ErrorAction stop | Out-Null
|
||||
}
|
||||
}
|
||||
|
||||
# Add Safe OS
|
||||
Write-Output "$(Get-TS): Adding package $SAFE_OS_DU_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $SAFE_OS_DU_PATH to WinRE"
|
||||
Add-WindowsPackage -Path $WINRE_MOUNT -PackagePath $SAFE_OS_DU_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
# Perform image cleanup
|
||||
@ -347,54 +356,54 @@ Foreach ($IMAGE in $WINOS_IMAGES) {
|
||||
# includes the servicing stack updates (i.e. SSU + LCU are combined). Windows 11, version 21H2 and Windows 11, version 22H2 are examples. In these
|
||||
# cases, the servicing stack update is not published seperately; the combined cumulative update should be used for this step. However, in hopefully
|
||||
# rare cases, there may breaking change in the combined cumulative update format, that requires a standalone servicing stack update to be published,
|
||||
# and installed first before the combined cumulative update can be installed.
|
||||
# and installed first before the combined cumulative update can be installed.
|
||||
|
||||
# This is the code to handle the rare case that the SSU is published and required for the combined cumulative update
|
||||
# Write-Output "$(Get-TS): Adding package $SSU_PATH"
|
||||
# Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
# Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
|
||||
# Now, attempt the combined cumulative update. Unlike WinRE and WinPE, we don't need to check for error 0x8007007e
|
||||
Write-Output "$(Get-TS): Adding package $LCU_PATH"
|
||||
Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $LCU_PATH | Out-Null
|
||||
Write-Output "$(Get-TS): Adding package $LCU_PATH to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $LCU_PATH | Out-Null
|
||||
|
||||
# The second approach for Step 18 is for Windows releases that have not adopted the combined cumulative update
|
||||
# but instead continue to have a seperate servicing stack update published. In this case, we'll install the SSU
|
||||
# update. This second approach is commented out below.
|
||||
|
||||
# Write-Output "$(Get-TS): Adding package $SSU_PATH"
|
||||
# Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
# Write-Output "$(Get-TS): Adding package $SSU_PATH to main OS, index $($IMAGE.ImageIndex)"
|
||||
# Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
|
||||
# Optional: Add language to main OS
|
||||
Write-Output "$(Get-TS): Adding package $OS_LP_PATH"
|
||||
Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $OS_LP_PATH -ErrorAction stop | Out-Null
|
||||
Write-Output "$(Get-TS): Adding package $OS_LP_PATH to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $OS_LP_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
# Optional: Add a Features on Demand to the image
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.Fonts.Jpan~~~und-JPAN~0.0.1.0"
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.Fonts.Jpan~~~und-JPAN~0.0.1.0 to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsCapability -Name "Language.Fonts.$LANG_FONT_CAPABILITY~~~und-$LANG_FONT_CAPABILITY~0.0.1.0" -Path $MAIN_OS_MOUNT -Source $FOD_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.Basic~~~$LANG~0.0.1.0"
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.Basic~~~$LANG~0.0.1.0 to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsCapability -Name "Language.Basic~~~$LANG~0.0.1.0" -Path $MAIN_OS_MOUNT -Source $FOD_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.OCR~~~$LANG~0.0.1.0"
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.OCR~~~$LANG~0.0.1.0 to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsCapability -Name "Language.OCR~~~$LANG~0.0.1.0" -Path $MAIN_OS_MOUNT -Source $FOD_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.Handwriting~~~$LANG~0.0.1.0"
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.Handwriting~~~$LANG~0.0.1.0 to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsCapability -Name "Language.Handwriting~~~$LANG~0.0.1.0" -Path $MAIN_OS_MOUNT -Source $FOD_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.TextToSpeech~~~$LANG~0.0.1.0"
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.TextToSpeech~~~$LANG~0.0.1.0 to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsCapability -Name "Language.TextToSpeech~~~$LANG~0.0.1.0" -Path $MAIN_OS_MOUNT -Source $FOD_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
Write-Output "$(Get-TS): Adding language FOD:Language.Speech~~~$LANG~0.0.1.0"
|
||||
Write-Output "$(Get-TS): Adding language FOD: Language.Speech~~~$LANG~0.0.1.0 to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsCapability -Name "Language.Speech~~~$LANG~0.0.1.0" -Path $MAIN_OS_MOUNT -Source $FOD_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
# Note: If I wanted to enable additional Features on Demand, I'd add these here.
|
||||
|
||||
# Add latest cumulative update
|
||||
Write-Output "$(Get-TS): Adding package $LCU_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $LCU_PATH to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $LCU_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
# Perform image cleanup
|
||||
Write-Output "$(Get-TS): Performing image cleanup on main OS"
|
||||
Write-Output "$(Get-TS): Performing image cleanup on main OS, index $($IMAGE.ImageIndex)"
|
||||
DISM /image:$MAIN_OS_MOUNT /cleanup-image /StartComponentCleanup | Out-Null
|
||||
|
||||
#
|
||||
@ -403,11 +412,11 @@ Foreach ($IMAGE in $WINOS_IMAGES) {
|
||||
# the image to be booted, and thus if we tried to cleanup after installation, it would fail.
|
||||
#
|
||||
|
||||
Write-Output "$(Get-TS): Adding NetFX3~~~~"
|
||||
Write-Output "$(Get-TS): Adding NetFX3~~~~ to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsCapability -Name "NetFX3~~~~" -Path $MAIN_OS_MOUNT -Source $FOD_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
# Add .NET Cumulative Update
|
||||
Write-Output "$(Get-TS): Adding package $DOTNET_CU_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $DOTNET_CU_PATH to main OS, index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $MAIN_OS_MOUNT -PackagePath $DOTNET_CU_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
# Dismount
|
||||
@ -420,6 +429,7 @@ Foreach ($IMAGE in $WINOS_IMAGES) {
|
||||
}
|
||||
|
||||
Move-Item -Path $WORKING_PATH"\install2.wim" -Destination $MEDIA_NEW_PATH"\sources\install.wim" -Force -ErrorAction stop | Out-Null
|
||||
|
||||
```
|
||||
|
||||
### Update WinPE
|
||||
@ -438,7 +448,7 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
|
||||
# update WinPE
|
||||
Write-Output "$(Get-TS): Mounting WinPE, image index $($IMAGE.ImageIndex)"
|
||||
Mount-WindowsImage -ImagePath $MEDIA_NEW_PATH"\sources\boot.wim" -Index $IMAGE.ImageIndex -Path $WINPE_MOUNT -ErrorAction stop | Out-Null
|
||||
Mount-WindowsImage -ImagePath $MEDIA_NEW_PATH"\sources\boot.wim" -Index $IMAGE.ImageIndex -Path $WINPE_MOUNT -ErrorAction stop | Out-Null
|
||||
|
||||
# Add servicing stack update (Step 9 from the table)
|
||||
|
||||
@ -448,11 +458,11 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
# Windows 11, version 22H2 are examples. In these cases, the servicing stack update is not published separately; the combined
|
||||
# cumulative update should be used for this step. However, in hopefully rare cases, there may breaking change in the combined
|
||||
# cumulative update format, that requires a standalone servicing stack update to be published, and installed first before the
|
||||
# combined cumulative update can be installed.
|
||||
# combined cumulative update can be installed.
|
||||
|
||||
# This is the code to handle the rare case that the SSU is published and required for the combined cumulative update
|
||||
# Write-Output "$(Get-TS): Adding package $SSU_PATH"
|
||||
# Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
# Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
|
||||
# Now, attempt the combined cumulative update.
|
||||
# There is a known issue where the servicing stack update is installed, but the cumulative update will fail.
|
||||
@ -461,6 +471,7 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
|
||||
try
|
||||
{
|
||||
Write-Output "$(Get-TS): Adding package $LCU_PATH to WinPE, image index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $LCU_PATH | Out-Null
|
||||
}
|
||||
Catch
|
||||
@ -481,19 +492,17 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
# update. This second approach is commented out below.
|
||||
|
||||
# Write-Output "$(Get-TS): Adding package $SSU_PATH"
|
||||
# Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
# Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $SSU_PATH | Out-Null
|
||||
|
||||
# Install lp.cab cab
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_OC_LP_PATH"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $WINPE_OC_LP_PATH -ErrorAction stop | Out-Null
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_OC_LP_PATH to WinPE, image index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $WINPE_OC_LP_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
# Install language cabs for each optional package installed
|
||||
$WINPE_INSTALLED_OC = Get-WindowsPackage -Path $WINPE_MOUNT
|
||||
Foreach ($PACKAGE in $WINPE_INSTALLED_OC) {
|
||||
|
||||
if ( ($PACKAGE.PackageState -eq "Installed") `
|
||||
-and ($PACKAGE.PackageName.startsWith("WinPE-")) `
|
||||
-and ($PACKAGE.ReleaseType -eq "FeaturePack") ) {
|
||||
if ( ($PACKAGE.PackageState -eq "Installed") -and ($PACKAGE.PackageName.startsWith("WinPE-")) -and ($PACKAGE.ReleaseType -eq "FeaturePack") ) {
|
||||
|
||||
$INDEX = $PACKAGE.PackageName.IndexOf("-Package")
|
||||
if ($INDEX -ge 0) {
|
||||
@ -501,7 +510,7 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
$OC_CAB = $PACKAGE.PackageName.Substring(0, $INDEX) + "_" + $LANG + ".cab"
|
||||
if ($WINPE_OC_LANG_CABS.Contains($OC_CAB)) {
|
||||
$OC_CAB_PATH = Join-Path $WINPE_OC_LANG_PATH $OC_CAB
|
||||
Write-Output "$(Get-TS): Adding package $OC_CAB_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $OC_CAB_PATH to WinPE, image index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $OC_CAB_PATH -ErrorAction stop | Out-Null
|
||||
}
|
||||
}
|
||||
@ -510,7 +519,7 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
|
||||
# Add font support for the new language
|
||||
if ( (Test-Path -Path $WINPE_FONT_SUPPORT_PATH) ) {
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_FONT_SUPPORT_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_FONT_SUPPORT_PATH to WinPE, image index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $WINPE_FONT_SUPPORT_PATH -ErrorAction stop | Out-Null
|
||||
}
|
||||
|
||||
@ -518,10 +527,10 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
if (Test-Path -Path $WINPE_SPEECH_TTS_PATH) {
|
||||
if ( (Test-Path -Path $WINPE_SPEECH_TTS_LANG_PATH) ) {
|
||||
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_SPEECH_TTS_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_SPEECH_TTS_PATH to WinPE, image index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $WINPE_SPEECH_TTS_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_SPEECH_TTS_LANG_PATH"
|
||||
Write-Output "$(Get-TS): Adding package $WINPE_SPEECH_TTS_LANG_PATH to WinPE, image index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $WINPE_SPEECH_TTS_LANG_PATH -ErrorAction stop | Out-Null
|
||||
}
|
||||
}
|
||||
@ -533,11 +542,11 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
}
|
||||
|
||||
# Add latest cumulative update
|
||||
Write-Output "$(Get-TS): Adding package $LCU_PATH"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $LCU_PATH -ErrorAction stop | Out-Null
|
||||
Write-Output "$(Get-TS): Adding package $LCU_PATH to WinPE, image index $($IMAGE.ImageIndex)"
|
||||
Add-WindowsPackage -Path $WINPE_MOUNT -PackagePath $LCU_PATH -ErrorAction stop | Out-Null
|
||||
|
||||
# Perform image cleanup
|
||||
Write-Output "$(Get-TS): Performing image cleanup on WinPE"
|
||||
Write-Output "$(Get-TS): Performing image cleanup on WinPE, image index $($IMAGE.ImageIndex)"
|
||||
DISM /image:$WINPE_MOUNT /cleanup-image /StartComponentCleanup /ResetBase /Defer | Out-Null
|
||||
|
||||
if ($IMAGE.ImageIndex -eq "2") {
|
||||
@ -545,6 +554,18 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
# Save setup.exe for later use. This will address possible binary mismatch with the version in the main OS \sources folder
|
||||
Copy-Item -Path $WINPE_MOUNT"\sources\setup.exe" -Destination $WORKING_PATH"\setup.exe" -Force -ErrorAction stop | Out-Null
|
||||
|
||||
# Save setuphost.exe for later use. This will address possible binary mismatch with the version in the main OS \sources folder
|
||||
# This is only required starting with Windows 11 version 24H2
|
||||
$TEMP = Get-WindowsImage -ImagePath $MEDIA_NEW_PATH"\sources\boot.wim" -Index $IMAGE.ImageIndex
|
||||
if ([System.Version]$TEMP.Version -ge [System.Version]"10.0.26100") {
|
||||
|
||||
Copy-Item -Path $WINPE_MOUNT"\sources\setuphost.exe" -Destination $WORKING_PATH"\setuphost.exe" -Force -ErrorAction stop | Out-Null
|
||||
}
|
||||
else {
|
||||
|
||||
Write-Output "$(Get-TS): Skipping copy of setuphost.exe; image version $($TEMP.Version)"
|
||||
}
|
||||
|
||||
# Save serviced boot manager files later copy to the root media.
|
||||
Copy-Item -Path $WINPE_MOUNT"\Windows\boot\efi\bootmgfw.efi" -Destination $WORKING_PATH"\bootmgfw.efi" -Force -ErrorAction stop | Out-Null
|
||||
Copy-Item -Path $WINPE_MOUNT"\Windows\boot\efi\bootmgr.efi" -Destination $WORKING_PATH"\bootmgr.efi" -Force -ErrorAction stop | Out-Null
|
||||
@ -580,21 +601,26 @@ cmd.exe /c $env:SystemRoot\System32\expand.exe $SETUP_DU_PATH -F:* $MEDIA_NEW_PA
|
||||
Write-Output "$(Get-TS): Copying $WORKING_PATH\setup.exe to $MEDIA_NEW_PATH\sources\setup.exe"
|
||||
Copy-Item -Path $WORKING_PATH"\setup.exe" -Destination $MEDIA_NEW_PATH"\sources\setup.exe" -Force -ErrorAction stop | Out-Null
|
||||
|
||||
# Copy setuphost.exe from boot.wim, saved earlier.
|
||||
if (Test-Path -Path $WORKING_PATH"\setuphost.exe") {
|
||||
|
||||
Write-Output "$(Get-TS): Copying $WORKING_PATH\setuphost.exe to $MEDIA_NEW_PATH\sources\setuphost.exe"
|
||||
Copy-Item -Path $WORKING_PATH"\setuphost.exe" -Destination $MEDIA_NEW_PATH"\sources\setuphost.exe" -Force -ErrorAction stop | Out-Null
|
||||
}
|
||||
|
||||
# Copy bootmgr files from boot.wim, saved earlier.
|
||||
$MEDIA_NEW_FILES = Get-ChildItem $MEDIA_NEW_PATH -Force -Recurse -Filter b*.efi
|
||||
|
||||
Foreach ($File in $MEDIA_NEW_FILES){
|
||||
if (($File.Name -ieq "bootmgfw.efi") -or `
|
||||
($File.Name -ieq "bootx64.efi") -or `
|
||||
($File.Name -ieq "bootia32.efi") -or `
|
||||
($File.Name -ieq "bootaa64.efi"))
|
||||
if (($File.Name -ieq "bootmgfw.efi") -or ($File.Name -ieq "bootx64.efi") -or ($File.Name -ieq "bootia32.efi") -or ($File.Name -ieq "bootaa64.efi"))
|
||||
{
|
||||
|
||||
Write-Output "$(Get-TS): Copying $WORKING_PATH\bootmgfw.efi to $($File.FullName)"
|
||||
Copy-Item -Path $WORKING_PATH"\bootmgfw.efi" -Destination $File.FullName -Force -ErrorAction stop | Out-Null
|
||||
}
|
||||
elseif ($File.Name -ieq "bootmgr.efi")
|
||||
{
|
||||
|
||||
Write-Output "$(Get-TS): Copying $WORKING_PATH\bootmgr.efi to $($File.FullName)"
|
||||
Copy-Item -Path $WORKING_PATH"\bootmgr.efi" -Destination $File.FullName -Force -ErrorAction stop | Out-Null
|
||||
}
|
||||
|
||||
@ -1,63 +0,0 @@
|
||||
---
|
||||
title: Determine application readiness
|
||||
description: How to test your apps to identify which need attention prior to deploying an update in your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
# Determine application readiness
|
||||
|
||||
Before you deploy a Windows client update, you should know which apps will continue to work without problems, which need their own updates, and which just won't work and must be replaced. If you haven't already, it's worth [classifying your apps](plan-define-readiness.md) with respect to their criticality in your organization.
|
||||
|
||||
## Validation methods
|
||||
|
||||
You can choose from various methods to validate apps. Exactly which ones to use depends on the specifics of your environment.
|
||||
|
||||
|
||||
|Validation method |Description |
|
||||
|---------|---------|
|
||||
|Full regression | A full quality assurance probing. Staff that know the application well and can validate its core functionality should do this validation. |
|
||||
|Smoke testing | The application goes through formal validation. That is, a user validates the application following a detailed plan, ideally with limited, or no knowledge of the application they're validating. |
|
||||
|Automated testing | Software performs tests automatically. The software lets you know whether the tests have passed or failed, and provides detailed reporting for you automatically. |
|
||||
|Test in pilot | You preselect users to be in the pilot deployment group and carry out the same tasks they do on a day-to-day basis to validate the application. Normally you use this method in addition to one of the other validation types. |
|
||||
|Reactive response | Applications are validated in late pilot, and no specific users are selected. These applications normally aren't installed on many devices and aren't handled by enterprise application distribution. |
|
||||
|
||||
Combining the various validation methods with the app classifications you've previously established might look like this:
|
||||
|
||||
|
||||
|Validation method |Critical apps |Important apps |Not important apps |
|
||||
|---------|---------|---------|---------|
|
||||
|Full regression | x | | |
|
||||
|Smoke testing | | x | |
|
||||
|Automated testing | x | x | x |
|
||||
|Test in pilot | x | x | x |
|
||||
|
||||
|
||||
### Identify users
|
||||
|
||||
Since your organization no doubt has a wide variety of users, each with different background and regular tasks, you have to choose which users are best suited for validation testing. Some factors to consider include:
|
||||
|
||||
- **Location**: If users are in different physical locations, can you support them and get validation feedback from the region they're in?
|
||||
- **Application knowledge**: Do the users have appropriate knowledge of how the app is supposed to work?
|
||||
- **Technical ability**: Do the users have enough technical competence to provide useful feedback from various test scenarios?
|
||||
|
||||
You could seek volunteers who enjoy working with new features and include them in the pilot deployment. You might want to avoid using core users like department heads or project managers. Current application owners, operations personnel, and developers can help you identify the most appropriate pilot users.
|
||||
|
||||
### Identify and set up devices for validation
|
||||
|
||||
In addition to users, it's important to carefully choose devices to participate in app validation as well. For example, ideally, your selection includes devices representing all of the hardware models in your environment.
|
||||
|
||||
There's more than one way to choose devices for app validation:
|
||||
|
||||
- **Existing pilot devices**: You might already have a list of devices that you regularly use for testing updates as part of release cycles.
|
||||
- **Manual selection**: Some internal groups like operations have expertise to help choose devices manually based on specifications, usage, or records of past support problems.
|
||||
- **Data-driven analysis**: With appropriate tools, you can use diagnostic data from devices to inform your choices.
|
||||
@ -1,14 +1,14 @@
|
||||
---
|
||||
title: Prepare to deploy Windows
|
||||
description: Final steps to get ready to deploy Windows, including preparing infrastructure, environment, applications, devices, network, capability, and users
|
||||
description: Final steps to get ready to deploy Windows, including preparing infrastructure, environment, applications, devices, network, capability, and users.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 12/31/2017
|
||||
@ -19,7 +19,7 @@ ms.date: 12/31/2017
|
||||
Having worked through the activities in the planning phase, you should be in a good position to prepare your environment and process to deploy Windows client. The planning phase left you with these useful items:
|
||||
|
||||
- A clear understanding of necessary personnel and their roles and criteria for [rating app readiness](plan-define-readiness.md)
|
||||
- A plan for [testing and validating](plan-determine-app-readiness.md) apps
|
||||
- A plan for [testing and validating](/windows/compatibility/windows-11/testing-guidelines) apps
|
||||
- An assessment of your [deployment infrastructure](eval-infra-tools.md) and definitions for operational readiness
|
||||
- A [deployment plan](create-deployment-plan.md) that defines the rings you want to use
|
||||
|
||||
@ -35,7 +35,7 @@ Your infrastructure probably includes many different components and tools. You n
|
||||
|
||||
1. Review all of the infrastructure changes that you've identified in your plan. It's important to understand the changes that need to be made and to detail how to implement them. This process prevents problems later on.
|
||||
|
||||
2. Validate your changes. You validate the changes for your infrastructure's components and tools, to help you understand how your changes could affect your production environment.
|
||||
2. Validate your changes. You validate the changes for your infrastructure's components and tools, to help you understand how your changes could affect your production environment.
|
||||
|
||||
3. Implement the changes. Once the changes have been validated, you can implement the changes across the wider infrastructure.
|
||||
|
||||
@ -166,11 +166,11 @@ You can also create and run scripts to perform additional cleanup actions on dev
|
||||
|
||||
In the plan phase, you determined the specific infrastructure and configuration changes that needed to be implemented to add new capabilities to the environment. Now you can move on to implementing those changes defined in the plan phase. You need to complete these higher-level tasks to gain those new capabilities:
|
||||
|
||||
- Enable capabilities across the environment by implementing the changes. For example, implement updates to relevant ADMX templates in Active Directory. New Windows versions come with new policies that you use to update ADMX templates.
|
||||
- Enable capabilities across the environment by implementing the changes. For example, implement updates to relevant ADMX templates in Active Directory. New Windows versions come with new policies that you use to update ADMX templates.
|
||||
|
||||
- Validate new changes to understand how they affect the wider environment.
|
||||
|
||||
- Remediate any potential problems that have been identified through validation.
|
||||
- Remediate any potential problems that have been identified through validation.
|
||||
|
||||
## Prepare users
|
||||
|
||||
|
||||
@ -44,10 +44,10 @@ For more information, see [Assign devices to servicing channels for Windows clie
|
||||
|
||||
## Staying up to date
|
||||
|
||||
To stay up to date, deploy feature updates at an appropriate time after their release. You can use various management and update tools such as Windows Update, Windows Update for Business, Windows Server Update Services, Microsoft Configuration Manager, and non-Microsoft products to help with this process. [Upgrade Readiness](/windows/deployment/upgrade/upgrade-readiness-get-started), a free tool to streamline Windows upgrade projects, is another important tool to help.
|
||||
To stay up to date, deploy feature updates at an appropriate time after their release. You can use various management and update tools such as Windows Update, Windows Update for Business, Windows Server Update Services, Microsoft Configuration Manager, and non-Microsoft products to help with this process.
|
||||
|
||||
Extensive advanced testing isn't required. Instead, only business-critical apps need to be tested, with the remaining apps validated through a series of pilot deployment rings. Once these pilot deployments have validated most apps, broad deployment can begin.
|
||||
|
||||
This process repeats with each new feature update. These are small deployment projects, compared to the large projects that were necessary with the old three-to-five-year Windows release cycles.
|
||||
|
||||
Other technologies such as BranchCache and Delivery Optimization, both peer-to-peer distribution tools, can help with the distribution of the feature update installation files.
|
||||
Other technologies such as [BranchCache](waas-branchcache.md) and [Delivery Optimization](../do/waas-delivery-optimization-setup.md), both peer-to-peer distribution tools, can help with the distribution of the feature update installation files.
|
||||
|
||||
@ -4,7 +4,7 @@ titleSuffix: Windows Update for Business reports
|
||||
description: Windows Update for Business reports support, feedback, and troubleshooting information.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -5,7 +5,7 @@ ms.author: frankroj
|
||||
description: Resolve Windows upgrade errors for ITPros. Technical information for IT professionals to help diagnose Windows setup errors.
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 01/18/2024
|
||||
|
||||
@ -6,7 +6,7 @@ description: Download the Feedback Hub app, and then submit Windows upgrade erro
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 01/18/2024
|
||||
appliesto:
|
||||
|
||||
@ -6,7 +6,7 @@ description: Learn how to review the events generated by Windows Error Reporting
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 01/18/2024
|
||||
appliesto:
|
||||
|
||||
@ -5,7 +5,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 08/09/2023
|
||||
---
|
||||
@ -37,13 +37,13 @@ You can use USMT to automate migration during large deployments of the Windows o
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> USMT only supports devices that are joined to a local Active Directory domain. USMT doesn't support Microsoft Entra joined devices.
|
||||
> USMT only supports devices that are joined to a local Active Directory domain. USMT doesn't support Microsoft Entra joined devices.
|
||||
|
||||
## Upgrade and migration considerations
|
||||
Whether you're upgrading or migrating to a new version of Windows, you must be aware of the following issues and considerations:
|
||||
|
||||
### Application compatibility
|
||||
For more information about application compatibility in Windows, see [Use Upgrade Readiness to manage Windows upgrades](/windows/deployment/upgrade/use-upgrade-readiness-to-manage-windows-upgrades).
|
||||
For more information about application compatibility in Windows, see [Windows compatibility cookbook](/windows/compatibility/).
|
||||
|
||||
### Multilingual Windows image upgrades
|
||||
When performing multilingual Windows upgrades, cross-language upgrades aren't supported by USMT. If you're upgrading or migrating an operating system with multiple language packs installed, you can upgrade or migrate only to the system default user interface (UI) language. For example, if English is the default but you have a Spanish language pack installed, you can upgrade or migrate only to English.
|
||||
@ -58,11 +58,9 @@ During the configuration pass of Windows Setup, the root access control list (AC
|
||||
|
||||
Changing the ACLs may affect the performance of Windows Setup if the default Windows XP ACLs are applied to a partition with a large amount of data. Because of these performance concerns, you can change the following registry value to disable this feature:
|
||||
|
||||
``` syntax
|
||||
Key: HKLM\System\Setup
|
||||
Type: REG_DWORD
|
||||
Value: "DDACLSys_Disabled" = 1
|
||||
```
|
||||
`Key: HKLM\System\Setup`
|
||||
`Type: REG_DWORD`
|
||||
`Value: "DDACLSys_Disabled" = 1`
|
||||
|
||||
This feature is disabled if this registry key value exists and is configured to `1`.
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 01/09/2024
|
||||
appliesto:
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -6,7 +6,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 01/09/2024
|
||||
appliesto:
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -6,7 +6,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 01/09/2024
|
||||
appliesto:
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -6,7 +6,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
ms.localizationpriority: medium
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 01/09/2024
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user