mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge branch 'main' into andredm042420232
This commit is contained in:
commit
46e1b0cac3
@ -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.
|
||||
|
Loading…
x
Reference in New Issue
Block a user