Last modified by Sabrina V. on 2025/12/09 08:22
From version 4.1
edited by Sabrina V.
on 2025/09/25 05:59
Change comment: There is no comment for this version
To version 6.1
edited by Sabrina V.
on 2025/12/09 08:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,7 +7,7 @@
7 7  During the initial configuration, you select the various products from Microsoft or other third party providers that you need for your work. Based on this, you can later specify which updates, classifications and languages should be selected. These will be needed later so that the Windows Update Scanner of the respective ACMP agent can decide which update is really needed for the client. This step is essential and forms the basis for all subsequent work with Windows Update Management.
8 8  
9 9  {{aagon.infobox}}
10 -You can restart the wizard at any time via the ribbon bar (either via the module under First Steps or via //System// > //Help //> //Show Windows Update Management First Steps//) or adjust the configurations in the [[system settings>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.WebHome]] if, for example, you want to add or deselect other products or change the number of days until automatic update cleanup.
10 +You can restart the wizard at any time via the ribbon bar (either via the module under First Steps or via //System// > //Help //> //Show Windows Update Management First Steps//) or adjust the configurations in the [[system settings>>doc:ACMP.69.ACMP-Solutions.System.Einstellungen.WebHome]] if, for example, you want to add or deselect other products or change the number of days until automatic update cleanup.
11 11  {{/aagon.infobox}}
12 12  
13 13  Navigate to the Windows Update Management plugin (//Patch Management// > //Windows Update Management//). The wizard opens, which prepares the initial download of the Windows Update metadata. First, under //Update server used//, select where the updates should be obtained from. The option recommended by ACMP is via the Microsoft Update Server. From version 6.6 onwards, however, it is also possible to specify a WSUS server as the source for the metadata.
... ... @@ -21,7 +21,7 @@
21 21  {{/aagon.infobox}}
22 22  )))
23 23  
24 -If you would like to include third-party providers in addition to the regular updates from Microsoft, click on [[Manage Third Party Catalogs>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Drittanbieterkataloge.WebHome]] and select the providers that are relevant to you. To do this, tick the box in front of each provider and then click on //OK//. This will ensure that the additional providers are included in the next metadata download.
24 +If you would like to include third-party providers in addition to the regular updates from Microsoft, click on [[Manage Third Party Catalogs>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Drittanbieterkataloge.WebHome]] and select the providers that are relevant to you. To do this, tick the box in front of each provider and then click on //OK//. This will ensure that the additional providers are included in the next metadata download.
25 25  
26 26  {{aagon.infobox}}
27 27  There is no need to tick the other providers if you do not use them.
... ... @@ -38,7 +38,7 @@
38 38  When selecting products, you should follow the principle of minimalism: **Only select the products that are really relevant to you!** If you select all entries, the ACMP server would become overloaded and enormous performance problems could arise. Read through the selection of products very carefully and check the entries against their exact names.
39 39  
40 40  {{box}}
41 -Learn more about the products in the chapter „[[Configuration options in Windows Update Management>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HProducts"]]“.
41 +Learn more about the products in the chapter „[[Configuration options in Windows Update Management>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HProducts"]]“.
42 42  {{/box}}
43 43  
44 44  {{aagon.infobox}}
... ... @@ -70,7 +70,7 @@
70 70  Select all classifications relevant to you that you wish to provide in the event of an update.
71 71  
72 72  {{box}}
73 -Find out more about the various classifications in the chapter "[[Configuration options in Windows Update Management>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HClassifications"]]".
73 +Find out more about the various classifications in the chapter "[[Configuration options in Windows Update Management>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HClassifications"]]".
74 74  {{/box}}
75 75  
76 76  For this procedure, all classifications were selected except for the drivers. Confirm your selection by clicking //Next >//.
... ... @@ -78,7 +78,7 @@
78 78  [[Selected classifications>>image:67_CAWUM_First Steps Wizard_Seite 3_1015.png]]
79 79  
80 80  {{box}}
81 -Read on to find out how you can determine [[which classification Microsoft assigns to an update>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Wie finde ich heraus, nach welcher Klassifizierung Microsoft ein Update einstuft?.WebHome]].
81 +Read on to find out how you can determine [[which classification Microsoft assigns to an update>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Wie finde ich heraus, nach welcher Klassifizierung Microsoft ein Update einstuft?.WebHome]].
82 82  {{/box}}
83 83  
84 84  == Languages ==
... ... @@ -114,21 +114,17 @@
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 -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.68.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]], which are linked to the [[Containers>>doc:ACMP.68.ACMP-Solutions.Client-Management.Container.WebHome]]. Please note that old configurations are overwritten when a Client is added here.
127 +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.
132 132  
133 133  {{aagon.infobox}}
134 134  If you have an evaluation licence for Windows Update Management, you can only statically link up to 15 clients. With a full licence, you can also use a dynamic filter to manage ACMP WUM clients.
... ... @@ -136,7 +136,7 @@
136 136  
137 137  You can add clients using the button [[image:1733129658182-998.png||height="18" width="18"]] by selecting a query and adding clients from the query results. Alternatively, you can also remove entries from the list of clients ([[image:1733129658183-278.png||height="18" width="18"]]).
138 138  
139 -With a full licence, you can still choose whether you want to use the [[dynamic filter>>doc:ACMP.68.ACMP-Solutions.Client-Management.Container.Container verwalten.Arbeiten mit den Filtertypen.WebHome]] to obtain even more specific results. Otherwise click on //Next >//.
135 +With a full licence, you can still choose whether you want to use the [[dynamic filter>>doc:ACMP.69.ACMP-Solutions.Client-Management.Container.Container verwalten.Arbeiten mit den Filtertypen.WebHome]] to obtain even more specific results. Otherwise click on //Next >//.
140 140  
141 141  [[Clients managed by ACMP WUM>>image:67_CAWUM_First Steps Wizard_Seite 7_1015.png]]
142 142  
... ... @@ -158,13 +158,13 @@
158 158  1. Wait for the metadata download to complete. This process may take several minutes.
159 159  1. Scan your managed clients using the Windows Update Scanner.
160 160  1*. Initiate the process manually.
161 -1*. Alternatively you can wait until the [[//Windows Updates Scanner//>>doc:ACMP.68.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]] task has been completed.
157 +1*. Alternatively you can wait until the [[//Windows Updates Scanner//>>doc:ACMP.69.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]] task has been completed.
162 162  1. Start the download for the setup download.
163 -1*. To do this, you can click on Download in the [[Status of Download Jobs>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.WebHome]] widget on the dashboard, which will start the server job //Download WIndows Update Management Setup //or
164 -1*. Go to //[[Scheduled Server Tasks>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HGeplanteServeraufgaben"]] //(System > Settings > ACMP Server > Scheduled Server Tasks) and click on the server job with the same name.
165 -1. Create a //[[Windows Update Collections>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]] //and link them to existing [[Containers>>doc:ACMP.68.ACMP-Solutions.Client-Management.Container.WebHome]] or send them directly to your clients.
166 -1*. Ensure that you have configured at least one [[File Repository>>doc:ACMP.68.ACMP-Solutions.System.Verteilte File Repositories.WebHome]] so that your clients can obtain Windows Updates from here.
167 -1*. Ensure that you have defined a properly configured [[test and release process>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Upodate Management.WebHome||anchor="HAddtestandreleaseprocess"]].
159 +1*. To do this, you can click on Download in the [[Status of Download Jobs>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.WebHome]] widget on the dashboard, which will start the server job //Download WIndows Update Management Setup //or
160 +1*. Go to //[[Scheduled Server Tasks>>doc:ACMP.69.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HGeplanteServeraufgaben"]] //(System > Settings > ACMP Server > Scheduled Server Tasks) and click on the server job with the same name.
161 +1. Create a //[[Windows Update Collections>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]] //and link them to existing [[Containers>>doc:ACMP.69.ACMP-Solutions.Client-Management.Container.WebHome]] or send them directly to your clients.
162 +1*. Ensure that you have configured at least one [[File Repository>>doc:ACMP.69.ACMP-Solutions.System.Verteilte File Repositories.WebHome]] so that your clients can obtain Windows Updates from here.
163 +1*. Ensure that you have defined a properly configured [[test and release process>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Update Management.WebHome||anchor="HAddtestandreleaseprocess"]].
168 168  
169 169  {{aagon.warnungsbox}}
170 170  Please note that updates for Office 365 Apps products can only be successfully performed if the applications are closed beforehand. If this is not the case, the Office update will fail.
© Aagon GmbH 2026
Besuchen Sie unsere Aagon-Community