Last modified by Sabrina V. on 2026/05/27 10:02
Show last authors
1 {{aagon.floatingbox/}}
2
3 Windows Update Management offers numerous configuration options. These begin with the initial setup in the [[First Steps Wizard>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]], where you can explicitly select or deselect products and classifications, for example, and continue to allow you to make changes for your own corporate identity so that you can customize logos or banners. This section provides an overview of the various areas where you can make changes:
4
5 * Configuring the dashboard in Windows Update Management
6 * Products
7 * Classifications
8 * Jobs and tasks
9 * Using the "Reset Windows Update Cache" system job
10 * Sync Profiles and distributed File Repositories
11 * CI adjustments from the restart dialogue
12 * Configuring Office 365 apps outside of ACMP
13 * Special features of the display fields in Windows Update Management
14
15 = Configuring the dashboard in Windows Update Management =
16
17 [[Dashboards >>doc:ACMP.69.Arbeiten mit der ACMP Console.Aufbau der Console.Arbeitsbereich.Dashboards.WebHome]]consist of various widgets that provide you with the most important information about a plugin. You can choose from a selection of different widgets for Windows Update Management and create a customised dashboard:
18
19 |(% style="width:304px" %)Client status|(% style="width:1388px" %)The widget displays the number of clients with specific statuses.
20 |(% style="width:304px" %)Hard disk usage|(% style="width:1388px" %)(((
21 Hard disk usage shows the amount of storage space used. A chart displays how the hard disk is deployed and how much storage space is required at most. This is divided into:
22
23 * //Downloaded//,
24 * //Downloaded but marked for removal//,
25 * //Still downloading//,
26 * //Not downloaded//.
27
28 (((
29 {{aagon.infobox}}
30 The information varies and depends on which products and classifications you have selected for download (see //[[Digression: What determines the storage space requirements in Windows Update Management?>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Wovon hängt der Speicherplatzbedarf im Windows Update Management ab?.WebHome]]//)
31 {{/aagon.infobox}}
32 )))
33 )))
34 |(% style="width:304px" %)Managed by WUM|(% style="width:1388px" %)(((
35 The widget displays the number of clients that are //managed by WUM// and //Not Managed by WUM// in diagram form
36 )))
37 |(% style="width:304px" %)Status of WUM jobs|(% style="width:1388px" %)(((
38 The widget displays the status of Windows Update Management jobs. You can also view the current progress of the job, as well as the start and finish dates and the result, from the widget. Learn more about the [[jobs and download types>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.WebHome||anchor="HDownload-TypenimWindowsUpdateManagement"]] stored here.
39 )))
40 |(% style="width:304px" %)Updates to the distribution ring|(% style="width:1388px" %)(((
41 Displays the number of updates in the specific distribution rings. The deployed updates are divided among the rings: //No distribution ring//, //Test Ring 1//, //Test Ring 2//, and //Released.//
42
43 (((
44 |(((
45 **Tip**: Define your own individual test and release process for distributing your updates. Read the excursus [[Update cycle: How does the update get from Microsoft to the ACMP client?>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Update Zyklus\: Wie kommt das Update von Microsoft auf den ACMP Client?.WebHome]] to find out what an exemplary distribution process might look like.
46 )))
47 )))
48 )))
49 |(% style="width:304px" %)Update status|(% style="width:1388px" %)The widget displays the number of updates with their respective statuses.
50 |(% style="width:304px" %)Welcome to ACMP Windows Update Management|(% style="width:1388px" %)Displays a welcome page with basic information about the plugin, as well as some websites with further info on the topic.
51
52 When you open Windows Update Management for the first time, the dashboard is already pre-filled and displays two queries and their results (//Released Updates in last 30 days// and //Clients with required Updates//). These queries are included and can be opened via //Client Management //> //Query Management //> //Windows Update Management //to change fields or filters, for example.
53
54 To insert another widget in its place, click on (% class="wikigeneratedid" %)[[image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome@1745319901761-864.png]]// Select Widget //in the upper right corner of the widget and insert another one. You can insert another query via [[image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome@1745319901763-287.png]]// Configure. //(%%)To insert a query into a clear space afterwards, you must click on //Queries// > //Query// in the widget selector. A field will open where you can now insert the desired query.
55
56 [[Example of a configured query in the Windows Update Management widget>>image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome@67_CAWUM_Widget konfigurieren_1105.png]]
57
58 {{aagon.infobox}}
59 If you would like to fundamentally change the design of the dashboard, you can read about the necessary steps in the chapter [[Customize layout>>doc:ACMP.69.Arbeiten mit der ACMP Console.Aufbau der Console.Arbeitsbereich.Dashboards.WebHome||anchor="HLayoutanpassen"]].
60 {{/aagon.infobox}}
61
62 = Products =
63
64 Microsoft and the continuing manufacturers listed in the third-party catalogues offer a wide range of different products that you can select for your Windows Update Management tasks. All products that you can configure and use are listed under their respective names. For example, if you want to add a specific Windows operating system as a product, you can enter it directly in the search field or select it from the list of items.
65
66 Select all products for which you want to provide updates. All items are provided based on the official names from Microsoft and other providers and are only available with descriptions in only the English language.
67
68 When selecting products, you should follow the principle of minimalism: **Only select products that are truly relevant to you!** If you select all entries, the ACMP Server will be overloaded and enormous performance problems may occur. It does not make sense to include third-party catalogues if you do not use any products from these providers. Read through the selection of products very carefully and check the entries against their exact names.
69
70 {{box}}
71 **Tip:** The product list and the respective names are provided by the vendors. ACMP obtains the entries and summarises them for you. Especially for Windows entries, it is often useful to check the [[Microsoft help page>>https://learn.microsoft.com/de-de/mem/configmgr/sum/get-started/configure-classifications-and-products]] to see whether the same cumulative updates are offered for the different versions.
72
73 So check the selected products to keep maintenance costs low, for example.
74
75 **Windows 10 example**: Let's say you want to provide clients with updates for the Microsoft operating system //Windows 10//. However, almost forty items are listed for this search term, as the Business, Anniversary and Creator versions are also included. So which one is the right one to choose?
76
77 * Select //Windows 10, version 1903 and later//, as this covers all newer updates. All updates older than version 1903 would run on //Windows 10//. You can select the Business, Anniversary and Creator versions, as the names are often very clear.
78
79 **Windows 11 example**: Windows 11 has a much smaller number of possible products to choose from. This is partly because the operating system has not been on the market as long as its predecessor (as of 12/24), but also because there are not that many products available yet. Here, you can use the edition names to check what is and isn't suitable for you (many companies do not use //Windows 11 Client S//, so these options are already excluded). Also pay attention to the versions that are displayed (22H2, 24H2, etc.). This allows you to exclude incorrect versions as well.
80 {{/box}}
81
82 {{aagon.infobox}}
83 The more products you combine and add to the classification, the more storage space you will need. Always take this into account when selecting products!
84 {{/aagon.infobox}}
85
86
87 = Classifications =
88
89 Classifications are required to define and synchronise the previously selected products according to the various classifications. This allows software updates to be assigned to and organised according to the respective types of updates. During the synchronisation process, all metadata for the selected software is synchronised for the specified classifications. Microsoft distinguishes between the following classifications:
90
91 |(% style="width:202px" %)**Classification**|(% style="width:1491px" %)**Description**
92 |(% style="width:202px" %)Critical Updates|(% style="width:1491px" %)A broadly released fix for a specific problem addressing a critical, non-security related bug.
93 |(% style="width:202px" %)Definition Updates|(% style="width:1491px" %)A broadly-released and frequent software update containing additions to a products definition database. Definition databases are often used to detect objects with specific attributes, such as malicious code, phinishing Web sites, or junk e-mail.
94 |(% style="width:202px" %)Drivers|(% style="width:1491px" %)A software component necessary to control or regulate another device.{{aagon.warnungsbox}}Please note that the “Drivers” option can lead to a significant drop in performance and a considerable increase in the size of the database, as this option stores all drivers offered by Microsoft as metadata.{{/aagon.warnungsbox}}
95 |(% style="width:202px" %)Feature Packs|(% style="width:1491px" %)New product functionality that is first distributed outside the context oft a product release, and ususally included in the next full product release.
96 |(% style="width:202px" %)Security Updates|(% style="width:1491px" %)A broadly released fix for a product-specific security-related vulnerability. Security vulnerabilities are rated based on their severity which is indicated in the Microsoft security bulletin as critical, important, moderate, or low.
97 |(% style="width:202px" %)Service Packs|(% style="width:1491px" %)A tested, cumulative set of all hotfixes, security updates, ciritical updates and updates, as well as additional fixes for problems found internally since the release oft he product. Service packs may also contain a limited number of customer-requested design changes or features.
98 |(% style="width:202px" %)Tools|(% style="width:1491px" %)A utility or feature that aids in accomplishing a task or set of tasks
99 |(% style="width:202px" %)Update Rollups|(% style="width:1491px" %)A tested, cumulative set of hotfixes, security updates, critical updates, and updates packaged together for easy deployment. A rollup generally targets a specific area, such as security, or a component of a product, such as Internet Information Services „IIS“.
100 |(% style="width:202px" %)Updates|(% style="width:1491px" %)A broadly released fix for a specific problem addressing a noncritical, non-security-related bug.
101 |(% style="width:202px" %)Upgrades|(% style="width:1491px" %)A new product release bringing a device to the next version, containing bug fixes, design changes and new features.
102
103
104 {{aagon.infobox}}
105 All listed classifications that include the name //Updates// (Critical, Definition, Security Updates, Update Rollups, and Updates themselves) overlap to some extent. It is recommended that you select all five items if you want to receive the complete selection of updates.
106 {{/aagon.infobox}}
107
108 {{aagon.infobox}}
109 The entries are provided by the manufacturers (Microsoft, Lenovo, etc.) and are not translated in the ACMP Console.
110 {{/aagon.infobox}}
111
112 {{box}}
113 **Tip:** If you consciously decide to include the drivers, the Metadata download may take longer, require a lot of storage space, and increase the size of the database accordingly. Base your decision on the hardware you are using and whether the option is really worthwhile. If you only use hardware (computers, notebooks) from other companies (e.g. Lenovo, Dell or HP), you can select and include them via the third-party catalogues.
114 {{/box}}
115
116 = Jobs and tasks =
117
118 Several server jobs and tasks are required for Windows Update Management to function smoothly. Among other things, the jobs are based on the server load, which is determined by configured intervals. You can assign both the Agent Tasks job and the server tasks a [[start condition>>doc:ACMP.69.ACMP-Solutions.Client-Management.Agentenplaner.WebHome||anchor="HStartbedingungen"]] that you can customize to your environment. The jobs and tasks are performed at intervals and sequentially one after the other. You can check the sequence in the [[monitors>>doc:ACMP.69.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome]] (including the job, client and server monitors)
119
120 Below is a brief list of the jobs and the tasks they perform for Windows Update Management:
121
122 **[[Agent Tasks>>doc:ACMP.69.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]] **(//Client Management// > //Agent Task//)
123
124 |(% style="width:431px" %)**Agent Task**|(% style="width:863px" %)**Description**|(% style="width:399px" %)**Condition**
125 |(% style="width:431px" %)Windows Updates Scanner|(% style="width:863px" %)The Windows Updates Scanner scans the clients to see whether they have reported an update as required/installed. The scanner is also executed when an [[Update Collection>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]] is triggered.|(% style="width:399px" %)Start every day
126
127 **[[Scheduled Server Tasks>>doc:ACMP.69.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HGeplanteServeraufgaben"]] **(//System// > //Settings //> //ACMP// //Server// > //Scheduled Server Tasks//)
128
129 |(% style="width:418px" %)**Serveraufgabe**|(% style="width:878px" %)**Description**|(% style="width:397px" %)**Condition**
130 |(% style="width:418px" %)Windows Update Management metadata download|(% style="width:878px" %)Downloads meta information about Windows Updates|(% style="width:397px" %)Start every day
131 |(% style="width:418px" %)Windows Update Management setup download|(% style="width:878px" %)Downloads setup files for Windows Updates|(% style="width:397px" %)Start every day
132 |(% style="width:418px" %)Windows Update Managed Clients recalc|(% style="width:878px" %)Recalculates dynamic links of Clients which are managed by ACMP Windows Update Management.|(% style="width:397px" %)Start every hour
133 |(% style="width:418px" %)Windows Update Management cleanup|(% style="width:878px" %)Frees disk space that is occupied by unneeded Windows Updates.|(% style="width:397px" %)Start every day
134 |(% style="width:418px" %)Windows Update log cleanup|(% style="width:878px" %)Cleanup logs, which are older than 30 days.|(% style="width:397px" %)Start every five hours
135
136 = Using the "Reset Windows Update Cache" system job =
137
138 You can use the “Reset Windows Update Cache” system job, which runs on the agent, via a job collection or a job push using the query. This job resets the Windows Update agent on the client. This stops the Windows Update services (Wuauserv, Bits, and Cryptsvc), clears the Software Distribution folder in the Windows directory, and then restarts the service. If you encounter problems with the Windows Update agent during runtime, you can use the system job to manually reset the agent.
139
140 {{aagon.infobox}}
141 If you have processes running in this area when executing the system job, they may be interrupted.
142 {{/aagon.infobox}}
143
144 {{box}}
145 Info: In the event of an error, you can display the result in the [[Job Monitor>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HJobMonitor"]].
146 {{/box}}
147
148 Add the system job as needed.
149
150 = Sync Profiles and distributed File Repositories =
151
152 Sync profiles allow you to specify within Windows Update Management which updates should be synchronized to which file repositories. Access the sync profiles from the //[[Updates>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Updates.WebHome||anchor="HWorkingwithupdates"]] //([[image:1779346293908-172.png||height="19" width="19"]]) tab. A new window will open, where you will find a default profile (“All Windows Updates”: This filter includes all updates you have already subscribed to). This sync profile contains Windows Updates and includes filters for all products (both current and future) that are automatically synchronized. This means that future updates for a specific product will also be included. This option allows you to automatically include all selected products without making manual changes.
153
154 {{box}}
155 If you have not assigned a sync profile to the deployed file repository, an error message will appear.
156 {{/box}}
157
158 == Add a sync profile ==
159
160 To add a new sync profile, click the button with the same name in the toolbar. A multi-page wizard will open. On the first page, insert a name for the sync profile under General, then click //Next >//.
161
162 You can now use the filter to link items to the sync profile. To do this, tick the "Use dynamic filter" checkbox so that you can use the following configurations. Now select the products, classifications, and languages to be included in the profile. For each, you can choose between the two options: “All Updates” or “Only Updates for Selected Products, Classifications, and/or Languages.” With the first option, all items are synchronized; with the second option, you must make the selection manually.
163
164 [[Set filters for the content in the sync profile>>image:610_Sync-Profil hinzufügen Filter_965.png||alt="610_Sync Profil hinzufügen Filter_966.png"]]
165
166 After making your selection, click //Next >// to continue.
167
168 If you want to create a static shortcut between the elements, you can configure this on this page. On the last page, you can now select the file repository to be used for the sync profile.
169
170 Exit your work and click //Done//. The newly created sync profile will now appear in the list. In the Sync Profile menu, you can now view the available profiles and see, for example, which filter has been set, which items have been linked, and what file repository has been specified.
171
172 If you wish to make changes to a profile at a later date, you can do so via [[image:Sync-Profil bearbeiten Icon.png||height="21" width="19"]]// Edit//. You can permanently delete the profile using the [[image:Sync-Profil löschen Icon.png||height="22" width="20"]] //Delete //button.
173
174 = Windows Update Management CI customize (Restart dialog) =
175
176 Similar to other areas in ACMP, as an administrator, you can also customize the Windows Update Management restart dialogue to match your corporate identity. Both the logo and the banner for the dialogue can be replaced.
177
178 [[Restart dialog>>image:67_CAWUM Neustart Dialog_593.png]]
179
180 To make these changes, first navigate to the installation directory //ACMPClient// (e.g. C:\Program Files (x86)\ACMPClient). Now copy the graphics for the logo and, optional, for the banner into the directory. Please note the following information about the graphics:
181
182 |**File name**|**Dimensions**|**Original graphic**|**Description**
183 |RebootOptionDialogLogo.png|128x128|[[image:1733739229758-177.png||data-xwiki-image-style-alignment="center" height="70" width="70"]]|This allows you to change the logo and, for example, integrate your own company logo. The advantage of this logo is that it immediately shows that new Windows Updates are being installed.
184 |RebootOptionDialogBanner.png|128x49|[[image:1733739229759-896.png||data-xwiki-image-style-alignment="center" height="34" width="89"]]|The standard banner says ACMP. You can enter your own company name here, for example.
185
186 {{aagon.infobox}}
187 The standard graphics are not stored in this directory. If you wish to restore the factory settings, delete the graphics you have added.
188 {{/aagon.infobox}}
189
190 = Configuring the Office 365 apps installation outside of ACMP =
191
192 As a prerequisite for distributing updates via Windows Update Management for Office 365, the apps must already have been installed in advance. This is a basic requirement for the administrator so that configuration outside of ACMP is also possible.
193
194 Using the Microsoft //Office Customisation Tool//, you can configure the desired configuration for download and installation of Office 365. To do this, you first specify the deployment settings (e.g. import or export) and define which products, versions and apps are to be deployed. You are guided through the application step by step and can specify individual settings there. The download and installation are then carried out using the tool.
195
196 {{box}}
197 **Tip:** You can find more information about the [[deployment tool>>https://learn.microsoft.com/de-de/microsoft-365-apps/deploy/overview-office-deployment-tool]] and the [[configuration options>>https://learn.microsoft.com/de-de/microsoft-365-apps/deploy/office-deployment-tool-configuration-options]] on the official Microsoft help page.
198 {{/box}}
199
200 Optionally you can install the ACMP Client Command "[[Microsoft Office 365 und 2019>>https://www.aagon.com/service-support/downloads/client-commands/]]", which also uses the Office deployment tools.
201
202 As a rule, in the first step at Microsoft the configuration of so-called update channels is also carried out. Microsoft regularly publishes new and/or updated features for Office apps via the channel. The administrator can decide for themselves which type of update channel and which update cycle to choose. Windows Update Management obtains the necessary updates via this channel.
203
204 {{aagon.infobox}}
205 The update channel// Current Channel// can affect the size of files due to frequent updates. This may mean that the file repositories require significantly more storage space, and you may need to expand the capacity.
206 {{/aagon.infobox}}
207
208 = Special features of the display fields in Windows Update Management =
209
210 === **Display Field: Windows Update Management > Updates > Uninstallation possible** ===
211
212 Using the "Uninstallation possible" display field, you can check within a query (//Query Management //> //Create Query //> Query base "Windows Update Management") whether uninstallation is possible for the available updates.
213
214 {{aagon.infobox}}
215 Please note that the data for this display field comes from Microsoft. This means that you may be able to uninstall some Updates that cannot officially be uninstalled.
216 {{/aagon.infobox}}
217
218 === **Display Field: Summary of display fields relating to installation and uninstallation behavior (Windows Update Management)** ===
219
220 One of the properties of Windows Updates is that they describe potential restart behavior. This allows the user to see, for example, whether an uninstallation or installation requires user input or a network connection. This information can be viewed in the [[details view of a selected update>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Updates.WebHome||anchor="H3.DetailedviewofaselectedUpdate"]] in Windows Update Management. You can use the fields below to create a specific query to retrieve the info. The following display fields are available for this purpose:
221
222 Installation:
223
224 * Installation impact
225 * Installation restart behavior
226 * Installation may require user input
227 * Installation requires a network connection
228
229 Uninstallation:
230
231 * Uninstallation impact
232 * Uninstallation restart behavior
233 * Uninstallation may require user input
234 * Uninstallation requires a network connection
235
236 === **Display Field: Update Files** ===
237
238 An update usually contains several files, and there are four display fields for the most important properties of these files, which you can use to view the information. These include the file name, the file size, the “Downloaded” field, and the “Last Download HTTP Status Code”.
239
240 {{box}}
241 **Info**: As soon as you download an update, the result is recorded and displayed in the "Last download HTTP status code" field. If, for example, an error message appears here, you can view it directly in this field.
242 {{/box}}
243
244 === **Display Field: Total File Size** ===
245
246 The Display Field shows the total file size of an update.
247
248 {{box}}
249 **Info**: Please note the following regarding the “Total file size” property:
250 - When calculating the size of an update, all files associated with that update are included.
251 - As a single file may be associated with multiple updates, the total file size for all updates may be greater than the actual storage space used in the file repository.
252 {{/box}}
253
254
© Aagon GmbH 2026
Besuchen Sie unsere Aagon Community