Changes for page First Steps Wizard des Windows Update Managements

Summary

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

Details

Page properties

Content

...	...	@@ -114,18 +114,14 @@
114	114
115	115	== Automatic Cleanup of Windows Updates ==
116	116
117		-Now configure the clean-up mechanism for updates under //Automatic Clean-up of Updates//. When you activate this option, specify the number of days that must pass before an update that is no longer needed is automatically rejected. Only the rejected updates are deleted from the hard drive by the clean-up job (//System// > //Settings// > //ACMP// //Server// > //Scheduled// //Server Tasks// > //Clean up Windows Update Management//).
	117	+Now configure the clean-up mechanism for updates under //Automatic Clean-up of Updates//. When this option is enabled, you can create a custom filter that automatically declines updates that are no longer needed. Only the rejected updates are deleted from the hard drive by the clean-up job (//System// > //Settings// > //ACMP// //Server// > //Scheduled// //Server Tasks// > //Clean up Windows Update Management//).
118	118
119		-An update is considered no longer needed if it has not been requested by the clients within the configured period. This function is disabled by default and must be explicitly enabled by ticking the checkbox. The default value stored here is 180 days.
	119	+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.). You can use the filter to define the automatic denial of Windows updates and determine individually, according to your criteria, what should be denied and what should not.
120	120
121		-{{aagon.infobox}}
122		-The applicability of the //Automatic Cleanup of Windows Updates// option depends primarily on whether current images are installed during initial installation (and the associated operating system, for example) or whether outdated ones must first be patched. In the latter case, the period should be as long as possible when activated (e.g. 180 days). Alternatively, the function can be left deactivated and you can reject the updates manually. If you have implemented a defined and functioning update process that, for example, provides for the rollout of current images, you can usually leave the option deactivated.
123		-{{/aagon.infobox}}
	121	+Since the update clean-up mechanism only starts once metadata is available, you can specify individual configurations for the filter at a later date (see //Settings //> //Automatic rejection//). Continue by clicking //Next >// in the wizard.
124	124
125		-[[Automatic Cleanup of Windows Updates>>image:67_CAWUM_First Steps Wizard_Seite 6_abgewählt_1015.png||alt="67_CAWUM_First Steps Wizard_Seite 6_1015.png"]]
	123	+[[Automatic Cleanup of Windows Updates>>image:69_CAWUM Automatisches Bereinigen von Update_1015.png||alt="67_CAWUM_First Steps Wizard_Seite 6_1015.png"]]
126	126
127		-Click //Next >// when you have finished the configuration.
128		-
129	129	== Clients managed by ACMP WUM ==
130	130
131	131	The //Clients managed by ACMP WUM //page lists all clients managed by ACMP. The entries listed here are all clients that have registered the ACMP server as their new Windows Update server. They now only obtain updates via the ACMP server or one of its file repositories. The automatic distribution and installation of updates takes place at a later point in time via the [[Windows Update Collections>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]], which are linked to the [[Containers>>doc:ACMP.69.ACMP-Solutions.Client-Management.Container.WebHome]]. Please note that old configurations are overwritten when a Client is added here.