Last modified by Sabrina V. on 2026/06/09 11:39
From version 7.1
edited by Sabrina V.
on 2025/12/09 09:04
Change comment: There is no comment for this version
To version 14.1
edited by Sabrina V.
on 2026/05/22 10:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,7 +14,7 @@
14 14  * [[Classifications>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HClassifications"]]
15 15  * [[Languages>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HLanguages"]] (as well as Microsoft 365 app languages and additional correction tools)
16 16  
17 -[[Settings for products, classifications and languages>>image:68_CAWUM_Einstellungen_Produkte_1658.png]]
17 +[[Settings for products, classifications and languages>>image:610_CAWUM_Einstellungen_Produkte_1658.png]]
18 18  
19 19  If you need to add or deselect products, classifications or languages, you can make these changes conveniently on this page. To save, click// //[[image:1733144384832-822.png||height="18" width="18"]]// Save //in the ribbon bar.
20 20  
... ... @@ -46,7 +46,7 @@
46 46  
47 47  With the checkbox //Only download updates newer than//, you can specify a specific date for the downloads. To do this, activate the checkbox and select a date that sets the time limit.
48 48  
49 -[[Update download Options>>image:68_CAWUM Einstellungen Update-Download-Optionen_1337.png||alt="67_CAWUM Einstellungen Update-Download-Optionen_1337.png"]]
49 +[[Update download Options>>image:610_CAWUM Einstellungen Update-Download-Optionen_1251.png||alt="610_CAWUM Einstellungen Update-Download-Optionen_1337.png"]]
50 50  
51 51  == Special feature: //Always download updates for these products and classifications// ==
52 52  
... ... @@ -66,7 +66,7 @@
66 66  
67 67  Now select the entry from the products that you want to designate as an exception. In the following illustration, this is //Microsoft Defender Antivirus//. Now tick all the boxes under the classifications for the types of updates that you want to download. For Microsoft Defender, for example, only critical and security-related updates should always be downloaded.
68 68  
69 -[[On-demand settings for downloading updates>>image:67_CAWUM Download-Typ On Demand_932.png]]
69 +[[On-demand settings for downloading updates>>image:610_CAWUM Download-Typ On Demand_932.png]]
70 70  
71 71  {{aagon.infobox}}
72 72  You can specify a time frame in which updates may be downloaded. To do this, enter the number of months to be included in the download. The default value is 24 months.
... ... @@ -104,7 +104,7 @@
104 104  
105 105  [[Windows Update Management settings>>image:69_CAWUM Einstellungen_Optionen2_1070.png||alt="67_CAWUM Einstellungen_Optionen2_1070.png"]]
106 106  
107 -== Automatic declination of Updates ==
107 += Automatic declination of Updates =
108 108  
109 109  This setting allows you to create a filter that automatically denies updates based on the applicable criteria. The declined updates that fall under the filter are then deleted from the hard drive by the clean-up job. By default, the ‘Last used on’ field is suggested when the filter is opened for the first time, as this corresponded to the behaviour up to ACMP version 6.9: All updates that are recognised as no longer needed after the defined number of days are automatically denied and removed by the server task. 
110 110  An update is considered no longer needed if, for example, it has not been requested by clients within the configured period (filter option: Last used on) or if certain types of updates are generally irrelevant (preview updates from a specific third-party provider, etc.). With the help of the filter, you can define the automatic decline of Windows Updates and individually determine what should and should not be declined according to your criteria.
... ... @@ -133,7 +133,7 @@
133 133  
134 134  * "All updates that have not been used for more than 180 days."
135 135  
136 -In this configuration, updates that have a name similar to %ARM64%, have a status of "Revoked" and were last reported as needed more than 180 days ago (filter: Last used "not in the last x days") are automatically declined (condition: OR).
136 +In this configuration, updates that have a name similar to %ARM64%, have a status of "Revoked" or were last reported as needed more than 180 days ago (filter: Last used "not in the last x days") are automatically declined (condition: OR).
137 137  
138 138  [[image:69_CAWUM Filter 1.png||data-xwiki-image-style-alignment="center"]]
139 139  
... ... @@ -151,7 +151,7 @@
151 151  
152 152  **Example: "Reject Windows 11 22H2 updates"**
153 153  
154 -Updates with the update product name "Windows 11" (filter: In) __and__ a designation (filter: similar) of "22H2%" are automatically rejected. The percent signs represent a wildcard. This means that similar-sounding version updates of Windows 11 are also denied with this filter configuration.
154 +Updates with the update product name "Windows 11" (filter: In) __AND__ a designation (filter: similar) of "22H2%" are automatically rejected. The percent signs represent a wildcard. This means that similar-sounding version updates of Windows 11 are also denied with this filter configuration.
155 155  
156 156  [[image:69_CAWUM Filter 4.png||data-xwiki-image-style-alignment="center"]]
157 157  
... ... @@ -216,10 +216,22 @@
216 216  **Tip:** As already mentioned, it is advisable to create a separate testing and release process for each product/product group. Do not mix different products if different classifications involve different processes. It is better to create a separate process for each product with the respective classification so that you can determine the degree of distribution more individually.
217 217  {{/box}}
218 218  
219 -In this example, the release process for the product //Office// > //Microsoft 365 Apps/Office 2019/Office LTSC// is to be determined. Therefore, tick this entry and select the classifications that are to be covered by it. If necessary, read [[here>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HKlassifizierungen"]] again to find out what type of update covers what. All types of "Updates" should be taken into account here (//critical//, //definition//, //security updates//, //update rollups// and //updates//). Click //Next >// again after you have activated all relevant checkboxes.
219 +In this example, the release process for the product //Office// > //Microsoft 365 Apps/Office 2019/Office LTSC// is to be determined. You can use the [[filter mode>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome||anchor="HAddWindowsUpdateCollection"]] (standard filter or advanced filter) to define the content.
220 220  
221 -[[Define content for testing and release>>image:67_Einstellungen_Inhalte für Test und Freigabe_966.png]]
221 +{{box}}
222 +**Info**: When using the advanced filter, you can create a filter for the content directly by using the SingleValue or MultiValue fields.
223 +{{/box}}
222 222  
225 +Using the filter at the bottom, you can select whether you want to display all checked or suggested products.
226 +
227 +{{box}}
228 +**Info**: Using the “Suggested” column, you can see directly from the product list whether a product is suggested for the filter or not.
229 +{{/box}}
230 +
231 +Therefore, tick this entry and select the classifications that are to be covered by it. If necessary, read [[here>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HKlassifizierungen"]] again to find out what type of update covers what. All types of "Updates" should be taken into account here (//critical//, //definition//, //security updates//, //update rollups// and //updates//). Click //Next >// again after you have activated all relevant checkboxes.
232 +
233 +[[Define content for testing and release>>image:610_CAWUM Test und Freigabering Inhalte_966.png||alt="610_Einstellungen_Inhalte für Test und Freigabe_966.png"]]
234 +
223 223  On the last page, you must now define the test ring configuration. The structure of the rings stored here is similar and always follows the same sequence: The updates can be moved either manually or automatically (after a number of days specified by you) from //No ring //to //Test ring 1 //and //Test ring 2 //until they reach the release ring, where they are distributed and installed on all clients that meet the update requirements.
224 224  
225 225  You can then view the respective distribution process and ring via the grid in Windows Update Management under the //Updates //tab. The two entries refer to the configurations you have made here and are listed as table entries.
© Aagon GmbH 2026
Besuchen Sie unsere Aagon Community