Changes for page Einstellungen zum Windows Update Management

Summary

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

Details

Page properties

Content

...	...	@@ -1,6 +1,6 @@
1	1	{{aagon.floatingbox/}}
2	2
3		-Within the Windows Update Management settings, you can subsequently make changes to settings already set for [[products>>doc:||anchor="HProducts"]] and [[classifications>>doc:||anchor="HClassifications"]] and configure the [[testing and release processes>>doc:||anchor="HTestandRelease"]]. This makes it possible to remove or add further products and classifications at a later date, as well as to take language adjustments into account. If your selection of hardware manufacturers is expanded, you can also include additional third-party providers at a later stage and select them via the settings and include them in the meta and setup data download.
	3	+Within the Windows Update Management settings, you can subsequently make changes to settings already set for [[products>>doc:||anchor="HProducts"]] and [[classifications>>doc:||anchor="HClassifications"]], as well as customize the automatic decline of updates and configure the [[testing and release processes>>doc:||anchor="HTestandRelease"]]. This makes it possible to remove or add further products and classifications at a later date, as well as to take language adjustments into account. If your selection of hardware manufacturers is expanded, you can also include additional third-party providers at a later stage and select them via the settings and include them in the meta and setup data download.
4	4
5	5	The settings were stored in the [[First Steps Wizard>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]] for Windows Update Management during the initial setup.
6	6
...	...	@@ -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
...	...	@@ -80,14 +80,6 @@
80	80	Be careful with the number of selected products and classifications for updates, as this can result in high storage space requirements and is equivalent to the option// Always – download all updates//.
81	81	{{/aagon.warnungsbox}}
82	82
83		-== Automatic declination of Windows Updates ==
84		-
85		-This setting allows you to specify the number of days that must pass before an update that is no longer needed is automatically rejected. You defined the number entered here during the initial configuration in the [[First Steps Wizard>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HAutomatischesBereinigenvonWindowsUpdates"]]. If you no longer wish to use this automatic function, uncheck the //Automatically reject updates// checkbox.
86		-
87		-{{aagon.infobox}}
88		-Checking this option helps ACMP to start cleaning itself after the time you have specified. Outdated updates, patches, etc. are automatically sorted out by this option. If you have implemented a functioning update process, you can leave the option deactivated.
89		-{{/aagon.infobox}}
90		-
91	91	== Automatically accept Update EULAs ==
92	92
93	93	You can use this checkbox to automatically accept any update changes to the EULAs. The EULAs will then be automatically accepted as unread without you having to read the amended terms of use.
...	...	@@ -110,8 +110,74 @@
110	110	Tick the appropriate option as required. To save your changes, click [[image:1733143922810-452.png||height="18" width="18"]]// Save//.
111	111
112	112
113		-[[Windows Update Management settings>>image:67_CAWUM Einstellungen_Optionen2_1070.png]]
	105	+[[Windows Update Management settings>>image:69_CAWUM Einstellungen_Optionen2_1070.png||alt="67_CAWUM Einstellungen_Optionen2_1070.png"]]
114	114
	107	+= Automatic declination of Updates =
	108	+
	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	+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.
	111	+
	112	+{{aagon.infobox}}
	113	+The “Last used on” field helps you to ensure that ACMP automatically starts cleaning up after the time you have specified, based on this fulfilled criterion and any continuing filter options. Outdated updates, patches, etc. are automatically sorted out using this option. If you have implemented a functioning update process, you can leave this option disabled.
	114	+{{/aagon.infobox}}
	115	+
	116	+To use the filter, you must first tick the box under //Automatic reject updates//. Then click on the button [[image:1765269883037-206.png]]//Filter for automatic reject updates//. A new wizard will open, in which you can now configure an individual filter according to which updates should be rejected in future. Helpful tips and explanations for the various filter options can be found [[here>>doc:ACMP.69.ACMP-Solutions.Client-Management.Container.Container verwalten.WebHome]].
	117	+
	118	+[[Filter for automatic decline of updates >>image:69_CAWUM_FIlter Konfiguration für das automatische Verweigern_965.png]]
	119	+
	120	+== Examples of filter configurations to decline updates ==
	121	+
	122	+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.
	123	+
	124	+{{box}}
	125	+**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]].
	126	+{{/box}}
	127	+
	128	+Examples:
	129	+
	130	+* "Decline all updates that contain the string %ARM64% in their name"
	131	+
	132	+* "All updates that have been revoked by Microsoft (expiry status IN Revoked)"
	133	+
	134	+* "All updates that have not been used for more than 180 days."
	135	+
	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	+
	138	+[[image:69_CAWUM Filter 1.png||data-xwiki-image-style-alignment="center"]]
	139	+
	140	+**Example: "Decline Microsoft Defender Antivirus updates that have not been needed for more than X days"**
	141	+
	142	+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.
	143	+
	144	+[[image:69_CAWUM Filter 2.png||data-xwiki-image-style-alignment="center"]]
	145	+
	146	+**Example: "Decline Microsoft Edge updates that are in the Beta or Dev channel"**
	147	+
	148	+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.
	149	+
	150	+[[image:69_CAWUM Filter 3.png||data-xwiki-image-style-alignment="center"]]
	151	+
	152	+**Example: "Reject Windows 11 22H2 updates"**
	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.
	155	+
	156	+[[image:69_CAWUM Filter 4.png||data-xwiki-image-style-alignment="center"]]
	157	+
	158	+**Combination of all filter options**
	159	+
	160	+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.
	161	+
	162	+[[Filter combination>>image:69_CAWUM Automatisches Verweigern Updates Beispiele_1732.png]]
	163	+
	164	+The advanced filter allows you to focus on specific environments and provide exactly the updates that meet your criteria.
	165	+
	166	+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’.
	167	+
	168	+Continue your work by displaying a preview on the second page of which Windows Updates will be automatically denied by the filter. Exit the configurations and click //Done//. Save your changes in the ribbon bar and save them.
	169	+
	170	+[[Filter for automatic decline of updates >>image:69_CAWUM Automatische Verweigerung von Windows Updates Einstellungen_993.png]]
	171	+
	172	+
115	115	= Third Party Catalogues =
116	116
117	117	Third party catalogues can also be used to obtain updates from providers other than Microsoft.
...	...	@@ -158,10 +158,22 @@
158	158	**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.
159	159	{{/box}}
160	160
161		-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.
162	162
163		-[[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}}
164	164
	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	+
165	165	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.
166	166
167	167	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.