Changes for page Updates und verweigerte Updates

Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.SV
	1	+XWiki.SF

Content

...	...	@@ -259,9 +259,9 @@
259	259
260	260	Confirm the dialogue box with //Yes//. This will display the selected update again in the //Updates// tab, where it will be available for you to install on the network.
261	261
262		-= Replace the distribution ring =
	262	+= Change the release process for updates =
263	263
264		-Updates that are already in a release process and have already been assigned a [[distribution ring>>distribution ring||anchor="HTestandRelease"]] (Test Ring 1 or Test Ring 2) can be manually changed to a different distribution ring using the ribbon bar or the context menu. This may be necessary, for example, if an important update needs to be moved to another ring so that it can be distributed more quickly. To do this, first select the relevant update from the grid and click on //Change distribution ring //([[image:1747373939888-917.png]]). The distribution ring editor opens, where you can now select the new distribution ring for the update. Also check that the //Automatic move items to the next distribution ring// checkbox is enabled so that this automatic function takes effect and the update is moved to the next ring at a later point in time. Exit your work by clicking //Change//. The grid view is automatically updated so that the update is assigned to the appropriate distribution ring.
	264	+Updates that are already in a release process and have already been assigned a distribution ring (Test Ring 1 or Test Ring 2) can be manually changed to a different distribution ring using the ribbon bar or the context menu. This may be necessary, for example, if an important update needs to be moved to another ring so that it can be distributed more quickly. To do this, first select the relevant update from the grid and click on //Change distribution ring //([[image:1747373939888-917.png]]). The distribution ring editor opens, where you can now select the new distribution ring for the update. Also check that the //Automatic move items to the next distribution ring// checkbox is enabled so that this automatic function takes effect and the update is moved to the next ring at a later point in time. Exit your work by clicking //Change//. The grid view is automatically updated so that the update is assigned to the appropriate distribution ring.
265	265
266	266	[[Distribution ring editor in Windows Update Management>>image:67_CAWUM_Verteilungsring wechseln_453.png]]
267	267
...	...	@@ -275,7 +275,7 @@
275	275	Please note that by setting the automatic transition mode to disabled, you are overriding the automatic update postponement feature.
276	276	{{/aagon.warnungsbox}}
277	277
278		-In principle, it is also possible to move the updates to a prior [[distribution ring>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Update Management.WebHome||anchor="HTestandRelease"]], and the change does not necessarily have to be closer to release. For example, if you want to keep an update in a test ring for longer and see if there are any changes from Microsoft, you could keep it in the test environment for longer and send it back to a test ring if you do not want to completely change the number of days configured for the process.
	278	+In principle, it is also possible to move the updates to a prior distribution ring, and the change does not necessarily have to be closer to release. For example, if you want to keep an update in a test ring for longer and see if there are any changes from Microsoft, you could keep it in the test environment for longer and send it back to a test ring if you do not want to completely change the number of days configured for the process.
279	279
280	280
281	281	= Obtain updates from the MS Catalog =
...	...	@@ -294,11 +294,6 @@
294	294
295	295	The next time Metadata download is performed, the selected updates will also be downloaded and made available to you in the ACMP Console.
296	296
297		-{{aagon.infobox}}
298		-Please note that, in general, the update must first be downloaded before the distribution ring can be changed.
299		-For the update to be downloaded in an [[On Demand configuration>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Update Management.WebHome||anchor="HUpdate-Download-Optionen"]], it must first be reported as "required" by an agent (see also [[Update Properties>>doc:||anchor="H2.EigenschaftenderUpdates"]]). To do this, simply run a [[Windows Update Scanner>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HJobsundAufgaben"]] or a [[Windows Update Collection>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]] on the affected client after adding the update.
300		-{{/aagon.infobox}}
301		-
302	302	{{box}}
303	303	**Tip**: Updates that you obtain directly from the MS Catalog are displayed within the grid in the //Origin //column with "Manual import".
304	304	{{/box}}