mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-21 13:23:36 +00:00
Merge branch 'main' into patch-6
This commit is contained in:
Tiara Quan
GitHub
@ -28,8 +28,8 @@ ms.localizationpriority: medium
|
||||
| TotalBytesDownloaded | The number of bytes from any source downloaded so far |
|
||||
| PercentPeerCaching |The percentage of bytes downloaded from peers versus over HTTP |
|
||||
| BytesFromPeers | Total bytes downloaded from peer devices (sum of bytes downloaded from LAN, Group, and Internet Peers) |
|
||||
| BytesfromHTTP | Total number of bytes received over HTTP. This represents all HTTP sources, which includes BytesFromCacheServer |
|
||||
| Status | Current state of the operation. Possible values are: **Downloading** (download in progress); **Complete** (download completed, but is not uploading yet); **Caching** (download completed successfully and is ready to upload or uploading); **Paused** (download/upload paused by caller) |
|
||||
| BytesfromHTTP | Total number of bytes received over HTTP. This metric represents all HTTP sources, which includes BytesFromCacheServer |
|
||||
| Status | Current state of the operation. Possible values are: **Downloading** (download in progress); **Complete** (download completed, but isn't uploading yet); **Caching** (download completed successfully and is ready to upload or uploading); **Paused** (download/upload paused by caller) |
|
||||
| Priority | Priority of the download; values are **foreground** or **background** |
|
||||
| BytesFromCacheServer | Total number of bytes received from cache server (MCC) |
|
||||
| BytesFromLanPeers | Total number of bytes received from peers found on the LAN |
|
||||
@ -98,9 +98,19 @@ Using the `-Verbose` option returns additional information:
|
||||
- Bytes from CDN (the number of bytes received over HTTP)
|
||||
- Average number of peer connections per download
|
||||
|
||||
**Starting in Windows 10, version 2004**, `Get-DeliveryOptimizationStatus` has a new option `-PeerInfo` which returns a real-time list of the connected peers.
|
||||
**Starting in Windows 10, version 2004**, `Get-DeliveryOptimizationStatus` has a new option `-PeerInfo`, which returns a real-time list of potential peers per file, including which peers are successfully connected and the total bytes sent or received from each peer.
|
||||
|
||||
Starting in Windows 10, version 1803, `Get-DeliveryOptimizationPerfSnapThisMonth` returns data similar to that from `Get-DeliveryOptimizationPerfSnap` but limited to the current calendar month.
|
||||
| Key | Value |
|
||||
| --- | --- |
|
||||
| IP | Peer device IP address |
|
||||
| PeerType | The type of peer used (LAN/Group/Internet/LinkLocal), determined by the Delivery Optimization Service, except for the LinkLocal option, which uses the DNS-SD protocol. |
|
||||
| ConnectionEstablished | True/False to indicate if peer is connected |
|
||||
| BytesSent | Bytes sent to/from the peer on the current connection |
|
||||
| BytesReceived | Bytes received to/from the peer on the current connection |
|
||||
| UploadRateBytes | Average value of upload rates on the current connection, over the past 20 seconds |
|
||||
| DownloadRateBytes | Average value of download rates on the current connection, over the past 20 seconds |
|
||||
|
||||
Starting in Windows 10, version 1803, `Get-DeliveryOptimizationPerfSnapThisMonth` returns data similar to data from `Get-DeliveryOptimizationPerfSnap` but limited to the current calendar month.
|
||||
|
||||
#### Manage the Delivery Optimization cache
|
||||
|
||||
@ -110,7 +120,7 @@ Starting in Windows 10, version 1803, `Get-DeliveryOptimizationPerfSnapThisMonth
|
||||
|
||||
`set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID]` extends expiration for a single specific file in the cache.
|
||||
|
||||
You can now "pin" files to keep them persistent in the cache. You can only do this with files that are downloaded in modes 1, 2, or 3.
|
||||
You can now "pin" files to keep them persistent in the cache, only with files that are downloaded in modes 1, 2, or 3.
|
||||
|
||||
`set-DeliveryOptimizationStatus -Pin [True] -File ID [FileID]` keeps a specific file in the cache such that it won't be deleted until the expiration date and time (which you set with `set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID]`). The file is also excluded from the cache quota calculation.
|
||||
|
||||
@ -155,6 +165,6 @@ Using the `-ListConnections` option returns these details about peers:
|
||||
|
||||
`Get-DeliveryOptimizationLog [-Path <etl file path, supports wildcards>] [-Flush]`
|
||||
|
||||
If `Path` is not specified, this cmdlet reads all logs from the DoSvc log directory, which requires administrator permissions. If `Flush` is specified, the cmdlet stops DoSvc before reading logs.
|
||||
If `Path` isn't specified, this cmdlet reads all logs from the DoSvc log directory, which requires administrator permissions. If `Flush` is specified, the cmdlet stops DoSvc before reading logs.
|
||||
|
||||
Log entries are written to the PowerShell pipeline as objects. To dump logs to a text file, run `Get-DeliveryOptimizationLog | Set-Content <output file>` or something similar.
|
||||
|
||||
@ -152,7 +152,7 @@ Try these steps:
|
||||
4. If the number of peers is zero and **[DODownloadMode](waas-delivery-optimization-reference.md#download-mode)** is 1, ensure that both devices are using the same public IP address to reach the internet (you can easily do this by opening a browser window and do a search for “what is my IP”). In the case where devices aren't reporting the same public IP address, configure **[DODownloadMode](waas-delivery-optimization-reference.md#download-mode)** to 2 (Group) and use a custom **[DOGroupID (Guid)](waas-delivery-optimization-reference.md#group-id)**, to fix this.
|
||||
|
||||
> [!NOTE]
|
||||
> Starting in Windows 10, version 2004, `Get-DeliveryOptimizationStatus` has a new option `-PeerInfo` which returns a real-time list of the connected peers.
|
||||
> Starting in Windows 10, version 2004, `Get-DeliveryOptimizationStatus` has a new option `-PeerInfo` which returns a real-time list of potential peers per file, including which peers are successfully connected and the total bytes sent or received from each peer.
|
||||
|
||||
### Clients aren't able to connect to peers offered by the cloud service
|
||||
|
||||
|
||||
@ -5,25 +5,42 @@ manager: aaroncz
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 03/15/2023
|
||||
ms.date: 04/26/2023
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
<!--This file is shared by updates/wufb-reports-enable.md and the update/wufb-reports-admin-center.md articles. Headings may be driven by article context. -->
|
||||
Accessing Windows Update for Business reports typcially requires permissions from multiple sources including:
|
||||
|
||||
To enroll into Windows Update for Business reports, edit configuration settings, display and edit the workbook, and view the **Windows** tab in the **Software Updates** page from the [Microsoft 365 admin center](https://admin.microsoft.com) use one of the following roles:
|
||||
- [Azure Active Directory (Azure AD)](/azure/active-directory/roles/custom-overview) or [Intune](/mem/intune/fundamentals/role-based-access-control): Used for managing Windows Update for Business services through Microsoft Graph API, such as enrolling into reports
|
||||
- [Azure](/azure/role-based-access-control/overview): Used for controlling access to Azure resources through Azure Resource Management, such as access to the Log Analytics workspace
|
||||
- [Microsoft 365 admin center](/microsoft-365/admin/add-users/about-admin-roles): Manages access to the Microsoft 365 admin center, which allows only users with certain Azure AD roles access to sign in
|
||||
|
||||
- [Global Administrator role](/azure/active-directory/roles/permissions-reference#global-administrator)
|
||||
- [Intune Administrator](/azure/active-directory/roles/permissions-reference#intune-administrator)
|
||||
- [Windows Update deployment administrator](/azure/active-directory/roles/permissions-reference#windows-update-deployment-administrator)
|
||||
- This role allows enrollment through the [workbook](../wufb-reports-enable.md#bkmk_enroll-workbook) but doesn't allow any access to the Microsoft 365 admin center
|
||||
- [Policy and profile manager](/mem/intune/fundamentals/role-based-access-control#built-in-roles) Intune role
|
||||
- This role allows enrollment through the [workbook](../wufb-reports-enable.md#bkmk_enroll-workbook) but doesn't allow any access to the Microsoft 365 admin center
|
||||
**Roles that can enroll into Windows Update for Business reports**
|
||||
|
||||
To display the workbook and view the **Windows** tab in the **Software Updates** page [Microsoft 365 admin center](https://admin.microsoft.com) use the following role:
|
||||
- [Global Reader role](/azure/active-directory/roles/permissions-reference#global-reader)
|
||||
To [enroll](../wufb-reports-enable.md#bkmk_enroll) into Windows Update for Business reports from the [Azure portal](https://portal.azure.com) or the [Microsoft 365 admin center](https://admin.microsoft.com) requires one of the following roles:
|
||||
|
||||
**Log Analytics permissions**:
|
||||
- [Global Administrator](/azure/active-directory/roles/permissions-reference#global-administrator) Azure AD role
|
||||
- [Intune Administrator](/azure/active-directory/roles/permissions-reference#intune-administrator) Azure AD role
|
||||
- [Windows Update deployment administrator](/azure/active-directory/roles/permissions-reference#windows-update-deployment-administrator) Azure AD role
|
||||
- [Policy and profile manager](/mem/intune/fundamentals/role-based-access-control#built-in-roles) Microsoft Intune role
|
||||
- Microsoft Intune RBAC roles don't allow access to the Microsoft 365 admin center
|
||||
|
||||
**Azure roles that allow access to the Log Analytics workspace**
|
||||
|
||||
The data for Windows Update for Business reports is routed to a Log Analytics workspace for querying and analysis. To display or query any of Windows Update for Business reports data, users must have the following roles, or the equivalent permissions for the workspace:
|
||||
|
||||
The data for Windows Update for Business reports is routed to a Log Analytics workspace for querying and analysis. To display or query data, users must have one of the following roles, or the equivalent permissions:
|
||||
- [Log Analytics Contributor](/azure/role-based-access-control/built-in-roles#log-analytics-contributor) role can be used to edit and write queries
|
||||
- [Log Analytics Reader](/azure/role-based-access-control/built-in-roles#log-analytics-reader) role can be used to read data
|
||||
- [Log Analytics Contributor](/azure/role-based-access-control/built-in-roles#log-analytics-contributor) role can be used if creating a new workspace or write access is needed
|
||||
|
||||
Examples of commonly assigned roles for Windows Update for Business reports users:
|
||||
|
||||
| Roles | Enroll though the workbook | Enroll through Microsoft 365 admin center | Display the workbook | Microsoft 365 admin center access | Create Log Analytics workspace |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Intune Administrator + Log Analytics Contributor | Yes | Yes | Yes | Yes | Yes |
|
||||
| Windows Update deployment administrator + Log Analytics reader | Yes | Yes | Yes | Yes| No |
|
||||
| Policy and profile manager (Intune role)+ Log Analytics reader | Yes | No | Yes | No | No |
|
||||
| Log Analytics reader | No | No | Yes | No | No|
|
||||
| [Global reader](/azure/active-directory/roles/permissions-reference#global-reader) + Log Analytics reader | No | No | Yes | Yes | No |
|
||||
|
||||
> [!NOTE]
|
||||
> The Azure AD roles discussed in this article for the Microsoft 365 admin center access apply specifically to the **Windows** tab of the **Software Updates** page. For more information about the **Microsoft 365 Apps** tab, see [Microsoft 365 Apps updates in the admin center](/DeployOffice/updates/software-update-status).
|
||||
|
||||
@ -11,7 +11,7 @@ ms.collection:
|
||||
- highpri
|
||||
- tier2
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 03/09/2023
|
||||
ms.date: 04/25/2023
|
||||
---
|
||||
|
||||
# Manage additional Windows Update settings
|
||||
@ -35,6 +35,8 @@ You can use Group Policy settings or mobile device management (MDM) to configure
|
||||
| [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](#display-organization-name-in-windows-update-notifications) </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-->|
|
||||
| | [Allow Windows updates to install before initial user sign-in](#allow-windows-updates-to-install-before-initial-user-sign-in) (registry only)| Windows 11 version 22H2 with 2023-04 Cumulative Update Preview, or a later cumulative update <!--7679187-->|
|
||||
|
||||
|
||||
>[!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)**.
|
||||
@ -47,7 +49,7 @@ Admins have a lot of flexibility in configuring how their devices scan and recei
|
||||
|
||||
[Specify Intranet Microsoft update service location](#specify-intranet-microsoft-update-service-location) allows admins to point devices to an internal Microsoft update service location, while [Do not connect to any Windows Update Internet locations](#do-not-connect-to-any-windows-update-internet-locations) gives them the option to restrict devices to just that internal update service. [Automatic Updates Detection Frequency](#automatic-updates-detection-frequency) controls how frequently devices scan for updates.
|
||||
|
||||
You can make custom device groups that'll work with your internal Microsoft update service by using [Enable client-side targeting](#enable-client-side-targeting). You can also make sure your devices receive updates that were not signed by Microsoft from your internal Microsoft update service, through [Allow signed updates from an intranet Microsoft update service location](#allow-signed-updates-from-an-intranet-microsoft-update-service-location).
|
||||
You can make custom device groups that will work with your internal Microsoft update service by using [Enable client-side targeting](#enable-client-side-targeting). You can also make sure your devices receive updates that weren't signed by Microsoft from your internal Microsoft update service, through [Allow signed updates from an intranet Microsoft update service location](#allow-signed-updates-from-an-intranet-microsoft-update-service-location).
|
||||
|
||||
Finally, to make sure the updating experience is fully controlled by the admins, you can [Remove access to use all Windows Update features](#remove-access-to-use-all-windows-update-features) for users.
|
||||
|
||||
@ -61,10 +63,10 @@ This setting lets you specify a server on your network to function as an interna
|
||||
To use this setting in Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Windows Update\Specify Intranet Microsoft update service location**. You must set two server name values: the server from which the Automatic Updates client detects and downloads updates, and the server to which updated workstations upload statistics. You can set both values to be the same server. An optional server name value can be specified to configure Windows Update Agent to download updates from an alternate download server instead of the intranet update service.
|
||||
|
||||
If the setting is set to **Enabled**, the Automatic Updates client connects to the specified intranet Microsoft update service (or alternate download server), instead of Windows Update, to search for and download updates. Enabling this setting means that end users in your organization don't have to go through a firewall to get updates, and it gives you the opportunity to test updates after deploying them.
|
||||
If the setting is set to **Disabled** or **Not Configured**, and if Automatic Updates is not disabled by policy or user preference, the Automatic Updates client connects directly to the Windows Update site on the Internet.
|
||||
If the setting is set to **Disabled** or **Not Configured**, and if Automatic Updates isn't disabled by policy or user preference, the Automatic Updates client connects directly to the Windows Update site on the Internet.
|
||||
|
||||
The alternate download server configures the Windows Update Agent to download files from an alternative download server instead of the intranet update service.
|
||||
The option to download files with missing Urls allows content to be downloaded from the Alternate Download Server when there are no download Urls for files in the update metadata. This option should only be used when the intranet update service does not provide download Urls in the update metadata for files which are present on the alternate download server.
|
||||
The option to download files with missing Urls allows content to be downloaded from the Alternate Download Server when there are no download Urls for files in the update metadata. This option should only be used when the intranet update service doesn't provide download Urls in the update metadata for files that are present on the alternate download server.
|
||||
|
||||
>[!NOTE]
|
||||
>If the "Configure Automatic Updates" policy is disabled, then this policy has no effect.
|
||||
@ -109,7 +111,7 @@ Use **Computer Configuration\Administrative Templates\Windows Components\Windows
|
||||
Specifies the target group name or names that should be used to receive updates from an intranet Microsoft update service. This allows admins to configure device groups that will receive different updates from sources like WSUS or Configuration Manager.
|
||||
|
||||
This Group Policy setting can be found under **Computer Configuration\Administrative Templates\Windows Components\Windows update\Enable client-side targeting**.
|
||||
If the setting is set to **Enabled**, the specified target group information is sent to the intranet Microsoft update service which uses it to determine which updates should be deployed to this computer.
|
||||
If the setting is set to **Enabled**, the specified target group information is sent to the intranet Microsoft update service, which uses it to determine which updates should be deployed to this computer.
|
||||
If the setting is set to **Disabled** or **Not Configured**, no target group information will be sent to the intranet Microsoft update service.
|
||||
|
||||
If the intranet Microsoft update service supports multiple target groups, this policy can specify multiple group names separated by semicolons. Otherwise, a single group must be specified.
|
||||
@ -123,8 +125,8 @@ This policy setting allows you to manage whether Automatic Updates accepts updat
|
||||
|
||||
To configure this setting in Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Windows update\Allow signed updates from an intranet Microsoft update service location**.
|
||||
|
||||
If you enable this policy setting, Automatic Updates accepts updates received through an intranet Microsoft update service location, as specified by [Specify Intranet Microsoft update service location](#specify-intranet-microsoft-update-service-location), if they are signed by a certificate found in the "Trusted Publishers" certificate store of the local computer.
|
||||
If you disable or do not configure this policy setting, updates from an intranet Microsoft update service location must be signed by Microsoft.
|
||||
If you enable this policy setting, Automatic Updates accepts updates received through an intranet Microsoft update service location, as specified by [Specify Intranet Microsoft update service location](#specify-intranet-microsoft-update-service-location), if they're signed by a certificate found in the "Trusted Publishers" certificate store of the local computer.
|
||||
If you disable or don't configure this policy setting, updates from an intranet Microsoft update service location must be signed by Microsoft.
|
||||
|
||||
>[!NOTE]
|
||||
>Updates from a service other than an intranet Microsoft update service must always be signed by Microsoft and are not affected by this policy setting.
|
||||
@ -136,7 +138,7 @@ To configure this policy with MDM, use [AllowNonMicrosoftSignedUpdate](/windows/
|
||||
|
||||
To add more flexibility to the update process, settings are available to control update installation.
|
||||
|
||||
[Configure Automatic Updates](#configure-automatic-updates) offers four different options for automatic update installation, while [Do not include drivers with Windows Updates](#do-not-include-drivers-with-windows-updates) makes sure drivers are not installed with the rest of the received updates.
|
||||
[Configure Automatic Updates](#configure-automatic-updates) offers four different options for automatic update installation, while [Do not include drivers with Windows Updates](#do-not-include-drivers-with-windows-updates) makes sure drivers aren't installed with the rest of the received updates.
|
||||
|
||||
### Do not include drivers with Windows Updates
|
||||
|
||||
@ -144,7 +146,7 @@ Allows admins to exclude Windows Update drivers during updates.
|
||||
|
||||
To configure this setting in Group Policy, use **Computer Configuration\Administrative Templates\Windows Components\Windows update\Do not include drivers with Windows Updates**.
|
||||
Enable this policy to not include drivers with Windows quality updates.
|
||||
If you disable or do not configure this policy, Windows Update will include updates that have a Driver classification.
|
||||
If you disable or don't configure this policy, Windows Update will include updates that have a Driver classification.
|
||||
|
||||
### Configure Automatic Updates
|
||||
|
||||
@ -156,13 +158,13 @@ Under **Computer Configuration\Administrative Templates\Windows Components\Windo
|
||||
|
||||
**2 - Notify for download and auto install** - When Windows finds updates that apply to this device, users will be notified that updates are ready to be downloaded. After going to **Settings > Update & security > Windows Update**, users can download and install any available updates.
|
||||
|
||||
**3 - Auto download and notify for Install** - Windows finds updates that apply to the device and downloads them in the background (the user is not notified or interrupted during this process). When the downloads are complete, users will be notified that they are ready to install. After going to **Settings > Update & security > Windows Update**, users can install them.
|
||||
**3 - Auto download and notify for Install** - Windows finds updates that apply to the device and downloads them in the background (the user isn't notified or interrupted during this process). When the downloads are complete, users will be notified that they're ready to install. After going to **Settings > Update & security > Windows Update**, users can install them.
|
||||
|
||||
**4 - Auto download and schedule the install** - Specify the schedule using the options in the Group Policy Setting. For more information about this setting, see [Schedule update installation](waas-restart.md#schedule-update-installation).
|
||||
|
||||
**5 - Allow local admin to choose setting** - With this option, local administrators will be allowed to use the settings app to select a configuration option of their choice. Local administrators will not be allowed to disable the configuration for Automatic Updates. This option is not available in any Windows 10 or later versions.
|
||||
**5 - Allow local admin to choose setting** - With this option, local administrators will be allowed to use the settings app to select a configuration option of their choice. Local administrators won't be allowed to disable the configuration for Automatic Updates. This option isn't available in any Windows 10 or later versions.
|
||||
|
||||
**7 - Notify for install and notify for restart** (Windows Server 2016 and later only) - With this option, when Windows finds updates that apply to this device, they will be downloaded, then users will be notified that updates are ready to be installed. Once updates are installed, a notification will be displayed to users to restart the device.
|
||||
**7 - Notify for install and notify for restart** (Windows Server 2016 and later only) - With this option, when Windows finds updates that apply to this device, they'll be downloaded, then users will be notified that updates are ready to be installed. Once updates are installed, a notification will be displayed to users to restart the device.
|
||||
|
||||
If this setting is set to **Disabled**, any updates that are available on Windows Update must be downloaded and installed manually. To do this, users must go to **Settings > Update & security > Windows Update**.
|
||||
|
||||
@ -173,7 +175,7 @@ If this setting is set to **Not Configured**, an administrator can still configu
|
||||
> [!NOTE]
|
||||
> Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be resolved. Modify the registry at your own risk.
|
||||
|
||||
In an environment that does not have Active Directory deployed, you can edit registry settings to configure group policies for Automatic Update.
|
||||
In an environment that doesn't have Active Directory deployed, you can edit registry settings to configure group policies for Automatic Update.
|
||||
|
||||
To do this, follow these steps:
|
||||
|
||||
@ -203,7 +205,7 @@ To do this, follow these steps:
|
||||
|
||||
* **4**: Automatically download and scheduled installation.
|
||||
|
||||
* **5**: Allow local admin to select the configuration mode. This option is not available for Windows 10 or later versions.
|
||||
* **5**: Allow local admin to select the configuration mode. This option isn't available for Windows 10 or later versions.
|
||||
|
||||
* **7**: Notify for install and notify for restart. (Windows Server 2016 and later only)
|
||||
|
||||
@ -230,7 +232,7 @@ To do this, follow these steps:
|
||||
|
||||
* NoAutoRebootWithLoggedOnUsers (REG_DWORD):
|
||||
|
||||
**0** (false) or **1** (true). If set to **1**, Automatic Updates does not automatically restart a computer while users are logged on.
|
||||
**0** (false) or **1** (true). If set to **1**, Automatic Updates doesn't automatically restart a computer while users are logged on.
|
||||
|
||||
> [!NOTE]
|
||||
> This setting affects client behavior after the clients have updated to the SUS SP1 client version or later versions.
|
||||
@ -264,7 +266,7 @@ The organization name appears automatically for Windows 11 clients that are asso
|
||||
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
|
||||
- **DWORD value name**: UsoDisableAADJAttribution
|
||||
- **Value data:** 1
|
||||
|
||||
The following PowerShell script is provided as an example to you:
|
||||
@ -280,3 +282,17 @@ if (!(Test-Path $registryPath))
|
||||
|
||||
New-ItemProperty -Path $registryPath -Name $name -Value $value -PropertyType DWORD -Force | Out-Null
|
||||
```
|
||||
|
||||
## Allow Windows updates to install before initial user sign-in
|
||||
*(Starting in Windows 11, version 22H2 with 2023-04 Cumulative Update Preview, or a later cumulative update)* <!--7679187-->
|
||||
|
||||
On new devices, Windows Update doesn't begin installing background updates until a user has completed the Out of Box Experience (OOBE) and signs in for the first time. In many cases, the user signs in immediately after completing the OOBE. However, some VM-based solutions provision a device and automate the first user experience. These VMs may not be immediately assigned to a user so they won't see an initial sign-in until several days later.
|
||||
|
||||
In scenarios where initial sign-in is delayed, setting the following registry values allow devices to begin background update work before a user first signs in:
|
||||
|
||||
- **Registry key**: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Orchestrator
|
||||
- **DWORD value name**: ScanBeforeInitialLogonAllowed
|
||||
- **Value data**: 1
|
||||
|
||||
> [!Warning]
|
||||
> This value is designed to be used only for scenarios with a deferred initial user sign in. Setting this value on devices where initial user sign in isn't delayed could have a detrimental effect on performance since it may allow update work to occur as the user is signing in for the first time.
|
||||
|
||||
@ -7,7 +7,7 @@ author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
ms.date: 11/15/2022
|
||||
ms.date: 04/26/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -25,20 +25,14 @@ The **Software updates** page has following tabs to assist you in monitoring upd
|
||||
|
||||
:::image type="content" source="media/37063317-admin-center-software-updates.png" alt-text="Screenshot of the Microsoft 365 admin center displaying the software updates page with the Windows tab selected." lightbox="media/37063317-admin-center-software-updates.png":::
|
||||
|
||||
## Permissions
|
||||
|
||||
<!--Using include Microsoft 365 admin center permissions-->
|
||||
[!INCLUDE [Windows Update for Business reports permissions](./includes/wufb-reports-admin-center-permissions.md)]
|
||||
|
||||
> [!NOTE]
|
||||
> These permissions for the Microsoft 365 admin center apply specifically to the **Windows** tab of the **Software Updates** page. For more information about the **Microsoft 365 Apps** tab, see [Microsoft 365 Apps updates in the admin center](/DeployOffice/updates/software-update-status).
|
||||
|
||||
## Limitations
|
||||
|
||||
Windows Update for Business reports is a Windows service hosted in Azure that uses Windows diagnostic data. Windows Update for Business reports is available in the Azure Commercial cloud, but not available for GCC High or United States Department of Defense customers since it doesn't meet [US Government community compliance (GCC)](/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc#us-government-community-compliance) requirements. For a list of GCC offerings for Microsoft products and services, see the [Microsoft Trust Center](/compliance/regulatory/offering-home).
|
||||
|
||||
## Get started
|
||||
|
||||
After verifying that you've met the [prerequisites and permissions](wufb-reports-prerequisites.md) for Windows Update for Business reports, enroll using the instructions below if needed:
|
||||
|
||||
<!--Using include for onboarding Windows Update for Business reports through the Microsoft 365 admin center-->
|
||||
[!INCLUDE [Onboarding Windows Update for Business reports through the Microsoft 365 admin center](./includes/wufb-reports-onboard-admin-center.md)]
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 11/15/2022
|
||||
ms.date: 04/26/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 03/15/2023
|
||||
ms.date: 04/26/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -25,7 +25,6 @@ Before you begin the process of adding Windows Update for Business reports to yo
|
||||
- The Log Analytics workspace must be in a [supported region](#log-analytics-regions)
|
||||
- Data in the **Driver update** tab of the [workbook](wufb-reports-workbook.md) is only available for devices that receive driver and firmware updates from the [Windows Update for Business deployment service](deployment-service-overview.md)
|
||||
|
||||
|
||||
## Permissions
|
||||
|
||||
[!INCLUDE [Windows Update for Business reports permissions](./includes/wufb-reports-admin-center-permissions.md)]
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.topic: reference
|
||||
ms.date: 06/06/2022
|
||||
ms.date: 04/24/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -37,7 +37,7 @@ Update Event that combines the latest client-based data with the latest service-
|
||||
| **SourceSystem** | [string](/azure/kusto/query/scalar-data-types/string)| `Azure`| |
|
||||
| **TargetBuild** | [string](/azure/kusto/query/scalar-data-types/string) | `10.0.18363.836` | The full build of the content this DeviceUpdateEvent is tracking. For Windows 10 updates, this value would correspond to the full build (10.0.14393.385). |
|
||||
| **TargetBuildNumber** | [int](/azure/kusto/query/scalar-data-types/int) | `18363` | Integer of the Major portion of Build. |
|
||||
| **TargetKBNumber** | [int](/azure/kusto/query/scalar-data-types/int) | `4524570` | KB Article. |
|
||||
| **TargetKBNumber** | [string](/azure/kusto/query/scalar-data-types/string) | `KB4524570` | KB Article. |
|
||||
| **TargetRevisionNumber** | [int](/azure/kusto/query/scalar-data-types/int) | `836` | Integer or the minor (or revision) portion of the build. |
|
||||
| **TargetVersion** | [int](/azure/kusto/query/scalar-data-types/int) | `1909` | The target operating system version, such as 1909. |
|
||||
| **TimeGenerated** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | The time the snapshot generated this specific record. This is to determine to which batch snapshot this record belongs. |
|
||||
@ -50,3 +50,4 @@ Update Event that combines the latest client-based data with the latest service-
|
||||
| **UpdateManufacturer** | [string](/azure/kusto/query/scalar-data-types/string) | `Microsoft` | Manufacturer of update. Microsoft for feature or quality updates, for drivers the name of driver manufacturer. |
|
||||
| **UpdateReleaseTime** | [datetime](/azure/kusto/query/scalar-data-types/datetime) | `2020-05-14 09:26:03.478039` | The release date of the update |
|
||||
| **UpdateSource** | [string](/azure/kusto/query/scalar-data-types/string) | `UUP` | The source of the update such as UUP, MUv6, Media |
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 04/12/2023
|
||||
ms.date: 04/26/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -97,7 +97,6 @@ The **Update deployment status** table displays the quality updates for each ope
|
||||
The **Device status** group for quality updates contains the following items:
|
||||
|
||||
- **OS build number**: Chart containing a count of devices by OS build that are getting security updates.
|
||||
- **Target version**: Chart containing how many devices by operating system version that are getting security updates.
|
||||
- **Device alerts**: Chart containing the count of active device errors and warnings for quality updates.
|
||||
- **Device compliance status**: Table containing a list of devices getting security updates and update installation information including active alerts for the devices.
|
||||
- This table is limited to the first 250 rows. Select `...` to export the full list, or display the query in [Log Analytics](/azure/azure-monitor/logs/log-analytics-tutorial).
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Register your devices
|
||||
description: This article details how to register devices in Autopatch
|
||||
ms.date: 02/03/2023
|
||||
ms.date: 04/24/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -83,8 +83,8 @@ To be eligible for Windows Autopatch management, devices must meet a minimum set
|
||||
> [!NOTE]
|
||||
> Windows Autopatch doesn't support device emulators that don't generate the serial number, model and manufacturer information. Devices that use a non-supported device emulator fail the **Intune or Cloud-Attached** prerequisite check. Additionally, devices with duplicated serial numbers will fail to register with Windows Autopatch.
|
||||
|
||||
> [!NOTE]
|
||||
> Windows Autopatch supports registering [Windows 10 Long-Term Servicing Channel (LTSC)](/windows/whats-new/ltsc/) devices that are being currently serviced by the [Windows LTSC](/windows/release-health/release-information). The service only supports managing the [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) workload for devices currently serviced by the LTSC. Additionally, Windows Autopatch can only manage Windows quality updates for devices that haven't reached the LTSC's [end of servicing date](/windows/release-health/release-information#enterprise-and-iot-enterprise-ltsbltsc-editions).
|
||||
> [!IMPORTANT]
|
||||
> Windows Autopatch supports registering [Windows 10 Long-Term Servicing Channel (LTSC)](/windows/whats-new/ltsc/) devices that are being currently serviced by the [Windows LTSC](/windows/release-health/release-information). The service only supports managing the [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) workload for devices currently serviced by the LTSC. Windows Update for Business service and Windows Autopatch don't offer Windows feature updates for devices that are part of the LTSC. You must either use [LTSC media](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise) or the [Configuration Manager Operating System Deployment capabilities to perform an in-place upgrade](/windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager) for Windows devices that are part of the LTSC.
|
||||
|
||||
For more information, see [Windows Autopatch Prerequisites](../prepare/windows-autopatch-prerequisites.md).
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows quality updates
|
||||
description: This article explains how Windows quality updates are managed in Autopatch
|
||||
ms.date: 02/17/2023
|
||||
ms.date: 04/24/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -33,8 +33,8 @@ For a device to be eligible for Windows quality updates as a part of Windows Aut
|
||||
| Mobile device management (MDM) policy conflict | Devices must not have deployed any policies that would prevent device management. For more information, see [Conflicting and unsupported policies](../references/windows-autopatch-windows-update-unsupported-policies.md). |
|
||||
| Group policy conflict | Devices must not have group policies deployed which would prevent device management. For more information, see [Group policy](../references/windows-autopatch-windows-update-unsupported-policies.md#group-policy-and-other-policy-managers) |
|
||||
|
||||
> [!NOTE]
|
||||
> Windows Autopatch supports registering [Windows 10 Long-Term Servicing Channel (LTSC)](/windows/whats-new/ltsc/) devices that are being currently serviced by the [Windows LTSC](/windows/release-health/release-information). The service only supports managing the [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) workload for devices currently serviced by the LTSC. Additionally, Windows Autopatch can only manage Windows quality updates for devices that haven't reached the LTSC's [end of servicing date](/windows/release-health/release-information#enterprise-and-iot-enterprise-ltsbltsc-editions).
|
||||
> [!IMPORTANT]
|
||||
> Windows Autopatch supports registering [Windows 10 Long-Term Servicing Channel (LTSC)](/windows/whats-new/ltsc/) devices that are being currently serviced by the [Windows LTSC](/windows/release-health/release-information). The service only supports managing the [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) workload for devices currently serviced by the LTSC. Windows Update for Business service and Windows Autopatch don't offer Windows feature updates for devices that are part of the LTSC. You must either use [LTSC media](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise) or the [Configuration Manager Operating System Deployment capabilities to perform an in-place upgrade](/windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager) for Windows devices that are part of the LTSC.
|
||||
|
||||
## Windows quality update releases
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Prerequisites
|
||||
description: This article details the prerequisites needed for Windows Autopatch
|
||||
ms.date: 02/17/2023
|
||||
ms.date: 04/24/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -44,23 +44,26 @@ Windows Autopatch is included with Windows 10/11 Enterprise E3 or higher (user-b
|
||||
| [Windows 10/11 Enterprise E5](/azure/active-directory/enterprise-users/licensing-service-plan-reference) | WIN10_VDA_E5 | 488ba24a-39a9-4473-8ee5-19291e71b002 |
|
||||
| [Windows 10/11 Enterprise VDA](/windows/deployment/deploy-enterprise-licenses#virtual-desktop-access-vda) | E3_VDA_only | d13ef257-988a-46f3-8fce-f47484dd4550 |
|
||||
|
||||
The following Windows OS 10 editions, 1809+ builds and architecture are supported in Windows Autopatch:
|
||||
The following Windows 10 editions, build version and architecture are supported to be [registered](../deploy/windows-autopatch-register-devices.md) with Windows Autopatch:
|
||||
|
||||
- Windows 10 (1809+)/11 Pro
|
||||
- Windows 10 (1809+)/11 Enterprise
|
||||
- Windows 10 (1809+)/11 Pro for Workstations
|
||||
|
||||
> [!IMPORTANT]
|
||||
> While Windows Autopatch supports registering devices below the [minimum Windows OS version enforced by the service](../operate/windows-autopatch-windows-feature-update-overview.md#enforcing-a-minimum-windows-os-version), once registered, devices are automatically offered with the [minimum windows OS version](../operate/windows-autopatch-windows-feature-update-overview.md#enforcing-a-minimum-windows-os-version). The devices must be on a [minimum Windows OS currently serviced](/windows/release-health/release-information?msclkid=ee885719baa511ecb838e1a689da96d2) by the [Windows servicing channels](/windows/release-health/release-information?msclkid=ee885719baa511ecb838e1a689da96d2) to keep receiving monthly security updates that are critical to security and the health Windows.
|
||||
|
||||
> [!NOTE]
|
||||
> Windows Autopatch supports registering [Windows 10 Long-Term Servicing Channel (LTSC)](/windows/whats-new/ltsc/) devices that are being currently serviced by the [Windows LTSC](/windows/release-health/release-information). The service only supports managing the [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) workload for devices currently serviced by the LTSC. Additionally, Windows Autopatch can only manage Windows quality updates for devices that haven't reached the LTSC's [end of servicing date](/windows/release-health/release-information#enterprise-and-iot-enterprise-ltsbltsc-editions).
|
||||
> Windows Autopatch supports registering [Windows 10 Long-Term Servicing Channel (LTSC)](/windows/whats-new/ltsc/) devices that are being currently serviced by the [Windows LTSC](/windows/release-health/release-information). The service only supports managing the [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) workload for devices currently serviced by the LTSC. Windows Update for Business service and Windows Autopatch don't offer Windows feature updates for devices that are part of the LTSC. You must either use [LTSC media](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise) or the [Configuration Manager Operating System Deployment capabilities to perform an in-place upgrade](/windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager) for Windows devices that are part of the LTSC.
|
||||
|
||||
## Configuration Manager co-management requirements
|
||||
|
||||
Windows Autopatch fully supports co-management. The following co-management requirements apply:
|
||||
|
||||
- Use a currently supported [Configuration Manager version](/mem/configmgr/core/servers/manage/updates#supported-versions).
|
||||
- ConfigMgr must be [cloud-attached with Intune (co-management)](/mem/configmgr/cloud-attach/overview) and must have the following co-management workloads enabled:
|
||||
- Set the [Windows Update policies workload](/mem/configmgr/comanage/workloads#windows-update-policies) to Pilot Intune or Intune.
|
||||
- Set the [Device configuration workload](/mem/configmgr/comanage/workloads#device-configuration) to Pilot Intune or Intune.
|
||||
- Set the [Office Click-to-Run apps workload](/mem/configmgr/comanage/workloads#office-click-to-run-apps) to Pilot Intune or Intune.
|
||||
- Configuration Manager must be [cloud-attached with Intune (co-management)](/mem/configmgr/cloud-attach/overview) and must have the following co-management workloads enabled and set to either **Pilot Intune** or **Intune**:
|
||||
- [Windows Update policies workload](/mem/configmgr/comanage/workloads#windows-update-policies)
|
||||
- [Device configuration workload](/mem/configmgr/comanage/workloads#device-configuration)
|
||||
- [Office Click-to-Run apps workload](/mem/configmgr/comanage/workloads#office-click-to-run-apps)
|
||||
|
||||
For more information, see [paths to co-management](/mem/configmgr/comanage/quickstart-paths).
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2023
|
||||
description: This article lists the 2023 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 04/11/2023
|
||||
ms.date: 04/18/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: whats-new
|
||||
@ -24,6 +24,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
|
||||
| Message center post number | Description |
|
||||
| ----- | ----- |
|
||||
| [MC542842](https://admin.microsoft.com/adminportal/home#/MessageCenter) | April 2023 Windows Autopatch baseline configuration update |
|
||||
| [MC538728](https://admin.microsoft.com/adminportal/home#/MessageCenter) | Update: Windows Autopatch quality updates release communication |
|
||||
| [MC536881](https://admin.microsoft.com/adminportal/home#/MessageCenter) | Take action: Review Windows Autopatch Tenant management blade for potential action required to prevent inactive status |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user