Changes for page Windows Update Collection

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,6 +1,6 @@
1	1	{{aagon.floatingbox/}}
2	2
3		-A Windows Update Collection is a compilation of various updates consisting of selected products and classifications. The updates are stored dynamically and can be distributed via the [[containers>>doc:ACMP.69.ACMP-Solutions.Client-Management.Container.WebHome]], used to prepare new clients (via [[rollout>>doc:ACMP.69.ACMP-Solutions.OS Deployment.Windows Deployment.Rollout Templates.WebHome]]) and used during [[job execution>>doc:ACMP.69.ACMP-Solutions.Desktop Automation.Client Commands.Jobs ausführen.WebHome]] (collection is pushed). This allows you to perform regularly scheduled installations of Windows updates in a targeted manner. The log entry for the respective Windows Update Collection can be used to check the result.
	3	+A Windows Update Collection is a compilation of various updates consisting of selected products and classifications. The updates are stored dynamically and can be distributed via the [[containers>>doc:ACMP.68.ACMP-Solutions.Client-Management.Container.WebHome]], used to prepare new clients (via [[rollout>>doc:ACMP.68.ACMP-Solutions.OS Deployment.Rollout Templates.WebHome]]) and used during [[job execution>>doc:ACMP.68.ACMP-Solutions.Desktop Automation.Client Commands.Jobs ausführen.WebHome]] (collection is pushed). This allows you to perform regularly scheduled installations of Windows updates in a targeted manner. The log entry for the respective Windows Update Collection can be used to check the result.
4	4
5	5	You can create as many Windows Update Collections as you like, allowing you to control the distribution of updates individually. Different reboot options can be assigned to each collection, and it is also possible to manually link individual updates to an update collection.
6	6
...	...	@@ -18,7 +18,7 @@
18	18	We recommend that you pack the operating system upgrades into individual update collections. This gives you better control over when feature upgrades or in-place upgrades are performed. When linking the collection to a container, we also recommend that you offer the user a job delay so that they can help determine the timing of the upgrade.
19	19	{{/aagon.infobox}}
20	20
21		-== Add Windows Update Collection ==
	21	+== Add Windows Update Collection ==
22	22
23	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:
24	24
...	...	@@ -32,68 +32,15 @@
32	32
33	33	[[Add a new Windows Update Collection (General)>>image:67_CAWUM_Windows Update Collection hinzufügen Allgemein_832.png]]
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//.
	35	+On the next page, define a filter that includes the products and classifications that should apply to this update collection. Only the products and classifications that you previously selected using the First Steps Wizard or subsequently in the settings are displayed here. In other words, you can only assign products and classifications to a collection that you have obtained as metadata. In this example, a collection is to be created for a Windows 11 upgrade, so only the product //Windows 11// is selected in the upper part and only //Upgrades// under the classifications.
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.
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.
40		-
41		-
42		-**Continuing examples:**
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.
45		-
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//>>doc:ACMP.69.ACMP-Solutions.Client-Management.Container.Container verwalten.Arbeiten mit den Filtertypen.WebHome]].
48		-{{/box}}
49		-
50		-Examples:
51		-
52		-* "Decline all updates that contain the string %ARM64% in their name"
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 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).
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		-{{box}}
91	91	**Tip**: For a better overview, you can tick the //Display selected entries only// checkbox under the products.
92	92	{{/box}}
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"]]
	43	+[[Add Windows Update Collection (filter)>>image:67_CAWUM_Windows Update Collection hinzufügen Filter_832.png]]
97	97
98	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.
99	99