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

Merge pull request #9568 from aczechowski/cz-20240205-autopatch

Browse Source 
bulk update manager metadata for autopatch
This commit is contained in:
Gary Moore 2024-02-05 16:50:46 -08:00 committed by GitHub
commit 0eb471ce95
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
50 changed files with 146 additions and 146 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/windows-autopatch/deploy/windows-autopatch-admin-contacts.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- tier2 - tier2
@ -41,6 +41,6 @@ Your admin contacts will receive notifications about support request updates and
1. Under **Tenant administration** in the **Windows Autopatch** section, select **Admin contacts**. 1. Under **Tenant administration** in the **Windows Autopatch** section, select **Admin contacts**.
1. Select **+Add**. 1. Select **+Add**.
1. Enter the contact details including name, email, phone number and preferred language. For a support ticket, the ticket's primary contact's preferred language will determine the language used for email communications. 1. Enter the contact details including name, email, phone number and preferred language. For a support ticket, the ticket's primary contact's preferred language will determine the language used for email communications.
1. Select an [Area of focus](#area-of-focus) and enter details of the contact's knowledge and authority in the specified area of focus. 1. Select an [Area of focus](#area-of-focus) and enter details of the contact's knowledge and authority in the specified area of focus.
1. Select **Save** to add the contact. 1. Select **Save** to add the contact.
1. Repeat for each area of focus. 1. Repeat for each area of focus.

4
windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri
@ -67,7 +67,7 @@ As described in **step #4** in the previous [Detailed device registration workfl
During the tenant enrollment process, Windows Autopatch creates two different deployment ring sets: During the tenant enrollment process, Windows Autopatch creates two different deployment ring sets:
- [Service-based deployment ring set](../deploy/windows-autopatch-groups-overview.md#service-based-deployment-rings) - [Service-based deployment ring set](../deploy/windows-autopatch-groups-overview.md#service-based-deployment-rings)
- [Software update-based deployment ring set](../deploy/windows-autopatch-groups-overview.md#software-based-deployment-rings) - [Software update-based deployment ring set](../deploy/windows-autopatch-groups-overview.md#software-based-deployment-rings)
The following four Microsoft Entra ID assigned groups are used to organize devices for the service-based deployment ring set: The following four Microsoft Entra ID assigned groups are used to organize devices for the service-based deployment ring set:

4
windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri
@ -123,7 +123,7 @@ You **can’t** rename the Default Autopatch group. However, you can rename a Cu
## Delete a Custom Autopatch group ## Delete a Custom Autopatch group
You **can’t** delete the Default Autopatch group. However, you can delete a Custom Autopatch group. You **can’t** delete the Default Autopatch group. However, you can delete a Custom Autopatch group.
**To delete a Custom Autopatch group:** **To delete a Custom Autopatch group:**

2
windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri

4
windows/deployment/windows-autopatch/deploy/windows-autopatch-post-reg-readiness-checks.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri
@ -20,7 +20,7 @@ ms.collection:
> [!IMPORTANT] > [!IMPORTANT]
> This feature is in "public preview". It is being actively developed, and may not be complete. They're made available on a “Preview” basis. You can test and use these features in production environments and scenarios, and provide feedback. > This feature is in "public preview". It is being actively developed, and may not be complete. They're made available on a “Preview” basis. You can test and use these features in production environments and scenarios, and provide feedback.
One of the most expensive aspects of the software update management process is to make sure devices are always healthy to receive and report software updates for each software update release cycle. One of the most expensive aspects of the software update management process is to make sure devices are always healthy to receive and report software updates for each software update release cycle.
Having a way of measuring, quickly detecting and remediating when something goes wrong with on-going change management processes is important; it helps mitigate high Helpdesk ticket volumes, reduces cost, and improves overall update management results. Having a way of measuring, quickly detecting and remediating when something goes wrong with on-going change management processes is important; it helps mitigate high Helpdesk ticket volumes, reduces cost, and improves overall update management results.

8
windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri
@ -31,7 +31,7 @@ Windows Autopatch can take over software update management control of devices th
### Windows Autopatch groups device registration ### Windows Autopatch groups device registration
When you either create/edit a [Custom Autopatch group](../deploy/windows-autopatch-groups-overview.md#about-custom-autopatch-groups) or edit the [Default Autopatch group](../deploy/windows-autopatch-groups-overview.md#about-the-default-autopatch-group) to add or remove deployment rings, the device-based Microsoft Entra groups you use when setting up your deployment rings are scanned to see if devices need to be registered with the Windows Autopatch service. When you either create/edit a [Custom Autopatch group](../deploy/windows-autopatch-groups-overview.md#about-custom-autopatch-groups) or edit the [Default Autopatch group](../deploy/windows-autopatch-groups-overview.md#about-the-default-autopatch-group) to add or remove deployment rings, the device-based Microsoft Entra groups you use when setting up your deployment rings are scanned to see if devices need to be registered with the Windows Autopatch service.
If devices aren’t registered, Autopatch groups starts the device registration process by using your existing device-based Microsoft Entra groups instead of the Windows Autopatch Device Registration group. If devices aren’t registered, Autopatch groups starts the device registration process by using your existing device-based Microsoft Entra groups instead of the Windows Autopatch Device Registration group.
@ -152,7 +152,7 @@ Windows 365 Enterprise gives IT admins the option to register devices with the W
1. In the left pane, select **Devices**. 1. In the left pane, select **Devices**.
1. Navigate to Provisioning > **Windows 365**. 1. Navigate to Provisioning > **Windows 365**.
1. Select Provisioning policies > **Create policy**. 1. Select Provisioning policies > **Create policy**.
1. Provide a policy name and select **Join Type**. For more information, see [Device join types](/windows-365/enterprise/identity-authentication#device-join-types). 1. Provide a policy name and select **Join Type**. For more information, see [Device join types](/windows-365/enterprise/identity-authentication#device-join-types).
1. Select **Next**. 1. Select **Next**.
1. Choose the desired image and select **Next**. 1. Choose the desired image and select **Next**.
1. Under the **Microsoft managed services** section, select **Windows Autopatch**. Then, select **Next**. If the *Windows Autopatch (preview) can't manage your Cloud PCs until a Global Admin has finished setting it up.* message appears, you must [enroll your tenant](../prepare/windows-autopatch-enroll-tenant.md) to continue. 1. Under the **Microsoft managed services** section, select **Windows Autopatch**. Then, select **Next**. If the *Windows Autopatch (preview) can't manage your Cloud PCs until a Global Admin has finished setting it up.* message appears, you must [enroll your tenant](../prepare/windows-autopatch-enroll-tenant.md) to continue.
@ -200,7 +200,7 @@ Support is available either through Windows 365, or the Windows Autopatch Servic
- For Windows 365 support, see [Get support](/mem/get-support). - For Windows 365 support, see [Get support](/mem/get-support).
- For Azure Virtual Desktop support, see [Get support](https://azure.microsoft.com/support/create-ticket/). - For Azure Virtual Desktop support, see [Get support](https://azure.microsoft.com/support/create-ticket/).
- For Windows Autopatch support, see [Submit a support request](/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request). - For Windows Autopatch support, see [Submit a support request](/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request).
## Device management lifecycle scenarios ## Device management lifecycle scenarios

4
windows/deployment/windows-autopatch/index.yml
View File

@ -10,7 +10,7 @@ metadata:
ms.topic: landing-page # Required ms.topic: landing-page # Required
author: tiaraquan #Required; your GitHub user alias, with correct capitalization. author: tiaraquan #Required; your GitHub user alias, with correct capitalization.
ms.author: tiaraquan #Required; microsoft alias of author; optional team alias. ms.author: tiaraquan #Required; microsoft alias of author; optional team alias.
manager: dougeby manager: aaroncz
ms.date: 05/30/2022 #Required; mm/dd/yyyy format. ms.date: 05/30/2022 #Required; mm/dd/yyyy format.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
@ -34,7 +34,7 @@ landingContent:
url: ./overview/windows-autopatch-overview.md url: ./overview/windows-autopatch-overview.md
- text: Windows Autopatch FAQ - text: Windows Autopatch FAQ
url: ./overview/windows-autopatch-faq.yml url: ./overview/windows-autopatch-faq.yml
# Card (optional) # Card (optional)
- title: Articles and blog posts - title: Articles and blog posts
linkLists: linkLists:

4
windows/deployment/windows-autopatch/operate/windows-autopatch-device-alerts.md
View File

@ -1,6 +1,6 @@
--- ---
title: Device alerts title: Device alerts
description: Provide notifications and information about the necessary steps to keep your devices up to date. description: Provide notifications and information about the necessary steps to keep your devices up to date.
ms.date: 08/01/2023 ms.date: 08/01/2023
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: adnich ms.reviewer: adnich
ms.collection: ms.collection:
- highpri - highpri

10
windows/deployment/windows-autopatch/operate/windows-autopatch-edge.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri
@ -17,14 +17,14 @@ ms.collection:
# Microsoft Edge # Microsoft Edge
Windows Autopatch uses the [Stable Channel](/deployedge/microsoft-edge-channels#stable-channel) of Microsoft Edge. Windows Autopatch uses the [Stable Channel](/deployedge/microsoft-edge-channels#stable-channel) of Microsoft Edge.
## Device eligibility ## Device eligibility
For a device to be eligible for Microsoft Edge updates as a part of Windows Autopatch, they must meet the following criteria: For a device to be eligible for Microsoft Edge updates as a part of Windows Autopatch, they must meet the following criteria:
- The device must be powered on and have an internet connection. - The device must be powered on and have an internet connection.
- There are no policy conflicts between Windows Autopatch policies and customer policies. - There are no policy conflicts between Windows Autopatch policies and customer policies.
- The device must be able to access the required network endpoints to reach the Microsoft Edge update service. - The device must be able to access the required network endpoints to reach the Microsoft Edge update service.
- If Microsoft Edge is open, it must restart for the update process to complete. - If Microsoft Edge is open, it must restart for the update process to complete.

2
windows/deployment/windows-autopatch/operate/windows-autopatch-exclude-device.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- tier2 - tier2

10
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-manage-windows-feature-update-release.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri
@ -42,7 +42,7 @@ The following table explains the auto-populating assignment of your deployments
| Phase 3 | Ring2 | Ring2 | | Phase 3 | Ring2 | Ring2 |
| Phase 4 | Last | Ring3 | | Phase 4 | Last | Ring3 |
If the Autopatch groups are edited after a release is created (Active status), the changes to the Autopatch group won’t be reflected unless you create a new custom release. If the Autopatch groups are edited after a release is created (Active status), the changes to the Autopatch group won’t be reflected unless you create a new custom release.
If you wish to change the auto-populating assignment of your deployment rings to release phases, you can do so by adding, removing, or editing the auto-populated phases. If you wish to change the auto-populating assignment of your deployment rings to release phases, you can do so by adding, removing, or editing the auto-populated phases.
@ -110,7 +110,7 @@ A phase is made of one or more Autopatch group deployment rings. Each phase repo
#### Details about Windows feature update policies #### Details about Windows feature update policies
Windows Autopatch creates one Windows feature update policy per phase using the following naming convention: Windows Autopatch creates one Windows feature update policy per phase using the following naming convention:
`Windows Autopatch – DSS policy – <Release Name> – Phase <Phase Number>` `Windows Autopatch – DSS policy – <Release Name> – Phase <Phase Number>`
@ -195,12 +195,12 @@ The following table is an example of the Windows feature update policies that we
> [!IMPORTANT] > [!IMPORTANT]
> You can only cancel a release under the Scheduled status. You cannot cancel a release under the **Active**, **Inactive** or **Paused** statuses. > You can only cancel a release under the Scheduled status. You cannot cancel a release under the **Active**, **Inactive** or **Paused** statuses.
**To cancel a release:** **To cancel a release:**
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). 1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
1. Select **Devices** from the left navigation menu. 1. Select **Devices** from the left navigation menu.
1. Under the **Windows Autopatch** section, select **Release management**. 1. Under the **Windows Autopatch** section, select **Release management**.
1. In the **Release schedule** tab, select **Windows feature updates**. 1. In the **Release schedule** tab, select **Windows feature updates**.
1. In the **Windows feature updates** blade, select the **horizontal ellipses (…)** > **Cancel** to cancel your feature updates release. 1. In the **Windows feature updates** blade, select the **horizontal ellipses (…)** > **Cancel** to cancel your feature updates release.
1. Select a reason for cancellation from the dropdown menu. 1. Select a reason for cancellation from the dropdown menu.
1. Optional. Enter details about why you're pausing or resuming the selected update. 1. Optional. Enter details about why you're pausing or resuming the selected update.

4
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-update-management.md
View File

@ -8,7 +8,7 @@ ms.topic: overview
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri
@ -33,7 +33,7 @@ Keeping your devices up to date is a balance of speed and stability. Windows Aut
## Autopatch groups ## Autopatch groups
Autopatch groups help Microsoft Cloud-Managed services meet all organizations where they are at in their update management journey. Autopatch groups help Microsoft Cloud-Managed services meet all organizations where they are at in their update management journey.
Autopatch groups is a logical container that groups several [Microsoft Entra groups](/azure/active-directory/fundamentals/active-directory-groups-view-azure-portal), and software update policies, such as Windows Update rings and feature update policies, together. Autopatch groups is a logical container that groups several [Microsoft Entra groups](/azure/active-directory/fundamentals/active-directory-groups-view-azure-portal), and software update policies, such as Windows Update rings and feature update policies, together.

2
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri

4
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-status-report.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri
@ -17,7 +17,7 @@ ms.collection:
# Feature update status report # Feature update status report
The Feature update status report provides a per device view of the current Windows OS upgrade status for all devices registered with Windows Autopatch.  The Feature update status report provides a per device view of the current Windows OS upgrade status for all devices registered with Windows Autopatch. 
**To view the Feature update status report:** **To view the Feature update status report:**

2
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-summary-dashboard.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri

2
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-trending-report.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri

4
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: adnich ms.reviewer: adnich
ms.collection: ms.collection:
- highpri - highpri
@ -36,7 +36,7 @@ The Windows quality report types are organized into the following focus areas:
## Windows feature update reports ## Windows feature update reports
The Windows feature update reports monitor the health and activity of your deployments and help you understand if your devices are maintaining update compliance targets. The Windows feature update reports monitor the health and activity of your deployments and help you understand if your devices are maintaining update compliance targets.
If update deployments aren’t successful, Windows Autopatch provides information on update deployment failures and who needs to remediate. Certain update deployment failures might require either Windows Autopatch to act on your behalf or you to fix the issue. If update deployments aren’t successful, Windows Autopatch provides information on update deployment failures and who needs to remediate. Certain update deployment failures might require either Windows Autopatch to act on your behalf or you to fix the issue.

2
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-communications.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri

8
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-end-user-exp.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: adnich ms.reviewer: adnich
ms.collection: ms.collection:
- highpri - highpri
@ -17,7 +17,7 @@ ms.collection:
# Windows quality update end user experience # Windows quality update end user experience
## User notifications ## User notifications
In this section we'll review what an end user would see in the following three scenarios: In this section we'll review what an end user would see in the following three scenarios:
@ -58,7 +58,7 @@ The deadline specified in the update policy is five days. Therefore, once this d
In the following example, the user is on holiday and the device is offline beyond the quality update deadline. The user then returns to work and the device is turned back on. In the following example, the user is on holiday and the device is offline beyond the quality update deadline. The user then returns to work and the device is turned back on.
Since the deadline has already passed, the device is granted a two-day grace period to install the update and restart. The user will be notified of a pending installation and given options to choose from. Once the two-day grace period has expired, the user is forced to restart with a 15-minute warning notification. Since the deadline has already passed, the device is granted a two-day grace period to install the update and restart. The user will be notified of a pending installation and given options to choose from. Once the two-day grace period has expired, the user is forced to restart with a 15-minute warning notification.
:::image type="content" source="../media/windows-quality-update-grace-period.png" alt-text="Windows quality update grace period" lightbox="../media/windows-quality-update-grace-period.png"::: :::image type="content" source="../media/windows-quality-update-grace-period.png" alt-text="Windows quality update grace period" lightbox="../media/windows-quality-update-grace-period.png":::
@ -66,4 +66,4 @@ Since the deadline has already passed, the device is granted a two-day grace per
Windows Autopatch understands the importance of not disrupting end users but also updating the devices quickly. To achieve this goal, updates are automatically downloaded and installed at an optimal time determined by the device. By default, [Active hours](/windows/client-management/mdm/policy-csp-update#activehoursstart) are configured dynamically based on device usage patterns. Device restarts occur outside of active hours until the deadline is reached. Windows Autopatch understands the importance of not disrupting end users but also updating the devices quickly. To achieve this goal, updates are automatically downloaded and installed at an optimal time determined by the device. By default, [Active hours](/windows/client-management/mdm/policy-csp-update#activehoursstart) are configured dynamically based on device usage patterns. Device restarts occur outside of active hours until the deadline is reached.
Windows Autopatch understands the importance of not disrupting critical devices but also updating the devices quickly. If you wish to configure a specific installation time or [Active hours](/windows/client-management/mdm/policy-csp-update#activehoursstart), use the [Customize Windows Update settings](../operate/windows-autopatch-groups-windows-update.md), and select the [**ScheduledInstall**](../operate/windows-autopatch-groups-windows-update.md#scheduled-install) option. Using this option removes the deadline enforced for a device restart. Devices with this configuration will also **not** be counted towards the [service level objective](../operate/windows-autopatch-groups-windows-quality-update-overview.md#service-level-objective). Windows Autopatch understands the importance of not disrupting critical devices but also updating the devices quickly. If you wish to configure a specific installation time or [Active hours](/windows/client-management/mdm/policy-csp-update#activehoursstart), use the [Customize Windows Update settings](../operate/windows-autopatch-groups-windows-update.md), and select the [**ScheduledInstall**](../operate/windows-autopatch-groups-windows-update.md#scheduled-install) option. Using this option removes the deadline enforced for a device restart. Devices with this configuration will also **not** be counted towards the [service level objective](../operate/windows-autopatch-groups-windows-quality-update-overview.md#service-level-objective).

32
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-overview.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri
@ -68,7 +68,7 @@ The service level objective for each of these states is calculated as:
> [!IMPORTANT] > [!IMPORTANT]
> This feature is in **public preview**. It's being actively developed, and might not be complete. > This feature is in **public preview**. It's being actively developed, and might not be complete.
You can import your organization’s existing Intune Update rings for Windows 10 and later into Windows Autopatch. Importing your organization’s Update rings provides the benefits of the Windows Autopatch's reporting and device readiness without the need to redeploy, or change your organization’s existing update rings.  You can import your organization’s existing Intune Update rings for Windows 10 and later into Windows Autopatch. Importing your organization’s Update rings provides the benefits of the Windows Autopatch's reporting and device readiness without the need to redeploy, or change your organization’s existing update rings. 
Imported rings automatically register all targeted devices into Windows Autopatch. For more information about device registration, see the [device registration workflow diagram](../deploy/windows-autopatch-device-registration-overview.md#detailed-device-registration-workflow-diagram). Imported rings automatically register all targeted devices into Windows Autopatch. For more information about device registration, see the [device registration workflow diagram](../deploy/windows-autopatch-device-registration-overview.md#detailed-device-registration-workflow-diagram).
@ -82,32 +82,32 @@ Imported rings automatically register all targeted devices into Windows Autopatc
**To import Update rings for Windows 10 and later:** **To import Update rings for Windows 10 and later:**
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).  1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). 
2. Select **Devices** from the left navigation menu.  2. Select **Devices** from the left navigation menu. 
3. Under the **Windows Autopatch** section, select **Release management**.  3. Under the **Windows Autopatch** section, select **Release management**. 
4. In the **Release management** blade, go to the **Release schedule** tab and select **Windows quality updates**.  4. In the **Release management** blade, go to the **Release schedule** tab and select **Windows quality updates**. 
5. Select **Import Update rings for Windows 10 and later**.  5. Select **Import Update rings for Windows 10 and later**. 
6. Select the existing rings you would like to import.  6. Select the existing rings you would like to import. 
7. Select **Import**. 7. Select **Import**.
### Remove an imported Update ring for Windows 10 and later ### Remove an imported Update ring for Windows 10 and later
**To remove an Imported Update rings for Windows 10 and later:** **To remove an Imported Update rings for Windows 10 and later:**
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).  1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). 
2. Select **Devices** from the left navigation menu.  2. Select **Devices** from the left navigation menu. 
3. Under the **Windows Autopatch** section, select **Release management**.  3. Under the **Windows Autopatch** section, select **Release management**. 
4. In the **Release management** blade, go to the **Release schedule** tab and select **Windows quality updates**.  4. In the **Release management** blade, go to the **Release schedule** tab and select **Windows quality updates**. 
5. Select the Update rings for Windows 10 and later you would like to remove.  5. Select the Update rings for Windows 10 and later you would like to remove. 
6. Select the **horizontal ellipses (...)** and select **Remove**. 6. Select the **horizontal ellipses (...)** and select **Remove**.
### Known limitations ### Known limitations
The following Windows Autopatch features aren't available with imported Intune Update rings:  The following Windows Autopatch features aren't available with imported Intune Update rings: 
- Autopatch groups and features dependent on Autopatch groups  - Autopatch groups and features dependent on Autopatch groups 
- Moving devices in between deployment rings in devices - Moving devices in between deployment rings in devices
- Automated deployment ring remediation functions  - Automated deployment ring remediation functions 
- Policy health and remediation - Policy health and remediation
## Release management ## Release management

2
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-signals.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri

2
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-status-report.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: adnich ms.reviewer: adnich
ms.collection: ms.collection:
- highpri - highpri

2
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-summary-dashboard.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: adnich ms.reviewer: adnich
ms.collection: ms.collection:
- highpri - highpri

2
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-trending-report.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: adnich ms.reviewer: adnich
ms.collection: ms.collection:
- highpri - highpri

2
windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-update.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: rekhanr ms.reviewer: rekhanr
ms.collection: ms.collection:
- highpri - highpri

4
windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: smithcharles ms.reviewer: smithcharles
ms.collection: ms.collection:
- highpri - highpri
@ -65,7 +65,7 @@ The type of banner that appears depends on the severity of the action. Currently
> [!NOTE] > [!NOTE]
> Only the Windows Autopatch sections of your tenant will be marked as **inactive**. > Only the Windows Autopatch sections of your tenant will be marked as **inactive**.
When Windows Autopatch is **inactive**, you're alerted with banners on all Windows Autopatch blades. You only have access to the Tenant management and Support requests blades. All other blades return an error message and redirect you to Tenant management blade. When Windows Autopatch is **inactive**, you're alerted with banners on all Windows Autopatch blades. You only have access to the Tenant management and Support requests blades. All other blades return an error message and redirect you to Tenant management blade.
To be taken out of the **inactive** status, you must [resolve any critical actions shown in the Tenant management blade](#critical-actions). To be taken out of the **inactive** status, you must [resolve any critical actions shown in the Tenant management blade](#critical-actions).

4
windows/deployment/windows-autopatch/operate/windows-autopatch-manage-driver-and-firmware-updates.md
View File

@ -1,14 +1,14 @@
--- ---
title: Manage driver and firmware updates title: Manage driver and firmware updates
description: This article explains how you can manage driver and firmware updates with Windows Autopatch description: This article explains how you can manage driver and firmware updates with Windows Autopatch
ms.date: 08/22/2023 ms.date: 08/22/2023
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: andredm7 ms.reviewer: andredm7
ms.collection: ms.collection:
- highpri - highpri

14
windows/deployment/windows-autopatch/operate/windows-autopatch-microsoft-365-apps-enterprise.md
View File

@ -1,14 +1,14 @@
--- ---
title: Microsoft 365 Apps for enterprise title: Microsoft 365 Apps for enterprise
description: This article explains how Windows Autopatch manages Microsoft 365 Apps for enterprise updates description: This article explains how Windows Autopatch manages Microsoft 365 Apps for enterprise updates
ms.date: 10/27/2023 ms.date: 10/27/2023
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri
@ -31,7 +31,7 @@ Microsoft 365 Apps deployed on the [Monthly Enterprise Channel](/deployoffice/ov
## Device eligibility ## Device eligibility
For a device to be eligible for Microsoft 365 Apps for enterprise updates (both 32-bit and 64-bit versions), as a part of Windows Autopatch, they must meet the following criteria: For a device to be eligible for Microsoft 365 Apps for enterprise updates (both 32-bit and 64-bit versions), as a part of Windows Autopatch, they must meet the following criteria:
- The device must be turned on and have an internet connection. - The device must be turned on and have an internet connection.
- The device must be able to access the [required network endpoints](../prepare/windows-autopatch-configure-network.md#required-microsoft-product-endpoints) to reach the Office Content Delivery Network (CDN). - The device must be able to access the [required network endpoints](../prepare/windows-autopatch-configure-network.md#required-microsoft-product-endpoints) to reach the Office Content Delivery Network (CDN).
@ -43,7 +43,7 @@ For a device to be eligible for Microsoft 365 Apps for enterprise updates (both
All devices registered for Windows Autopatch receive updates from the [Monthly Enterprise Channel](/deployoffice/overview-update-channels#monthly-enterprise-channel-overview). This practice provides your users with new features each month, and they receive just one update per month on a predictable release schedule. Updates are released on the second Tuesday of the month; these updates can include feature, security, and quality updates. These updates occur automatically and pulled directly from the Office Content Delivery Network (CDN). All devices registered for Windows Autopatch receive updates from the [Monthly Enterprise Channel](/deployoffice/overview-update-channels#monthly-enterprise-channel-overview). This practice provides your users with new features each month, and they receive just one update per month on a predictable release schedule. Updates are released on the second Tuesday of the month; these updates can include feature, security, and quality updates. These updates occur automatically and pulled directly from the Office Content Delivery Network (CDN).
Unlike Windows update, the Office CDN doesn't make the update available to all devices at once. Over the course of the release, the Office CDN gradually makes the update available to the whole population of devices. Windows Autopatch doesn't control the order in which updates are offered to devices across your estate. After the update downloads, there's a seven day [update deadline](../references/windows-autopatch-microsoft-365-policies.md) that specifies how long the user has until the user must apply the update. Unlike Windows update, the Office CDN doesn't make the update available to all devices at once. Over the course of the release, the Office CDN gradually makes the update available to the whole population of devices. Windows Autopatch doesn't control the order in which updates are offered to devices across your estate. After the update downloads, there's a seven day [update deadline](../references/windows-autopatch-microsoft-365-policies.md) that specifies how long the user has until the user must apply the update.
## Deployment rings ## Deployment rings
@ -68,16 +68,16 @@ Updates are only applied when Microsoft 365 Apps aren't running. Therefore, [end
### Office client app configuration ### Office client app configuration
To ensure that users are receiving automatic updates, Windows Autopatch prevents the user from opting out of automatic updates. To ensure that users are receiving automatic updates, Windows Autopatch prevents the user from opting out of automatic updates.
## Microsoft 365 Apps for enterprise update controls ## Microsoft 365 Apps for enterprise update controls
Windows Autopatch doesn't allow you to pause or roll back an update in the Microsoft Intune admin center. Windows Autopatch doesn't allow you to pause or roll back an update in the Microsoft Intune admin center.
[Submit a support request](../operate/windows-autopatch-support-request.md) to the Windows Autopatch Service Engineering Team to pause or roll back an update when needed. [Submit a support request](../operate/windows-autopatch-support-request.md) to the Windows Autopatch Service Engineering Team to pause or roll back an update when needed.
> [!NOTE] > [!NOTE]
> Updates are bundled together into a single release in the [Monthly Enterprise Channel](/deployoffice/overview-update-channels#monthly-enterprise-channel-overview). Therefore, we can't roll back only a portion of the update for Microsoft 365 Apps for enterprise. > Updates are bundled together into a single release in the [Monthly Enterprise Channel](/deployoffice/overview-update-channels#monthly-enterprise-channel-overview). Therefore, we can't roll back only a portion of the update for Microsoft 365 Apps for enterprise.
## Allow or block Microsoft 365 App updates ## Allow or block Microsoft 365 App updates

12
windows/deployment/windows-autopatch/operate/windows-autopatch-policy-health-and-remediation.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: rekhanr ms.reviewer: rekhanr
ms.collection: ms.collection:
- highpri - highpri
@ -27,7 +27,7 @@ When Windows Autopatch detects policies in the tenant are either missing or modi
IT admins must respond to the service-generated alerts to ensure that Autopatch services can be delivered, and devices remain eligible for the service. IT admins must respond to the service-generated alerts to ensure that Autopatch services can be delivered, and devices remain eligible for the service.
With this feature, IT admins can: With this feature, IT admins can:
- View alerts, in line with the features you commonly use: - View alerts, in line with the features you commonly use:
- Windows Update related alerts in the Release management blade. - Windows Update related alerts in the Release management blade.
@ -46,7 +46,7 @@ Alerts are raised when deployment rings don't have the required policies and the
The minimum role required to restore configurations is **Intune Service Administrator**. You can also perform these actions in the Global administrator role. The minimum role required to restore configurations is **Intune Service Administrator**. You can also perform these actions in the Global administrator role.
## Restore device configuration policy ## Restore device configuration policy
**To initiate remediation action for device configuration alerts:** **To initiate remediation action for device configuration alerts:**
@ -59,7 +59,7 @@ The minimum role required to restore configurations is **Intune Service Administ
There will be an alert for each policy that is missing or has deviated from the service defined values. There will be an alert for each policy that is missing or has deviated from the service defined values.
## Restore Windows Update policies ## Restore Windows Update policies
**To initiate remediation actions for Windows quality update policies:** **To initiate remediation actions for Windows quality update policies:**
@ -72,14 +72,14 @@ There will be an alert for each policy that is missing or has deviated from the
**To initiate remediation actions for Windows feature update policies:** **To initiate remediation actions for Windows feature update policies:**
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). 1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
1. Navigate to **Devices** > **Windows Autopatch** > **Release management** > **Release schedule** > **Windows feature updates** > **Status**. 1. Navigate to **Devices** > **Windows Autopatch** > **Release management** > **Release schedule** > **Windows feature updates** > **Status**.
1. Select **Policy Error** to launch the Policy error workflow. 1. Select **Policy Error** to launch the Policy error workflow.
1. Review the message. 1. Review the message.
1. If this is a missing policy error, select **Restore policy** to complete the workflow. 1. If this is a missing policy error, select **Restore policy** to complete the workflow.
2. If this is a modified policy, select **Submit changes** to restore to service required values. 2. If this is a modified policy, select **Submit changes** to restore to service required values.
## Restore deployment groups ## Restore deployment groups
Windows Autopatch will automatically restore any missing groups that are required by the service. When a missing deployment group is restored, and the policies are also missing, the policies be restored to the deployment groups. Windows Autopatch will automatically restore any missing groups that are required by the service. When a missing deployment group is restored, and the policies are also missing, the policies be restored to the deployment groups.

2
windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri

8
windows/deployment/windows-autopatch/operate/windows-autopatch-teams.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri
@ -36,12 +36,12 @@ Updates undergo vigorous internal testing and are first released to members of T
## End user experience ## End user experience
Teams will check for updates every few hours behind the scenes, download the updates, and then will wait for the computer to be idle for at least 40 minutes before automatically installing the update. Teams will check for updates every few hours behind the scenes, download the updates, and then will wait for the computer to be idle for at least 40 minutes before automatically installing the update.
When an update is available, the following are required to be able to download the update: When an update is available, the following are required to be able to download the update:
- The user must be signed into both the device and Teams. - The user must be signed into both the device and Teams.
- The device must have an internet connection. - The device must have an internet connection.
- The device must be able to access the required network endpoints to reach the Teams update service. - The device must be able to access the required network endpoints to reach the Teams update service.
> [!NOTE] > [!NOTE]

6
windows/deployment/windows-autopatch/operate/windows-autopatch-unenroll-tenant.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri
@ -22,7 +22,7 @@ If you're looking to unenroll your tenant from Windows Autopatch, this article d
> [!IMPORTANT] > [!IMPORTANT]
> You must be a Global Administrator to unenroll your tenant. > You must be a Global Administrator to unenroll your tenant.
Unenrolling from Windows Autopatch requires manual actions from both you and from the Windows Autopatch Service Engineering Team. The Windows Autopatch Service Engineering Team will: Unenrolling from Windows Autopatch requires manual actions from both you and from the Windows Autopatch Service Engineering Team. The Windows Autopatch Service Engineering Team will:
- Remove Windows Autopatch access to your tenant. - Remove Windows Autopatch access to your tenant.
- Exclude your devices from the Windows Autopatch service. Excluding your devices from Windows Autopatch won't remove your devices from Intune, Microsoft Entra ID or Configuration Manager. The Windows Autopatch Service Engineering Team follows the same process and principles as laid out in [Exclude a device](../operate/windows-autopatch-exclude-device.md). - Exclude your devices from the Windows Autopatch service. Excluding your devices from Windows Autopatch won't remove your devices from Intune, Microsoft Entra ID or Configuration Manager. The Windows Autopatch Service Engineering Team follows the same process and principles as laid out in [Exclude a device](../operate/windows-autopatch-exclude-device.md).
@ -51,7 +51,7 @@ Unenrolling from Windows Autopatch requires manual actions from both you and fro
**To unenroll from Windows Autopatch:** **To unenroll from Windows Autopatch:**
1. [Submit a support request](../operate/windows-autopatch-support-request.md) and request to unenroll from the Windows Autopatch service. 1. [Submit a support request](../operate/windows-autopatch-support-request.md) and request to unenroll from the Windows Autopatch service.
1. The Windows Autopatch Service Engineering Team communicates with your IT Administrator to confirm your intent to unenroll from the service. 1. The Windows Autopatch Service Engineering Team communicates with your IT Administrator to confirm your intent to unenroll from the service.
1. You have 14 days to review and confirm the communication sent by the Windows Autopatch Service Engineering Team. 1. You have 14 days to review and confirm the communication sent by the Windows Autopatch Service Engineering Team.
2. The Windows Autopatch Service Engineering Team can proceed sooner than 14 days if your confirmation arrives sooner. 2. The Windows Autopatch Service Engineering Team can proceed sooner than 14 days if your confirmation arrives sooner.
1. The Windows Autopatch Service Engineering Team proceeds with the removal of all items listed under [Microsoft's responsibilities during unenrollment](#microsofts-responsibilities-during-unenrollment). 1. The Windows Autopatch Service Engineering Team proceeds with the removal of all items listed under [Microsoft's responsibilities during unenrollment](#microsofts-responsibilities-during-unenrollment).

22
windows/deployment/windows-autopatch/overview/windows-autopatch-deployment-guide.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- tier2 - tier2
@ -35,7 +35,7 @@ This guide:
## Determine your objectives ## Determine your objectives
This section details some common objectives when using Windows Autopatch. This section details some common objectives when using Windows Autopatch.
Once an organization is onboarded, Windows Autopatch automatically creates multiple progressive deployment rings and applies the latest updates according to Windows Autopatch recommended practices and your organization's custom configuration. While there are options to adjust configurations such as quality update cadence, the service provides you with a baseline to begin establishing your update objectives. Once an organization is onboarded, Windows Autopatch automatically creates multiple progressive deployment rings and applies the latest updates according to Windows Autopatch recommended practices and your organization's custom configuration. While there are options to adjust configurations such as quality update cadence, the service provides you with a baseline to begin establishing your update objectives.
@ -46,7 +46,7 @@ Use Windows Autopatch to solve the following challenges:
- Achieving a consistent update success rate - Achieving a consistent update success rate
- Standardize and optimize the configuration for devices, policies, tools and versions across their environment - Standardize and optimize the configuration for devices, policies, tools and versions across their environment
- Transition to modern update management by configuring Intune and Windows Update for Business - Transition to modern update management by configuring Intune and Windows Update for Business
- Make update processes more efficient and less reliant on IT admin resources - Make update processes more efficient and less reliant on IT admin resources
- Address vulnerabilities and Windows quality updates as soon as possible to improve security - Address vulnerabilities and Windows quality updates as soon as possible to improve security
- Assist with compliance to align with industry standards - Assist with compliance to align with industry standards
- Invest more time on value-add IT projects rather than monthly updates - Invest more time on value-add IT projects rather than monthly updates
@ -112,7 +112,7 @@ If you're an existing Windows Update for Business (WUfB) or Configuration Manage
Customers who are using Windows Update for Business (WUfB) or Configuration Manager can quickly adopt Windows Autopatch and take advantage of the key benefits that Windows Autopatch provides. Customers who are using Windows Update for Business (WUfB) or Configuration Manager can quickly adopt Windows Autopatch and take advantage of the key benefits that Windows Autopatch provides.
When moving from Windows Update for Business (WUfB) or Configuration Manager to Windows Autopatch, you can enhance and optimize the update experience that you're already familiar with. When moving from Windows Update for Business (WUfB) or Configuration Manager to Windows Autopatch, you can enhance and optimize the update experience that you're already familiar with.
Once migrated, there are several configuration tasks that you no longer need to carry out: Once migrated, there are several configuration tasks that you no longer need to carry out:
@ -180,7 +180,7 @@ When you migrate from Configuration Manager to Windows Autopatch, the fastest pa
| **1** | Turn on co-management | If you're using co-management across Configuration Manager and your managed devices, you meet the key requirements to use Windows Autopatch.<br><br>If you don't have co-management, see [How to use co-management in Configuration Manager](/mem/configmgr/comanage/how-to-enable) | | **1** | Turn on co-management | If you're using co-management across Configuration Manager and your managed devices, you meet the key requirements to use Windows Autopatch.<br><br>If you don't have co-management, see [How to use co-management in Configuration Manager](/mem/configmgr/comanage/how-to-enable) |
| **2** | Use required co-management workloads | Using Windows Autopatch requires that your managed devices use the following three co-management workloads:<ul><li>Windows Update policies workload</li><li>Device configuration workload</li><li>Office Click-to-Run apps workload</li></ul><br>If you have these workloads configured, you meet the key requirements to use Windows Autopatch. If you don't have these workloads configured, review [How to switch Configuration Manager workloads to Intune](/mem/configmgr/comanage/how-to-switch-workloads) | | **2** | Use required co-management workloads | Using Windows Autopatch requires that your managed devices use the following three co-management workloads:<ul><li>Windows Update policies workload</li><li>Device configuration workload</li><li>Office Click-to-Run apps workload</li></ul><br>If you have these workloads configured, you meet the key requirements to use Windows Autopatch. If you don't have these workloads configured, review [How to switch Configuration Manager workloads to Intune](/mem/configmgr/comanage/how-to-switch-workloads) |
| **3** | Prepare your policies | You should consider any existing policy configurations in your Configuration Manager (or on-premises) environment that could impact your deployment of Windows Autopatch. For more information, review [General considerations](#general-considerations) | | **3** | Prepare your policies | You should consider any existing policy configurations in your Configuration Manager (or on-premises) environment that could impact your deployment of Windows Autopatch. For more information, review [General considerations](#general-considerations) |
| **4** | Ensure Configuration Manager collections or Microsoft Entra device groups readiness | To move devices to Windows Autopatch, you must register devices with the Windows Autopatch service. To do so, use either Microsoft Entra device groups, or Configuration Manager collections. Ensure you have either Microsoft Entra device groups or Configuration Manager collections that allow you to evaluate, pilot and then migrate to the Windows Autopatch service. For more information, see [Register your devices](../deploy/windows-autopatch-register-devices.md#before-you-begin). | | **4** | Ensure Configuration Manager collections or Microsoft Entra device groups readiness | To move devices to Windows Autopatch, you must register devices with the Windows Autopatch service. To do so, use either Microsoft Entra device groups, or Configuration Manager collections. Ensure you have either Microsoft Entra device groups or Configuration Manager collections that allow you to evaluate, pilot and then migrate to the Windows Autopatch service. For more information, see [Register your devices](../deploy/windows-autopatch-register-devices.md#before-you-begin). |
### Optimized deployment path: Configuration Manager to Windows Autopatch ### Optimized deployment path: Configuration Manager to Windows Autopatch
@ -196,7 +196,7 @@ Once you have assessed your readiness state to ensure you're aligned to Windows
## General considerations ## General considerations
As part of your planning process, you should consider any existing enterprise configurations in your environment that could affect your deployment of Windows Autopatch. As part of your planning process, you should consider any existing enterprise configurations in your environment that could affect your deployment of Windows Autopatch.
Many organizations have existing policies and device management infrastructure, for example: Many organizations have existing policies and device management infrastructure, for example:
@ -271,7 +271,7 @@ For example, Configuration Manager Software Update Policy settings exclude Autop
#### Servicing profiles for Microsoft 365 Apps for enterprise #### Servicing profiles for Microsoft 365 Apps for enterprise
You can use automation to deliver monthly updates to Microsoft 365 Apps for enterprise directly from the Office Content Delivery Network (CDN) using [Servicing profiles](/windows/deployment/windows-autopatch/operate/windows-autopatch-microsoft-365-apps-enterprise#compatibility-with-servicing-profiles). A servicing profile takes precedence over other policies, such as a Microsoft Intune policy or the Office Deployment Tool. The servicing profile affects all devices that meet the [device eligibility requirements](/windows/deployment/windows-autopatch/operate/windows-autopatch-microsoft-365-apps-enterprise#device-eligibility) regardless of existing management tools in your environment. You can use automation to deliver monthly updates to Microsoft 365 Apps for enterprise directly from the Office Content Delivery Network (CDN) using [Servicing profiles](/windows/deployment/windows-autopatch/operate/windows-autopatch-microsoft-365-apps-enterprise#compatibility-with-servicing-profiles). A servicing profile takes precedence over other policies, such as a Microsoft Intune policy or the Office Deployment Tool. The servicing profile affects all devices that meet the [device eligibility requirements](/windows/deployment/windows-autopatch/operate/windows-autopatch-microsoft-365-apps-enterprise#device-eligibility) regardless of existing management tools in your environment.
You can consider retargeting servicing profiles to non-Windows Autopatch devices or if you plan to continue using them, you can [block Windows Autopatch delivered Microsoft 365 App updates](/windows/deployment/windows-autopatch/operate/windows-autopatch-microsoft-365-apps-enterprise#allow-or-block-microsoft-365-app-updates) for Windows Autopatch-enrolled devices. You can consider retargeting servicing profiles to non-Windows Autopatch devices or if you plan to continue using them, you can [block Windows Autopatch delivered Microsoft 365 App updates](/windows/deployment/windows-autopatch/operate/windows-autopatch-microsoft-365-apps-enterprise#allow-or-block-microsoft-365-app-updates) for Windows Autopatch-enrolled devices.
@ -286,14 +286,14 @@ Part of your planning might require articulating the business benefits of moving
## Stakeholder communications ## Stakeholder communications
Change management relies on clear and helpful communication about upcoming changes. The best way to have a smooth deployment is to make sure end users and stakeholders are aware of all changes and disruptions. Your rollout communication plan should include all pertinent information, how to notify users, and when to communicate. Change management relies on clear and helpful communication about upcoming changes. The best way to have a smooth deployment is to make sure end users and stakeholders are aware of all changes and disruptions. Your rollout communication plan should include all pertinent information, how to notify users, and when to communicate.
- Identify groups impacted by the Autopatch deployment - Identify groups impacted by the Autopatch deployment
- Identify key stakeholders in the impacted groups - Identify key stakeholders in the impacted groups
- Determine the types of communications needed - Determine the types of communications needed
- Develop your messaging based on the [Recommended deployment steps](#recommended-deployment-steps) - Develop your messaging based on the [Recommended deployment steps](#recommended-deployment-steps)
- Create your stakeholder and communication plan schedule based on the [Recommended deployment steps](#recommended-deployment-steps) - Create your stakeholder and communication plan schedule based on the [Recommended deployment steps](#recommended-deployment-steps)
- Have communications drafted and reviewed, and consider your delivery channels such as: - Have communications drafted and reviewed, and consider your delivery channels such as:
- Social media posts - Social media posts
- Internal messaging app (for example, Microsoft Teams) - Internal messaging app (for example, Microsoft Teams)
- Internal team site - Internal team site
@ -319,7 +319,7 @@ If you need assistance with your Windows Autopatch deployment journey, you have
- [Tenant enrollment support request](../prepare/windows-autopatch-enrollment-support-request.md) - [Tenant enrollment support request](../prepare/windows-autopatch-enrollment-support-request.md)
- [General support request](../operate/windows-autopatch-support-request.md) - [General support request](../operate/windows-autopatch-support-request.md)
First contact your Microsoft Account team who can work with you to establish any guidance or support you might need. If you don't have a Microsoft Account Team contact or wish to explore other routes, Microsoft FastTrack offers Microsoft 365 deployment guidance for customers with 150 or more licenses of an eligible subscription at no additional cost. Finally, you can also log a support request with the Windows Autopatch Service Engineering Team. First contact your Microsoft Account team who can work with you to establish any guidance or support you might need. If you don't have a Microsoft Account Team contact or wish to explore other routes, Microsoft FastTrack offers Microsoft 365 deployment guidance for customers with 150 or more licenses of an eligible subscription at no additional cost. Finally, you can also log a support request with the Windows Autopatch Service Engineering Team.
### Windows Autopatch Private Community (APC) ### Windows Autopatch Private Community (APC)
@ -333,6 +333,6 @@ Once you're underway with your deployment, consider joining the [Windows Autopat
- Teams discussions - Teams discussions
- Previews - Previews
### Windows Autopatch Technology Adoption Program (TAP) ### Windows Autopatch Technology Adoption Program (TAP)
If you have at least 500 devices enrolled in the service, and will test and give Microsoft feedback at least once a year, consider signing up to the [Windows Autopatch Technology Adoption Program (TAP)](https://aka.ms/JoinWindowsAutopatchTAP) to try out new and upcoming Windows Autopatch features. If you have at least 500 devices enrolled in the service, and will test and give Microsoft feedback at least once a year, consider signing up to the [Windows Autopatch Technology Adoption Program (TAP)](https://aka.ms/JoinWindowsAutopatchTAP) to try out new and upcoming Windows Autopatch features.

14
windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
View File

@ -7,7 +7,7 @@ metadata:
ms.date: 12/04/2023 ms.date: 12/04/2023
audience: itpro audience: itpro
ms.localizationpriority: medium ms.localizationpriority: medium
manager: dougeby manager: aaroncz
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
ms.reviwer: hathind ms.reviwer: hathind
@ -28,9 +28,9 @@ sections:
Windows Autopatch supports Windows 365 for Enterprise. Windows 365 for Business isn't supported. Windows Autopatch supports Windows 365 for Enterprise. Windows 365 for Business isn't supported.
- question: Does Windows Autopatch support Windows Education (A3/A5) or Windows Front Line Worker (F3) licensing? - question: Does Windows Autopatch support Windows Education (A3/A5) or Windows Front Line Worker (F3) licensing?
answer: | answer: |
Autopatch isn't available for 'A'. Windows Autopatch supports some 'F' series licensing. For more information, see [More about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses). Autopatch isn't available for 'A'. Windows Autopatch supports some 'F' series licensing. For more information, see [More about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses).
- question: Will Windows Autopatch support local domain join Windows 10? - question: Will Windows Autopatch support local domain join Windows 10?
answer: | answer: |
Windows Autopatch doesn't support local (on-premises) domain join. Windows Autopatch supports [Hybrid AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or pure [Microsoft Entra join](/azure/active-directory/devices/concept-azure-ad-join-hybrid). Windows Autopatch doesn't support local (on-premises) domain join. Windows Autopatch supports [Hybrid AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or pure [Microsoft Entra join](/azure/active-directory/devices/concept-azure-ad-join-hybrid).
- question: Will Windows Autopatch be available for state and local government customers? - question: Will Windows Autopatch be available for state and local government customers?
answer: | answer: |
@ -46,8 +46,8 @@ sections:
- [Azure Active Directory (Azure AD) Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses) - [Azure Active Directory (Azure AD) Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses)
- [Hybrid Azure AD-Joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or [Azure AD-joined only](/azure/active-directory/devices/concept-azure-ad-join-hybrid) - [Hybrid Azure AD-Joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or [Azure AD-joined only](/azure/active-directory/devices/concept-azure-ad-join-hybrid)
- [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune) - [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune)
Additional prerequisites for devices managed by Configuration Manager: Additional prerequisites for devices managed by Configuration Manager:
- [Configuration Manager Co-management requirements](../prepare/windows-autopatch-prerequisites.md#configuration-manager-co-management-requirements) - [Configuration Manager Co-management requirements](../prepare/windows-autopatch-prerequisites.md#configuration-manager-co-management-requirements)
- [A supported version of Configuration Manager](/mem/configmgr/core/servers/manage/updates#supported-versions) - [A supported version of Configuration Manager](/mem/configmgr/core/servers/manage/updates#supported-versions)
@ -77,11 +77,11 @@ sections:
- question: Can you change the policies and configurations created by Windows Autopatch? - question: Can you change the policies and configurations created by Windows Autopatch?
answer: | answer: |
No. Don't change, edit, add to, or remove any of the configurations. Doing so might cause unintended configuration conflicts and impact the Windows Autopatch service. For more information about policies and configurations, see [Changes made at tenant enrollment](/windows/deployment/windows-autopatch/references/windows-autopatch-changes-to-tenant). No. Don't change, edit, add to, or remove any of the configurations. Doing so might cause unintended configuration conflicts and impact the Windows Autopatch service. For more information about policies and configurations, see [Changes made at tenant enrollment](/windows/deployment/windows-autopatch/references/windows-autopatch-changes-to-tenant).
- question: How can I represent our organizational structure with our own deployment cadence? - question: How can I represent our organizational structure with our own deployment cadence?
answer: | answer: |
[Windows Autopatch groups](../deploy/windows-autopatch-groups-overview.md) helps you manage updates in a way that makes sense for your businesses. For more information, see [Windows Autopatch groups overview](../deploy/windows-autopatch-groups-overview.md) and [Manage Windows Autopatch groups](../deploy/windows-autopatch-groups-manage-autopatch-groups.md). [Windows Autopatch groups](../deploy/windows-autopatch-groups-overview.md) helps you manage updates in a way that makes sense for your businesses. For more information, see [Windows Autopatch groups overview](../deploy/windows-autopatch-groups-overview.md) and [Manage Windows Autopatch groups](../deploy/windows-autopatch-groups-manage-autopatch-groups.md).
- name: Update management - name: Update management
questions: questions:
- question: What systems does Windows Autopatch update? - question: What systems does Windows Autopatch update?
answer: | answer: |
- Windows 10/11 quality updates: Windows Autopatch manages all aspects of deployment rings. - Windows 10/11 quality updates: Windows Autopatch manages all aspects of deployment rings.

6
windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.collection: ms.collection:
- highpri - highpri
- tier1 - tier1
@ -27,8 +27,8 @@ Rather than maintaining complex digital infrastructure, businesses want to focus
- **Close the security gap**: Windows Autopatch keeps software current, there are fewer vulnerabilities and threats to your devices. - **Close the security gap**: Windows Autopatch keeps software current, there are fewer vulnerabilities and threats to your devices.
- **Close the productivity gap**: Windows Autopatch adopts features as they're made available. End users get the latest tools to amplify their collaboration and work. - **Close the productivity gap**: Windows Autopatch adopts features as they're made available. End users get the latest tools to amplify their collaboration and work.
- **Optimize your IT admin resources**: Windows Autopatch automates routine endpoint updates. IT pros have more time to create value. - **Optimize your IT admin resources**: Windows Autopatch automates routine endpoint updates. IT pros have more time to create value.
- **On-premises infrastructure**: Transitioning to the world of software as a service (SaaS) allows you to minimize your investment in on-premises hardware since updates are delivered from the cloud. - **On-premises infrastructure**: Transitioning to the world of software as a service (SaaS) allows you to minimize your investment in on-premises hardware since updates are delivered from the cloud.
- **Onboard new services**: Windows Autopatch makes it easy to enroll and minimizes the time required from your IT Admins to get started. - **Onboard new services**: Windows Autopatch makes it easy to enroll and minimizes the time required from your IT Admins to get started.
- **Minimize end user disruption**: Windows Autopatch releases updates in sequential deployment rings, and responding to reliability and compatibility signals, user disruptions due to updates are minimized. - **Minimize end user disruption**: Windows Autopatch releases updates in sequential deployment rings, and responding to reliability and compatibility signals, user disruptions due to updates are minimized.
Windows Autopatch helps you minimize the involvement of your scarce IT resources in the planning and deployment of updates for Windows, Microsoft 365 Apps, Microsoft Edge or Teams. Windows Autopatch uses careful rollout sequences and communicates with you throughout the release, allowing your IT Admins can focus on other activities and tasks. Windows Autopatch helps you minimize the involvement of your scarce IT resources in the planning and deployment of updates for Windows, Microsoft 365 Apps, Microsoft Edge or Teams. Windows Autopatch uses careful rollout sequences and communicates with you throughout the release, allowing your IT Admins can focus on other activities and tasks.

2
windows/deployment/windows-autopatch/overview/windows-autopatch-privacy.md
View File

@ -8,7 +8,7 @@ ms.topic: reference
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri

2
windows/deployment/windows-autopatch/overview/windows-autopatch-roles-responsibilities.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri

2
windows/deployment/windows-autopatch/prepare/windows-autopatch-configure-network.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- tier2 - tier2

8
windows/deployment/windows-autopatch/prepare/windows-autopatch-enroll-tenant.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri
@ -22,7 +22,7 @@ Before you enroll in Windows Autopatch, there are settings, and other parameters
> [!IMPORTANT] > [!IMPORTANT]
> You must be a Global Administrator to enroll your tenant. > You must be a Global Administrator to enroll your tenant.
The Readiness assessment tool, accessed in the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), checks management or configuration-related settings. This tool allows you to check the relevant settings, and details steps to fix any settings that aren't configured properly for Windows Autopatch. The Readiness assessment tool, accessed in the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), checks management or configuration-related settings. This tool allows you to check the relevant settings, and details steps to fix any settings that aren't configured properly for Windows Autopatch.
## Step 1: Review all prerequisites ## Step 1: Review all prerequisites
@ -69,7 +69,7 @@ The following are the Microsoft Entra settings:
### Check results ### Check results
For each check, the tool reports one of four possible results: For each check, the tool reports one of four possible results:
| Result | Meaning | | Result | Meaning |
| ----- | ----- | | ----- | ----- |
@ -80,7 +80,7 @@ For each check, the tool reports one of four possible results:
## Step 3: Fix issues with your tenant ## Step 3: Fix issues with your tenant
If the Readiness assessment tool is displaying issues with your tenant, see [Fix issues found by the Readiness assessment tool](../prepare/windows-autopatch-fix-issues.md) for more information on how to remediate. If the Readiness assessment tool is displaying issues with your tenant, see [Fix issues found by the Readiness assessment tool](../prepare/windows-autopatch-fix-issues.md) for more information on how to remediate.
## Step 4: Enroll your tenant ## Step 4: Enroll your tenant

2
windows/deployment/windows-autopatch/prepare/windows-autopatch-enrollment-support-request.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- tier2 - tier2

2
windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
View File

@ -8,7 +8,7 @@ ms.topic: how-to
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri

2
windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri

2
windows/deployment/windows-autopatch/references/windows-autopatch-changes-to-tenant.md
View File

@ -8,7 +8,7 @@ ms.topic: reference
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri

30
windows/deployment/windows-autopatch/references/windows-autopatch-conflicting-configurations.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: adnich ms.reviewer: adnich
ms.collection: ms.collection:
- highpri - highpri
@ -20,16 +20,16 @@ ms.collection:
> [!IMPORTANT] > [!IMPORTANT]
> This feature is in **public preview**. The feature is being actively developed and might not be complete. > This feature is in **public preview**. The feature is being actively developed and might not be complete.
During Readiness checks, if there are devices with conflicting registry configurations, notifications are listed in the **Not ready** tab. The notifications include a list of alerts that explain why the device isn't ready for updates. Instructions are provided on how to resolve the issue(s). You can review any device marked as **Not ready** and remediate them to a **Ready** state. During Readiness checks, if there are devices with conflicting registry configurations, notifications are listed in the **Not ready** tab. The notifications include a list of alerts that explain why the device isn't ready for updates. Instructions are provided on how to resolve the issue(s). You can review any device marked as **Not ready** and remediate them to a **Ready** state.
Windows Autopatch monitors conflicting configurations. You’re notified of the specific registry values that prevent Windows from updating properly. These registry keys should be removed to resolve the conflict. However, it’s possible that other services write back the registry keys. It’s recommended that you review common sources for conflicting configurations to ensure your devices continue to receive Windows Updates. Windows Autopatch monitors conflicting configurations. You’re notified of the specific registry values that prevent Windows from updating properly. These registry keys should be removed to resolve the conflict. However, it’s possible that other services write back the registry keys. It’s recommended that you review common sources for conflicting configurations to ensure your devices continue to receive Windows Updates.
The most common sources of conflicting configurations include: The most common sources of conflicting configurations include:
- Active Directory Group Policy (GPO) - Active Directory Group Policy (GPO)
- Configuration Manager Device client settings - Configuration Manager Device client settings
- Windows Update for Business (WUfB) policies - Windows Update for Business (WUfB) policies
- Manual registry updates - Manual registry updates
- Local Group Policy settings applied during imaging (LGPO) - Local Group Policy settings applied during imaging (LGPO)
## Registry keys inspected by Autopatch ## Registry keys inspected by Autopatch
@ -51,18 +51,18 @@ Windows Autopatch recommends removing the conflicting configurations. The follow
### Intune Remediation ### Intune Remediation
Navigate to Intune Remediations and create a remediation using the following examples. It’s recommended to create a single remediation per value to understand if the value persists after removal. Navigate to Intune Remediations and create a remediation using the following examples. It’s recommended to create a single remediation per value to understand if the value persists after removal.
If you use either [**Detect**](#detect) and/or [**Remediate**](#remediate) actions, ensure to update the appropriate **Path** and **Value** called out in the Alert. For more information, see [Remediations](/mem/intune/fundamentals/remediations). If you use either [**Detect**](#detect) and/or [**Remediate**](#remediate) actions, ensure to update the appropriate **Path** and **Value** called out in the Alert. For more information, see [Remediations](/mem/intune/fundamentals/remediations).
#### Detect #### Detect
```powershell ```powershell
if((Get-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate).PSObject.Properties.Name -contains 'DoNotConnectToWindowsUpdateInternetLocations') { if((Get-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate).PSObject.Properties.Name -contains 'DoNotConnectToWindowsUpdateInternetLocations') {
Exit 1 Exit 1
} else { } else {
exit 0 exit 0
} }
``` ```
| Alert details | Description | | Alert details | Description |
@ -73,9 +73,9 @@ if((Get-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate).PS
#### Remediate #### Remediate
```powershell ```powershell
if((Get-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate).PSObject.Properties.Name -contains 'DoNotConnectToWindowsUpdateInternetLocations') { if((Get-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate).PSObject.Properties.Name -contains 'DoNotConnectToWindowsUpdateInternetLocations') {
Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "DoNotConnectToWindowsUpdateInternetLocations" Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "DoNotConnectToWindowsUpdateInternetLocations"
} }
``` ```
| Alert details | Description | | Alert details | Description |
@ -121,7 +121,7 @@ Windows Registry Editor Version 5.00
"DoNotConnectToWindowsUpdateInternetLocations"=- "DoNotConnectToWindowsUpdateInternetLocations"=-
"DisableWindowsUpdateAccess"=- "DisableWindowsUpdateAccess"=-
"WUServer"=- "WUServer"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU] [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"UseWUServer"=- "UseWUServer"=-
"NoAutoUpdate"=- "NoAutoUpdate"=-
``` ```
@ -145,7 +145,7 @@ Group Policy management is the most popular client configuration tool in most or
Configuration Manager is a common enterprise management tool that, among many things, can help manage Windows Updates. For this reason, we see many environments misconfigured when moving to either a 100% cloud or co-managed workloads even when the workloads are configured correctly. The client settings are often missed. For more information, see [About client settings and software updates](/mem/configmgr/core/clients/deploy/about-client-settings#software-updates). Configuration Manager is a common enterprise management tool that, among many things, can help manage Windows Updates. For this reason, we see many environments misconfigured when moving to either a 100% cloud or co-managed workloads even when the workloads are configured correctly. The client settings are often missed. For more information, see [About client settings and software updates](/mem/configmgr/core/clients/deploy/about-client-settings#software-updates).
1. Go the **Microsoft Endpoint Configuration Manager Console**. 1. Go the **Microsoft Endpoint Configuration Manager Console**.
1. Navigate to **Administration** > **Overview** > **Client Settings**. 1. Navigate to **Administration** > **Overview** > **Client Settings**.
1. Ensure **Software Updates** isn’t configured. If configured, it’s recommended to remove these settings to prevent conflicts with Windows Autopatch. 1. Ensure **Software Updates** isn’t configured. If configured, it’s recommended to remove these settings to prevent conflicts with Windows Autopatch.
## Third-party solutions ## Third-party solutions

4
windows/deployment/windows-autopatch/references/windows-autopatch-driver-and-firmware-updates-public-preview-addendum.md
View File

@ -1,14 +1,14 @@
--- ---
title: Driver and firmware updates for Windows Autopatch Public Preview Addendum title: Driver and firmware updates for Windows Autopatch Public Preview Addendum
description: This article explains how driver and firmware updates are managed in Autopatch description: This article explains how driver and firmware updates are managed in Autopatch
ms.date: 06/26/2023 ms.date: 06/26/2023
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: conceptual ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
msreviewer: hathind msreviewer: hathind
--- ---

2
windows/deployment/windows-autopatch/references/windows-autopatch-microsoft-365-policies.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- tier2 - tier2

4
windows/deployment/windows-autopatch/references/windows-autopatch-windows-update-unsupported-policies.md
View File

@ -8,7 +8,7 @@ ms.topic: conceptual
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: adnich ms.reviewer: adnich
ms.collection: ms.collection:
- tier2 - tier2
@ -57,7 +57,7 @@ The following policies contain settings that apply to both Windows quality and f
## Windows feature update policies ## Windows feature update policies
The service deploys policies using Microsoft Intune to control how Windows feature updates are deployed to devices. The service deploys policies using Microsoft Intune to control how Windows feature updates are deployed to devices.
### Windows feature updates for Windows 10 and later ### Windows feature updates for Windows 10 and later

2
windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md
View File

@ -8,7 +8,7 @@ ms.topic: whats-new
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
--- ---

6
windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
View File

@ -1,14 +1,14 @@
--- ---
title: What's new 2023 title: What's new 2023
description: This article lists the 2023 feature releases and any corresponding Message center post numbers. description: This article lists the 2023 feature releases and any corresponding Message center post numbers.
ms.date: 12/14/2023 ms.date: 12/14/2023
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: whats-new ms.topic: whats-new
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri

4
windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md
View File

@ -6,9 +6,9 @@ ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: whats-new ms.topic: whats-new
ms.localizationpriority: medium ms.localizationpriority: medium
author: tiaraquan author: tiaraquan
ms.author: tiaraquan ms.author: tiaraquan
manager: dougeby manager: aaroncz
ms.reviewer: hathind ms.reviewer: hathind
ms.collection: ms.collection:
- highpri - highpri