Last modified by Sabrina V. on 2025/12/09 08:22
Show last authors
1 {{aagon.floatingbox/}}
2
3 = Running the First Steps Wizard =
4
5 In order to use the //Windows Update Management //module, you must first run the First Steps Wizard. This starts automatically and guides you step by step through the wizard when you click on the module in the ACMP Console for the first time.
6
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
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.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 {{/aagon.infobox}}
12
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.
14
15 |Microsoft Update Server|If your ACMP server has an internet connection, Aagon recommends using the Microsoft Update Server. This will provide you with all relevant updates directly from the current server.
16 |WSUS or other compatible USS|(((
17 Not all functions are supported when using WSUS or another upstream server (USS). For example, WSUS does not support apps from Microsoft 365, Office 2019 or Office LTSC.
18
19 {{aagon.infobox}}
20 If you still choose this option, you must enter the corresponding server URL in the field below so that the data can be retrieved.
21 {{/aagon.infobox}}
22 )))
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.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
26 {{aagon.infobox}}
27 There is no need to tick the other providers if you do not use them.
28 {{/aagon.infobox}}
29
30 Click on [[image:1733127031542-391.png||height="24" width="20"]] //Download Windows Update metadata. //The download may take a few minutes, as the Microsoft catalog is downloaded in the background. Once the download is complete, the view will change (//"Download complete, please continue"//) and you can click on //Next > //to proceed to the next page.
31
32 [[Initial download of Windows Update metadata>>image:68_CAWUM_First Steps Wizard_Seite 1_1015.png||alt="67_CAWUM_First Steps Wizard_Seite 1a_1015.png"]]
33
34 == Products ==
35
36 Now select all products for which you want to provide updates. The entries listed here are provided based on the official designation by Microsoft or third-party providers and are only available with a description in English or as published by the manufacturers.
37
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
40 {{box}}
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 {{/box}}
43
44 {{aagon.infobox}}
45 The list of products is continuously updated by Microsoft and third party vendors and may change from time to time.
46 {{/aagon.infobox}}
47
48 Carefully check the entries you have selected. For greater clarity, use the //Show selected entries only// checkbox at the bottom to ensure that your list is complete and correct.
49
50 The following products are selected for the subsequent tasks:
51
52 * //Microsoft// > //Office// > //Microsoft 365 Apps/Office 2019/Office LTSC//
53 * //Microsoft// > //Windows// > //Microsoft Defender Antivirus//
54 * //Microsoft// > //Windows// > //Microsoft// //Edge//
55 * //Microsoft// > //Windows// > //Windows 10, version 1903 and later//
56 * //Microsoft// > //Windows// > //Windows 11//
57
58 Then click //Next >// and continue with the classifications you want to provide.
59
60 [[Selected products>>image:67_CAWUM_First Steps Wizard_Update Produkte_1015.png]]
61
62 == Classifications ==
63
64 Classifications are required to define and synchronise the previously selected products according to the various classifications. This allows software updates to be assigned to and organised according to the respective types of updates. During the synchronisation process, all metadata for the selected software is synchronised for the specified classifications. Microsoft distinguishes between the following classifications: //Critical Updates, Definition Updates, Drivers, Feature Packs, Security Updates, Service Packs, Tools, Update Rollups, Updates// and //Upgrades//.
65
66 {{aagon.infobox}}
67 The entries are provided by Microsoft and are not translated in the ACMP Console.
68 {{/aagon.infobox}}
69
70 Select all classifications relevant to you that you wish to provide in the event of an update.
71
72 {{box}}
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 {{/box}}
75
76 For this procedure, all classifications were selected except for the drivers. Confirm your selection by clicking //Next >//.
77
78 [[Selected classifications>>image:67_CAWUM_First Steps Wizard_Seite 3_1015.png]]
79
80 {{box}}
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 {{/box}}
83
84 == Languages ==
85
86 On the next page of the wizard, specify the languages in which you want to provide updates. Tick the appropriate entries and, for a better overview, click on //Show selected entries only// again.
87
88 {{aagon.infobox}}
89 The entry "English" is required for language-independent updates to be carried out correctly. Select this entry as well so that the entries are displayed correctly.
90 {{/aagon.infobox}}
91
92 [[Languages>>image:67_CAWUM_First Steps Wizard_Seite 4_1015.png]]
93
94 Continue by clicking on //Next >//.
95
96 {{aagon.infobox}}
97 If you have selected //Microsoft 365 Apps/Office 2019/Office LTSC// from the products, the wizard will expand to include an additional page.
98 {{/aagon.infobox}}
99
100 On the //Microsoft 365 App Languages //wizard page, you can select additional languages exclusively for the apps. To do this, tick the appropriate checkboxes as required, as well as if you want to include additional correction aids. The additional languages include all languages that are required in addition to the standard languages, but for which updates are not to be carried out in that language. These are divided into three types:
101
102 |(% style="width:196px" %)**Type**|(% style="width:1496px" %)**Meaning**
103 |(% style="width:196px" %)Complete|(% style="width:1496px" %)The entire Office interface is translated into the additional language.
104 |(% style="width:196px" %)Partial|(% style="width:1496px" %)The Office interface is only partially translated. Some language elements are still in the other language.
105 |(% style="width:196px" %)Document verification|(% style="width:1496px" %)Only the spell checker is provided in the additional language.
106
107 {{aagon.infobox}}
108 The correction tools include spelling and grammar checks, hyphenation and auto-correction for the selected language. For example, if you have selected updates in German but have texts in French, the correction tool will only be installed for these texts in the language selected here.
109 {{/aagon.infobox}}
110
111 If you do not wish to select any additional languages, click //Next > //and skip this page.
112
113 [[Languages for Microsoft 365 Apps>>image:67_CAWUM_First Steps Wizard_Seite 5_1015.png]]
114
115 == Automatic Cleanup of Windows Updates ==
116
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
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
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.
122
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"]]
124
125 == Clients managed by ACMP WUM ==
126
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.
128
129 {{aagon.infobox}}
130 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.
131 {{/aagon.infobox}}
132
133 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"]]).
134
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 >//.
136
137 [[Clients managed by ACMP WUM>>image:67_CAWUM_First Steps Wizard_Seite 7_1015.png]]
138
139 On the last page, you will find a summary of the ACMP Windows Update Management First Steps Wizard. Here you will find information about what happens after the wizard has finished in the //Windows Update Management //plugin.
140
141 The summary states, among other things, that ...
142
143 * next, all required Windows updates will be downloaded via the metadata, which may take some time.
144 * You can then start defining Windows Update Collections and assign them to a container so that the clients receive the updates.
145
146 Read the entire summary carefully and then close the wizard by clicking //Finish//.
147
148 [[Summary of the Windows Update Management Wizard>>image:67_CAWUM_First Steps Wizard_Seite 8_1015.png]]
149
150 === Next steps ===
151
152 Once you have completed the First Steps Wizard for Windows Update Management, you can now follow these steps:
153
154 1. Wait for the metadata download to complete. This process may take several minutes.
155 1. Scan your managed clients using the Windows Update Scanner.
156 1*. Initiate the process manually.
157 1*. Alternatively you can wait until the [[//Windows Updates Scanner//>>doc:ACMP.69.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]] task has been completed.
158 1. Start the download for the setup download.
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"]].
164
165 {{aagon.warnungsbox}}
166 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.
167 {{/aagon.warnungsbox}}
© Aagon GmbH 2025
Besuchen Sie unsere Aagon-Community