Last modified by Sabrina V. on 2026/07/22 11:16
Show last authors
1 = Initial situation =
2
3 As soon as a client is listed as “Managed by WUM” in Windows Update Management, ACMP automatically sets the required registry items on the respective system. In doing so, existing items that were previously set are generally overwritten, so that they no longer affect the update process. If problems do occur, however, it is recommended that you manually check the relevant registry items.
4
5 = Procedure =
6
7 == Open Registry Paths ==
8
9 1. First, make sure that the affected Clients are listed under the “Managed by WUM” tab and are actually managed via ACMP.
10 1. Next, open the Registry Editor by pressing the Win key + R and entering //regedit//.
11 1. Navigate to the relevant registry paths to check the set values. As soon as a client is managed via CAWUM, the corresponding registry keys should be present automatically.
12
13
14
15 [[View of the opend Registry Editor>>image:67_CAWUM_Use Case Registrykeys_785.png]]
16
17 == List of Registry Entries ==
18
19 |=Registrykey|=Description
20 |(% colspan="2" %)(((
21 {{{[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]}}}
22 )))
23 |"WUServer"="[[https:~~/~~/127.0.0.1:8530>>url:http://127.0.0.1:8530/]]"|Defines the Windows Update server from which the client obtains updates. For CAWUM, this value refers to the local ACMP update service.
24 |"WUStatusServer"="[[https:~~/~~/127.0.0.1:8530>>url:http://127.0.0.1:8530/]]"|Specifies the server to which the client sends status and acknowledgment data regarding installed updates. This is also the local CAWUM service.
25 |"UpdateServiceUrlAlternate"="[[https:~~/~~/127.0.0.1:8530>>url:http://127.0.0.1:8530/]]|Alternative Update Service URL. Ensures that Windows Update uses only the CAWUM service.
26 |"DisableDualScan"=dword:00000001|Disables Dual Scan. Prevents Windows from finding Windows Updates simultaneously through Microsoft Update and an internal Update Server.
27
28 |(% colspan="2" %)(((
29 {{{[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]}}}
30 )))
31 |(% style="width:461px" %)"NoAutoUpdate"=dword:00000001|(% style="width:1231px" %)Disables Windows' automatic search for updates and Update installation.
32 |(% style="width:461px" %)"NoAUShutdownOption"=dword:00000001|(% style="width:1231px" %)Removes the “Install Updates and shut down” option from the Windows shutdown menu.
33 |(% style="width:461px" %)"AUOptions"=dword:00000002|(% style="width:1231px" %)Sets the update behavior. A value of 2 means: Updates are reported but not automatically installed.
34 |(% style="width:461px" %)"UseWUServer"=dword:00000001|(% style="width:1231px" %)(((
35 Forces the use of the Update Server (CAWUM) defined under //WUServer// instead of Microsoft Update.
36 )))
37 |(% style="width:461px" %)"NoAutoRebootWithLoggedOnUsers"=dword:00000001|(% style="width:1231px" %)Prevents automatic restarts after Updates as long as a user is logged in to the system.
38
39 |(% colspan="2" %)(((
40 {{{HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Common\OfficeUpdate}}}
41 )))
42 |OfficeMgmtCOM=1|(((
43 Transfers Office update management to a central management tool—in this case, ACMP.
44
45 {{aagon.infobox}}
46 This key excludes Office updates and includes Windows Updates! The key applies to Microsoft 365 apps and/or Office 2019/2021 (Click-to-Run).
47 {{/aagon.infobox}}
48 )))
49
50 {{box}}
51 **Note on the Fullness of Registry Entries**
52 The registry entries listed in the table represent the key registry keys used by ACMP / CAWUM for Windows Update Management and Office Update Management.
53 This is not a full list of all registry keys set or affected by ACMP.
54 In addition, there are numerous other custom Windows registry keys that are not actively managed by ACMP and are therefore not included in this table.
55 {{/box}}
56
57 = Customize Active GPO Settings =
58
59 If there are still active GPOs that affect the registry values mentioned above or set different settings in the path
60
61 {{{HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate}}}
62
63 these GPOs must be disabled or customized.
64
65 Here is a simple method to determine this:
66
67 ~1. First, exit the ACMP Client service.
68
69 2. Next, delete the following registry key:
70
71 {{{HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate}}}
72
73 3. Then, in an elevated Command Prompt, execute the command
74
75 gpupdate /force.
76
77 4. Next, check whether the registry key
78
79 {{{HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate}}}
80
81 has been created again.
82
83 * If the key is created again, the configuration originates from one or more active GPOs. In this case, please identify the relevant GPOs and disable or correct them.
84 * If the key is not recreated, there is no GPO influence. In this case, restart the ACMP Client service.
85
86 5. Next, delete the local Windows Update cache and execute a Windows Update scan again via ACMP.
87
88 6. Finally, restart the ACMP Client service to fully enable update management.
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community