Changes for page Einstellungen zum Windows Update Management

Summary

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

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
...	...	@@ -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.