mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
Merge branch 'main' into alexbuckgit/docutune-autopr-docs-link-absolute-20220924-042359-2181884
This commit is contained in:
Emily Prindeville
GitHub
@ -1,11 +1,14 @@
|
||||
---
|
||||
title: "How to check Windows release health"
|
||||
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.author: v-nishmi
|
||||
author: DocsPreview
|
||||
manager: jren
|
||||
ms.topic: article
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: how-to
|
||||
ms.prod: w10
|
||||
localization_priority: Normal
|
||||
localization_priority: medium
|
||||
ms.custom:
|
||||
- Adm_O365
|
||||
- 'O365P_ServiceHealthModern'
|
||||
@ -21,36 +24,35 @@ search.appverid:
|
||||
- MOE150
|
||||
- BCS160
|
||||
- IWA160
|
||||
description: "Check the release health status of Microsoft 365 services before you call support to see if there is an active service interruption."
|
||||
---
|
||||
|
||||
# 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 so you can troubleshoot issues your users may be experiencing and/or to 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 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.
|
||||
|
||||
If you are 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 logging into your tenant.
|
||||
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.
|
||||
|
||||
To be informed about the latest updates and releases, follow us on Twitter [@WindowsUpdate](https://twitter.com/windowsupdate).
|
||||
To be informed about the latest updates and releases, follow [@WindowsUpdate](https://twitter.com/windowsupdate) on Twitter.
|
||||
|
||||
## How to review Windows release health information
|
||||
|
||||
1. Go to the Microsoft 365 admin center at [https://admin.microsoft.com](https://go.microsoft.com/fwlink/p/?linkid=2024339), 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?view=o365-worldwide&preserve-view=true#roles-available-in-the-microsoft-365-admin-center).
|
||||
> 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).
|
||||
|
||||
2. To view Windows release health in the Microsoft 365 Admin Center, go to **Health > Windows release health**.
|
||||
|
||||
3. On the **Windows release health** page, you will have access to known issue information for all supported versions of the Windows operating system.
|
||||
3. On the **Windows release health** page, you'll have access to known issue information for all supported versions of the Windows operating system.
|
||||
|
||||
The **All versions** tab (the default view) shows all Windows products with access to their posted known issues.
|
||||
|
||||
|
||||
|
||||
A known issue is an issue that has been identified in a Windows monthly update or feature update that impacts Windows devices. The **Active and recently resolved** column provides a link to the **Known issues** tab filtered to the version selected. Selecting the **Known issues** tab will show known issues that are active or resolved within the last 30 days.
|
||||
|
||||
A known issue is an issue that has been identified in a Windows monthly update or feature update that impacts Windows devices. The **Active and recently resolved** column provides a link to the **Known issues** tab filtered to the version selected. Selecting the **Known issues** tab will show known issues that are active or resolved within the last 30 days.
|
||||
|
||||
|
||||
|
||||
|
||||
The **History** tab shows the history of known issues that have been resolved for up to 6 months.
|
||||
|
||||
|
||||
@ -63,24 +65,23 @@ To be informed about the latest updates and releases, follow us on Twitter [@Win
|
||||
- **Originating KB** - The KB number where the issue was first identified.
|
||||
- **Originating build** - The build number for the KB.
|
||||
|
||||
Select the **Issue title** to access more information, including a link to the history of all status updates posted while we work on a solution. Here is an example:
|
||||
Select the **Issue title** to access more information, including a link to the history of all status updates posted while we work on a solution. For example:
|
||||
|
||||
|
||||
|
||||
|
||||
## Status definitions
|
||||
|
||||
In the **Windows release health** experience, every known issue is assigned as status. Those statuses are defined as follows:
|
||||
|
||||
|
||||
| Status | Definition |
|
||||
|:-----|:-----|
|
||||
|**Reported** | An issue has been brought to the attention of the Windows teams. At this stage, there is no confirmation that users are affected. |
|
||||
|**Investigating** | The issue is believed to affect users and efforts are underway to gather more information about the issue’s scope of impact, mitigation steps, and root cause. |
|
||||
|**Confirmed** | After close review, Microsoft teams have determined the issue is affecting Windows users, and progress is being made on mitigation steps and root cause. |
|
||||
|**Reported** | An issue has been brought to the attention of the Windows teams. At this stage, there's no confirmation that users are affected. |
|
||||
|**Investigating** | The issue is believed to affect users and efforts are underway to gather more information about the issue's scope, mitigation steps, and root cause. |
|
||||
|**Confirmed** | After close review, Microsoft has determined the issue is affecting Windows users, and progress is being made on mitigation steps and root cause. |
|
||||
|**Mitigated** | A workaround is available and communicated to Windows customers for a known issue. A known issue will stay in this state until a KB article is released by Microsoft to resolve the known issue. |
|
||||
|**Mitigated: External** | A workaround is available and communicated to Windows customers for a known issue that was caused by a software or driver from a third-party software or device manufacturer. A known issue will stay in this state until the issue is resolved by Microsoft or the third-party. |
|
||||
|**Resolved** | A solution has been released by Microsoft and has been documented in a KB article that will resolve the known issue once it’s deployed in the customer’s environment. |
|
||||
|**Resolved: External** | A solution has been released by a Microsoft or a third-party that will resolve the known issue once it’s deployed in the customer’s environment. |
|
||||
|**Resolved** | A solution has been released by Microsoft and has been documented in a KB article that will resolve the known issue once it's deployed in the customer's environment. |
|
||||
|**Resolved: External** | A solution has been released by a Microsoft or a third-party that will resolve the known issue once it's deployed in the customer's environment. |
|
||||
|
||||
## Known issue history
|
||||
|
||||
@ -96,14 +97,15 @@ A list of all status updates posted in the selected timeframe will be displayed,
|
||||
|
||||
### Windows release health coverage
|
||||
|
||||
- **What is Windows release health?**
|
||||
- **What is Windows release health?**
|
||||
Windows release health is a Microsoft informational service created to keep licensed Windows customers aware of identified known issues and important announcements.
|
||||
|
||||
- **Microsoft 365 service health content is specific to my tenants and services. Is the content in Windows release health specific to my Windows environment?**
|
||||
Windows release health does not monitor user environments or collect customer environment information. In Windows release health, all known issue content across all supported Windows versions is published to all subscribed customers. Future iterations of the solution may target content based on customer location, industry, or Windows version.
|
||||
Windows release health doesn't monitor user environments or collect customer environment information. In Windows release health, all known issue content across all supported Windows versions is published to all subscribed customers. Future iterations of the solution may target content based on customer location, industry, or Windows version.
|
||||
|
||||
- **Where do I find Windows release health?**
|
||||
After logging into Microsoft 365 admin center, expand the left-hand menu using **…Show All**, click **Health** and you’ll see **Windows release health**.
|
||||
After logging into Microsoft 365 admin center, expand the left-hand menu using **…Show All**, select **Health** and you'll see **Windows release health**.
|
||||
|
||||
|
||||
- **Is the Windows release health content published to Microsoft 365 admin center the same as the content on Windows release health on Microsoft Learn?**
|
||||
No. While the content is similar, you may see more issues and more technical details published to Windows release health on Microsoft 365 admin center to better support the IT admin. For example, you’ll find details to help you diagnose issues in your environment, steps to mitigate issues, and root cause analysis.
|
||||
@ -112,13 +114,13 @@ A list of all status updates posted in the selected timeframe will be displayed,
|
||||
In an effort to ensure Windows customers have important information as soon as possible, all major known issues will be shared with Windows customers on both Microsoft Learn and the Microsoft 365 admin center. We may also update the details available for Windows release health in the Microsoft 365 admin center when we have additional details on workarounds, root cause, or other information to help you plan for updates and handle issues in your environment.
|
||||
|
||||
- **Can I share this content publicly or with other Windows customers?**
|
||||
Windows release health is provided to you as a licensed Windows customer and is not to be shared publicly.
|
||||
Windows release health is provided to you as a licensed Windows customer and isn't to be shared publicly.
|
||||
|
||||
- **Is the content redundant? How is the content organized in the different tabs?**
|
||||
Windows release health provides three tabs. The landing **All versions** tab allows you to click into a specific version of Windows. The Known issues tab shows the list of issues that are active or resolved in the past 30 days. The History tab shows a six-month history of known issues that have been resolved.
|
||||
Windows release health provides three tabs. The landing **All versions** tab allows you to select a specific version of Windows. The **Known issues** tab shows the list of issues that are active or resolved in the past 30 days. The **History** tab shows a six-month history of known issues that have been resolved.
|
||||
|
||||
- **How do I find information for the versions of Windows I’m managing?**
|
||||
On the **All versions** tab, you can select any Windows version. This will take you to the Known issues tab filtered for the version you selected. The known issues tab provides the list of active known issues and those resolved in the last 30 days. This selection persists throughout your session until changed. From the History tab you can view the list of resolved issues for that version. To change versions, use the filter in the tab.
|
||||
- **How do I find information for the versions of Windows I'm managing?**
|
||||
On the **All versions** tab, you can select any Windows version. This action takes you to the **Known issues** tab filtered for the version you selected. The **Known issues** tab provides the list of active known issues and the issues resolved in the last 30 days. This selection persists throughout your session until changed. From the **History** tab, you can view the list of resolved issues for that version. To change versions, use the filter in the tab.
|
||||
|
||||
### Microsoft 365 Admin Center functions
|
||||
|
||||
@ -126,13 +128,13 @@ A list of all status updates posted in the selected timeframe will be displayed,
|
||||
You can search Microsoft 365 admin center pages using keywords. For Windows release health, go to the desired product page and search using KB numbers, build numbers, or keywords.
|
||||
|
||||
- **How do I add other Windows admins?**
|
||||
Using the left-hand menu, go to Users, then select the Active Users tab and follow the prompts to add a new user, or assign an existing user, to the role of “Service Support admin.”
|
||||
Using the left-hand menu, go to Users, then select the Active Users tab and follow the prompts to add a new user, or assign an existing user, to the role of **Service Support admin**.
|
||||
|
||||
- **Why can’t I click to the KB article from the Known issues or History tabs?**
|
||||
Within the issue description, you’ll find links to the KB articles. In the Known issue and History tabs, the entire row is a clickable entry to the issue’s Details pane.
|
||||
- **Why can't I click to the KB article from the Known issues or History tabs?**
|
||||
Within the issue description, you'll find links to the KB articles. In the Known issue and History tabs, the entire row is a clickable entry to the issue's Details pane.
|
||||
|
||||
- **Microsoft 365 admin center has a mobile app but I don’t see Windows release health under the Health menu. Is this an open issue?**
|
||||
We are working to build the Windows release health experience on mobile devices in a future release.
|
||||
- **Microsoft 365 admin center has a mobile app but I don't see Windows release health under the Health menu. Is this an open issue?**
|
||||
We're working to build the Windows release health experience on mobile devices in a future release.
|
||||
|
||||
### Help and support
|
||||
|
||||
@ -140,7 +142,7 @@ A list of all status updates posted in the selected timeframe will be displayed,
|
||||
Seek assistance through Premier support, the [Microsoft Support website](https://support.microsoft.com), or connect with your normal channels for Windows support.
|
||||
|
||||
- **When reaching out to Support, they asked me for an advisory ID. What is this and where can it?**
|
||||
The advisory ID can be found in the upper left-hand corner of the known issue Details pane. To find it, select the Known issue you’re seeking help on, click the Details pane and you’ll find the ID under the issue title. It will be the letters WI followed by a number, similar to “WI123456”.
|
||||
The advisory ID can be found in the upper left-hand corner of the known issue Details pane. To find it, select the known issue you're seeking help on, select the **Details** pane, and you'll find the ID under the issue title. It will be the letters `WI` followed by a number, similar to `WI123456`.
|
||||
|
||||
- **How can I learn more about expanding my use of Microsoft 365 admin center?**
|
||||
To learn more, see the [Microsoft 365 admin center documentation](/microsoft-365/admin/admin-overview/about-the-admin-center).
|
||||
For more information, see the [Microsoft 365 admin center documentation](/microsoft-365/admin/admin-overview/about-the-admin-center).
|
||||
|
||||
@ -2,9 +2,9 @@
|
||||
title: Deploy Windows client updates with Configuration Manager
|
||||
description: Deploy Windows client updates with Configuration Manager
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: aaroncz
|
||||
ms.author: mstewart
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.topic: article
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Manually configuring devices for Update Compliance
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Manually configuring devices for Update Compliance
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Configuring Microsoft Endpoint Manager devices for Update Compliance
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Configuring devices that are enrolled in Endpoint Manager for Update Compliance
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
@ -21,62 +21,64 @@ ms.topic: article
|
||||
This article is specifically targeted at configuring devices enrolled to [Microsoft Endpoint Manager](/mem/endpoint-manager-overview) for Update Compliance, within Microsoft Endpoint Manager itself. Configuring devices for Update Compliance in Microsoft Endpoint Manager breaks down to the following steps:
|
||||
|
||||
1. [Create a configuration profile](#create-a-configuration-profile) for devices you want to enroll, that contains settings for all the MDM policies that must be configured.
|
||||
2. [Deploy the configuration script](#deploy-the-configuration-script) as a Win32 app to those same devices, so additional checks can be performed to ensure devices are correctly configured.
|
||||
3. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. You can learn more about this in the broad section on [enrolling devices to Update Compliance](update-compliance-get-started.md#enroll-devices-in-update-compliance).
|
||||
1. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. You can learn more about this in the broad section on [enrolling devices to Update Compliance](update-compliance-get-started.md#enroll-devices-in-update-compliance).
|
||||
|
||||
> [!TIP]
|
||||
> If you need to troubleshoot client enrollment, consider deploying the [configuration script](#deploy-the-configuration-script) as a Win32 app to a few devices and reviewing the logs it creates. Additional checks are performed with the script to ensure devices are correctly configured.
|
||||
|
||||
## Create a configuration profile
|
||||
|
||||
Take the following steps to create a configuration profile that will set required policies for Update Compliance:
|
||||
|
||||
1. Go to the Admin portal in Endpoint Manager and navigate to **Devices/Windows/Configuration profiles**.
|
||||
2. On the **Configuration profiles** view, select **Create a profile**.
|
||||
3. Select **Platform**="Windows 10 and later" and **Profile type**="Templates".
|
||||
4. For **Template name**, select **Custom**, and then press **Create**.
|
||||
5. You are now on the Configuration profile creation screen. On the **Basics** tab, give a **Name** and **Description**.
|
||||
6. On the **Configuration settings** page, you will be adding multiple OMA-URI Settings that correspond to the policies described in [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md).
|
||||
1. On the **Configuration profiles** view, select **Create a profile**.
|
||||
1. Select **Platform**="Windows 10 and later" and **Profile type**="Templates".
|
||||
1. For **Template name**, select **Custom**, and then press **Create**.
|
||||
1. You are now on the Configuration profile creation screen. On the **Basics** tab, give a **Name** and **Description**.
|
||||
1. On the **Configuration settings** page, you will be adding multiple OMA-URI Settings that correspond to the policies described in [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md).
|
||||
1. If you don't already have it, get your Commercial ID. For steps, see [Get your CommmercialID](update-compliance-get-started.md#get-your-commercialid).
|
||||
2. Add a setting for **Commercial ID** with the following values:
|
||||
1. Add a setting for **Commercial ID** with the following values:
|
||||
- **Name**: Commercial ID
|
||||
- **Description**: Sets the Commercial ID that corresponds to the Update Compliance Log Analytics workspace.
|
||||
- **OMA-URI**: `./Vendor/MSFT/DMClient/Provider/ProviderID/CommercialID`
|
||||
- **Data type**: String
|
||||
- **Value**: *Set this to your Commercial ID*
|
||||
2. Add a setting configuring the **Windows Diagnostic Data level** for devices:
|
||||
1. Add a setting configuring the **Windows Diagnostic Data level** for devices:
|
||||
- **Name**: Allow Telemetry
|
||||
- **Description**: Sets the maximum allowed diagnostic data to be sent to Microsoft, required for Update Compliance.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowTelemetry`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1 (*all that is required is 1, but it can be safely set to a higher value*).
|
||||
3. (*Recommended, but not required*) Add a setting for **disabling devices' Diagnostic Data opt-in settings interface**. If this is not disabled, users of each device can potentially override the diagnostic data level of devices such that data will not be available for those devices in Update Compliance:
|
||||
1. (*Recommended, but not required*) Add a setting for **disabling devices' Diagnostic Data opt-in settings interface**. If this is not disabled, users of each device can potentially override the diagnostic data level of devices such that data will not be available for those devices in Update Compliance:
|
||||
- **Name**: Disable Telemetry opt-in interface
|
||||
- **Description**: Disables the ability for end-users of devices can adjust diagnostic data to levels lower than defined by the Allow Telemetry setting.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/ConfigureTelemetryOptInSettingsUx`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1
|
||||
4. Add a setting to **Allow device name in diagnostic data**; otherwise, there will be no device name in Update Compliance:
|
||||
1. Add a setting to **Allow device name in diagnostic data**; otherwise, there will be no device name in Update Compliance:
|
||||
- **Name**: Allow device name in Diagnostic Data
|
||||
- **Description**: Allows device name in Diagnostic Data.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowDeviceNameInDiagnosticData`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1
|
||||
5. Add a setting to **Allow Update Compliance processing**; this policy is required for Update Compliance:
|
||||
1. Add a setting to **Allow Update Compliance processing**; this policy is required for Update Compliance:
|
||||
- **Name**: Allow Update Compliance Processing
|
||||
- **Description**: Opts device data into Update Compliance processing. Required to see data.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowUpdateComplianceProcessing`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 16
|
||||
6. Add a setting to **Allow commercial data pipeline**; this policy is required for Update Compliance:
|
||||
1. Add a setting to **Allow commercial data pipeline**; this policy is required for Update Compliance:
|
||||
- **Name**: Allow commercial data pipeline
|
||||
- **Description**: Configures Microsoft to be the processor of the Windows diagnostic data collected from an Azure Active Directory-joined device.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowCommercialDataPipeline`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1
|
||||
|
||||
7. Proceed through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll.
|
||||
8. Review and select **Create**.
|
||||
1. Proceed through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll.
|
||||
1. Review and select **Create**.
|
||||
|
||||
## Deploy the configuration script
|
||||
|
||||
The [Update Compliance Configuration Script](update-compliance-configuration-script.md) is an important component of properly enrolling devices in Update Compliance, though it isn't strictly necessary. It checks to ensure that devices have the required services running and checks connectivity to the endpoints detailed in the section on [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md). You can deploy the script as a Win32 app. For more information, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management).
|
||||
The [Update Compliance Configuration Script](update-compliance-configuration-script.md) is a useful tool for properly enrolling devices in Update Compliance, though it isn't strictly necessary. It checks to ensure that devices have the required services running and checks connectivity to the endpoints detailed in the section on [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md). You can deploy the script as a Win32 app. For more information, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management).
|
||||
|
||||
When you deploy the configuration script as a Win32 app, you won't be able to retrieve the results of logs on the device without having access to the device, or saving results of the logs to a shared filesystem. We recommend deploying the script in Pilot mode to a set of devices that you do have access to, or have a way to access the resultant log output the script provides, with as similar of a configuration profile as other devices which will be enrolled to Update Compliance, and analyzing the logs for any potential issues. Following this, you can deploy the configuration script in Deployment mode as a Win32 app to all Update Compliance devices.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Update Compliance Configuration Script
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Downloading and using the Update Compliance Configuration Script
|
||||
ms.prod: w10
|
||||
author: mestew
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Delivery Optimization in Update Compliance
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Learn how the Update Compliance solution provides you with information about your Delivery Optimization configuration.
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
@ -46,7 +46,7 @@ The table breaks down the number of bytes from each download source into specifi
|
||||
The download sources that could be included are:
|
||||
- LAN Bytes: Bytes downloaded from LAN Peers which are other devices on the same local network
|
||||
- Group Bytes: Bytes downloaded from Group Peers which are other devices that belong to the same Group (available when the "Group" download mode is used)
|
||||
- HTTP Bytes: Non-peer bytes. The HTTP download source can be Microsoft Servers, Windows Update Servers, a WSUS server or an Configuration Manager Distribution Point for Express Updates.
|
||||
- HTTP Bytes: Non-peer bytes. The HTTP download source can be Microsoft Servers, Windows Update Servers, a WSUS server or a Configuration Manager Distribution Point for Express Updates.
|
||||
|
||||
<!--Using include file, waas-delivery-optimization-monitor.md, for shared content on DO monitoring-->
|
||||
[!INCLUDE [Monitor Delivery Optimization](../do/includes/waas-delivery-optimization-monitor.md)]
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Update Compliance - Feature Update Status report
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Learn how the Feature Update Status report provides information about the status of feature updates across all devices.
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: Get started with Update Compliance
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Prerequisites, Azure onboarding, and configuring devices for Update Compliance
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
ms.collection:
|
||||
- M365-analytics
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Monitor Windows Updates and Microsoft Defender AV with Update Compliance
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: You can use Update Compliance in Azure portal to monitor the progress of updates and key anti-malware protection features on devices in your network.
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
---
|
||||
title: Update Compliance - Need Attention! report
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Learn how the Need attention! section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance.
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Privacy in Update Compliance
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: an overview of the Feature Update Status report
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Update Compliance - Safeguard Holds report
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Learn how the Safeguard Holds report provides information about safeguard holds in your population.
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Update Compliance Schema - WaaSDeploymentStatus
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: WaaSDeploymentStatus schema
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Update Compliance Schema - WaaSInsiderStatus
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: WaaSInsiderStatus schema
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Update Compliance Schema - WaaSUpdateStatus
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: WaaSUpdateStatus schema
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Update Compliance Schema - WUDOAggregatedStatus
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: WUDOAggregatedStatus schema
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Update Compliance Schema - WUDOStatus
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: WUDOStatus schema
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Update Compliance Data Schema
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: an overview of Update Compliance data schema
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
---
|
||||
@ -21,7 +21,7 @@ The table below summarizes the different tables that are part of the Update Comp
|
||||
|
||||
|Table |Category |Description |
|
||||
|--|--|--|
|
||||
|[**WaaSUpdateStatus**](update-compliance-schema-waasupdatestatus.md) |Device record |This table houses device-centric data and acts as the device record for Update Compliance. Each record provided in daily snapshots map to a single device in a single tenant. This table has data such as the current device's installed version of Windows, whether it is on the latest available updates, and whether the device needs attention. |
|
||||
|[**WaaSUpdateStatus**](update-compliance-schema-waasupdatestatus.md) |Device record |This table houses device-centric data and acts as the device record for Update Compliance. Each record provided in daily snapshots maps to a single device in a single tenant. This table has data such as the current device's installed version of Windows, whether it is on the latest available updates, and whether the device needs attention. |
|
||||
|[**WaaSInsiderStatus**](update-compliance-schema-waasinsiderstatus.md) |Device record |This table houses device-centric data specifically for devices enrolled to the Windows Insider Program. Devices enrolled to the Windows Insider Program do not currently have any WaaSDeploymentStatus records, so do not have Update Session data to report on update deployment progress. |
|
||||
|[**WaaSDeploymentStatus**](update-compliance-schema-waasdeploymentstatus.md) |Update Session record |This table tracks a specific update on a specific device. Multiple WaaSDeploymentStatus records can exist simultaneously for a given device, as each record is specific to a given update and its type. For example, a device can have both a WaaSDeploymentStatus tracking a Windows Feature Update, as well as one tracking a Windows Quality Update, at the same time. |
|
||||
|[**WUDOStatus**](update-compliance-schema-wudostatus.md) |Delivery Optimization record |This table provides information, for a single device, on their bandwidth utilization across content types in the event they use [Delivery Optimization](https://support.microsoft.com/help/4468254/windows-update-delivery-optimization-faq). |
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Update Compliance - Security Update Status report
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Learn how the Security Update Status section provides information about security updates across all devices.
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Using Update Compliance
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
manager: aczechowski
|
||||
description: Learn how to use Update Compliance to monitor your device's Windows updates.
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
|
||||
@ -24,8 +24,10 @@ ms.date: 08/24/2022
|
||||
This article is specifically targeted at configuring devices enrolled to [Microsoft Endpoint Manager](/mem/endpoint-manager-overview) for Update Compliance, within Microsoft Endpoint Manager itself. Configuring devices for Update Compliance in Microsoft Endpoint Manager breaks down to the following steps:
|
||||
|
||||
1. [Create a configuration profile](#create-a-configuration-profile) for devices you want to enroll. The configuration profile contains settings for all the Mobile Device Management (MDM) policies that must be configured.
|
||||
2. [Deploy the configuration script](#deploy-the-configuration-script) as a Win32 app to those same devices, so additional checks can be performed to ensure devices are correctly configured.
|
||||
3. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. For more information, see [Use Update Compliance](update-compliance-v2-use.md).
|
||||
1. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. For more information, see [Use Update Compliance](update-compliance-v2-use.md).
|
||||
|
||||
> [!TIP]
|
||||
> If you need to troubleshoot client enrollment, consider deploying the [configuration script](#deploy-the-configuration-script) as a Win32 app to a few devices and reviewing the logs it creates. Additional checks are performed with the script to ensure devices are correctly configured.
|
||||
|
||||
## Create a configuration profile
|
||||
|
||||
@ -105,7 +107,7 @@ Create a configuration profile that will set the required policies for Update Co
|
||||
|
||||
## Deploy the configuration script
|
||||
|
||||
The [Update Compliance Configuration Script](update-compliance-v2-configuration-script.md) is an important component of properly enrolling devices in Update Compliance, though it isn't strictly necessary. It checks to ensure that devices have the required services running and checks connectivity to the endpoints detailed in the section on [Manually configuring devices for Update Compliance](update-compliance-v2-configuration-manual.md). You can deploy the script as a Win32 app. For more information, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management).
|
||||
The [Update Compliance Configuration Script](update-compliance-v2-configuration-script.md) is a useful tool for properly enrolling devices in Update Compliance, though it isn't strictly necessary. It checks to ensure that devices have the required services running and checks connectivity to the endpoints detailed in the section on [Manually configuring devices for Update Compliance](update-compliance-v2-configuration-manual.md). You can deploy the script as a Win32 app. For more information, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management).
|
||||
|
||||
When you deploy the configuration script as a Win32 app, you won't be able to retrieve the results of logs on the device without having access to the device, or saving results of the logs to a shared filesystem. We recommend deploying the script in pilot mode to a set of devices that you do have access to, or have a way to access the resultant log output the script provides, with as similar of a configuration profile as other devices which will be enrolled to Update Compliance, and analyzing the logs for any potential issues. Following this, you can deploy the configuration script in deployment mode as a Win32 app to all Update Compliance devices.
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ ms.topic: article
|
||||
ms.custom:
|
||||
- seo-marvel-apr2020
|
||||
ms.collection: highpri
|
||||
date: 09/22/2022
|
||||
---
|
||||
|
||||
# Manage device restarts after updates
|
||||
@ -18,11 +19,11 @@ ms.collection: highpri
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
- Windows 11
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
You can use Group Policy settings, mobile device management (MDM), or Registry (not recommended) to configure when devices will restart after a Windows 10 update is installed. You can schedule update installation and set policies for restart, configure active hours for when restarts will not occur, or you can do both.
|
||||
You can use Group Policy settings, mobile device management (MDM), or Registry (not recommended) to configure when devices will restart after a Windows update is installed. You can schedule update installation and set policies for restart, configure active hours for when restarts will not occur, or you can do both.
|
||||
|
||||
## Schedule update installation
|
||||
|
||||
@ -100,15 +101,27 @@ To configure active hours max range through MDM, use [**Update/ActiveHoursMaxRan
|
||||
|
||||
## Limit restart delays
|
||||
|
||||
After an update is installed, Windows 10 attempts automatic restart outside of active hours. If the restart does not succeed after seven days (by default), the user will see a notification that restart is required. You can use the **Specify deadline before auto-restart for update installation** policy to change the delay from seven days to any number of days between two and 14.
|
||||
After an update is installed, Windows attempts automatic restart outside of active hours. If the restart does not succeed after seven days (by default), the user will see a notification that restart is required. You can use the **Specify deadline before auto-restart for update installation** policy to change the delay from seven days to any number of days between two and 14.
|
||||
|
||||
## Control restart notifications
|
||||
|
||||
In Windows 10, version 1703, we have added settings to control restart notifications for users.
|
||||
### Display options for update notifications
|
||||
|
||||
Starting in Windows 10 version 1809, you can define which Windows Update notifications are displayed to the user. This policy doesn't control how and when updates are downloaded and installed. You can use **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Display options for update notifications** with these values:
|
||||
|
||||
**0** (default) - Use the default Windows Update notifications </br>
|
||||
**1** - Turn off all notifications, excluding restart warnings </br>
|
||||
**2** - Turn off all notifications, including restart warnings </br>
|
||||
|
||||
To configure this behavior through MDM, use [**Update/UpdateNotificationLevel**](/windows/client-management/mdm/policy-configuration-service-provider#update-updatenotificationlevel).
|
||||
|
||||
Starting in Windows 11, version 22H2, **Apply only during active hours** was added as an additional option for **Display options for update notifications**. When **Apply only during active hours** is selected, the notifications will only be disabled during active hours when options `1` or `2` are used. To ensure that the device stays updated, a notification will still be shown during active hours if **Apply only during active hours** is selected, and once a deadline has been reached when [Specify deadlines for automatic updates and restarts](wufb-compliancedeadlines.md) is configured. <!--6286260-->
|
||||
|
||||
To configure this behavior through MDM, use [**Update/UpdateNotificationLevel**](/windows/client-management/mdm/policy-csp-update#update-NoUpdateNotificationDuringActiveHours).
|
||||
|
||||
### Auto-restart notifications
|
||||
|
||||
Administrators can override the default behavior for the auto-restart required notification. By default, this notification will dismiss automatically.
|
||||
Administrators can override the default behavior for the auto-restart required notification. By default, this notification will dismiss automatically. This setting was added in Windows 10, version 1703.
|
||||
|
||||
To configure this behavior through Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Windows Update** and select **Configure auto-restart required notification for updates**. When configured to **2 - User Action**, a user that gets this notification must manually dismiss it.
|
||||
|
||||
@ -198,10 +211,10 @@ There are three different registry combinations for controlling restart behavior
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Update Windows 10 in the enterprise](index.md)
|
||||
- [Update Windows in the enterprise](index.md)
|
||||
- [Overview of Windows as a service](waas-overview.md)
|
||||
- [Configure Delivery Optimization for Windows 10 updates](../do/waas-delivery-optimization.md)
|
||||
- [Configure BranchCache for Windows 10 updates](waas-branchcache.md)
|
||||
- [Configure Delivery Optimization for Windows updates](../do/waas-delivery-optimization.md)
|
||||
- [Configure BranchCache for Windows updates](waas-branchcache.md)
|
||||
- [Configure Windows Update for Business](waas-configure-wufb.md)
|
||||
- [Integrate Windows Update for Business with management solutions](waas-integrate-wufb.md)
|
||||
- [Walkthrough: use Group Policy to configure Windows Update for Business](waas-wufb-group-policy.md)
|
||||
|
||||
@ -3,12 +3,12 @@ title: Manage additional Windows Update settings
|
||||
description: In this article, learn about additional settings to control the behavior of Windows Update.
|
||||
ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
manager: dougeby
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.collection: highpri
|
||||
date: 09/22/2022
|
||||
---
|
||||
|
||||
# Manage additional Windows Update settings
|
||||
@ -36,6 +36,7 @@ You can use Group Policy settings or mobile device management (MDM) to configure
|
||||
| [Allow signed updates from an intranet Microsoft update service location](#allow-signed-updates-from-an-intranet-microsoft-update-service-location) | [AllowNonMicrosoftSignedUpdate](/windows/client-management/mdm/policy-configuration-service-provider#update-allownonmicrosoftsignedupdate) | All |
|
||||
| [Do not include drivers with Windows Updates](#do-not-include-drivers-with-windows-updates) | [ExcludeWUDriversInQualityUpdate](/windows/client-management/mdm/policy-configuration-service-provider#update-excludewudriversinqualityupdate) | 1607 |
|
||||
| [Configure Automatic Updates](#configure-automatic-updates) | [AllowAutoUpdate](/windows/client-management/mdm/policy-configuration-service-provider#update-allowautoupdate) | All |
|
||||
| | [Windows Update notifications display organization name](#bkmk_display-name) </br></br> *Organization name is displayed by default. A registry value can disable this behavior. | Windows 11 devices that are Azure Active Directory joined or registered <!--6286260-->|
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Additional information about settings to manage device restarts and restart notifications for updates is available on **[Manage device restarts after updates](waas-restart.md)**.
|
||||
@ -230,7 +231,7 @@ To do this, follow these steps:
|
||||
> [!NOTE]
|
||||
> This setting affects client behavior after the clients have updated to the SUS SP1 client version or later versions.
|
||||
|
||||
To use Automatic Updates with a server that is running Software Update Services, see the Deploying Microsoft Windows Server Update Services 2.0 guidance.
|
||||
To use Automatic Updates with a server that is running Windows Software Update Services (WSUS), see the [Deploying Microsoft Windows Server Update Services](/windows-server/administration/windows-server-update-services/deploy/deploy-windows-server-update-services) guidance.
|
||||
|
||||
When you configure Automatic Updates directly by using the policy registry keys, the policy overrides the preferences that are set by the local administrative user to configure the client. If an administrator removes the registry keys at a later date, the preferences that were set by the local administrative user are used again.
|
||||
|
||||
@ -246,3 +247,32 @@ HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\
|
||||
* WUStatusServer (REG_SZ)
|
||||
|
||||
This value sets the SUS statistics server by HTTP name (for example, http://IntranetSUS).
|
||||
|
||||
## <a name="bkmk_display-name"> </a> Display organization name in Windows Update notifications
|
||||
<!--6286260-->
|
||||
When Windows 11 clients are associated with an Azure AD tenant, the organization name appears in the Windows Update notifications. For instance, when you have a compliance deadline configured for Windows Update for Business, the user notification will display a message similar to **Contoso requires important updates to be installed**. The organization name will also display on the **Windows Update** page in the **Settings** for Windows 11.
|
||||
|
||||
The organization name appears automatically for Windows 11 clients that are associated with Azure AD in any of the following ways:
|
||||
- [Azure AD joined](/azure/active-directory/devices/concept-azure-ad-join)
|
||||
- [Azure AD registered](/azure/active-directory/devices/concept-azure-ad-register)
|
||||
- [Hybrid Azure AD joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid)
|
||||
|
||||
To disable displaying the organization name in Windows Update notifications, add or modify the following in the registry:
|
||||
|
||||
- **Registry key**: `HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsUpdate\Orchestrator\Configurations`
|
||||
- **DWORD value name**: UsoDisableAADJAttribution
|
||||
- **Value data:** 1
|
||||
|
||||
The following PowerShell script is provided as an example to you:
|
||||
```powershell
|
||||
$registryPath = "HKLM:\Software\Microsoft\WindowsUpdate\Orchestrator\Configurations"
|
||||
$Name = "UsoDisableAADJAttribution"
|
||||
$value = "1"
|
||||
|
||||
if (!(Test-Path $registryPath))
|
||||
{
|
||||
New-Item -Path $registryPath -Force | Out-Null
|
||||
}
|
||||
|
||||
New-ItemProperty -Path $registryPath -Name $name -Value $value -PropertyType DWORD -Force | Out-Null
|
||||
```
|
||||
|
||||
@ -178,12 +178,14 @@ There are additional settings that affect the notifications.
|
||||
|
||||
We recommend that you use the default notifications as they aim to provide the best user experience while adjusting for the compliance policies that you have set. If you do have further needs that are not met by the default notification settings, you can use **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Display options for update notifications** with these values:
|
||||
|
||||
**0** (default) – Use the default Windows Update notifications
|
||||
**1** – Turn off all notifications, excluding restart warnings
|
||||
**2** – Turn off all notifications, including restart warnings
|
||||
**0** (default) - Use the default Windows Update notifications </br>
|
||||
**1** - Turn off all notifications, excluding restart warnings </br>
|
||||
**2** - Turn off all notifications, including restart warnings </br>
|
||||
|
||||
> [!NOTE]
|
||||
> Option **2** creates a poor experience for personal devices; it's only recommended for kiosk devices where automatic restarts have been disabled.
|
||||
Option **2** creates a poor experience for personal devices; it's only recommended for kiosk devices where automatic restarts have been disabled.
|
||||
|
||||
> [!NOTE]
|
||||
> Starting in Windows 11, version 22H2, **Apply only during active hours** was added as an additional option for **Display options for update notifications**. When **Apply only during active hours** is selected, the notifications will only be disabled during active hours when options `1` or `2` are used. To ensure that the device stays updated, a notification will still be shown during active hours if **Apply only during active hours** is selected, and once a deadline has been reached when [Specify deadlines for automatic updates and restarts](wufb-compliancedeadlines.md) is configured. <!--6286260-->
|
||||
|
||||
Still more options are available in **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure auto-restart restart warning notifications schedule for updates**. This setting allows you to specify the period for auto-restart warning reminder notifications (from 2-24 hours; 4 hours is the default) before the update and to specify the period for auto-restart imminent warning notifications (15-60 minutes is the default). We recommend using the default notifications.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user