Wiki source code of Exkurs: Der Weg vom Update zum Client
Last modified by Sabrina V. on 2025/09/22 07:38
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | An update deployed via Windows Update Management goes through several steps and requires preparation before it can be installed on a client. First, ensure that the client on which an update is to be distributed and later installed is listed under //managed by WUM// (//Windows Update Management > managed by WUM//). If the client is not yet managed by ACMP, do so (see //actions in managed by WUM//) and continue. |
| 2 | |||
| 3 | === Graphical representation of the individual steps === | ||
| 4 | |||
| 5 | [[Stations that a client must pass through for an update>>image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Der Weg vom Update zum Client.WebHome@Stationen Update Client.png]] | ||
| 6 | |||
| 7 | === Metadata download === | ||
| 8 | |||
| 9 | As soon as the administrator starts the metadata download on the Windows Update Management home page, an overview of the available products is downloaded. The download provides all the basic information about the Windows updates. The client must then be scanned. | ||
| 10 | |||
| 11 | |||
| 12 | [[image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Der Weg vom Update zum Client.WebHome@67_CAWUM_Metadaten-Download.png||data-xwiki-image-style-alignment="center"]] | ||
| 13 | |||
| 14 | === Windows Updates Scanner === | ||
| 15 | |||
| 16 | The Windows Updates Scanner is executed on the client on which an update is to be installed in future. The scanner (//Client Management// > //Agent Tasks// > //Windows Updates Scanner//) uses the metadata to check which updates are required and sends this information back to ACMP. This information can be viewed in Windows Update Management in the //Updates// tab in the grid (column: Clients required). If the scanner returns the result that the client requires an update, the number contained there increases (> 0). | ||
| 17 | |||
| 18 | [[image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Der Weg vom Update zum Client.WebHome@67_CAWUM_Agentenplaner.png||data-xwiki-image-style-alignment="center"]] | ||
| 19 | |||
| 20 | === Setup download === | ||
| 21 | |||
| 22 | The setup download can either be started manually (Dashboard //Windows Update Management// > //Status of WUM jobs//) or runs automatically at regular intervals via the server task (//System// > //settings// > //ACMP Server// > //Scheduled server tasks// > //Download Windows Update Management setup//). The setup download downloads all necessary installation resources that have been reported as needed by at least one client. You can also see whether the download was successful in the grid. Here, the content of the "Distribution status" column must now read ‘Synchronised’. | ||
| 23 | |||
| 24 | [[image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Der Weg vom Update zum Client.WebHome@67_CAWUM_Setup-Download.png||data-xwiki-image-style-alignment="center"]] | ||
| 25 | |||
| 26 | === Test and release process === | ||
| 27 | |||
| 28 | The update can only be continuing distributed once it has gone through a release process. Depending on the respective settings of the container (see next point), the update must have reached the distribution ring "Test ring 1", "Test Ring 2" or "Released". | ||
| 29 | |||
| 30 | |||
| 31 | [[image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Der Weg vom Update zum Client.WebHome@67_CAWUM_Test- und Freigabeprozes.png||data-xwiki-image-style-alignment="center"]] | ||
| 32 | |||
| 33 | === Windows Update Collections === | ||
| 34 | |||
| 35 | The update must now be added to a Windows Update Collection. The Update Collection is a collection of products and classifications for the installation of updates, which can be attached to a container later on. | ||
| 36 | |||
| 37 | |||
| 38 | [[image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Der Weg vom Update zum Client.WebHome@67_CAWUM_Collection anlegen.png||data-xwiki-image-style-alignment="center"]] | ||
| 39 | |||
| 40 | === Container === | ||
| 41 | |||
| 42 | The Windows Update Collection must now be assigned or linked to the appropriate container. Using the detailed view (//Jobs// tab), jobs can now be added via the ribbon bar. The type of job required in this case is Windows Update Collection. Windows Update will now be installed on the respective clients in accordance with the following configurations. | ||
| 43 | |||
| 44 | [[image:ACMP.67.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Der Weg vom Update zum Client.WebHome@67_CAWUM_Container.png||data-xwiki-image-style-alignment="center"]] |