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

Merge branch 'main' into release-win11-24h2

Browse Source
This commit is contained in:
Alma Jenks 2024-08-28 23:05:12 +00:00
commit 620da57647
10 changed files with 596 additions and 779 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.openpublishing.redirection.json
View File

@ -2477,7 +2477,7 @@
}, },
{ {
"source_path": "windows/deploy/windows-10-upgrade-paths.md", "source_path": "windows/deploy/windows-10-upgrade-paths.md",
"redirect_url": "/windows/deployment/upgrade/windows-10-upgrade-paths", "redirect_url": "/windows/deployment/upgrade/windows-upgrade-paths",
"redirect_document_id": false "redirect_document_id": false
}, },
{ {

10
.openpublishing.redirection.windows-deployment.json
View File

@ -1594,6 +1594,16 @@
"source_path": "windows/deployment/windows-autopatch/references/windows-autopatch-windows-update-unsupported-policies.md", "source_path": "windows/deployment/windows-autopatch/references/windows-autopatch-windows-update-unsupported-policies.md",
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-update-policies", "redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-update-policies",
"redirect_document_id": false "redirect_document_id": false
},
{
"source_path": "windows/deployment/update/PSFxWhitepaper.md",
"redirect_url": "/windows/deployment/update/forward-reverse-differentials",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/upgrade/windows-10-upgrade-paths.md",
"redirect_url": "/windows/deployment/upgrade/windows-upgrade-paths",
"redirect_document_id": false
} }
] ]
} }

428
windows/deployment/TOC.yml
View File

@ -1,10 +1,10 @@
items: items:
- name: Deploy and update Windows client - name: Deploy and update Windows
href: index.yml href: index.yml
items: items:
- name: Get started - name: Get started
items: items:
- name: Windows client deployment scenarios - name: Windows deployment scenarios
href: windows-deployment-scenarios.md href: windows-deployment-scenarios.md
- name: Quick guide to Windows as a service - name: Quick guide to Windows as a service
href: update/waas-quick-start.md href: update/waas-quick-start.md
@ -16,7 +16,7 @@ items:
href: update/get-started-updates-channels-tools.md href: update/get-started-updates-channels-tools.md
- name: Defining Windows update-managed devices - name: Defining Windows update-managed devices
href: update/update-managed-unmanaged-devices.md href: update/update-managed-unmanaged-devices.md
- name: Prepare servicing strategy for Windows client updates - name: Prepare servicing strategy for Windows updates
href: update/waas-servicing-strategy-windows-10-updates.md href: update/waas-servicing-strategy-windows-10-updates.md
- name: Plan - name: Plan
@ -31,80 +31,62 @@ items:
href: update/eval-infra-tools.md href: update/eval-infra-tools.md
- name: Define your servicing strategy - name: Define your servicing strategy
href: update/plan-define-strategy.md href: update/plan-define-strategy.md
- name: Delivery Optimization for Windows client updates - name: Windows Update security
href: update/windows-update-security.md
- name: Windows upgrade and migration considerations
href: upgrade/windows-upgrade-and-migration-considerations.md
- name: Delivery Optimization for Windows updates
href: do/waas-delivery-optimization.md?context=/windows/deployment/context/context href: do/waas-delivery-optimization.md?context=/windows/deployment/context/context
items:
- name: Using a proxy with Delivery Optimization
href: do/delivery-optimization-proxy.md?context=/windows/deployment/context/context
- name: Delivery Optimization client-service communication
href: do/delivery-optimization-workflow.md?context=/windows/deployment/context/context
- name: Windows 10 deployment considerations - name: Windows 10 deployment considerations
href: planning/windows-10-deployment-considerations.md href: planning/windows-10-deployment-considerations.md
- name: Windows 10 infrastructure requirements - name: Windows 10 infrastructure requirements
href: planning/windows-10-infrastructure-requirements.md 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 - name: Windows compatibility cookbook
href: /windows/compatibility/ href: /windows/compatibility/
- name: Features removed or planned for replacement
items:
- name: Windows client features lifecycle
href: /windows/whats-new/feature-lifecycle?context=/windows/deployment/context/context
- name: Deprecated features
href: /windows/whats-new/deprecated-features?context=/windows/deployment/context/context
- name: Resources for deprecated features
href: /windows/whats-new/deprecated-features-resources?context=/windows/deployment/context/context
- name: Removed features
href: /windows/whats-new/removed-features?context=/windows/deployment/context/context
- name: Prepare - name: Prepare
items: items:
- name: Prepare for Windows 11 - name: Prepare for Windows 11
href: /windows/whats-new/windows-11-prepare?context=/windows/deployment/context/context href: /windows/whats-new/windows-11-prepare?context=/windows/deployment/context/context
- name: Prepare to deploy Windows client updates - name: Prepare to deploy Windows updates
href: update/prepare-deploy-windows.md href: update/prepare-deploy-windows.md
- name: Evaluate and update infrastructure - name: Evaluate and update infrastructure
href: update/update-policies.md href: update/update-policies.md
- name: Update Baseline - name: Update baseline
href: update/update-baseline.md href: update/update-baseline.md
- name: Set up Delivery Optimization for Windows client updates - name: Set up Delivery Optimization for Windows updates
href: do/delivery-optimization-configure.md?context=/windows/deployment/context/context href: do/delivery-optimization-configure.md?context=/windows/deployment/context/context
- name: Configure BranchCache for Windows client updates - name: Configure BranchCache for Windows updates
href: update/waas-branchcache.md href: update/waas-branchcache.md
- name: Prepare for deployment with Configuration Manager - name: Prepare for deployment with Configuration Manager
href: /previous-versions/windows/it-pro/windows-10/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager href: /previous-versions/windows/it-pro/windows-10/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager
- name: Build a successful servicing strategy - name: Check release health
items: href: update/check-release-health.md
- name: Check release health
href: update/check-release-health.md
- name: Prepare updates using Windows Update for Business
href: update/waas-manage-updates-wufb.md
- name: Prepare updates using WSUS
href: update/waas-manage-updates-wsus.md
- name: Deploy - name: Deploy
items: items:
- name: Deploy Windows client - name: Deploy Windows
items: items:
- name: Deploy Windows client with Autopilot - name: Deploy Windows with Autopilot
href: /autopilot/ href: /autopilot/
- name: Windows deployment scenarios and tools - name: Windows deployment scenarios and tools
href: windows-deployment-scenarios-and-tools.md href: windows-deployment-scenarios-and-tools.md
- name: Deploy Windows client updates - name: Deploy Windows updates
items: items:
- name: Assign devices to servicing channels - name: Assign devices to servicing channels
href: update/waas-servicing-channels-windows-10-updates.md href: update/waas-servicing-channels-windows-10-updates.md
- name: Deploy updates with WSUS - name: Deploy updates with WSUS
href: update/waas-manage-updates-wsus.md href: update/waas-manage-updates-wsus.md
- name: Deploy updates with Group Policy - name: Update Windows media with dynamic update
href: update/waas-wufb-group-policy.md
- name: Deploy updates using CSPs and MDM
href: update/waas-wufb-csp-mdm.md
- name: Update Windows client media with Dynamic Update
href: update/media-dynamic-update.md href: update/media-dynamic-update.md
- name: Migrating and acquiring optional Windows content - name: Migrating and acquiring optional Windows content
href: update/optional-content.md href: update/optional-content.md
- name: Deploy feature updates for user-initiated installations
href: update/feature-update-user-install.md
- name: Safeguard holds - name: Safeguard holds
href: update/safeguard-holds.md items:
- name: Safeguard holds
href: update/safeguard-holds.md
- name: Opt out of safeguard holds
href: update/safeguard-opt-out.md
- name: Manage the Windows client update experience - name: Manage the Windows client update experience
items: items:
- name: Manage device restarts after updates - name: Manage device restarts after updates
@ -123,7 +105,7 @@ items:
href: update/wufb-compliancedeadlines.md href: update/wufb-compliancedeadlines.md
- name: Integrate Windows Update for Business with management solutions - name: Integrate Windows Update for Business with management solutions
href: update/waas-integrate-wufb.md href: update/waas-integrate-wufb.md
- name: 'Walkthrough: use Group Policy to configure Windows Update for Business' - name: Use group policy to configure Windows Update for Business
href: update/waas-wufb-group-policy.md href: update/waas-wufb-group-policy.md
- name: Deploy updates using CSPs and MDM - name: Deploy updates using CSPs and MDM
href: update/waas-wufb-csp-mdm.md href: update/waas-wufb-csp-mdm.md
@ -235,59 +217,57 @@ items:
href: volume-activation/vamt-known-issues.md href: volume-activation/vamt-known-issues.md
- name: Monitor - name: Monitor
items: items:
- name: Windows Update for Business reports - name: Windows Update for Business reports overview
href: update/wufb-reports-overview.md
- name: Enable Windows Update for Business reports
items: items:
- name: Windows Update for Business reports overview - name: Windows Update for Business reports prerequisites
href: update/wufb-reports-overview.md href: update/wufb-reports-prerequisites.md
- name: Enable Windows Update for Business reports - name: Enable Windows Update for Business reports
items: href: update/wufb-reports-enable.md
- name: Windows Update for Business reports prerequisites - name: Configure clients with a script
href: update/wufb-reports-prerequisites.md href: update/wufb-reports-configuration-script.md
- name: Enable Windows Update for Business reports - name: Configure clients manually
href: update/wufb-reports-enable.md href: update/wufb-reports-configuration-manual.md
- name: Configure clients with a script - name: Configure clients with Microsoft Intune
href: update/wufb-reports-configuration-script.md href: update/wufb-reports-configuration-intune.md
- name: Configure clients manually - name: Use Windows Update for Business reports
href: update/wufb-reports-configuration-manual.md items:
- name: Configure clients with Microsoft Intune - name: Windows Update for Business reports workbook
href: update/wufb-reports-configuration-intune.md href: update/wufb-reports-workbook.md
- name: Use Windows Update for Business reports - name: Delivery Optimization data in reports
items: href: update/wufb-reports-do.md
- name: Windows Update for Business reports workbook - name: Software updates in the Microsoft 365 admin center
href: update/wufb-reports-workbook.md href: update/wufb-reports-admin-center.md
- name: Delivery Optimization data in reports - name: Use Windows Update for Business reports data
href: update/wufb-reports-do.md href: update/wufb-reports-use.md
- name: Software updates in the Microsoft 365 admin center - name: FAQ for Windows Update for Business reports
href: update/wufb-reports-admin-center.md href: update/wufb-reports-faq.yml
- name: Use Windows Update for Business reports data - name: Feedback and support
href: update/wufb-reports-use.md href: update/wufb-reports-help.md
- name: FAQ for Windows Update for Business reports - name: Windows Update for Business reports schema reference
href: update/wufb-reports-faq.yml items:
- name: Feedback and support
href: update/wufb-reports-help.md
- name: Windows Update for Business reports schema reference - name: Windows Update for Business reports schema reference
items: href: update/wufb-reports-schema.md
- name: Windows Update for Business reports schema reference - name: UCClient
href: update/wufb-reports-schema.md href: update/wufb-reports-schema-ucclient.md
- name: UCClient - name: UCClientReadinessStatus
href: update/wufb-reports-schema-ucclient.md href: update/wufb-reports-schema-ucclientreadinessstatus.md
- name: UCClientReadinessStatus - name: UCClientUpdateStatus
href: update/wufb-reports-schema-ucclientreadinessstatus.md href: update/wufb-reports-schema-ucclientupdatestatus.md
- name: UCClientUpdateStatus - name: UCDeviceAlert
href: update/wufb-reports-schema-ucclientupdatestatus.md href: update/wufb-reports-schema-ucdevicealert.md
- name: UCDeviceAlert - name: UCDOAggregatedStatus
href: update/wufb-reports-schema-ucdevicealert.md href: update/wufb-reports-schema-ucdoaggregatedstatus.md
- name: UCDOAggregatedStatus - name: UCDOStatus
href: update/wufb-reports-schema-ucdoaggregatedstatus.md href: update/wufb-reports-schema-ucdostatus.md
- name: UCDOStatus - name: UCServiceUpdateStatus
href: update/wufb-reports-schema-ucdostatus.md href: update/wufb-reports-schema-ucserviceupdatestatus.md
- name: UCServiceUpdateStatus - name: UCUpdateAlert
href: update/wufb-reports-schema-ucserviceupdatestatus.md href: update/wufb-reports-schema-ucupdatealert.md
- name: UCUpdateAlert - name: Enumerated types
href: update/wufb-reports-schema-ucupdatealert.md href: update/wufb-reports-schema-enumerated-types.md
- name: Enumerated types - name: Troubleshoot
href: update/wufb-reports-schema-enumerated-types.md
- name: Troubleshooting
items: items:
- name: Resolve upgrade errors - name: Resolve upgrade errors
items: items:
@ -303,28 +283,20 @@ items:
href: upgrade/windows-error-reporting.md href: upgrade/windows-error-reporting.md
- name: Upgrade error codes - name: Upgrade error codes
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?context=/windows/deployment/context/context href: /troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?context=/windows/deployment/context/context
- name: Log files - name: Upgrade log files
href: upgrade/log-files.md href: upgrade/log-files.md
- name: Resolution procedures - name: Resolution procedures
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?context=/windows/deployment/context/context href: /troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?context=/windows/deployment/context/context
- name: Submit Windows client upgrade errors - name: Submit Windows upgrade errors
href: upgrade/submit-errors.md href: upgrade/submit-errors.md
- name: Troubleshoot Windows Update - name: Troubleshoot Windows Update
items: items:
- name: How to troubleshoot Windows Update - name: How to troubleshoot Windows Update
href: /troubleshoot/windows-client/deployment/windows-update-issues-troubleshooting?context=/windows/deployment/context/context href: /troubleshoot/windows-client/deployment/windows-update-issues-troubleshooting?context=/windows/deployment/context/context
- name: Opt out of safeguard holds
href: update/safeguard-opt-out.md
- name: Determine the source of Windows Updates
href: ./update/how-windows-update-works.md
- name: Windows Update security
href: ./update/windows-update-security.md
- name: Common Windows Update errors - name: Common Windows Update errors
href: /troubleshoot/windows-client/deployment/common-windows-update-errors?context=/windows/deployment/context/context href: /troubleshoot/windows-client/deployment/common-windows-update-errors?context=/windows/deployment/context/context
- name: Windows Update error code reference - name: Windows Update error code reference
href: update/windows-update-error-reference.md href: update/windows-update-error-reference.md
- name: Troubleshoot the Windows Update for Business deployment service
href: update/deployment-service-troubleshoot.md
- name: Reference - name: Reference
items: items:
@ -338,142 +310,138 @@ items:
href: deploy-m365.md href: deploy-m365.md
- name: Understand the Unified Update Platform - name: Understand the Unified Update Platform
href: update/windows-update-overview.md href: update/windows-update-overview.md
- name: Windows Update log files
href: update/windows-update-logs.md
- name: Servicing stack updates - name: Servicing stack updates
href: update/servicing-stack-updates.md href: update/servicing-stack-updates.md
- name: Update CSP policies - name: Update CSP policies
href: /windows/client-management/mdm/policy-csp-update?context=/windows/deployment/context/context href: /windows/client-management/mdm/policy-csp-update?context=/windows/deployment/context/context
- name: Additional Windows Update settings
href: update/waas-wu-settings.md
- name: Update other Microsoft products - name: Update other Microsoft products
href: update/update-other-microsoft-products.md href: update/update-other-microsoft-products.md
- name: Delivery Optimization reference - name: Delivery Optimization reference
href: do/waas-delivery-optimization-reference.md?context=/windows/deployment/context/context href: do/waas-delivery-optimization-reference.md?context=/windows/deployment/context/context
- name: FoD and language packs for WSUS and Configuration Manager - name: Features on Demand and language packs
href: update/fod-and-lang-packs.md href: update/fod-and-lang-packs.md
- name: Windows client deployment tools
items:
- name: Windows client deployment scenarios and tools
items:
- name: Windows Deployment Services (WDS) boot.wim support
href: wds-boot-support.md
- name: Convert MBR partition to GPT
href: mbr-to-gpt.md
- name: Configure a PXE server to load Windows PE
href: configure-a-pxe-server-to-load-windows-pe.md
- name: Windows ADK for Windows 10 scenarios for IT Pros
href: windows-adk-scenarios-for-it-pros.md
- name: User State Migration Tool (USMT) technical reference
items:
- name: USMT overview articles
items:
- name: USMT overview
href: usmt/usmt-overview.md
- name: Getting started with the USMT
href: usmt/getting-started-with-the-user-state-migration-tool.md
- name: Windows upgrade and migration considerations
href: upgrade/windows-upgrade-and-migration-considerations.md
- name: USMT How-to articles
items:
- name: Exclude Files and Settings
href: usmt/usmt-exclude-files-and-settings.md
- name: Extract Files from a Compressed USMT Migration Store
href: usmt/usmt-extract-files-from-a-compressed-migration-store.md
- name: Include Files and Settings
href: usmt/usmt-include-files-and-settings.md
- name: Migrate Application Settings
href: usmt/migrate-application-settings.md
- name: Migrate EFS Files and Certificates
href: usmt/usmt-migrate-efs-files-and-certificates.md
- name: Migrate User Accounts
href: usmt/usmt-migrate-user-accounts.md
- name: Reroute Files and Settings
href: usmt/usmt-reroute-files-and-settings.md
- name: Verify the Condition of a Compressed Migration Store
href: usmt/verify-the-condition-of-a-compressed-migration-store.md
- name: USMT Reference
items:
- name: USMT Requirements
href: usmt/usmt-requirements.md
- name: USMT Best Practices
href: usmt/usmt-best-practices.md
- name: How USMT Works
href: usmt/usmt-how-it-works.md
- name: Plan Your Migration
href: usmt/usmt-plan-your-migration.md
- name: Common Migration Scenarios
href: usmt/usmt-common-migration-scenarios.md
- name: What Does USMT Migrate?
href: usmt/usmt-what-does-usmt-migrate.md
- name: Choose a Migration Store Type
href: usmt/usmt-choose-migration-store-type.md
- name: Migration Store Types Overview
href: usmt/migration-store-types-overview.md
- name: Estimate Migration Store Size
href: usmt/usmt-estimate-migration-store-size.md
- name: Hard-Link Migration Store
href: usmt/usmt-hard-link-migration-store.md
- name: Migration Store Encryption
href: usmt/usmt-migration-store-encryption.md
- name: Determine What to Migrate
href: usmt/usmt-determine-what-to-migrate.md
- name: Identify users
href: usmt/usmt-identify-users.md
- name: Identify Applications Settings
href: usmt/usmt-identify-application-settings.md
- name: Identify Operating System Settings
href: usmt/usmt-identify-operating-system-settings.md
- name: Identify File Types, Files, and Folders
href: usmt/usmt-identify-file-types-files-and-folders.md
- name: Test Your Migration
href: usmt/usmt-test-your-migration.md
- name: USMT Command-line Syntax
href: usmt/usmt-command-line-syntax.md
- name: ScanState Syntax
href: usmt/usmt-scanstate-syntax.md
- name: LoadState Syntax
href: usmt/usmt-loadstate-syntax.md
- name: UsmtUtils Syntax
href: usmt/usmt-utilities.md
- name: USMT XML Reference
href: usmt/usmt-xml-reference.md
- name: Understanding Migration XML Files
href: usmt/understanding-migration-xml-files.md
- name: Config.xml File
href: usmt/usmt-configxml-file.md
- name: Customize USMT XML Files
href: usmt/usmt-customize-xml-files.md
- name: Custom XML Examples
href: usmt/usmt-custom-xml-examples.md
- name: Conflicts and Precedence
href: usmt/usmt-conflicts-and-precedence.md
- name: General Conventions
href: usmt/usmt-general-conventions.md
- name: XML File Requirements
href: usmt/xml-file-requirements.md
- name: Recognized Environment Variables
href: usmt/usmt-recognized-environment-variables.md
- name: XML Elements Library
href: usmt/usmt-xml-elements-library.md
- name: Offline Migration Reference
href: usmt/offline-migration-reference.md
- name: Troubleshoot USMT
items:
- name: USMT Troubleshooting
href: usmt/usmt-troubleshooting.md
- name: USMT Common Issues
href: /troubleshoot/windows-client/deployment/usmt-common-issues
- name: USMT Frequently Asked Questions
href: usmt/usmt-faq.yml
- name: USMT Log Files
href: usmt/usmt-log-files.md
- name: USMT Return Codes
href: /troubleshoot/windows-client/deployment/usmt-return-codes
- name: USMT Resources
href: usmt/usmt-resources.md
- name: Add fonts in Windows - name: Add fonts in Windows
href: windows-missing-fonts.md href: windows-missing-fonts.md
- name: Windows Updates using forward and reverse differentials
href: update/forward-reverse-differentials.md
- name: Deployment tools
items:
- name: Customize Windows PE boot images - name: Customize Windows PE boot images
href: customize-boot-image.md href: customize-boot-image.md
- name: Convert MBR partition to GPT
href: mbr-to-gpt.md
- name: Configure a PXE server to load Windows PE
href: configure-a-pxe-server-to-load-windows-pe.md
- name: Windows Deployment Services (WDS) boot.wim support
href: wds-boot-support.md
- name: Windows ADK for Windows 10 scenarios for IT Pros
href: windows-adk-scenarios-for-it-pros.md
- name: User State Migration Tool (USMT) technical reference
items:
- name: USMT overview articles
items:
- name: USMT overview
href: usmt/usmt-overview.md
- name: Getting started with the USMT
href: usmt/getting-started-with-the-user-state-migration-tool.md
- name: USMT How-to articles
items:
- name: Exclude Files and Settings
href: usmt/usmt-exclude-files-and-settings.md
- name: Extract Files from a Compressed USMT Migration Store
href: usmt/usmt-extract-files-from-a-compressed-migration-store.md
- name: Include Files and Settings
href: usmt/usmt-include-files-and-settings.md
- name: Migrate Application Settings
href: usmt/migrate-application-settings.md
- name: Migrate EFS Files and Certificates
href: usmt/usmt-migrate-efs-files-and-certificates.md
- name: Migrate User Accounts
href: usmt/usmt-migrate-user-accounts.md
- name: Reroute Files and Settings
href: usmt/usmt-reroute-files-and-settings.md
- name: Verify the Condition of a Compressed Migration Store
href: usmt/verify-the-condition-of-a-compressed-migration-store.md
- name: USMT Reference
items:
- name: USMT Requirements
href: usmt/usmt-requirements.md
- name: USMT Best Practices
href: usmt/usmt-best-practices.md
- name: How USMT Works
href: usmt/usmt-how-it-works.md
- name: Plan Your Migration
href: usmt/usmt-plan-your-migration.md
- name: Common Migration Scenarios
href: usmt/usmt-common-migration-scenarios.md
- name: What Does USMT Migrate?
href: usmt/usmt-what-does-usmt-migrate.md
- name: Choose a Migration Store Type
href: usmt/usmt-choose-migration-store-type.md
- name: Migration Store Types Overview
href: usmt/migration-store-types-overview.md
- name: Estimate Migration Store Size
href: usmt/usmt-estimate-migration-store-size.md
- name: Hard-Link Migration Store
href: usmt/usmt-hard-link-migration-store.md
- name: Migration Store Encryption
href: usmt/usmt-migration-store-encryption.md
- name: Determine What to Migrate
href: usmt/usmt-determine-what-to-migrate.md
- name: Identify users
href: usmt/usmt-identify-users.md
- name: Identify Applications Settings
href: usmt/usmt-identify-application-settings.md
- name: Identify Operating System Settings
href: usmt/usmt-identify-operating-system-settings.md
- name: Identify File Types, Files, and Folders
href: usmt/usmt-identify-file-types-files-and-folders.md
- name: Test Your Migration
href: usmt/usmt-test-your-migration.md
- name: USMT Command-line Syntax
href: usmt/usmt-command-line-syntax.md
- name: ScanState Syntax
href: usmt/usmt-scanstate-syntax.md
- name: LoadState Syntax
href: usmt/usmt-loadstate-syntax.md
- name: UsmtUtils Syntax
href: usmt/usmt-utilities.md
- name: USMT XML Reference
href: usmt/usmt-xml-reference.md
- name: Understanding Migration XML Files
href: usmt/understanding-migration-xml-files.md
- name: Config.xml File
href: usmt/usmt-configxml-file.md
- name: Customize USMT XML Files
href: usmt/usmt-customize-xml-files.md
- name: Custom XML Examples
href: usmt/usmt-custom-xml-examples.md
- name: Conflicts and Precedence
href: usmt/usmt-conflicts-and-precedence.md
- name: General Conventions
href: usmt/usmt-general-conventions.md
- name: XML File Requirements
href: usmt/xml-file-requirements.md
- name: Recognized Environment Variables
href: usmt/usmt-recognized-environment-variables.md
- name: XML Elements Library
href: usmt/usmt-xml-elements-library.md
- name: Offline Migration Reference
href: usmt/offline-migration-reference.md
- name: Troubleshoot USMT
items:
- name: USMT Troubleshooting
href: usmt/usmt-troubleshooting.md
- name: USMT Common Issues
href: /troubleshoot/windows-client/deployment/usmt-common-issues
- name: USMT Frequently Asked Questions
href: usmt/usmt-faq.yml
- name: USMT Log Files
href: usmt/usmt-log-files.md
- name: USMT Return Codes
href: /troubleshoot/windows-client/deployment/usmt-return-codes
- name: USMT Resources
href: usmt/usmt-resources.md

123
windows/deployment/index.yml
View File

@ -1,11 +1,11 @@
### YamlMime:Landing ### YamlMime:Landing
title: Deploy and update Windows # < 60 chars; shows at top of hub page title: Windows deployment documentation # < 60 chars; shows at top of hub page
summary: Learn about deploying and updating Windows client devices in your organization. # < 160 chars summary: Learn about deploying and updating Windows devices in your organization. # < 160 chars
metadata: metadata:
title: Windows client deployment documentation # Required; browser tab title displayed in search results. Include the brand. < 60 chars. title: Windows deployment documentation # Required; browser tab title displayed in search results. Include the brand. < 60 chars.
description: Learn about deploying and updating Windows client devices in your organization. # Required; article description that is displayed in search results. < 160 chars. description: Learn about deploying and updating Windows devices in your organization. # Required; article description that is displayed in search results. < 160 chars.
ms.topic: landing-page ms.topic: landing-page
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-deploy ms.subservice: itpro-deploy
@ -15,7 +15,7 @@ metadata:
author: aczechowski author: aczechowski
ms.author: aaroncz ms.author: aaroncz
manager: aaroncz manager: aaroncz
ms.date: 08/22/2024 ms.date: 08/27/2024
ms.localizationpriority: medium ms.localizationpriority: medium
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
@ -30,10 +30,6 @@ landingContent:
url: /windows/whats-new/windows-11-plan?context=/windows/deployment/context/context url: /windows/whats-new/windows-11-plan?context=/windows/deployment/context/context
- text: Create a deployment plan - text: Create a deployment plan
url: update/create-deployment-plan.md url: update/create-deployment-plan.md
- text: Define readiness criteria
url: update/plan-define-readiness.md
- text: Define your servicing strategy
url: update/plan-define-strategy.md
- text: Plan for volume activation - text: Plan for volume activation
url: volume-activation/plan-for-volume-activation-client.md url: volume-activation/plan-for-volume-activation-client.md
- text: Windows compatibility cookbook - text: Windows compatibility cookbook
@ -47,125 +43,80 @@ landingContent:
url: /windows/whats-new/windows-11-prepare?context=/windows/deployment/context/context url: /windows/whats-new/windows-11-prepare?context=/windows/deployment/context/context
- text: Prepare to deploy Windows updates - text: Prepare to deploy Windows updates
url: update/prepare-deploy-windows.md url: update/prepare-deploy-windows.md
- text: Prepare updates using Windows Update for Business - text: Prepare for Windows Update for Business
url: update/waas-manage-updates-wufb.md url: update/waas-manage-updates-wufb.md
- text: Evaluate and update infrastructure - text: Evaluate and update infrastructure
url: update/update-policies.md url: update/update-policies.md
- text: Set up Delivery Optimization for Windows client updates
url: do/delivery-optimization-configure.md?context=/windows/deployment/context/context
- text: Prepare for imaging with Configuration Manager
url: /previous-versions/windows/it-pro/windows-10/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager
- title: Deploy - title: Deploy
linkLists: linkLists:
- linkListType: deploy - linkListType: deploy
links: links:
- text: Deploy Windows with Autopilot - text: Compare Windows Autopilot solutions
url: /mem/autopilot/tutorial/autopilot-scenarios url: /autopilot/device-preparation/compare
- text: Assign devices to servicing channels
url: update/waas-servicing-channels-windows-10-updates.md
- text: Deploy updates with Intune - text: Deploy updates with Intune
url: update/deploy-updates-intune.md url: update/deploy-updates-intune.md
- text: Deploy Windows updates with Configuration Manager - text: Deploy Windows updates with Configuration Manager
url: update/deploy-updates-configmgr.md url: update/deploy-updates-configmgr.md
- text: Upgrade Windows using Configuration Manager - text: Optimize and cache content
url: /mem/configmgr/osd/deploy-use/upgrade-windows-to-the-latest-version url: do/index.yml
- text: Check release health
url: update/check-release-health.md
- title: Windows Autopilot - title: Use Windows Autopilot
linkLists: linkLists:
- linkListType: how-to-guide - linkListType: overview
links: links:
- text: Overview - text: Windows Autopilot device preparation overview
url: /mem/autopilot/windows-autopilot url: /autopilot/device-preparation/overview
- text: Scenarios - text: Windows Autopilot overview
url: /mem/autopilot/tutorial/autopilot-scenarios url: /autopilot/overview
- text: Device registration - linkListType: tutorial
url: /mem/autopilot/registration-overview links:
- text: Learn more about Windows Autopilot > - text: Windows Autopilot scenarios
url: /mem/autopilot url: /autopilot/tutorial/autopilot-scenarios
- text: Windows Autopilot device preparation scenarios
url: /autopilot/device-preparation/tutorial/scenarios
- title: Windows Autopatch - title: Use Windows Autopatch
linkLists: linkLists:
- linkListType: how-to-guide - linkListType: overview
links: links:
- text: What is Windows Autopatch? - text: What is Windows Autopatch?
url: windows-autopatch/overview/windows-autopatch-overview.md url: windows-autopatch/overview/windows-autopatch-overview.md
- text: Frequently asked questions (FAQ)
url: windows-autopatch/overview/windows-autopatch-faq.yml
- text: Prerequisites - text: Prerequisites
url: windows-autopatch/prepare/windows-autopatch-prerequisites.md url: windows-autopatch/prepare/windows-autopatch-prerequisites.md
- text: Learn more about Windows Autopatch > - text: Deployment guide
url: windows-autopatch/overview/windows-autopatch-deployment-guide.md
- text: See more >
url: windows-autopatch/index.yml url: windows-autopatch/index.yml
- title: Windows Update for Business - title: Use Windows Update for Business
linkLists: linkLists:
- linkListType: how-to-guide - linkListType: how-to-guide
links: links:
- text: What is Windows Update for Business? - text: What is Windows Update for Business?
url: update/waas-manage-updates-wufb.md url: update/waas-manage-updates-wufb.md
- text: Windows Update for Business deployment service - text: Configure Windows Update for Business
url: update/deployment-service-overview.md url: update/waas-configure-wufb.md
- text: Manage Windows Update settings
url: update/waas-wu-settings.md
- text: Windows Update for Business reports overview - text: Windows Update for Business reports overview
url: update/wufb-reports-overview.md url: update/wufb-reports-overview.md
- title: Optimize and cache content - title: Use tools for upgrade and imaging
linkLists: linkLists:
- linkListType: how-to-guide - linkListType: reference
links: links:
- text: What is Delivery Optimization? - text: Customize Windows PE boot images
url: do/waas-delivery-optimization.md url: customize-boot-image.md
- text: What is Microsoft Connected Cache?
url: do/waas-microsoft-connected-cache.md
- text: Frequently asked questions
url: do/waas-delivery-optimization-faq.yml
- text: Learn more about Delivery Optimization >
url: do/index.yml
- title: In-place upgrade and imaging
linkLists:
- linkListType: how-to-guide
links:
- text: Upgrade Windows using Configuration Manager
url: /mem/configmgr/osd/deploy-use/upgrade-windows-to-the-latest-version
- text: Deploy a Windows 10 image using Configuration Manager
url: /previous-versions/windows/it-pro/windows-10/deployment/deploy-windows-cm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager
- text: Convert a disk from MBR to GPT - text: Convert a disk from MBR to GPT
url: mbr-to-gpt.md url: mbr-to-gpt.md
- text: Configure a PXE server to load Windows PE
url: configure-a-pxe-server-to-load-windows-pe.md
- text: Resolve Windows upgrade errors - text: Resolve Windows upgrade errors
url: upgrade/resolve-windows-upgrade-errors.md url: upgrade/resolve-windows-upgrade-errors.md
- title: Licensing and activation
linkLists:
- linkListType: how-to-guide
links:
- text: Plan for volume activation
url: volume-activation/plan-for-volume-activation-client.md
- text: Subscription activation
url: windows-10-subscription-activation.md
- text: Volume activation management tool (VAMT)
url: volume-activation/introduction-vamt.md
- text: Activate using key management service (KMS)
url: volume-activation/activate-using-key-management-service-vamt.md
- text: Windows commercial licensing overview
url: /windows/whats-new/windows-licensing
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
- title: More resources - title: More resources
linkLists: linkLists:
- linkListType: reference
# Release and lifecycle
links:
- text: Windows release health dashboard
url: /windows/release-health
- text: Windows client features lifecycle
url: /windows/whats-new/feature-lifecycle
- text: Lifecycle FAQ - Windows
url: /lifecycle/faq/windows
- linkListType: download - linkListType: download
# Windows hardware # Windows hardware
links: links:
@ -177,6 +128,6 @@ landingContent:
# Community # Community
links: links:
- text: Windows IT pro blog - text: Windows IT pro blog
url: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/bg-p/Windows10Blog url: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/bg-p/Windows-ITPro-blog
- text: Windows office hours - text: Windows office hours
url: https://aka.ms/windows/officehours url: https://aka.ms/windows/officehours

258
windows/deployment/update/feature-update-user-install.md
View File

@ -1,44 +1,45 @@
--- ---
title: Best practices - user-initiated feature update installation title: Deploy feature updates for user-initiated installations
description: Learn recommendations and best practices for manually deploying a feature update for a user-initiated installation. description: Learn recommendations and best practices for manually deploying a feature update for a user-initiated installation during a fixed service window.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: best-practice ms.topic: how-to
author: mestew author: mestew
ms.author: mstewart ms.author: mstewart
manager: aaroncz manager: aaroncz
ms.localizationpriority: medium ms.localizationpriority: medium
appliesto: appliesto:
- ✅ <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/mem/configmgr/ > Microsoft Configuration Manager</a> - ✅ <a href=https://learn.microsoft.com/mem/configmgr/ > Microsoft Configuration Manager</a>
ms.date: 07/10/2018 ms.date: 07/10/2018
--- ---
# Deploy feature updates for user-initiated installations (during a fixed service window) # Deploy feature updates for user-initiated installations
Use the following steps to deploy a feature update for a user-initiated installation. Use the following steps to deploy a feature update for a user-initiated installation.
## Get ready to deploy feature updates ## Get ready to deploy feature updates
### Step 1: Enable Peer Cache ### Step 1: Enable peer cache
Use **Peer Cache** to help manage deployment of content to clients in remote locations. Peer Cache is a built-in Configuration Manager solution that enables clients to share content with other clients directly from their local cache.
[Enable Configuration Manager client in full OS to share content](/mem/configmgr/core/clients/deploy/about-client-settings#enable-configuration-manager-client-in-full-os-to-share-content) if you have clients in remote locations that would benefit from downloading feature update content from a peer instead of downloading it from a distribution point (or Microsoft Update). Use **peer cache** to help manage deployment of content to clients in remote locations. Peer cache is a built-in Configuration Manager solution that enables clients to share content with other clients directly from their local cache.
[Enable Configuration Manager client in full OS to share content](/mem/configmgr/core/clients/deploy/about-client-settings#enable-configuration-manager-client-in-full-os-to-share-content) if you have clients in remote locations that would benefit from downloading feature update content from a peer instead of downloading it from a distribution point (or Microsoft Update).
### Step 2: Override the default Windows setup priority (Windows 10, version 1709 and later) ### Step 2: Override the default Windows setup priority (Windows 10, version 1709 and later)
If you're deploying **Feature update to Windows 10, version 1709** or later, by default, portions of setup are configured to run at a lower priority. This can result in a longer total install time for the feature update. When deploying within a maintenance window, we recommend that you override this default behavior to benefit from faster total install times. To override the default priority, create a file called SetupConfig.ini on each machine to be upgraded in the below location containing the single section noted. If you're deploying **Feature update to Windows 10, version 1709** or later, by default, portions of setup are configured to run at a lower priority. This can result in a longer total install time for the feature update. When deploying within a maintenance window, we recommend that you override this default behavior to benefit from faster total install times. To override the default priority, create a file called SetupConfig.ini on each machine to be upgraded in the below location containing the single section noted.
%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini %systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini
``` ```ini
[SetupConfig] [SetupConfig]
Priority=Normal Priority=Normal
``` ```
You can use the new [Run Scripts](/mem/configmgr/apps/deploy-use/create-deploy-scripts) feature to run a PowerShell script like the sample below to create the SetupConfig.ini on target devices. You can use the new [Run Scripts](/mem/configmgr/apps/deploy-use/create-deploy-scripts) feature to run a PowerShell script like the sample below to create the SetupConfig.ini on target devices.
``` ```powershell
#Parameters #Parameters
Param( Param(
[string] $PriorityValue = "Normal" [string] $PriorityValue = "Normal"
@ -57,179 +58,190 @@ $iniSetupConfigSlogan
"@ "@
#Build SetupConfig content with settings #Build SetupConfig content with settings
foreach ($k in $iniSetupConfigKeyValuePair.Keys) foreach ($k in $iniSetupConfigKeyValuePair.Keys)
{ {
$val = $iniSetupConfigKeyValuePair[$k] $val = $iniSetupConfigKeyValuePair[$k]
$iniSetupConfigContent = $iniSetupConfigContent.Insert($iniSetupConfigContent.Length, "`r`n$k=$val") $iniSetupConfigContent = $iniSetupConfigContent.Insert($iniSetupConfigContent.Length, "`r`n$k=$val")
} }
#Write content to file #Write content to file
New-Item $iniFilePath -ItemType File -Value $iniSetupConfigContent -Force New-Item $iniFilePath -ItemType File -Value $iniSetupConfigContent -Force
<# <#
Disclaimer Disclaimer
Sample scripts are not supported under any Microsoft standard support program or service. The sample scripts is Sample scripts are not supported under any Microsoft standard support program or service. The sample scripts is
provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without
limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk
arising out of the use or performance of the sample script and documentation remains with you. In no event shall arising out of the use or performance of the sample script and documentation remains with you. In no event shall
Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable
for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption,
loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample script loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample script
or documentation, even if Microsoft has been advised of the possibility of such damages. or documentation, even if Microsoft has been advised of the possibility of such damages.
#> #>
``` ```
>[!NOTE] > [!NOTE]
> If you elect not to override the default setup priority, you will need to increase the [maximum run time](/mem/configmgr/sum/get-started/manage-settings-for-software-updates#BKMK_SetMaxRunTime) value for Feature Update to Windows 10, version 1709 or higher from the default of 60 minutes. A value of 240 minutes may be required. Remember to ensure that your maintenance window duration is larger than your defined maximum run time value. > If you elect not to override the default setup priority, you will need to increase the [maximum run time](/mem/configmgr/sum/get-started/manage-settings-for-software-updates#BKMK_SetMaxRunTime) value for Feature Update to Windows 10, version 1709 or higher from the default of 60 minutes. A value of 240 minutes may be required. Remember to ensure that your maintenance window duration is larger than your defined maximum run time value.
## Manually deploy feature updates in a user-initiated installation ## Manually deploy feature updates in a user-initiated installation
The following sections provide the steps to manually deploy a feature update. The following sections provide the steps to manually deploy a feature update.
### Step 1: Specify search criteria for feature updates ### Step 1: Specify search criteria for feature updates
There are potentially a thousand or more feature updates displayed in the Configuration Manager console. The first step in the workflow for manually deploying a feature update is to identify the feature updates that you want to deploy.
1. In the Configuration Manager console, select **Software Library**. There are potentially a thousand or more feature updates displayed in the Configuration Manager console. The first step in the workflow for manually deploying a feature update is to identify the feature updates that you want to deploy.
2. In the Software Library workspace, expand **Windows 10 Servicing**, and select **All Windows 10 Updates**. The synchronized feature updates are displayed.
1. In the Configuration Manager console, select **Software Library**.
2. In the Software Library workspace, expand **Windows 10 Servicing**, and select **All Windows 10 Updates**. The synchronized feature updates are displayed.
3. In the search pane, filter to identify the feature updates that you need by using one or both of the following steps: 3. In the search pane, filter to identify the feature updates that you need by using one or both of the following steps:
- In the **search** text box, type a search string that filters for the feature updates. For example, type the version number for a specific feature update, or enter a string that would appear in the title of the feature update. - In the **search** text box, type a search string that filters for the feature updates. For example, type the version number for a specific feature update, or enter a string that would appear in the title of the feature update.
- Select **Add Criteria**, select the criteria that you want to use to filter software updates, select **Add**, and then provide the values for the criteria. For example, Title contains 1803, **Required** is greater than or equal to 1, and **Language** equals English. - Select **Add Criteria**, select the criteria that you want to use to filter software updates, select **Add**, and then provide the values for the criteria. For example, Title contains 1803, **Required** is greater than or equal to 1, and **Language** equals English.
4. Save the search for future use. 4. Save the search for future use.
### Step 2: Download the content for the feature update(s) ### Step 2: Download the content for the feature update
Before you deploy the feature updates, you can download the content as a separate step. Do this download so you can verify that the content is available on the distribution points before you deploy the feature updates. Downloading first helps you avoid any unexpected issues with the content delivery. Use the following procedure to download the content for feature updates before creating the deployment.
1. In the Configuration Manager console, navigate to **Software Library > Windows 10 Servicing**. Before you deploy the feature updates, you can download the content as a separate step. Do this download so you can verify that the content is available on the distribution points before you deploy the feature updates. Downloading first helps you avoid any unexpected issues with the content delivery. Use the following procedure to download the content for feature updates before creating the deployment.
1. In the Configuration Manager console, navigate to **Software Library > Windows 10 Servicing**.
2. Choose the feature update(s) to download by using your saved search criteria. Select one or more of the feature updates returned, right-click, and select **Download**. 2. Choose the feature update(s) to download by using your saved search criteria. Select one or more of the feature updates returned, right-click, and select **Download**.
The **Download Software Updates Wizard** opens. The **Download Software Updates Wizard** opens.
3. On the **Deployment Package** page, configure the following settings: 3. On the **Deployment Package** page, configure the following settings:
**Create a new deployment package**: Select this setting to create a new deployment package for the software updates that are in the deployment. Configure the following settings: **Create a new deployment package**: Select this setting to create a new deployment package for the software updates that are in the deployment. Configure the following settings:
- **Name**: Specifies the name of the deployment package. The package must have a unique name that briefly describes the package content. It's limited to 50 characters. - **Name**: Specifies the name of the deployment package. The package must have a unique name that briefly describes the package content. It's limited to 50 characters.
- **Description**: Specifies the description of the deployment package. The package description provides information about the package contents and is limited to 127 characters. - **Description**: Specifies the description of the deployment package. The package description provides information about the package contents and is limited to 127 characters.
- **Package source**: Specifies the location of the feature update source files. Type a network path for the source location, for example, \\\server\sharename\path, or select **Browse** to find the network location. You must create the shared folder for the deployment package source files before you proceed to the next page. - **Package source**: Specifies the location of the feature update source files. Type a network path for the source location, for example, \\\server\sharename\path, or select **Browse** to find the network location. You must create the shared folder for the deployment package source files before you proceed to the next page.
> [!IMPORTANT] > [!IMPORTANT]
> - The deployment package source location that you specify cannot be used by another software deployment package. > - The deployment package source location that you specify cannot be used by another software deployment package.
> - The SMS Provider computer account and the user that is running the wizard to download the feature updates must both have Write NTFS permissions on the download location. You should carefully restrict access to the download location to reduce the risk of attackers tampering with the feature update source files. > - The SMS Provider computer account and the user that is running the wizard to download the feature updates must both have Write NTFS permissions on the download location. You should carefully restrict access to the download location to reduce the risk of attackers tampering with the feature update source files.
> - You can change the package source location in the deployment package properties after Configuration Manager creates the deployment package. But if you do so, you must first copy the content from the original package source to the new package source location. > - You can change the package source location in the deployment package properties after Configuration Manager creates the deployment package. But if you do so, you must first copy the content from the original package source to the new package source location.
Select **Next**. Select **Next**.
4. On the **Distribution Points** page, specify the distribution points or distribution point groups that will host the feature update files, and then select **Next**. For more information about distribution points, see [Distribution point configurations](/mem/configmgr/core/servers/deploy/configure/install-and-configure-distribution-points#bkmk_configs). 4. On the **Distribution Points** page, specify the distribution points or distribution point groups that will host the feature update files, and then select **Next**. For more information about distribution points, see [Distribution point configurations](/mem/configmgr/core/servers/deploy/configure/install-and-configure-distribution-points#bkmk_configs).
>[!NOTE] > [!NOTE]
> The Distribution Points page is available only when you create a new software update deployment package. > The Distribution Points page is available only when you create a new software update deployment package.
5. On the **Distribution Settings** page, specify the following settings: 5. On the **Distribution Settings** page, specify the following settings:
- **Distribution priority**: Use this setting to specify the distribution priority for the deployment package. The distribution priority applies when the deployment package is sent to distribution points at child sites. Deployment packages are sent in priority order: **High**, **Medium**, or **Low**. Packages with identical priorities are sent in the order in which they were created. If there's no backlog, the package processes immediately regardless of its priority. By default, packages are sent using Medium priority. - **Distribution priority**: Use this setting to specify the distribution priority for the deployment package. The distribution priority applies when the deployment package is sent to distribution points at child sites. Deployment packages are sent in priority order: **High**, **Medium**, or **Low**. Packages with identical priorities are sent in the order in which they were created. If there's no backlog, the package processes immediately regardless of its priority. By default, packages are sent using Medium priority.
- **Enable for on-demand distribution**: Use this setting to enable on-demand content distribution to preferred distribution points. When this setting is enabled, the management point creates a trigger for the distribution manager to distribute the content to all preferred distribution points when a client requests the content for the package and the content isn't available on any preferred distribution points. For more information about preferred distribution points and on-demand content, see [Content source location scenarios](/mem/configmgr/core/plan-design/hierarchy/content-source-location-scenarios). - **Enable for on-demand distribution**: Use this setting to enable on-demand content distribution to preferred distribution points. When this setting is enabled, the management point creates a trigger for the distribution manager to distribute the content to all preferred distribution points when a client requests the content for the package and the content isn't available on any preferred distribution points. For more information about preferred distribution points and on-demand content, see [Content source location scenarios](/mem/configmgr/core/plan-design/hierarchy/content-source-location-scenarios).
- **Prestaged distribution point settings**: Use this setting to specify how you want to distribute content to prestaged distribution points. Choose one of the following options: - **Prestaged distribution point settings**: Use this setting to specify how you want to distribute content to prestaged distribution points. Choose one of the following options:
- **Automatically download content when packages are assigned to distribution points**: Use this setting to ignore the prestage settings and distribute content to the distribution point. - **Automatically download content when packages are assigned to distribution points**: Use this setting to ignore the prestage settings and distribute content to the distribution point.
- **Download only content changes to the distribution point**: Use this setting to prestage the initial content to the distribution point, and then distribute content changes to the distribution point. - **Download only content changes to the distribution point**: Use this setting to prestage the initial content to the distribution point, and then distribute content changes to the distribution point.
- **Manually copy the content in this package to the distribution point**: Use this setting to always prestage content on the distribution point. This setting is the default. - **Manually copy the content in this package to the distribution point**: Use this setting to always prestage content on the distribution point. This setting is the default.
For more information about prestaging content to distribution points, see [Use Prestaged content](/mem/configmgr/core/servers/deploy/configure/deploy-and-manage-content#bkmk_prestage). For more information about prestaging content to distribution points, see [Use Prestaged content](/mem/configmgr/core/servers/deploy/configure/deploy-and-manage-content#bkmk_prestage).
Select **Next**. Select **Next**.
6. On the **Download Location** page, specify location that Configuration Manager will use to download the software update source files. As needed, use the following options: 6. On the **Download Location** page, specify location that Configuration Manager will use to download the software update source files. As needed, use the following options:
- **Download software updates from the Internet**: Select this setting to download the software updates from the location on the Internet. This is the default setting. - **Download software updates from the Internet**: Select this setting to download the software updates from the location on the Internet. This is the default setting.
- **Download software updates from a location on the local network**: Select this setting to download software updates from a local folder or shared network folder. Use this setting when the computer running the wizard doesn't have Internet access. - **Download software updates from a location on the local network**: Select this setting to download software updates from a local folder or shared network folder. Use this setting when the computer running the wizard doesn't have Internet access.
>[!NOTE] > [!NOTE]
> When you use this setting, download the software updates from any computer with Internet access, and then copy the software updates to a location on the local network that is accessible from the computer running the wizard. > When you use this setting, download the software updates from any computer with Internet access, and then copy the software updates to a location on the local network that is accessible from the computer running the wizard.
Select **Next**. Select **Next**.
7. On the **Language Selection** page, specify the languages for which the selected feature updates are to be downloaded, and then select **Next**. Ensure that your language selection matches the language(s) of the feature updates selected for download. For example, if you selected English and German based feature updates for download, select those same languages on the language selection page. 7. On the **Language Selection** page, specify the languages for which the selected feature updates are to be downloaded, and then select **Next**. Ensure that your language selection matches the language(s) of the feature updates selected for download. For example, if you selected English and German based feature updates for download, select those same languages on the language selection page.
8. On the **Summary** page, verify the settings that you selected in the wizard, and then select **Next** to download the software updates. 8. On the **Summary** page, verify the settings that you selected in the wizard, and then select **Next** to download the software updates.
9. On the **Completion** page, verify that the software updates were successfully downloaded, and then select **Close**. 9. On the **Completion** page, verify that the software updates were successfully downloaded, and then select **Close**.
#### To monitor content status #### To monitor content status
1. To monitor the content status for the feature updates, select **Monitoring** in the Configuration Manager console.
2. In the Monitoring workspace, expand **Distribution Status**, and then select **Content Status**. 1. To monitor the content status for the feature updates, select **Monitoring** in the Configuration Manager console.
3. Select the feature update package that you previously identified to download the feature updates. 2. In the Monitoring workspace, expand **Distribution Status**, and then select **Content Status**.
3. Select the feature update package that you previously identified to download the feature updates.
4. On the **Home** tab, in the Content group, select **View Status**. 4. On the **Home** tab, in the Content group, select **View Status**.
### Step 3: Deploy the feature update(s) ### Step 3: Deploy the feature update
After you determine which feature updates you intend to deploy, you can manually deploy the feature update(s). Use the following procedure to manually deploy the feature update(s).
1. In the Configuration Manager console, select **Software Library**. After you determine which feature updates you intend to deploy, you can manually deploy the feature update(s). Use the following procedure to manually deploy the feature update(s).
2. In the Software Library workspace, expand **Windows 10 Servicing**, and select **All Windows 10 Updates**.
1. In the Configuration Manager console, select **Software Library**.
2. In the Software Library workspace, expand **Windows 10 Servicing**, and select **All Windows 10 Updates**.
3. Choose the feature update(s) to deploy by using your saved search criteria. Select one or more of the feature updates returned, right select, and select **Deploy**. 3. Choose the feature update(s) to deploy by using your saved search criteria. Select one or more of the feature updates returned, right select, and select **Deploy**.
The **Deploy Software Updates Wizard** opens. The **Deploy Software Updates Wizard** opens.
4. On the General page, configure the following settings: 4. On the General page, configure the following settings:
- **Name**: Specify the name for the deployment. The deployment must have a unique name that describes the purpose of the deployment and differentiates it from other deployments in the Configuration Manager site. By default, Configuration Manager automatically provides a name for the deployment in the following format: **Microsoft Software Updates - \<date\>\<time\>** - **Name**: Specify the name for the deployment. The deployment must have a unique name that describes the purpose of the deployment and differentiates it from other deployments in the Configuration Manager site. By default, Configuration Manager automatically provides a name for the deployment in the following format: **Microsoft Software Updates - \<date\>\<time\>**
- **Description**: Specify a description for the deployment. The description provides an overview of the deployment and any other relevant information that helps to identify and differentiate the deployment among others in Configuration Manager site. The description field is optional, has a limit of 256 characters, and has a blank value by default. - **Description**: Specify a description for the deployment. The description provides an overview of the deployment and any other relevant information that helps to identify and differentiate the deployment among others in Configuration Manager site. The description field is optional, has a limit of 256 characters, and has a blank value by default.
- **Software Update/Software Update Group**: Verify that the displayed software update group, or software update, is correct. - **Software Update/Software Update Group**: Verify that the displayed software update group, or software update, is correct.
- **Select Deployment Template**: Specify whether to apply a previously saved deployment template. You can configure a deployment template to contain multiple common software update deployment properties and then apply the template when you deploy subsequent software updates to ensure consistency across similar deployments and to save time. - **Select Deployment Template**: Specify whether to apply a previously saved deployment template. You can configure a deployment template to contain multiple common software update deployment properties and then apply the template when you deploy subsequent software updates to ensure consistency across similar deployments and to save time.
- **Collection**: Specify the collection for the deployment, as applicable. Members of the collection receive the feature updates that are defined in the deployment. - **Collection**: Specify the collection for the deployment, as applicable. Members of the collection receive the feature updates that are defined in the deployment.
5. On the Deployment Settings page, configure the following settings: 5. On the Deployment Settings page, configure the following settings:
- **Type of deployment**: Specify the deployment type for the software update deployment. Select **Required** to create a mandatory software update deployment in which the feature updates are automatically installed on clients before a configured installation deadline. - **Type of deployment**: Specify the deployment type for the software update deployment. Select **Required** to create a mandatory software update deployment in which the feature updates are automatically installed on clients before a configured installation deadline.
>[!IMPORTANT]
> After you create the software update deployment, you cannot later change the type of deployment.
>[!NOTE]
>A software update group deployed as **Required** will be downloaded in background and honor BITS settings, if configured.
- **Use Wake-on-LAN to wake up clients for required deployments**: Specify whether to enable Wake On LAN at the deadline to send wake-up packets to computers that require one or more software updates in the deployment. Any computers that are in sleep mode at the installation deadline time will be awakened so the software update installation can initiate. Clients that are in sleep mode that don't require any software updates in the deployment aren't started. By default, this setting isn't enabled and is available only when **Type of deployment** is set to **Required**. > [!IMPORTANT]
> After you create the software update deployment, you cannot later change the type of deployment.
>[!WARNING] > [!NOTE]
>Before you can use this option, computers and networks must be configured for Wake On LAN. > A software update group deployed as **Required** will be downloaded in background and honor BITS settings, if configured.
- **Detail level**: Specify the level of detail for the state messages that are reported by client computers. - **Use Wake-on-LAN to wake up clients for required deployments**: Specify whether to enable Wake On LAN at the deadline to send wake-up packets to computers that require one or more software updates in the deployment. Any computers that are in sleep mode at the installation deadline time will be awakened so the software update installation can initiate. Clients that are in sleep mode that don't require any software updates in the deployment aren't started. By default, this setting isn't enabled and is available only when **Type of deployment** is set to **Required**.
> [!WARNING]
> Before you can use this option, computers and networks must be configured for Wake On LAN.
- **Detail level**: Specify the level of detail for the state messages that are reported by client computers.
6. On the Scheduling page, configure the following settings: 6. On the Scheduling page, configure the following settings:
- **Schedule evaluation**: Specify whether the available time and installation deadline times are evaluated according to UTC or the local time of the computer running the Configuration Manager console. - **Schedule evaluation**: Specify whether the available time and installation deadline times are evaluated according to UTC or the local time of the computer running the Configuration Manager console.
- **Software available time**: Select **Specific time** to specify when the software updates will be available to clients: - **Software available time**: Select **Specific time** to specify when the software updates will be available to clients:
- **Specific time**: Select this setting to make the feature update in the deployment available to clients at a specific date and time. Specify a date and time that corresponds with the start of your fixed servicing window. When the deployment is created, the client policy is updated and clients are made aware of the deployment at their next client policy polling cycle. However, the feature update in the deployment isn't available for installation until after the specified date and time are reached and the required content has been downloaded. - **Specific time**: Select this setting to make the feature update in the deployment available to clients at a specific date and time. Specify a date and time that corresponds with the start of your fixed servicing window. When the deployment is created, the client policy is updated and clients are made aware of the deployment at their next client policy polling cycle. However, the feature update in the deployment isn't available for installation until after the specified date and time are reached and the required content has been downloaded.
- **Installation deadline**: Select **Specific time** to specify the installation deadline for the software updates in the deployment.
>[!NOTE]
>You can configure the installation deadline setting only when **Type of deployment** is set to **Required** on the Deployment Settings page.
- **Specific time**: Select this setting to automatically install the software updates in the deployment at a specific date and time. However, for the purposes of the fixed servicing window, set the installation deadline date and time to a future value, well beyond the fixed servicing window. - **Installation deadline**: Select **Specific time** to specify the installation deadline for the software updates in the deployment.
> [!NOTE]
> You can configure the installation deadline setting only when **Type of deployment** is set to **Required** on the Deployment Settings page.
- **Specific time**: Select this setting to automatically install the software updates in the deployment at a specific date and time. However, for the purposes of the fixed servicing window, set the installation deadline date and time to a future value, well beyond the fixed servicing window.
Required deployments for software updates can benefit from functionality called advanced download. When the software available time is reached, clients start downloading the content based on a randomized time. The feature update won't be displayed in Software Center for installation until the content is fully downloaded. This ensures that the feature update installation starts immediately when initiated. Required deployments for software updates can benefit from functionality called advanced download. When the software available time is reached, clients start downloading the content based on a randomized time. The feature update won't be displayed in Software Center for installation until the content is fully downloaded. This ensures that the feature update installation starts immediately when initiated.
7. On the User Experience page, configure the following settings: 7. On the User Experience page, configure the following settings:
- **User notifications**: Specify **Display in Software Center and show all notifications**. - **User notifications**: Specify **Display in Software Center and show all notifications**.
- **Deadline behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify the behavior that is to occur when the deadline is reached for the software update deployment. Specify whether to install the software updates in the deployment. Also specify whether to perform a system restart after software update installation regardless of a configured maintenance window. - **Deadline behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify the behavior that is to occur when the deadline is reached for the software update deployment. Specify whether to install the software updates in the deployment. Also specify whether to perform a system restart after software update installation regardless of a configured maintenance window.
>[!NOTE]
>Remember that the installation deadline date and time will be well into the future to allow plenty of time for the user-initiated install during a fixed servicing window.
- **Device restart behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify whether to suppress a system restart on servers and workstations after software updates are installed and a system restart is required to complete the installation.
>[!IMPORTANT] > [!NOTE]
>Suppressing system restarts can be useful in server environments or for cases in which you do not want the computers that are installing the software updates to restart by default. However, doing so can leave computers in an insecure state, whereas allowing a forced restart helps to ensure immediate completion of the software update installation. > Remember that the installation deadline date and time will be well into the future to allow plenty of time for the user-initiated install during a fixed servicing window.
- **Write filter handling for Windows Embedded devices**: When you deploy software updates to Windows Embedded devices that are write filter enabled, you can specify to install the software update on the temporary overlay and either commit changes later or commit the changes at the installation deadline or during a maintenance window. When you commit changes at the installation deadline or during a maintenance window, a restart is required and the changes persist on the device.
>[!NOTE] - **Device restart behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify whether to suppress a system restart on servers and workstations after software updates are installed and a system restart is required to complete the installation.
>When you deploy a software update to a Windows Embedded device, make sure that the device is a member of a collection that has a configured maintenance window.
- **Software updates deployment re-evaluation behavior upon restart**: Starting in Configuration Manager version 1606, select this setting to configure software updates deployments to have clients run a software updates compliance scan immediately after a client installs software updates and restarts. This enables the client to check for additional software updates that become applicable after the client restarts, and to then install them (and become compliant) during the same maintenance window.
8. On the Alerts page, configure how Configuration Manager and System Center Operations Manager generate alerts for this deployment. You can configure alerts only when **Type of deployment** is set to **Required** on the Deployment Settings page.
>[!NOTE] > [!IMPORTANT]
>You can review recent software updates alerts from the **Software Updates** node in the **Software Library** workspace. > Suppressing system restarts can be useful in server environments or for cases in which you do not want the computers that are installing the software updates to restart by default. However, doing so can leave computers in an insecure state, whereas allowing a forced restart helps to ensure immediate completion of the software update installation.
9. On the Download Settings page, configure the following settings:
- Specify whether the client will download and install the software updates when a client is connected to a slow network or is using a fallback content location. - **Write filter handling for Windows Embedded devices**: When you deploy software updates to Windows Embedded devices that are write filter enabled, you can specify to install the software update on the temporary overlay and either commit changes later or commit the changes at the installation deadline or during a maintenance window. When you commit changes at the installation deadline or during a maintenance window, a restart is required and the changes persist on the device.
- Specify whether to have the client download and install the software updates from a fallback distribution point when the content for the software updates isn't available on a preferred distribution point.
- **Allow clients to share content with other clients on the same subnet**: Specify whether to enable the use of BranchCache for content downloads. For more information about BranchCache, see [Fundamental concepts for content management](/mem/configmgr/core/plan-design/hierarchy/fundamental-concepts-for-content-management#branchcache). > [!NOTE]
> When you deploy a software update to a Windows Embedded device, make sure that the device is a member of a collection that has a configured maintenance window.
- **Software updates deployment re-evaluation behavior upon restart**: Starting in Configuration Manager version 1606, select this setting to configure software updates deployments to have clients run a software updates compliance scan immediately after a client installs software updates and restarts. This enables the client to check for additional software updates that become applicable after the client restarts, and to then install them (and become compliant) during the same maintenance window.
8. On the Alerts page, configure how Configuration Manager and System Center Operations Manager generate alerts for this deployment. You can configure alerts only when **Type of deployment** is set to **Required** on the Deployment Settings page.
> [!NOTE]
> You can review recent software updates alerts from the **Software Updates** node in the **Software Library** workspace.
9. On the Download Settings page, configure the following settings:
- Specify whether the client will download and install the software updates when a client is connected to a slow network or is using a fallback content location.
- Specify whether to have the client download and install the software updates from a fallback distribution point when the content for the software updates isn't available on a preferred distribution point.
- **Allow clients to share content with other clients on the same subnet**: Specify whether to enable the use of BranchCache for content downloads. For more information about BranchCache, see [Fundamental concepts for content management](/mem/configmgr/core/plan-design/hierarchy/fundamental-concepts-for-content-management#branchcache).
- **If software updates are not available on distribution point in current, neighbor or site groups, download content from Microsoft Updates**: Select this setting to have clients that are connected to the intranet download software updates from Microsoft Update if software updates aren't available on distribution points. Internet-based clients can always go to Microsoft Update for software updates content. - **If software updates are not available on distribution point in current, neighbor or site groups, download content from Microsoft Updates**: Select this setting to have clients that are connected to the intranet download software updates from Microsoft Update if software updates aren't available on distribution points. Internet-based clients can always go to Microsoft Update for software updates content.
- Specify whether to allow clients to download after an installation deadline when they use metered Internet connections. Internet providers sometimes charge by the amount of data that you send and receive when you are on a metered Internet connection. - Specify whether to allow clients to download after an installation deadline when they use metered Internet connections. Internet providers sometimes charge by the amount of data that you send and receive when you are on a metered Internet connection.
>[!NOTE] > [!NOTE]
>Clients request the content location from a management point for the software updates in a deployment. The download behavior depends upon how you have configured the distribution point, the deployment package, and the settings on this page. For more information, see [Content source location scenarios](/mem/configmgr/core/plan-design/hierarchy/content-source-location-scenarios). > Clients request the content location from a management point for the software updates in a deployment. The download behavior depends upon how you have configured the distribution point, the deployment package, and the settings on this page. For more information, see [Content source location scenarios](/mem/configmgr/core/plan-design/hierarchy/content-source-location-scenarios).
10. On the Summary page, review the settings. To save the settings to a deployment template, select **Save As Template**, enter a name and select the settings that you want to include in the template, and then select **Save**. To change a configured setting, select the associated wizard page and change the setting.
11. Select **Next** to deploy the feature update(s). 10. On the Summary page, review the settings. To save the settings to a deployment template, select **Save As Template**, enter a name and select the settings that you want to include in the template, and then select **Save**. To change a configured setting, select the associated wizard page and change the setting.
11. Select **Next** to deploy the feature update(s).
### Step 4: Monitor the deployment status ### Step 4: Monitor the deployment status
After you deploy the feature update(s), you can monitor the deployment status. Use the following procedure to monitor the deployment status: After you deploy the feature update(s), you can monitor the deployment status. Use the following procedure to monitor the deployment status:
1. In the Configuration Manager console, navigate to **Monitoring > Overview > Deployments**. 1. In the Configuration Manager console, navigate to **Monitoring > Overview > Deployments**.
2. Select the software update group or software update for which you want to monitor the deployment status. 2. Select the software update group or software update for which you want to monitor the deployment status.
3. On the **Home** tab, in the **Deployment** group, select **View Status**. 3. On the **Home** tab, in the **Deployment** group, select **View Status**.

12
windows/deployment/update/PSFxWhitepaper.md → windows/deployment/update/forward-reverse-differentials.md
View File

@ -1,6 +1,6 @@
--- ---
title: Windows Updates using forward and reverse differentials title: Windows Updates using forward and reverse differentials
description: A technique to produce compact software updates optimized for any origin and destination revision pair description: A technique to produce compact software updates optimized for any origin and destination revision pair.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: reference ms.topic: reference
@ -8,7 +8,7 @@ author: mestew
ms.author: mstewart ms.author: mstewart
manager: aaroncz manager: aaroncz
ms.localizationpriority: medium 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 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: 08/21/2021 ms.date: 08/21/2021
@ -29,7 +29,7 @@ technique to build compact software update packages that are applicable to any
revision of the base version, and then describe how Windows quality updates revision of the base version, and then describe how Windows quality updates
use this technique. use this technique.
## General Terms ## General terms
The following general terms apply throughout this document: The following general terms apply throughout this document:
@ -76,7 +76,7 @@ The flip side of express download is that the size of PSF files can be large dep
In the following sections, we describe how quality updates use this technique based on forward and reverse differentials for newer releases of Windows and Windows Server to overcome the challenges with express downloads. In the following sections, we describe how quality updates use this technique based on forward and reverse differentials for newer releases of Windows and Windows Server to overcome the challenges with express downloads.
## High-level Design ## High-level design
### Update packaging ### Update packaging
@ -86,7 +86,7 @@ There can be cases where new files are added to the system during servicing. The
![Outer box labeled .msu containing two sub-boxes: 1) Applicability Logic, 2) box labeled .cab containing four sub-boxes: 1) update metadata, 2) content manifests, 3) delta sub RTM transform to sub N (file 1, file2, etc.), and 4) delta sub N transform to RTM (file 1, file 2, etc.).](images/PSF4.png) ![Outer box labeled .msu containing two sub-boxes: 1) Applicability Logic, 2) box labeled .cab containing four sub-boxes: 1) update metadata, 2) content manifests, 3) delta sub RTM transform to sub N (file 1, file2, etc.), and 4) delta sub N transform to RTM (file 1, file 2, etc.).](images/PSF4.png)
### Hydration and installation ### Hydration and installation
Once the usual applicability checks are performed on the update package and are determined to be applicable, the Windows component servicing infrastructure hydrates the full files during preinstallation and then proceeds with the usual installation process. Once the usual applicability checks are performed on the update package and are determined to be applicable, the Windows component servicing infrastructure hydrates the full files during preinstallation and then proceeds with the usual installation process.
@ -98,7 +98,7 @@ Below is a high-level sequence of activities that the component servicing infras
- Resolve any dependencies and install components. - Resolve any dependencies and install components.
- Clean up older state (V<sub>N-1</sub>); the previous state V<sub>N</sub> is retained for uninstallation and restoration or repair. - Clean up older state (V<sub>N-1</sub>); the previous state V<sub>N</sub> is retained for uninstallation and restoration or repair.
### **Resilient Hydration** ### Resilient hydration
To ensure resiliency against component store corruption or missing files that could occur due to susceptibility of certain types of hardware to file system corruption, a corruption repair service has been traditionally used to recover the component store automatically (automatic corruption repair) or on demand (manual corruption repair) using an online or local repair source. This service will continue to offer the ability to repair and recover content for hydration and successfully install an update, if needed. To ensure resiliency against component store corruption or missing files that could occur due to susceptibility of certain types of hardware to file system corruption, a corruption repair service has been traditionally used to recover the component store automatically (automatic corruption repair) or on demand (manual corruption repair) using an online or local repair source. This service will continue to offer the ability to repair and recover content for hydration and successfully install an update, if needed.

2
windows/deployment/update/waas-quick-start.md
View File

@ -32,7 +32,7 @@ Some new terms have been introduced as part of Windows as a service, so you shou
For more information, see [Overview of Windows as a service](waas-overview.md). For more information, see [Overview of Windows as a service](waas-overview.md).
For some interesting in-depth information about how cumulative updates work, see [Windows Updates using forward and reverse differentials](PSFxWhitepaper.md). For some interesting in-depth information about how cumulative updates work, see [Windows Updates using forward and reverse differentials](forward-reverse-differentials.md).
## Key concepts ## Key concepts

195
windows/deployment/update/windows-update-logs.md
View File

@ -3,25 +3,23 @@ title: Windows Update log files
description: Learn about the Windows Update log files and how to merge and convert Windows Update trace files (.etl files) into a single readable WindowsUpdate.log file. description: Learn about the Windows Update log files and how to merge and convert Windows Update trace files (.etl files) into a single readable WindowsUpdate.log file.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: troubleshooting ms.topic: reference
author: mestew author: mestew
ms.author: mstewart ms.author: mstewart
manager: aaroncz manager: aaroncz
ms.collection: ms.collection:
- highpri - highpri
- tier2 - tier2
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 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: 12/08/2023 ms.date: 12/08/2023
--- ---
# Windows Update log files # Windows Update log files
The following table describes the log files created by Windows Update. The following table describes the log files created by Windows Update.
|Log file|Location|Description|When to use | |Log file|Location|Description|When to use |
|-|-|-|-| |-|-|-|-|
|windowsupdate.log|C:\Windows\Logs\WindowsUpdate|Starting in Windows 8.1 and continuing in Windows 10, Windows Update client uses Event Tracing for Windows (ETW) to generate diagnostic logs.|If you receive an error message when you run Windows Update, you can use the information included in the Windowsupdate.log log file to troubleshoot the issue.| |windowsupdate.log|C:\Windows\Logs\WindowsUpdate|Starting in Windows 8.1 and continuing in Windows 10, Windows Update client uses Event Tracing for Windows (ETW) to generate diagnostic logs.|If you receive an error message when you run Windows Update, you can use the information included in the Windowsupdate.log log file to troubleshoot the issue.|
@ -31,126 +29,131 @@ The following table describes the log files created by Windows Update.
## Generating WindowsUpdate.log ## Generating WindowsUpdate.log
To merge and convert Windows Update trace files (.etl files) into a single readable WindowsUpdate.log file, see [Get-WindowsUpdateLog](/powershell/module/windowsupdate/get-windowsupdatelog?preserve-view=tru&view=win10-ps). To merge and convert Windows Update trace files (.etl files) into a single readable WindowsUpdate.log file, see [Get-WindowsUpdateLog](/powershell/module/windowsupdate/get-windowsupdatelog?preserve-view=tru&view=win10-ps).
> [!NOTE]
> When you run the **Get-WindowsUpdateLog** cmdlet, an copy of WindowsUpdate.log file is created as a static log file. It does not update as the old WindowsUpdate.log unless you run **Get-WindowsUpdateLog** again.
>[!NOTE]
>When you run the **Get-WindowsUpdateLog** cmdlet, an copy of WindowsUpdate.log file is created as a static log file. It does not update as the old WindowsUpdate.log unless you run **Get-WindowsUpdateLog** again.
## Windows Update log components ## Windows Update log components
The Windows Update engine has different component names. The following are some of the most common components that appear in the WindowsUpdate.log file: The Windows Update engine has different component names. The following are some of the most common components that appear in the WindowsUpdate.log file:
- AGENT- Windows Update agent - AGENT- Windows Update agent
- AU - Automatic Updates is performing this task - AU - Automatic Updates is performing this task
- AUCLNT- Interaction between AU and the logged-on user - AUCLNT- Interaction between AU and the logged-on user
- CDM- Device Manager - CDM- Device Manager
- CMPRESS- Compression agent - CMPRESS- Compression agent
- COMAPI- Windows Update API - COMAPI- Windows Update API
- DRIVER- Device driver information - DRIVER- Device driver information
- DTASTOR- Handles database transactions - DTASTOR- Handles database transactions
- EEHNDLER- Expression handler that's used to evaluate update applicability - EEHNDLER- Expression handler that's used to evaluate update applicability
- HANDLER- Manages the update installers - HANDLER- Manages the update installers
- MISC- General service information - MISC- General service information
- OFFLSNC- Detects available updates without network connection - OFFLSNC- Detects available updates without network connection
- PARSER- Parses expression information - PARSER- Parses expression information
- PT- Synchronizes updates information to the local datastore - PT- Synchronizes updates information to the local datastore
- REPORT- Collects reporting information - REPORT- Collects reporting information
- SERVICE- Startup/shutdown of the Automatic Updates service - SERVICE- Startup/shutdown of the Automatic Updates service
- SETUP- Installs new versions of the Windows Update client when it's available - SETUP- Installs new versions of the Windows Update client when it's available
- SHUTDWN- Install at shutdown feature - SHUTDWN- Install at shutdown feature
- WUREDIR- The Windows Update redirector files - WUREDIR- The Windows Update redirector files
- WUWEB- The Windows Update ActiveX control - WUWEB- The Windows Update ActiveX control
- ProtocolTalker - Client-server sync - ProtocolTalker - Client-server sync
- DownloadManager - Creates and monitors payload downloads - DownloadManager - Creates and monitors payload downloads
- Handler, Setup - Installer handlers (CBS, and so on) - Handler, Setup - Installer handlers (CBS, and so on)
- EEHandler - Evaluating update applicability rules - EEHandler - Evaluating update applicability rules
- DataStore - Caching update data locally - DataStore - Caching update data locally
- IdleTimer - Tracking active calls, stopping a service - IdleTimer - Tracking active calls, stopping a service
>[!NOTE]
>Many component log messages are invaluable if you are looking for problems in that specific area. However, they can be useless if you don't filter to exclude irrelevant components so that you can focus on what's important.
## Windows Update log structure
The Windows update log structure is separated into four main identities:
- Time Stamps > [!NOTE]
- Process ID and Thread ID > Many component log messages are invaluable if you are looking for problems in that specific area. However, they can be useless if you don't filter to exclude irrelevant components so that you can focus on what's important.
- Component Name
- Update Identifiers
- Update ID and Revision Number
- Revision ID
- Local ID
- Inconsistent terminology
The WindowsUpdate.log structure is discussed in the following sections. ## Windows Update log structure
### Time stamps The Windows update log structure is separated into four main identities:
The time stamp indicates the time at which the logging occurs.
- Messages are usually in chronological order, but there may be exceptions. - Time stamps
- A pause during a sync can indicate a network problem, even if the scan succeeds. - Process ID and thread ID
- A long pause near the end of a scan can indicate a supersedence chain issue. - Component name
- Update identifiers
- Update ID and revision number
- Revision ID
- Local ID
- Inconsistent terminology
The WindowsUpdate.log structure is discussed in the following sections.
### Time stamps
The time stamp indicates the time at which the logging occurs.
- Messages are usually in chronological order, but there may be exceptions.
- A pause during a sync can indicate a network problem, even if the scan succeeds.
- A long pause near the end of a scan can indicate a supersedence chain issue.
![Windows Update time stamps.](images/update-time-log.png) ![Windows Update time stamps.](images/update-time-log.png)
### Process ID and thread ID
### Process ID and thread ID The Process IDs and Thread IDs are random, and they can vary from log to log and even from service session to service session within the same log.
The Process IDs and Thread IDs are random, and they can vary from log to log and even from service session to service session within the same log.
- The first four digits, in hex, are the process ID. - The first four digits, in hex, are the process ID.
- The next four digits, in hex, are the thread ID. - The next four digits, in hex, are the thread ID.
- Each component, such as the USO, Windows Update engine, COM API callers, and Windows Update installer handlers, has its own process ID. - Each component, such as the USO, Windows Update engine, COM API callers, and Windows Update installer handlers, has its own process ID.
![Windows Update process and thread IDs.](images/update-process-id.png) ![Windows Update process and thread IDs.](images/update-process-id.png)
### Component name
### Component name Search for and identify the components that are associated with the IDs. Different parts of the Windows Update engine have different component names. Some of them are as follows:
Search for and identify the components that are associated with the IDs. Different parts of the Windows Update engine have different component names. Some of them are as follows:
- ProtocolTalker - Client-server sync - ProtocolTalker - Client-server sync
- DownloadManager - Creates and monitors payload downloads - DownloadManager - Creates and monitors payload downloads
- Handler, Setup - Installer handlers (CBS, etc.) - Handler, Setup - Installer handlers (CBS, etc.)
- EEHandler - Evaluating update applicability rules - EEHandler - Evaluating update applicability rules
- DataStore - Caching update data locally - DataStore - Caching update data locally
- IdleTimer - Tracking active calls, stopping service - IdleTimer - Tracking active calls, stopping service
![Windows Update component name.](images/update-component-name.png) ![Windows Update component name.](images/update-component-name.png)
### Update identifiers
### Update identifiers
The following items are update identifiers: The following items are update identifiers:
#### Update ID and revision number #### Update ID and revision number
There are different identifiers for the same update in different contexts. It's important to know the identifier schemes. There are different identifiers for the same update in different contexts. It's important to know the identifier schemes.
- Update ID: A GUID (indicated in the previous screenshot) assigned to a given update at publication time
- Revision number: A number incremented every time that a given update (that has a given update ID) is modified and republished on a service - Update ID: A GUID (indicated in the previous screenshot) assigned to a given update at publication time
- Revision numbers are reused from one update to another (not a unique identifier). - Revision number: A number incremented every time that a given update (that has a given update ID) is modified and republished on a service
- The update ID and revision number are often shown together as "{GUID}.revision." - Revision numbers are reused from one update to another (not a unique identifier).
- The update ID and revision number are often shown together as "{GUID}.revision."
![Windows Update update identifiers.](images/update-update-id.png) ![Windows Update update identifiers.](images/update-update-id.png)
#### Revision ID #### Revision ID
- A Revision ID (don't confuse this value with "revision number") is a serial number issued when an update is initially published or revised on a given service. - A Revision ID (don't confuse this value with "revision number") is a serial number issued when an update is initially published or revised on a given service.
- An existing update that is revised keeps the same update ID (GUID), has its revision number incremented (for example, from 100 to 101), but gets a new revision ID that isn't related to the previous ID. - An existing update that is revised keeps the same update ID (GUID), has its revision number incremented (for example, from 100 to 101), but gets a new revision ID that isn't related to the previous ID.
- Revision IDs are unique on a given update source, but not across multiple sources. - Revision IDs are unique on a given update source, but not across multiple sources.
- The same update revision might have different revision IDs on Windows Update and WSUS. - The same update revision might have different revision IDs on Windows Update and WSUS.
- The same revision ID might represent different updates on Windows Update and WSUS. - The same revision ID might represent different updates on Windows Update and WSUS.
#### Local ID #### Local ID
- Local ID is a serial number issued by a given Windows Update client when an update is received from a service. - Local ID is a serial number issued by a given Windows Update client when an update is received from a service.
- Typically seen in debug logs, especially involving the local cache for update info (Datastore) - Typically seen in debug logs, especially involving the local cache for update info (Datastore)
- Different client PCs assign different Local IDs to the same update - Different client PCs assign different Local IDs to the same update
- You can find the local IDs that a client is using by getting the client's %WINDIR%\SoftwareDistribution\Datastore\Datastore.edb file - You can find the local IDs that a client is using by getting the client's %WINDIR%\SoftwareDistribution\Datastore\Datastore.edb file
#### Inconsistent terminology #### Inconsistent terminology
- Sometimes the logs use terms inconsistently. For example, the InstalledNonLeafUpdateIDs list actually contains revision IDs, not update IDs.
- Recognize IDs by form and context: - Sometimes the logs use terms inconsistently. For example, the InstalledNonLeafUpdateIDs list actually contains revision IDs, not update IDs.
- Recognize IDs by form and context:
- GUIDs are update IDs
- Small integers that appear alongside an update ID are revision numbers - GUIDs are update IDs
- Large integers are typically revision IDs - Small integers that appear alongside an update ID are revision numbers
- Small integers (especially in Datastore) can be local IDs - Large integers are typically revision IDs
- Small integers (especially in Datastore) can be local IDs
![Windows Update inconsisten terminology.](images/update-inconsistent.png) ![Windows Update inconsisten terminology.](images/update-inconsistent.png)
## Windows Setup log files analysis using SetupDiag tool ## Windows Setup log files analysis using SetupDiag tool
SetupDiag is a diagnostic tool that can be used for analysis of logs related to installation of Windows Updates. For detailed information, see [SetupDiag](../upgrade/setupdiag.md).
SetupDiag is a diagnostic tool that can be used for analysis of logs related to installation of Windows Updates. For more information, see [SetupDiag](../upgrade/setupdiag.md).

104
windows/deployment/upgrade/windows-10-upgrade-paths.md
View File

@ -1,104 +0,0 @@
---
title: Windows 10 upgrade paths
description: You can upgrade to Windows 10 from a previous version of Windows if the upgrade path is supported.
ms.service: windows-client
ms.localizationpriority: medium
author: frankroj
manager: aaroncz
ms.author: frankroj
ms.topic: conceptual
ms.collection:
- highpri
- tier2
ms.subservice: itpro-deploy
ms.date: 02/13/2024
appliesto:
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
---
# Windows 10 upgrade paths
> [!IMPORTANT]
>
> This article deals with upgrading from Windows versions that are out of support. For a current version of this article, please see [Windows upgrade paths](windows-upgrade-paths.md) that deals with currently supported versions of Windows.
>
> For more information, see:
>
> - [Windows 8.1 support ended on January 10, 2023](https://support.microsoft.com/windows/windows-8-1-support-ended-on-january-10-2023-3cfd4cde-f611-496a-8057-923fba401e93).
> - [Windows 7 support ended on January 14, 2020](https://support.microsoft.com/windows/windows-7-support-ended-on-january-14-2020-b75d4580-2cc7-895a-2c9c-1466d9a53962).
> - [FAQ about Windows 7 ESU](/troubleshoot/windows-client/windows-7-eos-faq/windows-7-extended-security-updates-faq).
## Upgrade paths
This article provides a summary of available upgrade paths to Windows 10. You can upgrade to Windows 10 from Windows 7 or a later operating system. Paths include upgrading from one release of Windows 10 to later release of Windows 10. Migrating from one edition of Windows 10 to a different edition of the same release is also supported.
If you're also migrating to a different edition of Windows, see [Windows edition upgrade](windows-edition-upgrades.md). Methods and supported paths are described on this page to change the edition of Windows. These methods require that you input a license or product key for the new Windows edition prior to starting the upgrade process. Edition downgrade is also supported for some paths. However, applications and settings aren't maintained when the Windows edition is downgraded.
- **Windows 10 version upgrade**: You can directly upgrade any General Availability Channel version of Windows 10 to a newer, supported General Availability Channel version of Windows 10, even if it involves skipping versions. Work with your account representative if your current version of Windows is out of support. See the [Windows lifecycle fact sheet](/lifecycle/faq/windows) for availability and service information.
- **In-place upgrade from Windows 7, Windows 8.1, or [Windows 10 General Availability Channel](/windows/release-health/release-information)** to Windows 10 LTSC isn't supported. Windows 10 LTSC 2015 didn't block this in-place upgrade path. This issue was corrected in the Windows 10 LTSC 2016 release, which only allows data-only and clean install options.
You can upgrade from Windows 10 LTSC to Windows 10 General Availability Channel if you upgrade to the same or a newer build version. For example, Windows 10 Enterprise 2016 LTSB can be upgraded to Windows 10 Enterprise version 1607 or later. Upgrade is supported using the in-place upgrade process using Windows setup. The Product Key switch needs to be used if you want to keep your apps. If you don't use the switch, the option **Keep personal files and apps** option is grayed out. The command line would be `setup.exe /pkey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx`, using your relevant Windows 10 GA Channel product key. For example, if using a KMS, the command line would be `setup.exe /pkey NPPR9-FWDCX-D2C8J-H872K-2YT43`.
- **Windows N/KN**: Windows "N" and "KN" SKUs (editions without media-related functionality) follow the same upgrade paths shown in the following tables. If the pre-upgrade and post-upgrade editions aren't the same type (for example, Windows 8.1 Pro N to Windows 10 Pro), personal data is kept but applications and settings are removed during the upgrade process.
- **Windows 8.0**: You can't upgrade directly from Windows 8.0 to Windows 10. To upgrade from Windows 8.0, you must first install the [Windows 8.1 update](https://support.microsoft.com/help/15356/windows-8-install-update-kb-2919355).
## Windows 10
✔ = Full upgrade is supported including personal data, settings, and applications.
D = Edition downgrade; personal data is maintained, applications and settings are removed.
---
| | Windows 10 Home | Windows 10 Pro | Windows 10 Pro Education | Windows 10 Education | Windows 10 Enterprise |
|---|---|---|---|---|---|
| **Home** | | ✔ | ✔ | ✔ | |
| **Pro** | D | | ✔ | ✔ | ✔ |
| **Education** | | | | | D |
| **Enterprise** | | | | ✔ | |
---
## Windows 8.1
✔ = Full upgrade is supported including personal data, settings, and applications.
D = Edition downgrade; personal data is maintained, applications and settings are removed.
---
| | Windows 10 Home | Windows 10 Pro | Windows 10 Pro Education | Windows 10 Education | Windows 10 Enterprise |
|---|---|---|---|---|---|
| **(Core)** | ✔ | ✔ | ✔ | ✔ | |
| **Connected** | ✔ | ✔ | ✔ | ✔ | |
| **Pro** | D | ✔ | ✔ | ✔ | ✔ |
| **Pro Student** | D | ✔ | ✔ | ✔ | ✔ |
| **Pro WMC** | D | ✔ | ✔ | ✔ | ✔ |
| **Enterprise** | | | | ✔ | ✔ |
| **Embedded Industry** | | | | | ✔ |
---
## Windows 7
✔ = Full upgrade is supported including personal data, settings, and applications.
D = Edition downgrade; personal data is maintained, applications and settings are removed.
---
| | Windows 10 Home | Windows 10 Pro | Windows 10 Pro Education | Windows 10 Education | Windows 10 Enterprise |
|---|---|---|---|---|---|
| **Starter** | ✔ | ✔ | ✔ | ✔ | |
| **Home Basic** | ✔ | ✔ | ✔ | ✔ | |
| **Home Premium** | ✔ | ✔ | ✔ | ✔ | |
| **Professional** | D | ✔ | ✔ | ✔ | ✔ |
| **Ultimate** | D | ✔ | ✔ | ✔ | ✔ |
| **Enterprise** | | | | ✔ | ✔ |
---
## Related articles
- [Windows 10 deployment scenarios](../windows-deployment-scenarios.md).
- [Windows upgrade and migration considerations](windows-upgrade-and-migration-considerations.md).
- [Windows 10 edition upgrade](windows-edition-upgrades.md).

241
windows/hub/index.yml
View File

@ -1,148 +1,135 @@
### YamlMime:Hub ### YamlMime:Hub
title: Windows client documentation for IT Pros title: Windows client documentation
summary: Learn how to deploy, secure, and manage Windows clients for your organization. summary: Documentation for IT pros on how to deploy, secure, and manage Windows clients for your organization.
brand: windows brand: windows
metadata: metadata:
title: Windows client documentation for IT Pros title: Windows client documentation
description: Learn how to deploy, secure, and manage Windows clients for your organization. description: Documentation for IT pros on how to deploy, secure, and manage Windows clients for your organization.
ms.topic: hub-page ms.topic: hub-page
ms.service: windows-client ms.service: windows-client
ms.collection: ms.collection:
- tier1 - tier1
- essentials-navigation - essentials-navigation
author: paolomatarazzo author: aczechowski
ms.author: paoloma ms.author: aaroncz
manager: aaroncz manager: aaroncz
ms.date: 07/11/2024 ms.date: 08/27/2024
highlightedContent: highlightedContent:
# itemType: architecture | concept | deploy | download | get-started | how-to-guide | training | overview | quickstart | reference | sample | tutorial | video | whats-new
items: items:
- title: Get started with Windows 11 - title: Get started with Windows 11
itemType: get-started itemType: get-started
url: /windows/whats-new/windows-11-overview url: /windows/whats-new/windows-11-overview
- title: Windows 11, version 23H2 - title: Windows 11, version 23H2
itemType: whats-new itemType: whats-new
url: /windows/whats-new/whats-new-windows-11-version-23h2 url: /windows/whats-new/whats-new-windows-11-version-23h2
- title: Windows 11, version 23H2 group policy settings reference - title: Windows 11, version 23H2 group policy settings reference
itemType: download itemType: download
url: https://www.microsoft.com/download/details.aspx?id=105668 url: https://www.microsoft.com/download/details.aspx?id=105668
- title: Windows release health
itemType: whats-new
url: /windows/release-health
- title: Windows commercial licensing
itemType: overview
url: /windows/whats-new/windows-licensing
- title: Windows 365 documentation
itemType: overview
url: /windows-365
- title: Explore all Windows trainings and learning paths for IT pros
itemType: learn
url: https://learn.microsoft.com/en-us/training/browse/?products=windows&roles=administrator
- title: Enroll Windows client devices in Microsoft Intune
itemType: how-to-guide
url: /mem/intune/fundamentals/deployment-guide-enrollment-windows
productDirectory: - title: Windows administrative tools
title: Get started itemType: concept
url: /windows/client-management/client-tools/administrative-tools-in-windows
conceptualContent:
# itemType: architecture | concept | deploy | download | get-started | how-to-guide | training | overview | quickstart | reference | sample | tutorial | video | whats-new
items: items:
- title: Deploy Windows
- title: Learn how to deploy Windows
imageSrc: /media/common/i_deploy.svg
links: links:
- url: /autopilot/ - url: /autopilot/
text: Windows Autopilot itemType: deploy
- url: /autopilot/device-preparation/compare text: Windows Autopilot
text: Compare Windows Autopilot solutions - url: /windows/deployment/windows-autopatch
- url: /windows/deployment/do/ itemType: overview
text: Delivery optimization text: Windows Autopatch
- url: /windows/deployment/update/deployment-service-overview - url: /windows/deployment/do/
text: Windows Update for Business deployment service itemType: concept
- url: /windows/deployment/windows-autopatch text: Delivery optimization
text: Windows Autopatch overview footerLink:
- url: /windows/deployment url: /windows/deployment
text: Learn more about Windows deployment > text: See more
- title: Learn how to secure Windows - title: Secure Windows
imageSrc: /media/common/i_security-management.svg
links: links:
- url: /windows/security/threat-protection/windows-security-configuration-framework/windows-security-baselines - url: /windows/security/introduction
text: Windows security baselines itemType: overview
- url: /windows/security/identity-protection/hello-for-business text: Introduction to Windows security
text: Windows Hello for Business - url: /windows/security/operating-system-security/data-protection/bitlocker/
- url: /windows/security/identity-protection/web-sign-in itemType: concept
text: Web sign-in for Windows text: BitLocker
- url: /windows/security/threat-protection/windows-defender-application-control - url: /windows/security/identity-protection/hello-for-business
text: Windows Defender Application Control (WDAC) itemType: concept
- url: /windows/security/threat-protection/microsoft-defender-application-guard/md-app-guard-overview text: Windows Hello for Business
text: Microsoft Defender Application Guard footerLink:
- url: /windows/security url: /windows/security
text: Learn more about Windows security > text: See more
- title: Learn about privacy in Windows - title: Privacy in Windows
imageSrc: /media/common/i_lock.svg
links: links:
- url: /windows/privacy/required-diagnostic-events-fields-windows-11-22h2 - url: /windows/privacy/required-diagnostic-events-fields-windows-11-22h2
text: Windows 11 required diagnostic data itemType: reference
- url: /windows/privacy/configure-windows-diagnostic-data-in-your-organization text: Windows 11 required diagnostic data
text: Configure Windows diagnostic data in your organization - url: /windows/privacy/configure-windows-diagnostic-data-in-your-organization
- url: /windows/privacy/diagnostic-data-viewer-overview itemType: how-to-guide
text: Diagnostic Data Viewer text: Configure Windows diagnostic data in your organization
- url: /windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services - url: /windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services
text: Manage connections to Microsoft services itemType: reference
- url: /windows/privacy/windows-privacy-compliance-guide text: Manage connections to Microsoft services
text: Windows privacy compliance guide footerLink:
- url: /windows/privacy url: /windows/privacy
text: Learn more about privacy in Windows > text: See more
- title: Learn how to manage Windows - title: Manage Windows
imageSrc: /media/common/i_management.svg
links: links:
- url: /windows/client-management/administrative-tools-in-windows-10 - url: /windows/client-management/client-tools/administrative-tools-in-windows
text: Windows administrative tools itemType: concept
- url: /windows/client-management/client-tools/windows-version-search text: Windows administrative tools
text: What version of Windows am I running? - url: /windows/client-management/client-tools/windows-version-search
- url: /windows/client-management/mobile-device-enrollment itemType: how-to-guide
text: MDM enrollment text: What version of Windows am I running?
- url: /windows/client-management/mdm/ - url: /windows/client-management/mdm/
text: Configuration Service Provider (CSP) reference itemType: reference
- url: /windows/application-management/index text: Configuration Service Provider (CSP) policies
text: Learn more about application management > footerLink:
- url: /windows/client-management url: /windows/client-management
text: Learn more about Windows management > text: See more
- title: Learn how to configure Windows - title: Configure Windows
imageSrc: /media/common/i_config-tools.svg
links: links:
- url: /windows/configuration/windows-accessibility-for-itpros - url: /windows/configuration/accessibility/
text: Accessibility information itemType: overview
- url: /windows/configuration/provisioning-packages/provisioning-packages text: Accessibility information
text: Use Provisioning packages to configure new devices - url: /windows/configuration/start/layout
- url: /windows/configuration/customize-start-menu-layout-windows-11 itemType: how-to-guide
text: Customize the Start menu layout text: Customize the Start layout
- url: /windows/configuration/set-up-shared-or-guest-pc - url: /windows/configuration/assigned-access
text: Set up a shared or guest PC itemType: concept
- url: /windows/configuration/assigned-access text: Kiosks and restricted user experiences
text: Configure kiosks and restricted user experiences footerLink:
- url: /windows/configuration url: /windows/configuration
text: Learn more about Windows configuration > text: See more
- title: Learn about Windows for Education - title: Windows for Education
imageSrc: /media/common/i_advanced.svg
links: links:
- url: /education/windows/tutorial-school-deployment/ - url: /education/windows/federated-sign-in
text: "Tutorial: deploy and manage Windows devices in a school" itemType: how-to-guide
- url: /education/windows/windows-11-se-overview text: Configure federated sign-in for Windows devices
text: Windows 11 SE Overview - url: /education/windows/get-minecraft-for-education
- url: /education/windows/federated-sign-in itemType: concept
text: Configure federated sign-in for Windows devices text: Get and deploy Minecraft Education
- url: /education/windows/get-minecraft-for-education - url: /education/windows/windows-11-se-overview
text: Get and deploy Minecraft Education itemType: overview
- url: /education/windows/take-tests-in-windows text: Windows 11 SE
text: Take tests and assessments in Windows footerLink:
- url: /education/Windows url: /education/windows
text: Learn more about Windows for Education > text: See more
additionalContent: additionalContent:
sections: sections:
@ -151,46 +138,36 @@ additionalContent:
- title: Windows hardware - title: Windows hardware
links: links:
- text: Windows hardware developer documentation - text: Download and install the Windows ADK
url: /windows-hardware/drivers/ url: /windows-hardware/get-started/adk-install
- text: Get started with building Windows devices
url: /windows-hardware/get-started
- text: Download the Windows Driver Kit - text: Download the Windows Driver Kit
url: /windows-hardware/drivers/download-the-wdk url: /windows-hardware/drivers/download-the-wdk
- text: Device and driver installation - text: Device and driver installation
url: /windows-hardware/drivers/install/overview-of-device-and-driver-installation url: /windows-hardware/drivers/install/overview-of-device-and-driver-installation
- text: Windows Driver Frameworks
url: /windows-hardware/drivers/wdf/
- text: Kernel-mode driver architecture design guide
url: /windows-hardware/drivers/kernel/
- title: Windows Server - title: Windows Server
links: links:
- text: Windows Server documentation - text: Windows Server documentation
url: /windows-server url: /windows-server
- text: What's new in Windows Server 2022? - text: What's new in Windows Server 2025
url: /windows-server/get-started/whats-new-in-windows-server-2022 url: /windows-server/get-started/whats-new-windows-server-2025
- text: Windows Server blog - text: Windows Server blog
url: https://cloudblogs.microsoft.com/windowsserver/ url: https://www.microsoft.com/windows-server/blog/
- title: Windows product site and blogs - title: Windows product site and blogs
links: links:
- text: Find out how Windows enables your business to do more - text: Windows user documentation
url: https://www.microsoft.com/microsoft-365/windows url: https://support.microsoft.com/windows
- text: Windows blogs - text: Windows blogs
url: https://blogs.windows.com/ url: https://blogs.windows.com/
- text: Windows IT Pro blog - text: Windows IT Pro blog
url: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/bg-p/Windows10Blog url: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/bg-p/Windows-ITPro-blog
- text: Microsoft Intune blog
url: https://techcommunity.microsoft.com/t5/microsoft-intune-blog/bg-p/MicrosoftEndpointManagerBlog
- text: "Windows help & learning: end-user documentation"
url: https://support.microsoft.com/windows
- title: Participate in the community - title: Participate in the community
links: links:
- text: Windows community - text: Windows community
url: https://techcommunity.microsoft.com/t5/windows/ct-p/Windows10 url: https://techcommunity.microsoft.com/t5/windows/ct-p/Windows
- text: Microsoft Intune community - text: Windows office hours
url: https://techcommunity.microsoft.com/t5/microsoft-intune/bd-p/Microsoft-Intune url: https://aka.ms/Windows/OfficeHours
- text: Microsoft Support community - text: Microsoft support community
url: https://answers.microsoft.com/ url: https://answers.microsoft.com/windowsclient/forum