mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-20 09:17:25 +00:00
Update windows/deployment/update/update-compliance-configuration-manual.md
Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com>
This commit is contained in:
parent
97488f66e1
commit
c317ea46dd
@ -18,7 +18,7 @@ ms.topic: article
|
||||
# Manually Configuring Devices for Update Compliance
|
||||
|
||||
> [!NOTE]
|
||||
> As of May 10, 2021, new policy is required to use Update Compliance, referred to as Allow Update Compliance Processing. See more details below.
|
||||
> As of May 10, 2021, a new policy is required to use Update Compliance, referred to as Allow Update Compliance Processing. See more details below.
|
||||
|
||||
There are a number of requirements to consider when manually configuring devices for Update Compliance. These can potentially change with newer versions of Windows 10. The [Update Compliance Configuration Script](update-compliance-configuration-script.md) will be updated when any configuration requirements change so only a redeployment of the script will be required.
|
||||
|
||||
@ -94,4 +94,4 @@ A full Census sync adds a new registry value to Census's path. When this registr
|
||||
|
||||
1. For every device you are manually configuring for Update Compliance, add or modify the registry key located at **HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Census** to include a new **DWORD value** named **FullSync** and set to **1**.
|
||||
2. Run Devicecensus.exe with administrator privileges on every device. Devicecensus.exe is in the System32 folder. No additional run parameters are required.
|
||||
3. After Devicecensus.exe has run, the **FullSync** registry value can be removed or set to **0**.
|
||||
3. After Devicecensus.exe has run, the **FullSync** registry value can be removed or set to **0**.
|
||||
|
Loading…
x
Reference in New Issue
Block a user