Changes for page Windows Update Collection

Last modified by Sabrina V. on 2026/05/20 09:27
From version 3.1
edited by Sabrina V.
on 2025/12/09 08:28
Change comment: There is no comment for this version
To version 7.1
edited by Sabrina V.
on 2026/05/20 09:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -20,73 +20,44 @@
20 20  
21 21  == Add Windows Update Collection ==
22 22  
23 -To create a new Windows Update Collection, click //Add //[[image:1745390057699-607.png]] in the ribbon bar. EA multi-page wizard will open to guide you through the individual steps. On the first page (//General//), enter a name for the collection and an optional description. Check that the output directory is correct or customize it ([[image:1745390057699-386.png]]) and select the correct one. Set the reboot options in the lower section. Here you can choose between the following options:
23 +To create a new Windows Update Collection, click //Add //[[image:1745390057699-607.png]] in the ribbon bar. EA multi-page wizard will open to guide you through the individual steps. On the first page (//General//), enter a name for the collection and an optional description. Check that the output directory is correct or customize it ([[image:1745390057699-386.png]]) and select the correct one. Check the checkbox (“Prompt users to save their open files and close all Microsoft Office applications so that updates can be installed”) if you want to explicitly deploy Microsoft 365 updates via this collection. If this option is selected and the scanner detects that Office applications need to be updated, a dialog box will inform the user and prompt them to save all open Microsoft Office documents and close all Office applications. Otherwise, the installation of these Updates may fail.
24 24  
25 -* Do not restart, but inform the logged-in user that a restart is required.
26 -* Do not restart and do not notify the logged-in user that a restart is required.
27 -* Restart the computer if necessary.
28 -
29 29  {{aagon.infobox}}
30 -With the first option ("Do not restart, but inform the logged-in user that a restart is required"), the user on the client is displayed a restart dialogue box, which you can customize to match your corporate identity. Read [[here>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HWindowsUpdateManagementCIAnpassungen28Neustart-Dialog29"]] to find out how to make these changes.
26 +The dialog box is displayed only when Office-related Updates are actually installed.
31 31  {{/aagon.infobox}}
32 32  
33 -[[Add a new Windows Update Collection (General)>>image:67_CAWUM_Windows Update Collection hinzufügen Allgemein_832.png]]
29 +Configure the reboot options in the lower section. Here, you can choose from the following options:
34 34  
35 -On the next page, define a filter that includes the products and classifications that should apply to this update collection. You can choose between two filter modes: //Standard filter// or //Advanced filter//.
31 +* Do not restart, but notify the logged-in user that a restart is required.
36 36  
37 -__Standard filter__: Only the products and classifications that you previously selected via the First Steps Wizard or subsequently in the settings are displayed here. In other words, you can only assign the products and classification to a collection that you have subscribed to. Click on them to include them in the collection.
33 +{{aagon.infobox}}
34 +Here, you can specify how many reboot delays should occur (the number is configurable) and at what interval (wait time between reboot reminders; specified in minutes). Depending on the configuration, the user will be notified of the required restart accordingly.
35 +{{/aagon.infobox}}
38 38  
39 -__Advanced filter__: The advanced filter allows you to individually specify which updates you want to add to the Windows Update Collection. All fields related to an update are available for this purpose. The versatile constellations allow you to create specific collections that exactly meet your requirements, enabling the smooth deployment of various updates. This makes it possible, for example, to create a collection that contains all updates from Dell, but without distributing the BIOS updates. Conversely, it is also possible to add only Dell BIOS updates to a collection.
37 +{{aagon.infobox}}
38 +With this option, a restart dialog is displayed to the user on the client, which you can customize to match your corporate identity. Read [[here>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HWindowsUpdateManagementCIAnpassungen28Neustart-Dialog29"]] to find out how to make these changes.
39 +{{/aagon.infobox}}
40 40  
41 +* Do not restart the computer and do not notify the logged-in user that a restart is required.
42 +* Restart the computer if necessary.
43 +* Restart the computer if no user is logged in; otherwise, note to the user that a restart is required.
41 41  
42 -**Continuing examples:**
45 +[[Add a new Windows Update Collection (General)>>image:610_Windows Update Management_Collection Allgemein_965.jpg||alt="67_CAWUM_Windows Update Collection hinzufügen Allgemein_832.png"]]
43 43  
44 -The following examples illustrate some filter configurations that are designed to automatically deny these updates. Please note that the level at which you are located or set the filter option is crucial. This can significantly determine whether an update should be explicitly declined if one or more conditions apply.
47 +On the next page, define a filter that includes the products and classifications that should apply to this update collection. You can choose between two filter modes: //Standard filter// or //Advanced filter//.
45 45  
49 +__Standard filter__: Only the products and classifications that you previously selected via the First Steps Wizard or subsequently in the settings are displayed here. In other words, you can only assign the products and classification to a collection that you have subscribed to. Click on them to include them in the collection. Use the filter at the bottom to select whether you want to display all checked or suggested products.
50 +
46 46  {{box}}
47 -**Tip**: For information on how to create a filter and the different filter modes and basic elements available for each filter, see Working with filter types.
52 +In the “Suggested” column, you can see directly from the product list whether a product is suggested for the filter or not.
48 48  {{/box}}
49 49  
50 -Examples:
55 +__Advanced filter__: The advanced filter allows you to individually specify which updates you want to add to the Windows Update Collection. All fields related to an update are available for this purpose. The versatile constellations allow you to create specific collections that exactly meet your requirements, enabling the smooth deployment of various updates. This makes it possible, for example, to create a collection that contains all updates from Dell, but without distributing the BIOS updates. Conversely, it is also possible to add only Dell BIOS updates to a collection.
51 51  
52 -* ‘Decline all updates that contain the string %ARM64% in their name’
57 +{{box}}
58 +Within the settings, you will find continuing examples of possible [[//filter configurations for declining updates//>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Update Management.WebHome||anchor="HExamplesoffilterconfigurationstodeclineupdates"]].
59 +{{/box}}
53 53  
54 -* ‘All updates that have been revoked by Microsoft (expiry status IN Revoked)’
55 -
56 -* ‘All updates that have not been used for more than 180 days.’
57 -
58 -In this configuration, updates are automatically declined
59 -
60 -[[image:69_CAWUM Filter 1.png||data-xwiki-image-style-alignment="center"]]
61 -
62 -**Example: ‘Decline Microsoft Defender Antivirus updates that have not been needed for more than X days’**
63 -
64 -Since Defender updates tend to be short-lived, you may want to deny them a little faster so that they do not take up unnecessary hard drive space. This can be achieved as follows, for example: Updates with the update product name ‘Microsoft Defender Antivirus’ (filter: In) and the field ‘Last used on’ (filter value: not in the last) in 14 days are automatically rejected.
65 -
66 -[[image:69_CAWUM Filter 2.png||data-xwiki-image-style-alignment="center"]]
67 -
68 -**Example: ‘Decline Microsoft Edge updates that are in the Beta or Dev channel’**
69 -
70 -In this configuration, two filter options are combined: Only updates that have the product name ‘Microsoft Edge’ (filter: In) AND the designation %Microsoft Edge Beta Channel% (filter: similar) OR %Microsoft Edge Dev Channel% are automatically declined. This combination therefore declines all updates that are assigned to the beta or dev channel. The wildcards allow any number of characters to be taken into account.
71 -
72 -[[image:69_CAWUM Filter 3.png||data-xwiki-image-style-alignment="center"]]
73 -
74 -**Example: ‘Reject Windows 11 22H2 updates’**
75 -
76 -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.
77 -
78 -[[image:69_CAWUM Filter 4.png||data-xwiki-image-style-alignment="center"]]
79 -
80 -**Combination of all filter options**
81 -
82 -You can also create a more complex filter combination within the filter by establishing a connection between the individual filter operators. However, please note that the top operator also applies to the conditions below and that there is an AND/OR correlation between the individual filters. The following illustration shows how to use the above.
83 -
84 -[[Filter combination>>image:69_CAWUM Automatisches Verweigern Updates Beispiele_1732.png]]
85 -
86 -The advanced filter allows you to focus on specific environments and provide exactly the updates that meet your criteria.
87 -
88 -In this example, we want to create a collection for a Windows 11 upgrade, so we select only the product //Windows 11// in the upper section and only //Upgrades// under Classifications. The filter mode selected here is ‘Standard filter’.
89 -
90 90  {{box}}
91 91  **Tip**: For a better overview, you can tick the //Display selected entries only// checkbox under the products.
92 92  {{/box}}
... ... @@ -93,9 +93,9 @@
93 93  
94 94  Continue and click //Next >//.
95 95  
96 -[[Add Windows Update Collection (filter)>>image:69_CAWUM_Windows Update Collection hinzufügen Filter_832.png||alt="67_CAWUM_Windows Update Collection hinzufügen Filter_832.png"]]
67 +[[Add Windows Update Collection (filter)>>image:610_Windows Update Management_Collection Filter_965.jpg||alt="67_CAWUM_Windows Update Collection hinzufügen Filter_832.png"]]
97 97  
98 -Under //Update Links//, you can statically link selected updates to this collection. To do this, click on [[image:1745390129619-868.png]]// Add //and the Windows Updates element selection will open. In this view, the available updates are displayed in the same way as in the //Updates// tab (including detailed view). To store an update statically, select the desired number and mark the entries. To remove all entries, you can select the //deselect all// button below the detailed view. Otherwise, click //OK// once you have checked all the required updates.
69 +Under //Update Links//, you can statically link selected updates to this collection. To do this, click on [[image:1745390129619-868.png]]// Add //and the Windows Updates element selection will open. In this view, the available updates are displayed in the same way as in the //Updates// tab (including detailed view). To store an update statically, select the desired number (multiple selections are allowed) and mark the entries. To remove all entries, you can select the //deselect all// button below the detailed view. Otherwise, click //OK// once you have checked all the required updates.
99 99  
100 100  [[Selecting Windows Updates items for static linking>>image:67_CAWUM_Windows Update Collection hinzufügen Elementauswahl_1026.png]]
101 101  
... ... @@ -103,9 +103,8 @@
103 103  
104 104  [[Link updates statically to a collection>>image:67_CAWUM_Windows Update Collection hinzufügen Update Links_832.png]]
105 105  
106 -If you wish to remove a static link, select the relevant update and click on [[image:1745390173414-325.png]] Remove. To exit the wizard, click on //Finish//. The newly created Windows Update Collection will now be displayed in the overview.
77 +If you wish to remove a static link, select the appropriate number of Updates (one or more) and click on [[image:1745390173414-325.png]] Remove. To exit the wizard, click on //Finish//. The newly created Windows Update Collection will now be displayed in the overview.
107 107  
108 -
109 109  == Edit, delete or duplicate Windows Update Collections ==
110 110  
111 111  In addition to creating a new Windows Update Collection, you can also work with existing collections. All actions can be started either via the context menu or from the ribbon bar. To do this, click on the corresponding button for the action and follow the continuing instructions.
© Aagon GmbH 2026
Besuchen Sie unsere Aagon Community