Last modified by Sabrina V. on 2025/09/29 09:28
Show last authors
1 {{aagon.priorisierung}}
2 10
3 {{/aagon.priorisierung}}
4
5 {{aagon.floatingbox/}}
6
7
8 The //Updates// section displays all available updates that match your previously set settings (selected products, classifications and languages). This requires that the metadata download has been completed successfully (see [[Download Types in Windows Update Management>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.WebHome||anchor="HDownloadtypesinWindowsUpdateManagement"]]). The updates are listed according to the sorting of the grid. If individual updates are to be excluded from the distribution process (e.g. because they are no longer relevant to you), they can be explicitly rejected (//Declined Updates//).
9
10
11 = Working with updates =
12
13 The available updates are listed in a grid. As a rule, only updates that are current or may expire are displayed here (see [[expiry status>>doc:||anchor="H1.Expirystatusandupdatetype"]]).
14
15 {{box}}
16 **Tip**: Read the chapter //[[Structure of a grid in ACMP>>doc:ACMP.68.Arbeiten mit der ACMP Console.Aufbau der Console.Arbeitsbereich.Aufbau eines Grids in ACMP.WebHome]]// to find out what individueal editing options (filtering, sorting or grouping results) are available to you. The chapter //[[Grid optimisations in Windows Update Management>>doc:.Grid-Optimierungen im Windows Update Management.WebHome]]// contains further tips on how to group columns.
17 {{/box}}
18
19 The ribbon bar can be used to assign [[image:1747373593711-339.png]][[sync profiles>>doc:ACMP.68.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HSync-Profile"]] and [[image:1747373608196-936.png]] [[accept EULAs>>doc:||anchor="HAcceptEULA"]] if this is a prerequistite for update distribution. If an update is already in a distribution ring ([[image:1747373614472-578.png]]), this can be changed and adjusted manually. In addition, you can navigate directly from the updates to the [[image:1747373620038-623.png]] [[settings>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Upodate Management.WebHome]] and make changes (e.g. deselect or select products or classifications). The [[image:1747373625736-313.png]][[MS Catalog>>doc:||anchor="HObtainupdatesfromtheMSCatalog"]] takes you to the official Microsoft Update catalogue, where you can search for individual updates and select them for import.
20
21 {{box}}
22 **Tip**: The Microsoft Update Catalog is particularly useful for updates that are only available through the catalog.
23 {{/box}}
24
25 To give you a better understanding of the updates in Windows Update Management, the individual areas are broken down below and explained in more detail. These are as follows:
26
27 * 1. Process status and update type
28 * 2. Properties of the updates
29 * 3. Detailed view of a selected update
30
31 [[Structuring the areas of the updates>>image:67_CAWUM_Updates bearbeitete Übersicht_1676.png]]
32
33 == 1. Expiry status and update type ==
34
35 As soon as metadata is updated, new updates may be added, existing ones replaced, or updates already published by Microsoft withdrawn and thus disappear from the list. These dynamic updates are collected using the expiry status and listed under Updates. The release cycle also affects the status (e.g. an update may still have the status "May expire" at the beginning of the release process and have expired at the end of the process).
36
37
38 [[Expiry status and update type>>image:67_CAWUM_Ablaufstatus_777.png]]
39
40 The expiry status indicates what type of updates are displayed to you, regardless of the classification selected. This only refers to the relationship between the updates themselves or whether they have been withdrawn from distribution by Microsoft.
41
42 For a better overview, only //Current //and //May expire //are selected by default when ACMP is installed.
43
44 |(% style="width:145px" %)**Expiry status**|(% style="width:1547px" %)**Description**
45 |(% style="width:145px" %)Up-to-date|(% style="width:1547px" %)(((
46 Lists all current updates that have been released by Microsoft for the product and classification. There is currently no update that replaces this.
47 )))
48 |(% style="width:145px" %)Can expire|(% style="width:1547px" %)(((
49 Updates that may expire are listed in this status. There is at least one update that is newer. However, this update is not further along in the [[Release process>>doc:||anchor="HChangethereleaseprocessforupdates"]] than the one currently selected. In the //Replacement //tab, there should be at least one update on the right-hand side under //Replaced by the following updates//.
50 )))
51 |(% style="width:145px" %)Is expired|(% style="width:1547px" %)(((
52 Expired updates are updates for which a newer version is available. A newer version has already been released for the update AND the newer update is in the same or higher [[Release Ring>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Update Zyklus\: Wie kommt das Update von Microsoft auf den ACMP Client?.WebHome]] as the selected one.
53 \\__Example__: Microsoft releases new feature updates twice a year. These differ in the version number (Version 23H2, 24H2, etc.), which indicates how current the version is. If an update has expired, it is listed in the Replacement tab. The current Windows versions can be viewed on the official Microsoft website ([[Windows 10>>https://learn.microsoft.com/de-de/windows/release-health/release-information]] and [[Windows 11>>https://learn.microsoft.com/de-de/windows/release-health/windows11-release-information]]).
54 )))
55 |(% style="width:145px" %)Revoked|(% style="width:1547px" %)Updates may be withdrawn if they cause increased problems. In this case, Microsoft will withdraw the updates until a solution has been found and a replacement update is available. Withdrawn updates will then no longer be distributed or installed in this way. It is also not recommended that withdrawn updates be downloaded manually from the MS catalog and added to the network.
56
57 In addition to the status, you can also filter by update type. To do this, tick the checkboxes if you want to display updates for //software //and/or //drivers//. Drivers are only automatically selected if you have ticked them in the [[First Steps Wizard>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]] or subsequently in the [[settings>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Upodate Management.WebHome]] under the classifications
58
59 If you want to add or deselect another status or type, tick the checkbox and then refresh the view. Your changes will be taken into account in the system and displayed accordingly.
60
61
62 == 2. Properties of the updates ==
63
64 The grid contains a wealth of relevant information that you need to know about an update. The table shows whether an update is critical, its Knowledge ID, which product it belongs to, and when it was released.
65
66 {{box}}
67 **Tip: **Read more [[here>>doc:.Grid-Optimierungen im Windows Update Management.WebHome]] about how you can optimise the grid for your work in Windows Update Management.
68 {{/box}}
69
70 |**Property**|**Description**
71 |(((
72 Expiration State
73
74
75 )))|(((
76 The process status indicates which type of updates are displayed in the grid. If, for example, you have only selected the current updates in the [[process status>>doc:||anchor="H1.Expirystatusandupdatetype"]], this filter will also be applied here. If you would like to see additional "withdrawn" updates, you must select the status above and click //Update// in the ribbon bar to refresh the grid.
77 )))
78 |Title|The designation reflects the official name of the update.
79 |Clients Required|(((
80 If a client reports an update as required, this is displayed in this column: Any value greater than zero (0) means that at least one client has reported the update to the ACMP Console as required.
81
82 {{box}}
83 **Tip**: How does a client report an update to ACMP as required?
84
85 When a client reports an update as required in ACMP, this is done in the background either via the Windows Update Scanner, an Update Collection, or Windows sends a status report on its own initiative stating that the update is required. In one of these situations, the client updates the status of the update. The condition for this is that the agent is managed by WUM.
86
87 The client scans the status of its updates. Two lists of updates are then created: updates that are already installed and updates that still need to be installed. Both lists are stored in the database, which then determines the number of updates reported as required by the client. If, for example, several clients have the security update ‘2025-01 Cumulative Update for Windows 11 version 22H2 for arm64-based systems (KB5050021)’ in their table, the grid column Clients required would show exactly the number of clients that have reported it as required.
88 {{/box}}
89
90 {{aagon.infobox}}
91 The setting [[//On Demand - Only download if at least one client required the update//>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Upodate Management.WebHome||anchor="HUpdatedownloadoptions"]] you can specify that only those updates that have been reported as required by clients should be downloaded. This saves storage space, as not every update is downloaded in full.
92 {{/aagon.infobox}}
93
94 {{box}}
95 **Tip**: Once the Windows Update Scanner has successfully completed its scan, you can set the filter in the Clients Needed column to (> 0) so that only the updates that are needed are displayed. This allows you to significantly reduce the quantity of results.
96 {{/box}}
97 )))
98 |Clients Failed|If the installation or uninstallation of an update fails on a client, this is displayed in the column of the same name. The value zero (0) means that it did not fail on any client, while the value 1 indicates that it could not be installed/uninstalled correctly on at least one client. The column shows whether the last action failed.
99 |Clients Installed|The column shows the total number of updates that have installed this update.
100 |EULA status|(((
101 The EULA status indicates whether the licence agreements for the update have already been accepted or not. Possible values that may appear in the row:
102
103 * Accepted: The EULA has already been accepted for the update.
104 * Not yet accepted: The EULA has not yet been accepted for the selected update.
105 * Not required: No EULA needs to be accepted for this update, which is why the status is //Not required//.
106 )))
107 |KB-ID|The KB ID consists of the knowledge base and the article number.
108 |Classification|The [[classification>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HClassifications"]] indicates the update type (e.g. //critical updates//, //update rollups// or //upgrades//).
109 |Last Change of Distribution Ring|(((
110 Displays the date and time of the last change to the distribution ring. This also includes transitions between individual distribution rings, provided that an update was made, e.g. from //Test Ring 2// to //Released//.
111 )))
112 |Products|Products are the selected operating systems, software, or drivers for which you wish to obtain and distribute updates.
113 |Severity|(((
114 The severity level indicates how Microsoft categorises its updates. A distinction is made between //[[image:Niedrig Icon CAWUM.png||height="15" width="15"]] Low//, [[image:1747373720350-481.png]]//Important//, [[image:1747373720350-147.png]]// Critical//, [[image:1747373720351-361.png]] //Moderat//e and [[image:1747373720351-444.png]]// No security level defined//.Example: Microsoft's //security updates// are often classified as //Important// or //Critical//. Example: Microsoft's //security updates// are often classified as //Important// or //Critical//.
115 )))
116 |Transition mode|(((
117 The transition mode indicates whether an update switches automatically or manually from one distribution ring to another.
118 You can disable automatic transitions ([[image:1747373735179-436.png]]) via the ribbon bar. To reactivate them, use the function //Enable automatic transition mode //([[image:1747373739790-869.png]]).
119
120 {{aagon.warnungsbox}}
121 If you disable automatic transition mode for the selected update, the automatic move setting specified in the settings for it will be overridden.
122 {{/aagon.warnungsbox}}
123 )))
124 |Origin|(((
125 The origin indicates the source from which the update originates. Updates originating from the metadata download are indicated with //Windows Update//. Updates obtained from the MS catalogue are marked with //Manual import//.
126 )))
127 |Release Date|The publish date indicates the date on which it was published by Microsoft.
128 |Distribution Process|(((
129 The distribution process reflects the testing and approval process for Windows updates. Any Windows update that has not been explicitly assigned to a user-defined test and release process is always assigned to the //default// process. Otherwise, the processes you have created are listed here.
130 )))
131 |Distribution Ring|(((
132 The distribution ring indicates the transition phase the update is currently in and how far the automatic distribution has progressed. There are four rings that an update can typically pass through: //No distribution ring//, //Test Ring 1//, //Test Ring 2// and //Released.//
133
134 {{box}}
135 **Tip**: In the chapter //[[Testing and Release>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Upodate Management.WebHome||anchor="HTestandRelease"]] //you can learn more about how to define the individual processes and customize them for your specific needs.
136 {{/box}}
137 )))
138 |Distribution State|(((
139 This refers to the status of the downloaded files in the file repositories. A distinction is made between //Synchronised, Synchronisation //and //Not downloaded//.
140
141 * Synchronised: If the files have already been deployed to the relevant file repositories, the distribution status is //Synchronised//, as the files or updates are available. The updates have been successfully downloaded.
142 * Synchronisation: The current synchronisation with the file repository is still in progress.
143 * Not downloaded: The updates have not yet been downloaded and currently only exist as metadata.
144 )))
145
146 Properties that you will exclude from finding under the //declined updates //tab:
147
148 |(% style="width:210px" %)**Property**|(% style="width:1482px" %)**Description**
149 |(% style="width:210px" %)Declination Date|(% style="width:1482px" %)Returns the date on which an update was denied.
150 |(% style="width:210px" %)Declination Comment|(% style="width:1482px" %)Displays the reason or comment given when an update was refused.
151
152 {{aagon.infobox}}
153 Please note that you may not see all columns in the grid if you have hidden them. To display all columns, click on the asterisk (*) in the top left-hand corner of the grid and tick the desired entries or deselect them as required.
154 {{/aagon.infobox}}
155
156 == 3. Detailed view of a selected Update ==
157
158 The detailed view of a selected update provides you with a wealth of info, some of which supplements the existing info from the grid. Depending on the number of items, it is always worth opening the detailed view to avoid the risk of slipping in the row or column and reading out incorrect info, for example. The view opens below the grid as soon as you select an update.
159
160 {{aagon.infobox}}
161 The detailed view is not available for multiple selections.
162 {{/aagon.infobox}}
163
164 [[Example of a detailed view of a selected update>>image:67_CAWUM_Detailansicht eines ausgewählten Updates_1674.png]]
165
166 The information is divided into six tabs:
167
168 |**Tab**|**Description**
169 |General|This tab provides general details and information about the selected update. In addition to the official name and description from Microsoft and the publish date, you will also find the severity, KB ID and further information about the update.
170 |Installation/Uninstallation|(((
171 If you want to install or uninstall the update, you will find more detailed information on the respective behaviour here:
172
173 * Restart behavior: How does the update behave during installation or uninstallation? Does the computer need to be restarted?
174 * May require user input: Is it necessary for the user to enter information during installation/uninstallation in order for the update to be finished successfully?
175 * Installation impact: How must the update be installed? For example, should the update be installed on its own, even if several updates should execute?
176 * Requires network connection: Is a network connection required for the update installation/uninstallation to be successfully executed?
177 )))
178 |Affected Clients|(((
179 This tab lists all agents that are affected by the update in any way:
180
181 * Installed
182 * Failed
183 * Required
184
185 From this tab, you can perform a pushed installation. To do this, select a client and then click on //Install Updates// and provide your confirmation in the window that opens. In addition, you can uninstall updates or
186
187 (((
188 [[image:1747373799235-945.png]] //[[Run Jobs>>doc:ACMP.68.ACMP-Solutions.Desktop Automation.Client Commands.Jobs ausführen.WebHome]] //oder [[image:1747373803930-685.png]] [[rescan clients>>doc:ACMP.68.ACMP-Solutions.Client-Management.Abfrageverwaltung.Clients verwalten.WebHome]].
189 )))
190 )))
191 |Test runs|All executions of Update Collections, installations and uninstallations that were executed in Test Ring 1 or Test Ring 2 are listed.
192 |EULA|{{aagon.infobox}}This tab's visibility is only enabled if an EULA (End User Licence Agreement) must be agreed to for the update.{{/aagon.infobox}}(((
193 Here you will find info about the EULA status, as well as when and who accepted the EULA. Clicking the //Show EULA //button opens a new window where you can read the licence terms for the respective update.
194 )))
195 |Replacement|The tab indicates whether the selected update replaces another update or has already been replaced by another update. The updates to be replaced or that have been replaced are listed below, by name.
196
197 == Accept EULA ==
198
199 {{box}}
200 An EULA (End User Licence Agreement) is a legal agreement that grants a user a licence to use software. Only once the licence agreement has been accepted – if the software requires this – can the user utilise the application (e.g. download or install it).
201 {{/box}}
202
203 For some updates (often classified as //upgrades//), you must agree to an EULA (End User Licence Agreement) before distribution and continuing installation. For these updates, you can accept the licence terms by clicking the //accept EULA// button in the ribbon bar.
204
205 This opens a two-part window: in the upper part, you will see the knowledge base ID and the title of the update, and in the lower part, the licence agreements for the update. Read the text carefully, tick the checkbox and then click on //Accept// to agree to the terms and conditions.
206
207 [[Example of an accepted EULA for an upgrade>>image:67_CAWUM_EULA akzeptieren_785.png]]
208
209 Accepting the EULA also changes the EULA status in the grid to //accepted// for the selected upgrade.
210
211 {{aagon.infobox}}
212 If you have explicitly not accepted the EULA for an update, this update will not be downloaded. Subsequent distribution and installation will not be possible.
213 {{/aagon.infobox}}
214
215 {{aagon.warnungsbox}}
216 Within the [[settings>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Upodate Management.WebHome]] (//System// > //Settings //> //Windows Update Management// > //Options//), you will find a configuration option that allows you to automatically accept EULAs of Updates without reading them.
217
218 Please note that this automatic process may conflict with the laws applicable in your country.
219 {{/aagon.warnungsbox}}
220
221
222 = Declined Updates =
223
224 If you no longer want a displayed update to be distributed on your network (because it is outdated, for example), you can decline this update. A declined update will no longer be distributed or installed on clients and will be removed from all existing update collections ([[Windows Update Collections>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]]).
225
226 To decline an update, first select the relevant update in the grid and then click on [[image:1747373870721-499.png]]// Decline //in the ribbon bar or choose the action from the context menu (right click). A new window will open where you can specify an optional reason for rejection.
227
228 ​
229
230 [[Comment window for refusing an update>>image:67_CAWUM_Updates verweigern_475.png]]
231
232 {{aagon.infobox}}
233 Please note that, depending on your expiry date filter, older replaced updates may also appear after the selected updates have been dismissed.
234 {{/aagon.infobox}}
235
236 The hard drive space occupied by the update will only be freed up during the next cleanup (see [[Cleanup job>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HJobsandtasks"]]). To do this, refresh the view in the dashboard.
237
238 Declined updates will then be displayed in the tab of the same name, //Declined Updates//.
239
240 {{aagon.warnungsbox}}
241 If you decline an update that replaces another update, it will reappear in the overview.
242 {{/aagon.warnungsbox}}
243
244 {{aagon.infobox}}
245 Updates can also be automatically declined after a certain period of time if they have not been required for a predefined number of days. The default period is 180 days. The setting can be enabled either in the First Steps Wizard (Automatic Cleanup of Updates) or subsequently via the settings (//System// > //Settings// > //Windows Update Management// > //Options// > //Windows Update Cleanup//).
246 {{/aagon.infobox}}
247
248 == Approve declined updates ==
249
250 All updates that you have previously declined are listed under the tab of the same name in Windows Update Management. Similar to the [[Updates>>doc:||anchor="HWorkingwithupdates"]] the results are also displayed here in a grid, with only the columns and filled fields differing slightly (for example, you will find the [[decline date>>doc:||anchor="H2.Propertiesoftheupdates"]] and the comment entered here).
251
252 If you still want to distribute and install one of the displayed updates on your network, select it and click on [[image:1747373905472-717.png]]// Approve // in the ribbon bar.
253
254 [[Retrospectively approve declined updates>>image:67_CAWUM_Verweigerte Updates genehmigen_1384.png]]
255
256 Confirm the dialogue box with //Yes//. This will display the selected update again in the //Updates// tab, where it will be available for you to install on the network.
257
258 = Change the release process for updates =
259
260 Updates that are already in a release process and have already been assigned a distribution ring (Test Ring 1 or Test Ring 2) can be manually changed to a different distribution ring using the ribbon bar or the context menu. This may be necessary, for example, if an important update needs to be moved to another ring so that it can be distributed more quickly. To do this, first select the relevant update from the grid and click on //Change distribution ring //([[image:1747373939888-917.png]]). The distribution ring editor opens, where you can now select the new distribution ring for the update. Also check that the //Automatic move items to the next distribution ring// checkbox is enabled so that this automatic function takes effect and the update is moved to the next ring at a later point in time. Exit your work by clicking //Change//. The grid view is automatically updated so that the update is assigned to the appropriate distribution ring.
261
262 [[Distribution ring editor in Windows Update Management>>image:67_CAWUM_Verteilungsring wechseln_453.png]]
263
264 {{aagon.infobox}}
265 You can see whether there is an automatic transition mode for the respective update in the grid property //Transition Mode//. If the automatic mode is activated, the row will say "Automatic". If the mode is disabled, it will say "Manual".
266
267 You can also change the transition mode retrospectively by clicking on //Enable automatic transition mode //([[image:1747373997490-853.png]])// /// //disable //([[image:1747373997490-436.png]])//  //in the ribbon bar, depending on whether you want a transition mode or not.
268 {{/aagon.infobox}}
269
270 {{aagon.warnungsbox}}
271 Please note that by setting the automatic transition mode to disabled, you are overriding the automatic update postponement feature.
272 {{/aagon.warnungsbox}}
273
274 In principle, it is also possible to move the updates to a prior distribution ring, and the change does not necessarily have to be closer to release. For example, if you want to keep an update in a test ring for longer and see if there are any changes from Microsoft, you could keep it in the test environment for longer and send it back to a test ring if you do not want to completely change the number of days configured for the process.
275
276
277 = Obtain updates from the MS Catalog =
278
279 The [[Microsoft Update Catalog>>https://www.catalog.update.microsoft.com/Home.aspx]] is a Microsoft service that provides a wide range of updates that you can distribute via your company network. You can use the catalogue to find any type of Microsoft-specific software updates and, if necessary, download them manually and integrate them into your network.
280
281 Click on //MS Catalog// in the ribbon bar and a new window will open, consisting of two tabs: //Update catalog// and //Selected Updates//.
282
283 [[Microsoft Update Catalog>>image:67_CAWUM_MS Katalog_1282.png]]
284
285 Enter your search term in the search box at the top right. To narrow down the results, Microsoft recommends entering the appropriate Knowledge Base ID (KB ID).
286
287 [[Find updates in the MS Catalog>>image:67_CAWUM_MS Katalog KB Nummer_1282.png]]
288
289 Once you have found the appropriate update from the entries, click //Add// in the right-hand pane. The update will now be imported in the background and made available to you in the //Selected Updates// tab. Click //Remove// if you do not need the update and want to delete it from the list.
290
291 The next time Metadata download is performed, the selected updates will also be downloaded and made available to you in the ACMP Console.
292
293 {{box}}
294 **Tip**: Updates that you obtain directly from the MS Catalog are displayed within the grid in the //Origin //column with "Manual import".
295 {{/box}}
296
297
© Aagon GmbH 2025
Besuchen Sie unsere Aagon-Community