Skip to Content
Last modified by Sabrina V. on 2026/10/07 11:05
From version 11.1
edited by Steffi F
on 2026/06/15 12:22
Change comment: There is no comment for this version
To version 15.1
edited by Sabrina V.
on 2026/10/07 11:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.SF
1 +XWiki.SV
Content
... ... @@ -13,10 +13,10 @@
13 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.Expirystatus2Cupdatetypeandorigin"]]).
14 14  
15 15  {{box}}
16 -**Tip**: Read the chapter //[[Structure of a grid in ACMP>>doc:ACMP.610.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.
16 +**Tip**: Read the chapter //[[Structure of a grid in acmp>>doc:ACMP.610.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 17  {{/box}}
18 18  
19 -The ribbon bar can be used to assign [[image:1747373593711-339.png]][[sync profiles>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HSyncProfilesanddistributedFileRepositories"]] 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.610.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Update 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.
19 +The ribbon bar can be used to assign [[image:1747373593711-339.png||data-cmp-info="10"]][[sync profiles>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HSyncProfilesanddistributedFileRepositories"]] and [[image:1747373608196-936.png||data-cmp-info="10"]] [[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||data-cmp-info="10"]]), this can be changed and adjusted manually. In addition, you can navigate directly from the updates to the [[image:1747373620038-623.png||data-cmp-info="10"]] [[settings>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Update Management.WebHome]] and make changes (e.g. deselect or select products or classifications). The [[image:1747373625736-313.png||data-cmp-info="10"]][[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 20  
21 21  {{box}}
22 22  **Tip**: The Microsoft Update Catalog is particularly useful for updates that are only available through the catalog.
... ... @@ -28,7 +28,7 @@
28 28  * 2. Properties of the updates
29 29  * 3. Detailed view of a selected update
30 30  
31 -[[Structuring the areas of the updates>>image:610_CAWUM_Updates bearbeitete Übersicht_1676.png]]
31 +[[Structuring the areas of the updates>>image:610_CAWUM_Updates bearbeitete Übersicht_1676.png||data-cmp-info="10"]]
32 32  
33 33  == 1. Expiry status, update type and origin ==
34 34  
... ... @@ -35,11 +35,11 @@
35 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). The source indicates whether the updates are Windows Updates, manually added updates, or updates provided by a third party.
36 36  
37 37  
38 -[[Expiry status and update type>>image:610_CAWUM_Ablaufstatus Update-Typ und Ursprung_1074.png||alt="610_CAWUM_Ablaufstatus_777.png"]]
38 +[[Expiry status and update type>>image:610_CAWUM_Ablaufstatus Update-Typ und Ursprung_1074.png||alt="610_CAWUM_Ablaufstatus_777.png" data-cmp-info="10"]]
39 39  
40 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 41  
42 -For a better overview, only //Current //and //May expire //are selected by default when ACMP is installed.
42 +For a better overview, only //Current //and //May expire //are selected by default when acmp is installed.
43 43  
44 44  |(% style="width:145px" %)**Expiry status**|(% style="width:1547px" %)**Description**
45 45  |(% style="width:145px" %)Up-to-date|(% style="width:1547px" %)(((
... ... @@ -78,12 +78,12 @@
78 78  )))
79 79  |Title|The designation reflects the official name of the update.
80 80  |Clients Required|(((
81 -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 +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.
82 82  
83 83  {{box}}
84 -**Tip**: How does a client report an update to ACMP as required?
84 +**Tip**: How does a client report an update to acmp as required?
85 85  
86 -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 +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.
87 87  
88 88  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.
89 89  {{/box}}
... ... @@ -112,11 +112,11 @@
112 112  )))
113 113  |Products|Products are the selected operating systems, software, or drivers for which you wish to obtain and distribute updates.
114 114  |Severity|(((
115 -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 +The severity level indicates how Microsoft categorises its updates. A distinction is made between //[[image:Niedrig Icon CAWUM.png||data-cmp-info="10" height="15" width="15"]] Low//, [[image:1747373720350-481.png||data-cmp-info="10"]]//Important//, [[image:1747373720350-147.png||data-cmp-info="10"]]// Critical//, [[image:1747373720351-361.png||data-cmp-info="10"]] //Moderat//e and [[image:1747373720351-444.png||data-cmp-info="10"]]// 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//.
116 116  )))
117 117  |Transition mode|(((
118 118  The transition mode indicates whether an update switches automatically or manually from one distribution ring to another.
119 -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 +You can disable automatic transitions ([[image:1747373735179-436.png||data-cmp-info="10"]]) via the ribbon bar. To reactivate them, use the function //Enable automatic transition mode //([[image:1747373739790-869.png||data-cmp-info="10"]]).
120 120  
121 121  {{aagon.warnungsbox}}
122 122  If you disable automatic transition mode for the selected update, the automatic move setting specified in the settings for it will be overridden.
... ... @@ -165,7 +165,7 @@
165 165  The detailed view is not available for multiple selections.
166 166  {{/aagon.infobox}}
167 167  
168 -[[Example of a detailed view of a selected update>>image:67_CAWUM_Detailansicht eines ausgewählten Updates_1674.png]]
168 +[[Example of a detailed view of a selected update>>image:67_CAWUM_Detailansicht eines ausgewählten Updates_1674.png||data-cmp-info="10"]]
169 169  
170 170  The information is divided into six tabs:
171 171  
... ... @@ -189,7 +189,7 @@
189 189  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
190 190  
191 191  (((
192 - [[image:1747373799235-945.png]] //[[Run Jobs>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Client Commands.Jobs ausführen.WebHome]] //oder [[image:1747373803930-685.png]] [[rescan clients>>doc:ACMP.610.ACMP-Solutions.Client-Management.Abfrageverwaltung.Clients verwalten.WebHome]].
192 + [[image:1747373799235-945.png||data-cmp-info="10"]] //[[Run Jobs>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Client Commands.Jobs ausführen.WebHome]] //oder [[image:1747373803930-685.png||data-cmp-info="10"]] [[rescan clients>>doc:ACMP.610.ACMP-Solutions.Client-Management.Abfrageverwaltung.Clients verwalten.WebHome]].
193 193  )))
194 194  )))
195 195  |Test runs|All executions of Update Collections, installations and uninstallations that were executed in Test Ring 1 or Test Ring 2 are listed.
... ... @@ -208,7 +208,7 @@
208 208  
209 209  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.
210 210  
211 -[[Example of an accepted EULA for an upgrade>>image:67_CAWUM_EULA akzeptieren_785.png]]
211 +[[Example of an accepted EULA for an upgrade>>image:67_CAWUM_EULA akzeptieren_785.png||data-cmp-info="10"]]
212 212  
213 213  Accepting the EULA also changes the EULA status in the grid to //accepted// for the selected upgrade.
214 214  
... ... @@ -227,11 +227,11 @@
227 227  
228 228  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.610.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]]).
229 229  
230 -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.
230 +To decline an update, first select the relevant update in the grid and then click on [[image:1747373870721-499.png||data-cmp-info="10"]]// 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.
231 231  
232 232  ​
233 233  
234 -[[Comment window for refusing an update>>image:67_CAWUM_Updates verweigern_475.png]]
234 +[[Comment window for refusing an update>>image:67_CAWUM_Updates verweigern_475.png||data-cmp-info="10"]]
235 235  
236 236  {{aagon.infobox}}
237 237  Please note that, depending on your expiry date filter, older replaced updates may also appear after the selected updates have been dismissed.
... ... @@ -253,22 +253,22 @@
253 253  
254 254  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).
255 255  
256 -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.
256 +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||data-cmp-info="10"]]// Approve // in the ribbon bar.
257 257  
258 -[[Retrospectively approve declined updates>>image:67_CAWUM_Verweigerte Updates genehmigen_1384.png]]
258 +[[Retrospectively approve declined updates>>image:67_CAWUM_Verweigerte Updates genehmigen_1384.png||data-cmp-info="10"]]
259 259  
260 260  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.
261 261  
262 -= Change the release process for updates =
262 += Replace the distribution ring =
263 263  
264 -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.
264 +Updates that are already in a release process and have already been assigned a [[distribution ring>>distribution ring||anchor="HTestandRelease"]] (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||data-cmp-info="10"]]). 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.
265 265  
266 -[[Distribution ring editor in Windows Update Management>>image:67_CAWUM_Verteilungsring wechseln_453.png]]
266 +[[Distribution ring editor in Windows Update Management>>image:67_CAWUM_Verteilungsring wechseln_453.png||data-cmp-info="10"]]
267 267  
268 268  {{aagon.infobox}}
269 269  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".
270 270  
271 -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.
271 +You can also change the transition mode retrospectively by clicking on //Enable automatic transition mode //([[image:1747373997490-853.png||data-cmp-info="10"]])// /// //disable //([[image:1747373997490-436.png||data-cmp-info="10"]])//  //in the ribbon bar, depending on whether you want a transition mode or not.
272 272  {{/aagon.infobox}}
273 273  
274 274  {{aagon.warnungsbox}}
... ... @@ -275,7 +275,7 @@
275 275  Please note that by setting the automatic transition mode to disabled, you are overriding the automatic update postponement feature.
276 276  {{/aagon.warnungsbox}}
277 277  
278 -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.
278 +In principle, it is also possible to move the updates to a prior [[distribution ring>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Update Management.WebHome||anchor="HTestandRelease"]], 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.
279 279  
280 280  
281 281  = Obtain updates from the MS Catalog =
... ... @@ -284,16 +284,21 @@
284 284  
285 285  Click on //MS Catalog// in the ribbon bar and a new window will open, consisting of two tabs: //Update catalog// and //Selected Updates//.
286 286  
287 -[[Microsoft Update Catalog>>image:67_CAWUM_MS Katalog_1282.png]]
287 +[[Microsoft Update Catalog>>image:67_CAWUM_MS Katalog_1282.png||data-cmp-info="10"]]
288 288  
289 289  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).
290 290  
291 -[[Find updates in the MS Catalog>>image:67_CAWUM_MS Katalog KB Nummer_1282.png]]
291 +[[Find updates in the MS Catalog>>image:67_CAWUM_MS Katalog KB Nummer_1282.png||data-cmp-info="10"]]
292 292  
293 293  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.
294 294  
295 -The next time Metadata download is performed, the selected updates will also be downloaded and made available to you in the ACMP Console.
295 +The next time Metadata download is performed, the selected updates will also be downloaded and made available to you in the acmp Console.
296 296  
297 +{{aagon.infobox}}
298 +Please note that, in general, the update must first be downloaded before the distribution ring can be changed.
299 +For the update to be downloaded in an [[On Demand configuration>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Update Management.WebHome||anchor="HUpdatedownloadoptions"]], it must first be reported as "required" by an agent (see also [[Update Properties>>doc:||anchor="H2.Propertiesoftheupdates"]]). To do this, simply run a [[Windows Update Scanner>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HJobsandtasks"]] or a [[Windows Update Collection>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]] on the affected client after adding the update.
300 +{{/aagon.infobox}}
301 +
297 297  {{box}}
298 298  **Tip**: Updates that you obtain directly from the MS Catalog are displayed within the grid in the //Origin //column with "Manual import".
299 299  {{/box}}
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community