mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-16 07:17:24 +00:00
Merge branch 'main' into vp-csp-2304
This commit is contained in:
Angela Fleischmann
GitHub
commit
be9cd1d319
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: How to check Windows release health
|
||||
description: Check the release health status of Microsoft 365 services before you call support to see if there's an active service interruption.
|
||||
ms.date: 08/16/2022
|
||||
ms.date: 05/03/2023
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
@ -13,7 +13,7 @@ ms.technology: itpro-updates
|
||||
|
||||
# How to check Windows release health
|
||||
|
||||
The Windows release health page in the Microsoft 365 admin center enables you to view the latest information on known issues for Windows monthly and feature updates. A known issue is an issue that has been identified in a Windows monthly update or feature update that impacts Windows devices. The Windows release health page is designed to inform you about known issues. You can use this information to troubleshoot issues your users may be experiencing. You can also determine when, and at what scale, to deploy an update in your organization.
|
||||
The Windows release health page in the Microsoft 365 admin center enables you to view the latest information on known issues for Windows monthly and feature updates. A known issue is an issue that impacts Windows devices and that has been identified in a Windows monthly update or feature update. The Windows release health page is designed to inform you about known issues. You can use this information to troubleshoot issues your users may be experiencing. You can also determine when, and at what scale, to deploy an update in your organization.
|
||||
|
||||
If you're unable to sign in to the Microsoft 365 admin portal, check the [Microsoft 365 service health](https://status.office365.com) status page to check for known issues preventing you from signing into your tenant.
|
||||
|
||||
@ -21,7 +21,7 @@ To be informed about the latest updates and releases, follow [@WindowsUpdate](ht
|
||||
|
||||
## How to review Windows release health information
|
||||
|
||||
1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com), and sign in with an administrator account.
|
||||
1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com) and sign in with an administrator account.
|
||||
|
||||
> [!NOTE]
|
||||
> By default, the Windows release health page is available to individuals who have been assigned the global admin or service administrator role for their tenant. To allow Exchange, SharePoint, and Skype for Business admins to view the Windows release health page, you must first assign them to a Service admin role. For more information about roles that can view service health, see [About admin roles](/microsoft-365/admin/add-users/about-admin-roles#commonly-used-microsoft-365-admin-center-roles).
|
||||
@ -54,6 +54,21 @@ To be informed about the latest updates and releases, follow [@WindowsUpdate](ht
|
||||
|
||||
|
||||
|
||||
## Sign up for email notifications
|
||||
|
||||
You have the option to sign up for email notifications about Windows known issues and informational updates. Notifications include changes in issue status, new workarounds, and issue resolutions. To subscribe to notifications:
|
||||
|
||||
1. Go to the [Windows release health page](https://admin.microsoft.com/Adminportal/Home?#/windowsreleasehealth).
|
||||
1. Select **Preferences** > **Email**, then select **Send me email notifications about Windows release health**.
|
||||
1. Specify the following information:
|
||||
- Email address for the notifications
|
||||
- Each admin account can specify up to two email addresses under their email preferences
|
||||
- Windows versions to be notified about
|
||||
1. Select **Save** when you're finished specifying email addresses and Windows versions. It may take up to 8 hours for these changes to take effect.
|
||||
|
||||
> [!Note]
|
||||
> When a single known issue affects multiple versions of Windows, you'll receive only one email notification, even if you've selected notifications for multiple versions. Duplicate emails won't be sent.
|
||||
|
||||
## Status definitions
|
||||
|
||||
In the **Windows release health** experience, every known issue is assigned as status. Those statuses are defined as follows:
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Device registration overview
|
||||
description: This article provides an overview on how to register devices in Autopatch
|
||||
ms.date: 05/01/2023
|
||||
ms.date: 05/02/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Manage Windows Autopatch groups
|
||||
description: This article explains how to manage Autopatch groups
|
||||
ms.date: 05/01/2023
|
||||
ms.date: 05/03/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -26,6 +26,16 @@ Autopatch groups is a logical container or unit that groups several [Azure AD gr
|
||||
Before you start managing Autopatch groups, ensure you’ve met the following prerequisites:
|
||||
|
||||
- Review [Windows Autopatch groups overview documentation](../deploy/windows-autopatch-groups-overview.md) to understand [key benefits](../deploy/windows-autopatch-groups-overview.md#key-benefits), [concepts](../deploy/windows-autopatch-groups-overview.md#key-concepts) and [common ways to use Autopatch groups](../deploy/windows-autopatch-groups-overview.md#common-ways-to-use-autopatch-groups) within your organization.
|
||||
- Ensure the following [update rings for Windows 10 and later policy in Intune](/mem/intune/protect/windows-10-update-rings) are created in your tenant:
|
||||
- Modern Workplace Update Policy [Test]-[Windows Autopatch]
|
||||
- Modern Workplace Update Policy [First]-[Windows Autopatch]
|
||||
- Modern Workplace Update Policy [Fast]-[Windows Autopatch]
|
||||
- Modern Workplace Update Policy [Broad]-[Windows Autopatch]
|
||||
- Ensure the following [feature updates for Windows 10 and later policy in Intune](/mem/intune/protect/windows-10-feature-updates) are created in your tenant:
|
||||
- Windows Autopatch – DSS Policy [Test]
|
||||
- Windows Autopatch – DSS Policy [First]
|
||||
- Windows Autopatch – DSS Policy [Fast]
|
||||
- Windows Autopatch – DSS Policy [Broad]
|
||||
- Ensure the following Azure AD assigned groups are in your tenant before using Autopatch groups. **Don’t** modify the Azure AD group membership types (Assigned or Dynamic). Otherwise, the Windows Autopatch service won’t be able to read the device group membership from these groups and causes the Autopatch groups feature and other service-related operations to not work properly.
|
||||
- Modern Workplace Devices-Windows Autopatch-Test
|
||||
- Modern Workplace Devices-Windows Autopatch-First
|
||||
@ -45,6 +55,9 @@ Before you start managing Autopatch groups, ensure you’ve met the following pr
|
||||
- Review your existing Azure AD group dynamic queries and direct device memberships to avoid having device membership overlaps in between device-based Azure AD groups that are going to be used with Autopatch groups. This can help prevent device conflicts within an Autopatch group or across several Autopatch groups. **Autopatch groups doesn't support user-based Azure AD groups**.
|
||||
- Ensure devices used with your existing Azure AD groups meet [device registration prerequisite checks](../deploy/windows-autopatch-register-devices.md#prerequisites-for-device-registration) when being registered with the service. Autopatch groups register devices on your behalf, and devices can be moved to **Registered** or **Not registered** tabs in the Devices blade accordingly.
|
||||
|
||||
> [!TIP]
|
||||
> [Update rings](/mem/intune/protect/windows-10-update-rings) and [feature updates](/mem/intune/protect/windows-10-feature-updates) for Windows 10 and later policies that are created and managed by Windows Autopatch can be restored using the [Policy health](../operate/windows-autopatch-policy-health-and-remediation.md) feature. For more information on remediation actions, see [restore Windows update policies](../operate/windows-autopatch-policy-health-and-remediation.md#restore-windows-update-policies).
|
||||
|
||||
> [!NOTE]
|
||||
> During the public preview, Autopatch groups opt-in page will show a banner to let you know when one or more prerequisites are failing. Once you remediate the issue to meet the prerequisites, it can take up to an hour for your tenant to have the "Use preview" button available.
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Autopatch groups overview
|
||||
description: This article explains what Autopatch groups are
|
||||
ms.date: 05/01/2023
|
||||
ms.date: 05/03/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -247,4 +247,7 @@ Autopatch groups works with the following software update workloads:
|
||||
|
||||
Windows Autopatch will support up to 50 Autopatch groups in your tenant. You can create up to 49 [Custom Autopatch groups](#about-custom-autopatch-groups) in addition to the [Default Autopatch group](#about-the-default-autopatch-group). Each Autopatch group supports up to 15 deployment rings.
|
||||
|
||||
> [!TIP]
|
||||
> If you reach the maximum number of Autopatch groups supported (50), and try to create more Custom Autopatch groups, the "**Create**" option in the Autopatch groups blade will be greyed out.
|
||||
|
||||
To manage your Autopatch groups, see [Manage Windows Autopatch groups](../deploy/windows-autopatch-groups-manage-autopatch-groups.md).
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows feature updates overview with Autopatch groups
|
||||
description: This article explains how Windows feature updates are managed with Autopatch groups
|
||||
ms.date: 05/01/2023
|
||||
ms.date: 05/03/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -39,6 +39,15 @@ Windows Autopatch’s device eligibility criteria for Windows feature updates al
|
||||
|
||||
## Key benefits
|
||||
|
||||
- Windows Autopatch makes it easier and less expensive for you to keep your Windows devices up to date. You can focus on running your core businesses while Windows Autopatch runs update management on your behalf.
|
||||
- You’re in control of telling Windows Autopatch when your organization is ready to move to the next Windows OS version.
|
||||
- Combined with custom releases, Autopatch Groups gives your organization great control and flexibility to help you plan your gradual rollout in a way that works for your organization.
|
||||
- Simplified end-user experience with rich controls for gradual rollouts, deployment cadence and speed.
|
||||
- No need to manually modify the default Windows feature update policies (default release) to be on the Windows OS version your organization is currently ready for.
|
||||
- Allows for scenarios where you can deploy a single release across several Autopatch groups and its deployment rings.
|
||||
|
||||
## Key concepts
|
||||
|
||||
- A release is made of one or more deployment phases and contains the required OS version to be gradually rolled out throughout its deployment phases.
|
||||
- A phase (deployment phase) is made of one or more Autopatch group deployment rings. A phase:
|
||||
- Works as an additional layer of deployment cadence settings that can be defined by IT admins (only for Windows feature updates) on top of Autopatch group deployment rings (Windows update rings policies).
|
||||
@ -71,12 +80,12 @@ If the device is registered with Windows Autopatch, and the device is:
|
||||
|
||||
If your tenant is enrolled with Windows Autopatch, you can see the following default policies created by the service in the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431):
|
||||
|
||||
| Policy name | Feature update version | Rollout options | First deployment ring availability | Final deployment ring availability | Day between deployment rings | Support end date |
|
||||
| ----- | ----- | ----- | ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch – DSS Policy [Test] | Windows 10 21H2 | Make update available as soon as possible | May 9, 2023 | N/A | N/A | June 10, 2024 |
|
||||
| Windows Autopatch – DSS Policy [Ring1] | Windows 10 21H2 | Make update available as soon as possible | May 16, 2023 | N/A | N/A | June 10, 2024 |
|
||||
| Windows Autopatch – DSS Policy [Ring2] | Windows 10 21H2 | Make update available as soon as possible | May 23, 2023 | N/A | N/A | June 10, 2024 |
|
||||
| Windows Autopatch – DSS Policy [Ring3] | Windows 10 21H2 | Make update available as soon as possible | May 30, 2023 | N/A | N/A | June 10, 2024 |
|
||||
| Policy name | Phase mapping | Feature update version | Rollout options | First deployment ring availability | Final deployment ring availability | Day between deployment rings | Support end date |
|
||||
| ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch – DSS Policy [Test] | Phase 1 | Windows 10 21H2 | Make update available as soon as possible | May 9, 2023 | N/A | N/A | June 10, 2024 |
|
||||
| Windows Autopatch – DSS Policy [First] | Phase 2 | Windows 10 21H2 | Make update available as soon as possible | May 16, 2023 | N/A | N/A | June 10, 2024 |
|
||||
| Windows Autopatch – DSS Policy [Fast] | Phase 3 | Windows 10 21H2 | Make update available as soon as possible | May 23, 2023 | N/A | N/A | June 10, 2024 |
|
||||
| Windows Autopatch – DSS Policy [Broad] | Phase 4 | Windows 10 21H2 | Make update available as soon as possible | May 30, 2023 | N/A | N/A | June 10, 2024 |
|
||||
|
||||
> [!NOTE]
|
||||
> Gradual rollout settings aren't configured in the default Windows Update feature policy. If the date of the final group availability is changed to a past date, all remaining devices are offered the update as soon as possible. For more information, see [rollout options for Windows Updates in Microsoft Intune](/mem/intune/protect/windows-update-rollout-options#make-updates-available-gradually).
|
||||
|
||||
@ -50,7 +50,7 @@ The minimum role required to restore configurations is **Intune Service Administ
|
||||
**To initiate remediation action for device configuration alerts:**
|
||||
|
||||
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
1. Navigate to **Tenant administration** > **Tenant management** > **Alerts**.
|
||||
1. Navigate to **Tenant administration** > **Tenant management** > **Actions**.
|
||||
1. Select **Restore missing policy** to launch the workflow.
|
||||
1. Review the message and select **Restore policy**.
|
||||
1. If the **Change modified policy alert** appears, select this alert to launch the workflow.
|
||||
@ -83,7 +83,7 @@ There will be an alert for each policy that is missing or has deviated from the
|
||||
**To initiate remediation action for missing groups:**
|
||||
|
||||
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
1. Navigate to **Tenant administration** > **Tenant management** > **Alerts**.
|
||||
1. Navigate to **Tenant administration** > **Tenant management** > **Actions**.
|
||||
1. Select **Restore missing group** to launch the workflow.
|
||||
1. Review the message and select **Restore group**.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user