mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 16:27:22 +00:00
Merge branch 'main' of github.com:MicrosoftDocs/windows-docs-pr into pm-20221208-whfb
This commit is contained in:
Paolo Matarazzo
commit
90cf68eeb9
@ -2,6 +2,7 @@
|
||||
title: Activate by Proxy an Active Directory Forest (Windows 10)
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate by proxy an Active Directory (AD) forest.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Activate an Active Directory Forest Online (Windows 10)
|
||||
description: Use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate an Active Directory (AD) forest online.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -1,6 +1,8 @@
|
||||
---
|
||||
title: Activate using Active Directory-based activation
|
||||
description: Learn how active directory-based activation is implemented as a role service that relies on AD DS to store activation objects.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
author: frankroj
|
||||
ms.author: frankroj
|
||||
@ -14,7 +16,7 @@ ms.collection: highpri
|
||||
|
||||
# Activate using Active Directory-based activation
|
||||
|
||||
*Applies to:*
|
||||
**Applies to:**
|
||||
|
||||
- Windows
|
||||
- Windows Server
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
title: Activate using Key Management Service (Windows 10)
|
||||
description: Learn how to use Key Management Service (KMS) to activate Windows.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
description: How to activate using Key Management Service in Windows 10.
|
||||
ms.prod: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
@ -14,7 +16,7 @@ ms.technology: itpro-fundamentals
|
||||
|
||||
# Activate using Key Management Service
|
||||
|
||||
*Applies to:*
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Activate clients running Windows 10 (Windows 10)
|
||||
description: After you have configured Key Management Service (KMS) or Active Directory-based activation on your network, activating a client running Windows 10 is easy.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
@ -14,7 +15,7 @@ ms.technology: itpro-fundamentals
|
||||
|
||||
# Activate clients running Windows 10
|
||||
|
||||
*Applies to:*
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Active Directory-Based Activation Overview (Windows 10)
|
||||
description: Enable your enterprise to activate its computers through a connection to their domain using Active Directory-Based Activation (ADBA).
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Add and Manage Products (Windows 10)
|
||||
description: Add client computers into the Volume Activation Management Tool (VAMT). After you add the computers, you can manage the products that are installed on your network.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Add and Remove Computers (Windows 10)
|
||||
description: The Discover products function on the Volume Activation Management Tool (VAMT) allows you to search the Active Directory domain or a general LDAP query.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Add and Remove a Product Key (Windows 10)
|
||||
description: Add a product key to the Volume Activation Management Tool (VAMT) database. Also, learn how to remove the key from the database.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Appendix Information sent to Microsoft during activation (Windows 10)
|
||||
description: Learn about the information sent to Microsoft during activation.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
author: frankroj
|
||||
@ -14,7 +15,7 @@ ms.topic: article
|
||||
|
||||
# Appendix: Information sent to Microsoft during activation
|
||||
|
||||
*Applies to:*
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Configure Client Computers (Windows 10)
|
||||
description: Learn how to configure client computers to enable the Volume Activation Management Tool (VAMT) to function correctly.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
author: frankroj
|
||||
ms.author: frankroj
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Import and export VAMT data
|
||||
description: Learn how to use the VAMT to import product-activation data from a file into SQL Server.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Install and Configure VAMT (Windows 10)
|
||||
description: Learn how to install and configure the Volume Activation Management Tool (VAMT), and learn where to find information about the process.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Install a KMS Client Key (Windows 10)
|
||||
description: Learn to use the Volume Activation Management Tool (VAMT) to install Generic Volume License Key (GVLK), or KMS client, product keys.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Install a Product Key (Windows 10)
|
||||
description: Learn to use the Volume Activation Management Tool (VAMT) to install retail, Multiple Activation Key (MAK), and KMS Host key (CSVLK).
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -1,6 +1,8 @@
|
||||
---
|
||||
title: Install VAMT (Windows 10)
|
||||
description: Learn how to install Volume Activation Management Tool (VAMT) as part of the Windows Assessment and Deployment Kit (ADK) for Windows 10.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Introduction to VAMT (Windows 10)
|
||||
description: VAMT enables administrators to automate and centrally manage the Windows, Microsoft Office, and select other Microsoft products volume and retail activation process.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Perform KMS Activation (Windows 10)
|
||||
description: The Volume Activation Management Tool (VAMT) can be used to perform volume activation using the Key Management Service (KMS).
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Perform Local Reactivation (Windows 10)
|
||||
description: An initially activated a computer using scenarios like MAK, retail, or CSLVK (KMS host), can be reactivated with Volume Activation Management Tool (VAMT).
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Manage Activations (Windows 10)
|
||||
description: Learn how to manage activations and how to activate a client computer by using various activation methods.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Manage Product Keys (Windows 10)
|
||||
description: In this article, learn how to add and remove a product key from the Volume Activation Management Tool (VAMT).
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Manage VAMT Data (Windows 10)
|
||||
description: Learn how to save, import, export, and merge a Computer Information List (CILX) file using the Volume Activation Management Tool (VAMT).
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Monitor activation (Windows 10)
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
description: Understand the most common methods to monitor the success of the activation process for a computer running Windows.
|
||||
@ -14,7 +15,7 @@ ms.date: 11/07/2022
|
||||
|
||||
# Monitor activation
|
||||
|
||||
*Applies to:*
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Perform Online Activation (Windows 10)
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) to enable client products to be activated online.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Plan for volume activation (Windows 10)
|
||||
description: Product activation is the process of validating software with the manufacturer after it has been installed on a specific computer.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
@ -14,7 +15,7 @@ ms.date: 11/07/2022
|
||||
|
||||
# Plan for volume activation
|
||||
|
||||
*Applies to:*
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Perform Proxy Activation (Windows 10)
|
||||
description: Perform proxy activation by using the Volume Activation Management Tool (VAMT) to activate client computers that don't have Internet access.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Remove Products (Windows 10)
|
||||
description: Learn how you must delete products from the product list view so you can remove products from the Volume Activation Management Tool (VAMT).
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Scenario 3 KMS Client Activation (Windows 10)
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) to activate Key Management Service (KMS) client keys or Generic Volume License Keys (GVLKs).
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Scenario 1 Online Activation (Windows 10)
|
||||
description: Achieve network access by deploying the Volume Activation Management Tool (VAMT) in a Core Network environment.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Scenario 2 Proxy Activation (Windows 10)
|
||||
description: Use the Volume Activation Management Tool (VAMT) to activate products that are installed on workgroup computers in an isolated lab environment.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Update Product Status (Windows 10)
|
||||
description: Learn how to use the Update license status function to add the products that are installed on the computers.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Use the Volume Activation Management Tool (Windows 10)
|
||||
description: The Volume Activation Management Tool (VAMT) provides several useful features, including the ability to track and monitor several types of product keys.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
@ -14,7 +15,7 @@ ms.technology: itpro-fundamentals
|
||||
|
||||
# Use the Volume Activation Management Tool
|
||||
|
||||
*Applies to:*
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Use VAMT in Windows PowerShell (Windows 10)
|
||||
description: Learn how to use Volume Activation Management Tool (VAMT) PowerShell cmdlets to perform the same functions as the Vamt.exe command-line tool.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: VAMT known issues (Windows 10)
|
||||
description: Find out the current known issues with the Volume Activation Management Tool (VAMT), versions 3.0. and 3.1.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: VAMT Requirements (Windows 10)
|
||||
description: In this article, learn about the product key and system requierements for Volume Activation Management Tool (VAMT).
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: VAMT Step-by-Step Scenarios (Windows 10)
|
||||
description: Learn step-by-step instructions on implementing the Volume Activation Management Tool (VAMT) in typical environments.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -1,6 +1,8 @@
|
||||
---
|
||||
title: VAMT technical reference
|
||||
description: The Volume Activation Management Tool (VAMT) enables network administrators to automate and centrally manage volume activation and retail activation.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Volume Activation for Windows 10
|
||||
description: Learn how to use volume activation to deploy & activate Windows 10. Includes details for orgs that have used volume activation for earlier versions of Windows.
|
||||
ms.reviewer:
|
||||
- nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
@ -14,7 +15,7 @@ ms.technology: itpro-fundamentals
|
||||
|
||||
# Volume Activation for Windows 10
|
||||
|
||||
*Applies to:*
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Roles and responsibilities
|
||||
description: This article describes the roles and responsibilities provided by Windows Autopatch and what the customer must do
|
||||
ms.date: 12/09/2022
|
||||
ms.date: 12/12/2022
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -14,7 +14,7 @@ msreviewer: hathind
|
||||
|
||||
# Roles and responsibilities
|
||||
|
||||
This article outlines your and Windows Autopatch's responsibilities when:
|
||||
This article outlines your responsibilities and Windows Autopatch's responsibilities when:
|
||||
|
||||
- [Preparing to enroll into the Windows Autopatch service](#prepare)
|
||||
- [Deploying the service](#deploy)
|
||||
@ -25,8 +25,10 @@ This article outlines your and Windows Autopatch's responsibilities when:
|
||||
| Task | Your responsibility | Windows Autopatch |
|
||||
| ----- | :-----: | :-----: |
|
||||
| Review the [prerequisites](../prepare/windows-autopatch-prerequisites.md) | :heavy_check_mark: | :x: |
|
||||
| [Review the service data platform and privacy compliance details](../references/windows-autopatch-privacy.md) | :heavy_check_mark: | :x: |
|
||||
| Ensure device [prerequisites](../prepare/windows-autopatch-prerequisites.md) are met and in place prior to enrollment | :heavy_check_mark: | :x: |
|
||||
| Ensure [infrastructure and environment prerequisites](../prepare/windows-autopatch-configure-network.md) are met and in place prior to enrollment | :heavy_check_mark: | :x: |
|
||||
| Prepare to remove your devices from existing unsupported [Windows update](../references/windows-autopatch-wqu-unsupported-policies.md) and [Microsoft 365](../references/windows-autopatch-microsoft-365-policies.md) policies | :heavy_check_mark: | :x: |
|
||||
| [Configure required network endpoints](../prepare/windows-autopatch-configure-network.md#required-microsoft-product-endpoints) | :heavy_check_mark: | :x: |
|
||||
| [Fix issues identified by the Readiness assessment tool](../prepare/windows-autopatch-fix-issues.md) | :heavy_check_mark: | :x: |
|
||||
| [Enroll tenant into the Windows Autopatch service](../prepare/windows-autopatch-enroll-tenant.md) | :heavy_check_mark: | :x: |
|
||||
@ -38,14 +40,12 @@ This article outlines your and Windows Autopatch's responsibilities when:
|
||||
| ----- | :-----: | :-----: |
|
||||
| [Add and verify admin contacts](../deploy/windows-autopatch-admin-contacts.md) in Microsoft Endpoint Manager | :heavy_check_mark: | :x: |
|
||||
| [Deploy and configure Windows Autopatch service configuration](../references/windows-autopatch-changes-to-tenant.md) | :x: | :heavy_check_mark: |
|
||||
| [Run the pre-registration device readiness checks](../deploy/windows-autopatch-register-devices.md#about-the-ready-not-ready-and-not-registered-tabs) | :x: | :heavy_check_mark: |
|
||||
| [Maintain and manage the Windows Autopatch service configuration](../operate/windows-autopatch-maintain-environment.md) | :x: | :heavy_check_mark: |
|
||||
| [Maintain customer configuration to align with the Windows Autopatch service configuration](../operate/windows-autopatch-maintain-environment.md) | :heavy_check_mark: | :x: |
|
||||
| Resolve any conflicting and [unsupported Windows update](../references/windows-autopatch-wqu-unsupported-policies.md) and [Microsoft 365 policies](../references/windows-autopatch-microsoft-365-policies.md) | :heavy_check_mark: | :x: |
|
||||
| Educate users on the Windows Autopatch end user update experience<ul><li>[Windows quality update end user experience](../operate/windows-autopatch-wqu-end-user-exp.md)</li><li>[Windows feature update end user experience](../operate/windows-autopatch-fu-end-user-exp.md)</li><li>[Microsoft 365 Apps for enterprise end user experience](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#end-user-experience)</li><li>[Microsoft Teams end user experience](../operate/windows-autopatch-teams.md#end-user-experience)</li></ul> | :heavy_check_mark: | :x: |
|
||||
| Remove your devices from existing unsupported [Windows update](../references/windows-autopatch-wqu-unsupported-policies.md) and [Microsoft 365](../references/windows-autopatch-microsoft-365-policies.md) policies | :heavy_check_mark: | :x: |
|
||||
| [Register devices/add devices to the Windows Autopatch Device Registration group](../deploy/windows-autopatch-register-devices.md#steps-to-register-devices) | :heavy_check_mark: | :x: |
|
||||
| [Run the pre-registration device readiness checks](../deploy/windows-autopatch-register-devices.md#about-the-ready-not-ready-and-not-registered-tabs) | :x: | :heavy_check_mark: |
|
||||
| [Automatically assign devices to First, Fast & Broad deployment rings at device registration](../operate/windows-autopatch-update-management.md#deployment-ring-calculation-logic) | :x: | :heavy_check_mark: |
|
||||
| [Manually override device assignments to First, Fast & Broad deployment rings](../operate/windows-autopatch-update-management.md#moving-devices-in-between-deployment-rings) | :heavy_check_mark: | :x: |
|
||||
| [Run on-going post-registration device readiness checks](../deploy/windows-autopatch-post-reg-readiness-checks.md) | :x: | :heavy_check_mark: |
|
||||
| [Remediate devices displayed in the **Not ready** tab](../deploy/windows-autopatch-post-reg-readiness-checks.md#about-the-three-tabs-in-the-devices-blade) | :heavy_check_mark: | :x: |
|
||||
| [Remediate devices displayed in the **Not registered** tab](../deploy/windows-autopatch-post-reg-readiness-checks.md#about-the-three-tabs-in-the-devices-blade) | :heavy_check_mark: | :x: |
|
||||
| [Populate the Test deployment ring membership](../operate/windows-autopatch-update-management.md#deployment-ring-calculation-logic) | :heavy_check_mark: | :x: |
|
||||
@ -57,9 +57,14 @@ This article outlines your and Windows Autopatch's responsibilities when:
|
||||
| Task | Your responsibility | Windows Autopatch |
|
||||
| ----- | :-----: | :-----: |
|
||||
| [Maintain contacts in the Microsoft Endpoint Manager admin center](../deploy/windows-autopatch-admin-contacts.md) | :heavy_check_mark: | :x: |
|
||||
| [Maintain and manage the Windows Autopatch service configuration](../operate/windows-autopatch-maintain-environment.md) | :x: | :heavy_check_mark: |
|
||||
| [Maintain customer configuration to align with the Windows Autopatch service configuration](../operate/windows-autopatch-maintain-environment.md) | :heavy_check_mark: | :x: |
|
||||
| [Run on-going checks to ensure devices are only present in one deployment ring](../operate/windows-autopatch-update-management.md#automated-deployment-ring-remediation-functions) | :x: | :heavy_check_mark: |
|
||||
| [Maintain the Test deployment ring membership](../operate/windows-autopatch-update-management.md#deployment-ring-calculation-logic) | :heavy_check_mark: | :x: |
|
||||
| [Evaluate updates](../operate/windows-autopatch-wqu-signals.md) | :x: | :heavy_check_mark: |
|
||||
| Monitor [Windows update signals](../operate/windows-autopatch-wqu-signals.md) for safe update release | :x: | :heavy_check_mark: |
|
||||
| Test specific [business update scenarios](../operate/windows-autopatch-wqu-signals.md) | :heavy_check_mark: | :x: |
|
||||
| [Define and implement release schedule](../operate/windows-autopatch-wqu-overview.md) | :x: | :heavy_check_mark: |
|
||||
| Communicate the update [release schedule](../operate/windows-autopatch-wqu-communications.md) | :x: | :heavy_check_mark: |
|
||||
| Release updates (as scheduled)<ul><li>[Windows quality updates](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases)</li><li>[Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#update-release-schedule)</li><li>[Microsoft Edge](../operate/windows-autopatch-edge.md#update-release-schedule)</li><li>[Microsoft Teams](../operate/windows-autopatch-teams.md#update-release-schedule)</li><ul>| :x: | :heavy_check_mark: |
|
||||
| [Release updates (expedited)](../operate/windows-autopatch-wqu-overview.md#expedited-releases) | :x: | :heavy_check_mark: |
|
||||
| [Deploy updates to devices](../operate/windows-autopatch-update-management.md) | :x: | :heavy_check_mark: |
|
||||
@ -67,10 +72,12 @@ This article outlines your and Windows Autopatch's responsibilities when:
|
||||
| Review [update reports](../operate/windows-autopatch-wqu-reports-overview.md) | :heavy_check_mark: | :x: |
|
||||
| [Pause updates (Windows Autopatch initiated)](../operate/windows-autopatch-wqu-signals.md) | :x: | :heavy_check_mark: |
|
||||
| [Pause updates (initiated by you)](../operate/windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release) | :heavy_check_mark: | :x: |
|
||||
| Educate users on the Windows Autopatch end user update experience<ul><li>[Windows quality update end user experience](../operate/windows-autopatch-wqu-end-user-exp.md)</li><li>[Windows feature update end user experience](../operate/windows-autopatch-fu-end-user-exp.md)</li><li>[Microsoft 365 Apps for enterprise end user experience](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#end-user-experience)</li><li>[Microsoft Teams end user experience](../operate/windows-autopatch-teams.md#end-user-experience)</li></ul> | :heavy_check_mark: | :x: |
|
||||
| [Device not up to date (Microsoft action)](../operate/windows-autopatch-wqu-reports-overview.md#not-up-to-date-microsoft-action) | :x: | :heavy_check_mark: |
|
||||
| [Ineligible Devices (Customer action)](../operate/windows-autopatch-wqu-reports-overview.md#ineligible-devices-customer-action) | :heavy_check_mark: | :x: |
|
||||
| [Raise, manage and resolve an incident if devices aren't meeting the Service Level Objective](windows-autopatch-overview.md#update-management) | :x: | :heavy_check_mark: |
|
||||
| Run [on-going post-registration device readiness checks](../deploy/windows-autopatch-post-reg-readiness-checks.md) | :x: | :heavy_check_mark: |
|
||||
| [Remediate devices displayed in the **Not ready** tab](../deploy/windows-autopatch-post-reg-readiness-checks.md#about-the-three-tabs-in-the-devices-blade) | :heavy_check_mark: | :x: |
|
||||
| Resolve any conflicting and unsupported [Windows update](../references/windows-autopatch-wqu-unsupported-policies.md) and [Microsoft 365](../references/windows-autopatch-microsoft-365-policies.md) policies | :heavy_check_mark: | :x: |
|
||||
| [Investigate devices that aren't up to date within the service level objective (Microsoft action)](../operate/windows-autopatch-wqu-reports-overview.md#not-up-to-date-microsoft-action) | :x: | :heavy_check_mark: |
|
||||
| [Investigate and remediate devices that are marked as ineligible (Customer action)](../operate/windows-autopatch-wqu-reports-overview.md#ineligible-devices-customer-action) | :heavy_check_mark: | :x: |
|
||||
| [Raise, manage and resolve a service incident if an update management area isn't meeting the service level objective](windows-autopatch-overview.md#update-management) | :x: | :heavy_check_mark: |
|
||||
| [Deregister devices](../operate/windows-autopatch-deregister-devices.md) | :heavy_check_mark: | :x: |
|
||||
| [Register a device that was previously deregistered (upon customers request)](../operate/windows-autopatch-deregister-devices.md#excluded-devices) | :x: | :heavy_check_mark: |
|
||||
| [Request unenrollment from Windows Autopatch](../operate/windows-autopatch-unenroll-tenant.md) | :heavy_check_mark: | :x: |
|
||||
@ -81,3 +88,4 @@ This article outlines your and Windows Autopatch's responsibilities when:
|
||||
| [Review and respond to Windows Autopatch Tenant management alerts](../operate/windows-autopatch-maintain-environment.md#windows-autopatch-tenant-actions) | :heavy_check_mark: | :x: |
|
||||
| [Raise and respond to support requests](../operate/windows-autopatch-support-request.md) | :heavy_check_mark: | :x: |
|
||||
| [Manage and respond to support requests](../operate/windows-autopatch-support-request.md#manage-an-active-support-request) | :x: | :heavy_check_mark: |
|
||||
| Review the [What’s new](../whats-new/windows-autopatch-whats-new-2022.md) section to stay up to date with updated feature and service releases | :heavy_check_mark: | :x: |
|
||||
|
||||
@ -30,6 +30,8 @@ In Windows 10, version 1903 and later, you'll see taxonomy updates in both the *
|
||||
|
||||
Additionally, starting in Windows 11 and Windows Server 2022, we’re simplifying your diagnostic data controls by moving from four diagnostic data controls to three: **Diagnostic data off**, **Required**, and **Optional**. We’re also clarifying the Security diagnostic data level to reflect its behavior more accurately by changing it to **Diagnostic data off**. All these changes are explained in the section named **Behavioral changes**.
|
||||
|
||||
Prior to December 13 2022, the default setting for Windows Server 2022 Datacenter: Azure Edition images deployed using Azure Marketplace was **Diagnostic data off**. Beginning December 13 2022, all newly deployed images are set to **Required diagnostic data** to align with all other Windows releases. All other Windows releases and existing installations remain unchanged.
|
||||
|
||||
## Taxonomy changes
|
||||
|
||||
Starting in Windows 10, version 1903 and later, both the **Out-of-Box-Experience** (OOBE) and the **Diagnostics & feedback** privacy setting pages will reflect the following changes:
|
||||
|
||||
@ -164,6 +164,8 @@ Here’s a summary of the types of data that is included with each setting:
|
||||
|
||||
This setting was previously labeled as **Security**. When you configure this setting, no Windows diagnostic data is sent from your device. This is only available on Windows Server, Windows Enterprise, and Windows Education editions. If you choose this setting, devices in your organization will still be secure.
|
||||
|
||||
This was the default setting for Windows Server 2022 Datacenter: Azure Edition prior to December 13, 2022.
|
||||
|
||||
>[!NOTE]
|
||||
> If your organization relies on Windows Update, the minimum recommended setting is **Required diagnostic data**. Because no Windows Update information is collected when diagnostic data is off, important information about update failures is not sent. Microsoft uses this information to fix the causes of those failures and improve the quality of our updates.
|
||||
|
||||
@ -171,7 +173,7 @@ This setting was previously labeled as **Security**. When you configure this set
|
||||
|
||||
Required diagnostic data, previously labeled as **Basic**, gathers a limited set of data that’s critical for understanding the device and its configuration. This data helps to identify problems that can occur on a specific hardware or software configuration. For example, it can help determine if crashes are more frequent on devices with a specific amount of memory or that are running a specific driver version.
|
||||
|
||||
This is the default setting for current releases of Windows, Windows 10, version 1903.
|
||||
This is the default setting for current releases of Windows, Windows 10, version 1903. Beginning December 13, 2022, it is also the default setting for Windows Server 2022 Datacenter: Azure Edition.
|
||||
|
||||
Required diagnostic data includes:
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user