mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
fix merge conflict
This commit is contained in:
Meghan Stewart
@ -44,7 +44,7 @@ Windows 10 Insider Preview builds offer organizations a valuable and exciting op
|
||||
|Release channel |**Fast Ring:** Insider Preview builds in the Fast Ring are released approximately once a week and contain the very latest features. This makes them ideal for feature exploration.|
|
||||
|Users | Because Fast Ring builds are released so early in the development cycle, we recommend limiting feature exploration in your organization to IT administrators and developers running Insider Preview builds on secondary devices. |
|
||||
|Tasks | - Install and manage Insider Preview builds on devices (per device or centrally across multiple devices)<br> - Explore new features in Windows designed for organizations, including new features related to current and planned line of business applications<br> - Before running an Insider Preview build, check our [Windows Insider blog](https://blogs.windows.com/windowsexperience/tag/windows-insider-program/#k3WWwxKCTWHCO82H.97) for a summary of current features. |
|
||||
|Feedback | - This helps us make adjustments to features as quickly as possible.<br> - Encourage users to sign into the Feedback Hub using their Azure Active Directory work accounts. This enables both you and Microsoft to track feedback submitted by users within your specific organization. (Note: This tracking is only visible to Microsoft and registered Insiders within your organization’s domain.)<br> - [Learn how to provide effective feedback in the Feedback Hub](https://insider.windows.com/how-to-feedback/) |
|
||||
|Feedback | - This helps us make adjustments to features as quickly as possible.<br> - Encourage users to sign into the Feedback Hub using their Azure Active Directory work accounts. This enables both you and Microsoft to track feedback submitted by users within your specific organization. (Note: This tracking is only visible to Microsoft and registered Insiders within your organization’s domain.)<br> - [Learn how to provide effective feedback in the Feedback Hub](/windows-insider/feedback) |
|
||||
|
||||
## Validate Insider Preview builds
|
||||
Along with exploring new features, you also have the option to validate your apps and infrastructure on Insider Preview builds. Early validation has several benefits:
|
||||
|
||||
@ -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: 05/03/2023
|
||||
ms.date: 06/07/2023
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
@ -19,28 +19,39 @@ If you're unable to sign in to the Microsoft 365 admin portal, check the [Micros
|
||||
|
||||
To be informed about the latest updates and releases, follow [@WindowsUpdate](https://twitter.com/windowsupdate) on Twitter.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Ensure the following prerequisites are met to display the Windows release health page in the Microsoft 365 admin center: <!--7872213-->
|
||||
|
||||
- One of the following licenses:
|
||||
- Windows 10/11 Enterprise E3 or E5 (included in Microsoft 365 F3, E3, or E5)
|
||||
- Windows 10/11 Education A3 or A5 (included in Microsoft 365 A3 or A5)
|
||||
|
||||
- Sign into the Microsoft 365 admin center using an [admin role](/microsoft-365/admin/add-users/about-admin-roles).
|
||||
- Most roles containing the word `administrator` give you access to the Windows release health page such as [Global Administrator](/azure/active-directory/roles/permissions-reference#global-administrator), [Helpdesk Administrator](/azure/active-directory/roles/permissions-reference#helpdesk-administrator), and [Service Support Administrator](/azure/active-directory/roles/permissions-reference#service-support-administrator). For more information, see [Assign admin roles in the Microsoft 365 admin center](/microsoft-365/admin/add-users/assign-admin-roles).
|
||||
|
||||
> [!NOTE]
|
||||
> Currently, Windows release health isn't available for Government Community Cloud (GCC) tenants.
|
||||
|
||||
## 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.
|
||||
|
||||
> [!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).
|
||||
1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com) and sign in with an admin account.
|
||||
|
||||
2. To view Windows release health in the Microsoft 365 Admin Center, go to **Health > Windows release health**.
|
||||
1. 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'll have access to known issue information for all supported versions of the Windows operating system.
|
||||
1. On the **Windows release health** page, you 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 shows 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.
|
||||
|
||||
|
||||
|
||||
|
||||
The known issue summary provides the following information:
|
||||
|
||||
@ -56,7 +67,7 @@ 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:
|
||||
You can 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**.
|
||||
@ -78,20 +89,20 @@ In the **Windows release health** experience, every known issue is assigned as s
|
||||
|**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. |
|
||||
|**Mitigated** | A workaround is available and communicated to Windows customers for a known issue. A known issue stays 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 caused by a software or driver from a third-party software or device manufacturer. A known issue stays in this state until the issue is resolved by Microsoft or the third-party. |
|
||||
|**Resolved** | A solution was released by Microsoft and was documented in a KB article that resolves the known issue once it's deployed in the customer's environment. |
|
||||
|**Resolved: External** | A solution was released by Microsoft or a third-party that resolves the known issue once it's deployed in the customer's environment. |
|
||||
|
||||
## Known issue history
|
||||
|
||||
The Windows release health page lets you view the history of all status updates posted for a specific known issue. To view all past updates posted for a given issue, select **View history** on the issue detail page.
|
||||
|
||||
|
||||
|
||||
|
||||
A list of all status updates posted in the selected timeframe will be displayed, as shown below. You can expand any row to view the specific information provided in that status update.
|
||||
A list of all status updates posted in the selected time frame is displayed. You can expand any row to view the specific information provided in that status update.
|
||||
|
||||
|
||||
|
||||
|
||||
## Frequently asked questions
|
||||
|
||||
@ -104,14 +115,14 @@ A list of all status updates posted in the selected timeframe will be displayed,
|
||||
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**, select **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** to display the **Windows release health** menu option.
|
||||
|
||||
|
||||
- **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.
|
||||
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.
|
||||
|
||||
- **How often will content be updated?**
|
||||
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.
|
||||
To ensure Windows customers have important information as soon as possible, all major known issues are 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 isn't to be shared publicly.
|
||||
@ -131,7 +142,7 @@ A list of all status updates posted in the selected timeframe will be displayed,
|
||||
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.
|
||||
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're working to build the Windows release health experience on mobile devices in a future release.
|
||||
@ -142,7 +153,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, 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`.
|
||||
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. The ID is the letters `WI` followed by a number, similar to `WI123456`.
|
||||
|
||||
- **How can I learn more about expanding my use of Microsoft 365 admin center?**
|
||||
For more information, see the [Microsoft 365 admin center documentation](/microsoft-365/admin/admin-overview/about-the-admin-center).
|
||||
|
||||
@ -45,7 +45,7 @@ Keep security baselines current to help ensure that your environment is secure a
|
||||
|
||||
There are a number of Windows policies (set by Group Policy, Intune, or other methods) that affect when Windows updates are installed, deferral, end-user experience, and many other aspects. Check these policies to make sure they are set appropriately.
|
||||
|
||||
- **Windows Administrative templates**: Each Windows client feature update has a supporting Administrative template (.admx) file. Group Policy tools use Administrative template files to populate policy settings in the user interface. The templates are available in the Download Center, for example, this one for [Windows 10, version 1909](https://www.microsoft.com/download/100591).
|
||||
- **Windows Administrative templates**: Each Windows client feature update has a supporting Administrative template (.admx) file. Group Policy tools use Administrative template files to populate policy settings in the user interface. The templates are available in the Download Center, for example, this one for [Windows 11, version 22H2](https://www.microsoft.com/download/details.aspx?id=104593).
|
||||
- **Policies for update compliance and end-user experience**: A number of settings affect when a device installs updates, whether and for how long a user can defer an update, restart behavior after installation, and many other aspects of update behavior. It's especially important to look for existing policies that are out of date or could conflict with new ones.
|
||||
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 12/31/2017
|
||||
ms.date: 05/09/2023
|
||||
ms.reviewer: stevedia
|
||||
---
|
||||
|
||||
@ -77,6 +77,7 @@ This table shows the correct sequence for applying the various tasks to the file
|
||||
|Add Safe OS Dynamic Update | 6 | | |
|
||||
|Add Setup Dynamic Update | | | | 26
|
||||
|Add setup.exe from WinPE | | | | 27
|
||||
|Add boot manager from WinPE | | | | 28
|
||||
|Add latest cumulative update | | 15 | 21 |
|
||||
|Clean up the image | 7 | 16 | 22 |
|
||||
|Add Optional Components | | | 23 |
|
||||
@ -300,7 +301,7 @@ Move-Item -Path $WORKING_PATH"\winre2.wim" -Destination $WORKING_PATH"\winre.wim
|
||||
|
||||
### Update WinPE
|
||||
|
||||
This script is similar to the one that updates WinRE, but instead it mounts Boot.wim, applies the packages with the latest cumulative update last, and saves. It repeats this for all images inside of Boot.wim, typically two images. It starts by applying the servicing stack Dynamic Update. Since the script is customizing this media with Japanese, it installs the language pack from the WinPE folder on the language pack ISO. Additionally, add font support and text to speech (TTS) support. Since the script is adding a new language, it rebuilds lang.ini, used to identify languages installed in the image. For the second image, we'll save setup.exe for later use, to ensure this version matches the \sources\setup.exe version from the installation media. If these binaries are not identical, Windows Setup will fail during installation. Finally, it cleans and exports Boot.wim, and copies it back to the new media.
|
||||
This script is similar to the one that updates WinRE, but instead it mounts Boot.wim, applies the packages with the latest cumulative update last, and saves. It repeats this for all images inside of Boot.wim, typically two images. It starts by applying the servicing stack Dynamic Update. Since the script is customizing this media with Japanese, it installs the language pack from the WinPE folder on the language pack ISO. Additionally, it adds font support and text to speech (TTS) support. Since the script is adding a new language, it rebuilds lang.ini, used to identify languages installed in the image. For the second image, we'll save setup.exe for later use, to ensure this version matches the \sources\setup.exe version from the installation media. If these binaries are not identical, Windows Setup will fail during installation. We'll also save the serviced boot manager files for later use in the script. Finally, the script cleans and exports Boot.wim, and copies it back to the new media.
|
||||
|
||||
```powershell
|
||||
#
|
||||
@ -416,9 +417,15 @@ Foreach ($IMAGE in $WINPE_IMAGES) {
|
||||
Write-Output "$(Get-TS): Performing image cleanup on WinPE"
|
||||
DISM /image:$WINPE_MOUNT /cleanup-image /StartComponentCleanup | Out-Null
|
||||
|
||||
# If second image, save setup.exe for later use. This will address possible binary mismatch with the version in the main OS \sources folder
|
||||
if ($IMAGE.ImageIndex -eq "2") {
|
||||
|
||||
# Save setup.exe for later use. This will address possible binary mismatch with the version in the main OS \sources folder
|
||||
Copy-Item -Path $WINPE_MOUNT"\sources\setup.exe" -Destination $WORKING_PATH"\setup.exe" -Force -ErrorAction stop | Out-Null
|
||||
|
||||
# Save serviced boot manager files later copy to the root media.
|
||||
Copy-Item -Path $WINPE_MOUNT"\Windows\boot\efi\bootmgfw.efi" -Destination $WORKING_PATH"\bootmgfw.efi" -Force -ErrorAction stop | Out-Null
|
||||
Copy-Item -Path $WINPE_MOUNT"\Windows\boot\efi\bootmgr.efi" -Destination $WORKING_PATH"\bootmgr.efi" -Force -ErrorAction stop | Out-Null
|
||||
|
||||
}
|
||||
|
||||
# Dismount
|
||||
@ -532,7 +539,7 @@ Move-Item -Path $WORKING_PATH"\install2.wim" -Destination $MEDIA_NEW_PATH"\sourc
|
||||
|
||||
### Update remaining media files
|
||||
|
||||
This part of the script updates the Setup files. It simply copies the individual files in the Setup Dynamic Update package to the new media. This step brings an updated Setup files as needed, along with the latest compatibility database, and replacement component manifests. This script also does a final replacement of setup.exe using the previously saved version from WinPE.
|
||||
This part of the script updates the Setup files. It simply copies the individual files in the Setup Dynamic Update package to the new media. This step brings in updated Setup files as needed, along with the latest compatibility database, and replacement component manifests. This script also does a final replacement of setup.exe and boot manager files using the previously saved versions from WinPE.
|
||||
|
||||
```powershell
|
||||
#
|
||||
@ -544,8 +551,29 @@ Write-Output "$(Get-TS): Adding package $SETUP_DU_PATH"
|
||||
cmd.exe /c $env:SystemRoot\System32\expand.exe $SETUP_DU_PATH -F:* $MEDIA_NEW_PATH"\sources" | Out-Null
|
||||
|
||||
# Copy setup.exe from boot.wim, saved earlier.
|
||||
Write-Output "$(Get-TS): Copying $WORKING_PATH\setup.exe to $MEDIA_NEW_PATH\sources\setup.exe"
|
||||
Copy-Item -Path $WORKING_PATH"\setup.exe" -Destination $MEDIA_NEW_PATH"\sources\setup.exe" -Force -ErrorAction stop | Out-Null
|
||||
|
||||
|
||||
# Copy bootmgr files from boot.wim, saved earlier.
|
||||
$MEDIA_NEW_FILES = Get-ChildItem $MEDIA_NEW_PATH -Force -Recurse -Filter b*.efi
|
||||
|
||||
Foreach ($File in $MEDIA_NEW_FILES){
|
||||
if (($File.Name -ieq "bootmgfw.efi") -or `
|
||||
($File.Name -ieq "bootx64.efi") -or `
|
||||
($File.Name -ieq "bootia32.efi") -or `
|
||||
($File.Name -ieq "bootaa64.efi"))
|
||||
{
|
||||
Write-Output "$(Get-TS): Copying $WORKING_PATH\bootmgfw.efi to $($File.FullName)"
|
||||
Copy-Item -Path $WORKING_PATH"\bootmgfw.efi" -Destination $File.FullName -Force -ErrorAction stop | Out-Null
|
||||
}
|
||||
elseif ($File.Name -ieq "bootmgr.efi")
|
||||
{
|
||||
Write-Output "$(Get-TS): Copying $WORKING_PATH\bootmgr.efi to $($File.FullName)"
|
||||
Copy-Item -Path $WORKING_PATH"\bootmgr.efi" -Destination $File.FullName -Force -ErrorAction stop | Out-Null
|
||||
}
|
||||
}
|
||||
|
||||
```
|
||||
|
||||
### Finish up
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 288 KiB |
@ -8,7 +8,7 @@ ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 03/23/2023
|
||||
ms.date: 05/19/2023
|
||||
---
|
||||
|
||||
# Update release cycle for Windows clients
|
||||
@ -96,7 +96,7 @@ Some of the new features may be disruptive to organizations. By default, these s
|
||||
- WSUS
|
||||
- Devices that have updates managed by Configuration Manager use WSUS
|
||||
|
||||
Features that are turned off by default are listed in the KB article for the monthly cumulative update. If you want to enable these features, there's a client policy that allows admins to **Enable features introduced via servicing that are off by default**. For more information about this policy, see [Enable features introduced via servicing that are off by default](waas-configure-wufb.md#enable-features-introduced-via-servicing-that-are-off-by-default).
|
||||
Features that are turned off by default are listed in the KB article for the monthly cumulative update. If you want to enable these features, there's a client policy that allows admins to enable features that are behind temporary enterprise control. For more information about this policy, see [Enable features that are behind temporary enterprise feature control](waas-configure-wufb.md#enable-features-that-are-behind-temporary-enterprise-feature-control).
|
||||
|
||||
## Annual feature updates
|
||||
|
||||
|
||||
@ -37,8 +37,8 @@ to opt out of automatic restarts until the deadline is reached (although we reco
|
||||
restarts for maximum update velocity).
|
||||
|
||||
We recommend you set deadlines as follows:
|
||||
- Quality update deadline, in days: 3
|
||||
- Feature update deadline, in days: 7
|
||||
- Quality update deadline, in days: 2
|
||||
- Feature update deadline, in days: 2
|
||||
|
||||
Notifications are automatically presented to the user at appropriate times, and users can choose to be reminded
|
||||
later, to reschedule, or to restart immediately, depending on how close the deadline is. We recommend that you
|
||||
@ -62,7 +62,7 @@ be forced to update immediately when the user returns.
|
||||
|
||||
We recommend you set the following:
|
||||
|
||||
- Grace period, in days: 2
|
||||
- Grace period, in days: 5
|
||||
|
||||
Once the deadline and grace period have passed, updates are applied automatically, and a restart occurs
|
||||
regardless of [active hours](#active-hours).
|
||||
|
||||
@ -8,7 +8,7 @@ ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 02/28/2023
|
||||
ms.date: 05/19/2023
|
||||
---
|
||||
|
||||
# Configure Windows Update for Business
|
||||
@ -210,14 +210,14 @@ Starting with Windows 10, version 1607, you can selectively opt out of receiving
|
||||
| GPO for Windows 10, version 1607 or later: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Do not include drivers with Windows Updates** | \Policies\Microsoft\Windows\WindowsUpdate\ExcludeWUDriversInQualityUpdate |
|
||||
| MDM for Windows 10, version 1607 and later: </br>../Vendor/MSFT/Policy/Config/Update/</br>**ExcludeWUDriversInQualityUpdate** | \Microsoft\PolicyManager\default\Update\ExcludeWUDriversInQualityUpdate |
|
||||
|
||||
## Enable features introduced via servicing that are off by default
|
||||
## Enable features that are behind temporary enterprise feature control
|
||||
<!--6544872-->
|
||||
|
||||
New features and enhancements are introduced through the monthly cumulative update to provide continuous innovation for Windows 11. To give organizations time to plan and prepare, some of these new features are temporarily turned off by default. Features that are turned off by default are listed in the KB article for the monthly cumulative update. Typically, a feature is selected to be off by default because it either impacts the user experience or IT administrators significantly.
|
||||
New features and enhancements are introduced through the monthly cumulative update to provide continuous innovation for Windows 11. To give organizations time to plan and prepare, some of these new features are temporarily turned off by default. Features that are turned off by default are listed in the KB article for the monthly cumulative update. Typically, a feature is selected to be off by default because it either impacts the user experience or IT administrators significantly.
|
||||
|
||||
The features that are turned off by default from servicing updates will be enabled in the next annual feature update. Organizations can choose to deploy feature updates at their own pace, to delay these features until they're ready for them.
|
||||
The features that are behind temporary enterprise feature control will be enabled in the next annual feature update. Organizations can choose to deploy feature updates at their own pace, to delay these features until they're ready for them. For a list of features that are turned off by default, see [Windows 11 features behind temporary enterprise control](/windows/whats-new/temporary-enterprise-feature-control).
|
||||
|
||||
**Policy settings to enable features introduced via servicing that are off by default**
|
||||
**Policy settings to enable features that are behind temporary enterprise control**
|
||||
|
||||
| Policy | Sets registry key under HKLM\Software |
|
||||
| --- | --- |
|
||||
|
||||
@ -22,11 +22,12 @@ ms.date: 12/31/2017
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
|
||||
Windows Update for Business is a free service that is available for all premium editions including Windows 10 and Windows 11 Pro, Enterprise, Pro for Workstation, and Education editions.
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
Windows Update for Business is a free service that is available for the following editions of Windows 10 and Windows 11:
|
||||
- Pro, including Pro for Workstations
|
||||
- Education
|
||||
- Enterprise, including Enterprise LTSC, IoT Enterprise, and IoT Enterprise LTSC
|
||||
|
||||
Windows Update for Business enables IT administrators to keep the Windows client devices in their organization always up to date with the latest security defenses and Windows features by directly connecting these systems to Windows Update service. You can use Group Policy or Mobile Device Management (MDM) solutions such as Microsoft Intune to configure the Windows Update for Business settings that control how and when devices are updated.
|
||||
|
||||
@ -49,7 +50,7 @@ Windows Update for Business enables an IT administrator to receive and manage a
|
||||
|
||||
Windows Update for Business provides management policies for several types of updates to Windows 10 devices:
|
||||
|
||||
- **Feature updates:** Previously referred to as "upgrades," feature updates contain not only security and quality revisions, but also significant feature additions and changes. Feature updates are released as soon as they become available.
|
||||
- **Feature updates:** Previously referred to as "upgrades," feature updates contain not only security and quality revisions, but also significant feature additions and changes. Feature updates are released as soon as they become available. Feature updates aren't available for LTSC devices.
|
||||
- **Quality updates:** Quality updates are traditional operating system updates, typically released on the second Tuesday of each month (though they can be released at any time). These include security, critical, and driver updates.
|
||||
- **Driver updates:** Updates for non-Microsoft drivers that are relevant to your devices. Driver updates are on by default, but you can use Windows Update for Business policies to turn them off if you prefer.
|
||||
- **Microsoft product updates**: Updates for other Microsoft products, such as versions of Office that are installed by using Windows Installer (MSI). Versions of Office that are installed by using Click-to-Run can't be updated by using Windows Update for Business. Product updates are off by default. You can turn them on by using Windows Update for Business policies.
|
||||
@ -73,7 +74,7 @@ The branch readiness level enables administrators to specify which channel of fe
|
||||
|
||||
#### Defer an update
|
||||
|
||||
A Windows Update for Business administrator can defer the installation of both feature and quality updates from deploying to devices within a bounded range of time from when those updates are first made available on the Windows Update service. You can use this deferral to allow time to validate deployments as they are pushed to devices. Deferrals work by allowing you to specify the number of days after an update is released before it is offered to a device. That is, if you set a feature update deferral period of 365 days, the device will not install a feature update that has been released for less than 365 days. To defer feature updates, use the **Select when Preview Builds and feature updates are Received** policy.
|
||||
A Windows Update for Business administrator can defer the installation of both feature and quality updates from deploying to devices within a bounded range of time from when those updates are first made available on the Windows Update service. You can use this deferral to allow time to validate deployments as they're pushed to devices. Deferrals work by allowing you to specify the number of days after an update is released before it's offered to a device. That is, if you set a feature update deferral period of 365 days, the device won't install a feature update that has been released for less than 365 days. To defer feature updates, use the **Select when Preview Builds and feature updates are Received** policy.
|
||||
|
||||
|
||||
|Category |Maximum deferral period |
|
||||
|
||||
@ -48,10 +48,10 @@ The General Availability Channel is the default servicing channel for all Window
|
||||
|
||||
To get started with the Windows Insider Program for Business, follows these steps:
|
||||
|
||||
1. On the [Windows Insider](https://insider.windows.com) website, go to **For Business > Getting Started** to [register your organizational Azure AD account](https://insider.windows.com/insidersigninaad/).
|
||||
2. **Register your domain**. Rather than have each user register individually for Insider Preview builds, administrators can [register their domain](https://insider.windows.com/for-business-organization-admin/) and control settings centrally.</br>**Note:** The signed-in user needs to be a **Global Administrator** of the Azure AD domain in order to be able to register the domain.
|
||||
1. On the [Windows Insider](https://www.microsoft.com/windowsinsider/for-business) website, select **Register** to register your organizational Azure AD account.
|
||||
2. Follow the prompts to register your tenant.</br>**Note:** The signed-in user needs to be a **Global Administrator** of the Azure AD domain in order to be able to register.
|
||||
3. Make sure the **Allow Telemetry** setting is set to **2** or higher.
|
||||
4. For Windows 10, version 1709 or later, set policies to manage preview builds and their delivery:
|
||||
4. For Windows devices, set policies to manage preview builds and their delivery:
|
||||
|
||||
The **Manage preview builds** setting gives administrators control over enabling or disabling preview build installation on a device. You can also decide to stop preview builds once the release is public.
|
||||
* Group Policy: **Computer Configuration/Administrative Templates/Windows Components/Windows Update/Windows Update for Business** - *Manage preview builds*
|
||||
|
||||
@ -8,13 +8,13 @@ ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 12/31/2017
|
||||
ms.date: 05/12/2023
|
||||
---
|
||||
# Enforcing compliance deadlines for updates
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
Deploying feature or quality updates for many organizations is only part of the equation for managing their device ecosystem. The ability to enforce update compliance is the next important part. Windows Update for Business provides controls to manage deadlines for when devices should migrate to newer versions.
|
||||
@ -36,10 +36,13 @@ With a current version, it's best to use the new policy introduced in June 2019
|
||||
|
||||
|Policy|Location|Quality update deadline in days|Feature update deadline in days|Grace period in days|
|
||||
|-|-|-|-|-|
|
||||
|(Windows 10, version 1709 and later) Specify deadlines for automatic updates and restarts | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadlines for automatic updates and restarts | 3 | 7 | 2 |
|
||||
|(Windows 10, version 1709 and later) Specify deadlines for automatic updates and restarts | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadlines for automatic updates and restarts | 2 | 2 | 5 |
|
||||
|
||||
When **Specify deadlines for automatic updates and restarts** is set (Windows 10, version 1709 and later):
|
||||
|
||||
For feature updates, the deadline and grace period start their countdown from the time of a pending restart after the installation is complete. As soon as installation is complete and the device reaches pending restart, the device will try to update outside of active hours. Once the *effective deadline* is reached, the device will try to restart during active hours. (The effective deadline is whichever is the later of the restart pending date plus the specified deadline or the restart pending date plus the grace period.)
|
||||
|
||||
For quality updates, the deadline countdown starts from the time the update is *offered* (not downloaded or installed). The grace period countdown starts from the time of the pending restart. The device will try to download and install the update at a time based on your other download and installation policies (the default is to automatically download and install in in the background). When the pending restart time is reached, the device will notify the user and try to update outside of active hours. Once the effective deadline is reached, the device will try to restart during active hours.
|
||||
|
||||
> [!NOTE]
|
||||
> When **Specify deadlines for automatic updates and restarts** is used, download, installation, and reboot settings stemming from the [Configure Automatic Updates](waas-restart.md#schedule-update-installation) are ignored.
|
||||
|
||||
@ -11,17 +11,19 @@ ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
# Delivery Optimization data in Windows Update for Business reports
|
||||
|
||||
<!--7715481-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
[Delivery Optimization](../do/waas-delivery-optimization.md) (DO) is a Windows feature that can be used to reduce bandwidth consumption by sharing the work of downloading updates among multiple devices in your environment. You can use DO with many other deployment methods, but it's a cloud-managed solution, and access to the DO cloud services is a requirement.
|
||||
[Delivery Optimization](../do/waas-delivery-optimization.md) (DO) is a Windows feature that can be used to reduce bandwidth consumption by sharing the work of downloading updates among multiple devices in your environment. You can use DO with many other deployment methods, but it's a cloud-managed solution, and access to the DO cloud services is a requirement.
|
||||
|
||||
Windows Update for Business reports provides Delivery Optimization information in the following places:
|
||||
|
||||
- The Windows Update for Business reports [workbook](wufb-reports-workbook.md)
|
||||
- [UCDOAggregatedStatus](wufb-reports-schema-ucdoaggregatedstatus.md)
|
||||
- [UCDOStatus](wufb-reports-schema-ucdostatus.md)
|
||||
|
||||
Windows Update for Business reports doesn't include Delivery Optimization data for Windows Insider devices.
|
||||
Windows Update for Business reports doesn't include Delivery Optimization data for Windows Insider devices.
|
||||
|
||||
## Delivery Optimization terms
|
||||
|
||||
@ -29,23 +31,24 @@ Windows Update for Business reports uses the following Delivery Optimization ter
|
||||
|
||||
- **Peer**: A device in the solution
|
||||
- **Peering 'ON'** - Devices where DO peer-to-peer is enabled in one of the following modes:
|
||||
- LAN (1)
|
||||
- Group (2)
|
||||
- Internet (3)
|
||||
- LAN (1)
|
||||
- Group (2)
|
||||
- Internet (3)
|
||||
|
||||
- **Peering 'OFF'**: Devices where DO peer-to-peer is disabled, set to one of the following modes:
|
||||
- HTTP Only (0)
|
||||
- Simple Mode (99)
|
||||
- Bypass (100), deprecated in Windows 11
|
||||
- HTTP Only (0)
|
||||
- Simple Mode (99)
|
||||
- Bypass (100), deprecated in Windows 11
|
||||
- **Bandwidth savings**: The percentage of bandwidth that was downloaded from alternate sources (Peers or Microsoft Connected Cache (MCC) out of the total amount of data downloaded.
|
||||
- If bandwidth savings are <= 60%, a *Warning* icon is displayed
|
||||
- When bandwidth savings are <10%, an *Error* icon is displayed.
|
||||
- If bandwidth savings are <= 60%, a *Warning* icon is displayed
|
||||
- When bandwidth savings are <10%, an *Error* icon is displayed.
|
||||
- **Configurations**: Based on the DownloadMode configuration set via MDM, Group Policy, or end-user via the user interface.
|
||||
- **P2P Device Count**: The device count is the number of devices configured to use peering.
|
||||
- **Microsoft Connected Cache (MCC)**: Microsoft Connected Cache is a software-only caching solution that delivers Microsoft content. For more information, see [Microsoft Connected Cache overview](../do/waas-microsoft-connected-cache.md).
|
||||
- **MCC Device Count**: The device count is the number of devices that have received bytes from the cache server, for supported content types.
|
||||
- **Total # of Devices**: The total number of devices with activity in last 28 days.
|
||||
- **LAN Bytes**: Bytes delivered from LAN peers.
|
||||
- **Group Bytes**: Bytes from Group peers. If a device is using Group DownloadMode, Delivery Optimization will first look for peers on the LAN and then in the Group. Therefore, if bytes are delivered from LAN peers, they'll be calculated in 'LAN Bytes'.
|
||||
- **Group Bytes**: Bytes from Group peers. If a device is using Group DownloadMode, Delivery Optimization first looks for peers on the LAN and then in the Group. Therefore, if bytes are delivered from LAN peers, they are calculated in 'LAN Bytes'.
|
||||
- **CDN Bytes**: Bytes delivered from Content Delivery Network (CDN).
|
||||
- **City**: City is determined based on the location of the device where the maximum amount of data is downloaded.
|
||||
- **Country**: Country is determined based on the location of the device where the maximum amount of data is downloaded.
|
||||
@ -53,16 +56,16 @@ Windows Update for Business reports uses the following Delivery Optimization ter
|
||||
|
||||
## Calculations for Delivery Optimization
|
||||
|
||||
There are several calculated values that appear on the Delivery Optimization report. Listed below each calculation is the table that's used for it:
|
||||
Each calculated values used in the Delivery Optimization report are listed below.
|
||||
|
||||
**Efficiency (%) Calculations**:
|
||||
|
||||
|
||||
- Bandwidth Savings (BW SAV%) = 100 * (BytesFromPeers + BytesFromGroupPeers + BytesFromCache) /
|
||||
(BytesFromPeers + BytesFromGroupPeers+BytesFromCDN + BytesFromCache)
|
||||
- [UCDOAggregatedStatus](wufb-reports-schema-ucdostatus.md) table
|
||||
- % P2P Efficiency = 100 * (BytesFromPeers + BytesFromGroupPeers) / (BytesFromPeers + BytesFromGroupPeers+BytesFromCDN+BytesFromCache)
|
||||
- [UCDOStatus](wufb-reports-schema-ucdostatus.md) table
|
||||
- % MCC Efficiency = 100 * BytesFromCache / (BytesFromPeers + BytesFromGroupPeers+BytesFromCDN+BytesFromCache)
|
||||
- % MCC Efficiency = 100 * BytesFromCache / (BytesFromPeers + BytesFromGroupPeers+BytesFromCDN+BytesFromCache)
|
||||
- [UCDOStatus](wufb-reports-schema-ucdostatus.md) table
|
||||
|
||||
**Bytes Calculations**:
|
||||
@ -92,7 +95,7 @@ There are several calculated values that appear on the Delivery Optimization rep
|
||||
In the **Efficiency By Group** subsection, the **GroupID** is displayed as an encoded SHA256 hash. You can create a mapping of original to encoded GroupIDs using the following PowerShell example:
|
||||
|
||||
```powershell
|
||||
$text = "<myEncodedGroupID>`0"; (the null-terminator (`0) must be included in the string hash)
|
||||
$text = "<myOriginalGroupID>" ;
|
||||
|
||||
$hashObj = [System.Security.Cryptography.HashAlgorithm]::Create('sha256') ; $dig = $hashObj.ComputeHash([System.Text.Encoding]::Unicode.GetBytes($text)) ; $digB64 = [System.Convert]::ToBase64String($dig) ; Write-Host "$text ==> $digB64"
|
||||
```
|
||||
@ -106,8 +109,8 @@ Get-DeliveryOptimizationLog -Flush | Set-Content C:\dosvc.log
|
||||
The below two lines are together in verbose logs:
|
||||
|
||||
```text
|
||||
2023-02-15T12:33:11.3811337Z 1514 1F4 {CGlobalConfigManager::GetGroupId} Using groupID = **<myEncodedGroupId>**
|
||||
2023-02-15T12:33:11.3811432Z 1514 1F4 {CGlobalConfigManager::GetGroupId} Hashed groupID = **<myDecodedGroupId>**
|
||||
2023-02-15T12:33:11.3811337Z 1514 1F4 {CGlobalConfigManager::GetGroupId} Using groupID = **<myOriginalGroupId>**
|
||||
2023-02-15T12:33:11.3811432Z 1514 1F4 {CGlobalConfigManager::GetGroupId} Hashed groupID = **<myEncodedGroupId>**
|
||||
```
|
||||
|
||||
## Sample queries
|
||||
@ -142,6 +145,19 @@ DeviceCount = count_distinct(GlobalDeviceId) by GroupID | top 10 by DeviceCount
|
||||
| project GroupID , P2PPercentage , MCCPercentage , VolumeBytesFromPeers , VolumeBytesFromMCC ,VolumeByCDN , DeviceCount
|
||||
```
|
||||
|
||||
### Delivery Optimization Supported Content Types
|
||||
|
||||
There are many Microsoft [content types](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) that are supported by Delivery Optimization. All of these content types show up in the 'Content Distribution' section in the Delivery Optimization report. See the [complete table](waas-delivery-optimization.md#windows-client) for P2P/MCC support types.
|
||||
|
||||
| Content Category | Content Types Included |
|
||||
| --- | --- |
|
||||
| Apps | Windows 10 Store apps, Windows 10 Store for Business apps, Windows 11 UWP Store apps |
|
||||
| Driver Updates | Windows Update [Driver updates](get-started-updates-channels-tools.md#types-of-updates) |
|
||||
| Feature Updates | Windows Update [Feature updates](get-started-updates-channels-tools.md#types-of-updates) |
|
||||
| Office | Microsoft 365 Apps and updates |
|
||||
| Other | Windows Language Packs, Windows Defender definition updates, Intune Win32 apps, Edge Browser updates, Configuration Manager Express updates, Dynamic updates, MDM Agent, Xbox Game Pass (PC), Windows Package Manager, MSIX Installer (includes Windows 11 Store Win32 apps, Windows 11 Teams updates) |
|
||||
| Quality Updates | Windows Updates [Quality updates](get-started-updates-channels-tools.md#types-of-updates)) |
|
||||
|
||||
## Frequency Asked Questions
|
||||
|
||||
- **What time period does the Delivery Optimization data include?**
|
||||
@ -157,13 +173,19 @@ The top groups are represented by the number of devices in a particular group, f
|
||||
The GroupID values are encoded for data protection telemetry requirements. You can find more information in the 'Mapping GroupIDs' section above.
|
||||
|
||||
- **How can I see data for device in the office vs. out of the office?**
|
||||
Today, we don't have a distinction for data that was downloaded by location.
|
||||
Today, we don't have a distinction for data that was downloaded by location.
|
||||
|
||||
- **What does the data in UCDOStatus table represent?**
|
||||
A row in UCDOStatus represents data downloaded by a combination of a single device ID (AzureADDeviceId) by content type (ContentType).
|
||||
A row in UCDOStatus represents data downloaded by a combination of a single device ID (AzureADDeviceId) by content type (ContentType).
|
||||
|
||||
- **What does the data in UCDOAggregatedStatus table represent?**
|
||||
A row in UCDOAggregatedStatus represents data summarized at the tenant level (AzureADTenantID) for each content type (ContentType).
|
||||
|
||||
- **How are BytesFromCache calculated when there's a Connected Cache server used by my ISP?**
|
||||
If there's a Connected Cache server at the ISP level, BytesFromCache will filter out any bytes coming the ISP's Connected Cache.
|
||||
If there's a Connected Cache server at the ISP level, BytesFromCache filters out any bytes coming the ISP's Connected Cache.
|
||||
|
||||
- **How do the results from the Delivery Optimization PowerShell cmdlets compare to the results in the report?**
|
||||
[Delivery Optimization PowerShell cmdlets](waas-delivery-optimization-setup.md#monitor-delivery-optimization) can be a powerful tool used to monitor Delivery Optimization data on the device. These cmdlets use the cache on the device. The data calculated in the report is taken from the Delivery Optimization telemetry events.
|
||||
|
||||
- **The report represents the last 28 days of data, why do some queries include >= seven days?**
|
||||
The data in the report does represent the last 28 days of data. The query for last seven days is just to get the data for the latest snapshot from past seven days. It's possible that data is delayed for sometime and not available for current day, so we look for past 7 day snapshot in log analytics and show the latest snapshot.
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 04/26/2023
|
||||
ms.date: 06/09/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -62,7 +62,12 @@ Device names don't appear in Windows Update for Business reports unless you indi
|
||||
- CSP: System/[AllowDeviceNameInDiagnosticData](/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata)
|
||||
- Group Policy: **Allow device name to be sent in Windows diagnostic data** under **Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds**
|
||||
|
||||
Microsoft is committed to providing you with effective controls over your data and ongoing transparency into our data handling practices. For more information about data handling and privacy for Windows diagnostic data, see [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization) and [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#services-that-rely-on-enhanced-diagnostic-data).
|
||||
|
||||
> [!TIP]
|
||||
> Windows Update for Business reports uses [services configuration](/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services#bkmk-svccfg), also called OneSettings. Disabling the services configuration can cause some of the client data to be incorrect or missing in reports. For more information, see the [DisableOneSettingsDownloads](/windows/client-management/mdm/policy-csp-system#disableonesettingsdownloads) policy settings.
|
||||
|
||||
|
||||
Microsoft is committed to providing you with effective controls over your data and ongoing transparency into our data handling practices. For more information about data handling and privacy for Windows diagnostic data, see [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization) and [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#services-that-rely-on-enhanced-diagnostic-data).
|
||||
|
||||
## Data transmission requirements
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.topic: reference
|
||||
ms.date: 04/24/2023
|
||||
ms.date: 06/05/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 04/26/2023
|
||||
ms.date: 06/12/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -79,10 +79,9 @@ Below the tiles, the **Quality updates** tab is subdivided into **Update status*
|
||||
|
||||
The **Update status** group for quality updates contains the following items:
|
||||
|
||||
- **Update states for all security releases**: Chart containing the number of devices in a specific state, such as installing, for security updates.
|
||||
- **Update states for all security releases**: The update states for the last 3 security updates are used to populate this chart. The total number of update states is approximately 3 times the number of devices that have reported update data to Windows Update for Business reports in the past 30 days.
|
||||
- **Update alerts for all security releases**: Chart containing the count of active errors and warnings for security updates.
|
||||
|
||||
:::image type="content" source="media/33771278-update-deployment-status-table.png" alt-text="Screenshot of the charts and table in the workbook's quality updates tab" lightbox="media/33771278-update-deployment-status-table.png":::
|
||||
|
||||
The **Update deployment status** table displays the quality updates for each operating system version that were released within the last 60 days. For each update, drill-in further by selecting a value from the following columns:
|
||||
|
||||
@ -120,7 +119,7 @@ The **Update status** group for feature updates contains the following items:
|
||||
- **Safeguard holds**: Chart containing count of devices per operating system version that are under a safeguard hold for a feature update
|
||||
- **Update alerts**: Chart containing the count of active errors and warnings for feature updates.
|
||||
|
||||
**Update deployment status** table for feature updates displays the installation status by targeted operating system version. For each operating system version targeted the following columns are available:
|
||||
**Update deployment status** table for feature updates displays the installation status by targeted operating system version. For each operating system version targeted, the following columns are available:
|
||||
|
||||
| Column name | Description | Drill-in description |
|
||||
|---|---|---|
|
||||
|
||||
@ -46,7 +46,7 @@ To help you better understand the scan source policy, see the default scan behav
|
||||
- If you configure only the WSUS server policy:
|
||||
|
||||
- On Windows 10: All of your updates will come from WSUS.
|
||||
- On Windows 11: All of your updates will still come from Windows Update unless you configure the specify scan source policy.
|
||||
- On Windows 11: All of your updates will still come from WSUS unless you configure the specify scan source policy.
|
||||
|
||||
- If you configure a WSUS server and deferral policies: All of your updates will come from Windows Update unless you specify the scan source policy.
|
||||
- If you configure a WSUS server and the scan source policy: All of your updates will come from the source chosen in the scan source policy.
|
||||
|
||||
Reference in New Issue
Block a user