deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-28 21:27:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Change wording as suggested

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
This commit is contained in:
Gerardo Camacho 2023-03-09 10:36:55 -08:00 committed by GitHub
parent 8011fb6e7e
commit e9047ec25f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/deployment/update/waas-wu-settings.md
View File

@ -287,15 +287,15 @@ New-ItemProperty -Path $registryPath -Name $name -Value $value -PropertyType DWO
## <a name="allow-windows-update-before-initial-logon"> </a> Allow Windows Updates to install before initial user logon ## <a name="allow-windows-update-before-initial-logon"> </a> Allow Windows Updates to install before initial user logon
This value is supported on devices running Windows 11, version 22H2 or newer. This value is supported on devices running Windows 11, version 22H2, or later.
On new devices Windows Update does not begin to install background updates until a user has completed the Out of Box Experience and logs on for the first time. The initial logon typically happens immediately after completing that first user experience. Some VM-based solutions provision a device and automate the first user experience but are not immediately assigned to a user and don't see an initial logon until several days later. On new devices, Windows Update does not begin to install background updates until a user has completed the Out of Box Experience and signs in for the first time. The user typically signs in initially immediately after completing that first user experience. Some VM-based solutions provision a device and automate the first user experience but are not immediately assigned to a user and don't see a user initially signing in until several days later.
In those scenarios, setting the following registry value allows those devices to begin background update work before a first user logon: In those scenarios, setting the following registry values allows those devices to begin background update work before a user first signs in:
- **Registry key**: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Orchestrator - **Registry key**: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Orchestrator
- **DWORD value name**: ScanBeforeInitialLogonAllowed - **DWORD value name**: ScanBeforeInitialLogonAllowed
- **Value data**: 1 - **Value data**: 1
> [!CAUTION] > [!CAUTION]
> This value is designed to be used only for scenarios with a deferred initial user logon. Setting this value on normal consumer retail devices could have a detrimental effect on performance as it may allow update work to occur as the user is logging in for the first time. > This value is designed to be used only for scenarios where the initial signing-in of a user is deferred. Setting this value on normal consumer retail devices could have a detrimental effect on performance as it may allow update work to occur as the user signs in for the first time.