Changes for page ACMP Update
Last modified by Sabrina V. on 2026/02/25 13:58
From version 8.1
edited by Sabrina V.
on 2026/02/25 13:58
on 2026/02/25 13:58
Change comment:
There is no comment for this version
To version 2.1
edited by Sabrina V.
on 2025/03/18 11:30
on 2025/03/18 11:30
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -15,7 +15,7 @@ 15 15 The Update process consists of three steps: 16 16 17 17 {{figure}} 18 -[[image:hmfile_hash_3f81bd45.png||alt=" Updateprocess" data-xwiki-image-style-alignment="center"]]18 +[[image:hmfile_hash_3f81bd45.png||alt="https://manual.aagon.com/acmp/de/61/hmfile_hash_3f81bd45.png" data-xwiki-image-style-alignment="center"]] 19 19 20 20 {{figureCaption}} 21 21 Update process of ACMP Update ... ... @@ -28,11 +28,11 @@ 28 28 29 29 **2. Manage Updates** 30 30 31 -The previously downloaded updates need to be shared. This allows the ACMP Agents to receive the pending updates and cache them locally before installing them on the ACMP Server. During this distribution, the ACMP Agents obtain the ACMP Updates independently from the distributed file repositories (see [[distributed File Repositories>>doc:ACMP.6 9.ACMP-Solutions.System.Verteilte File Repositories.WebHome||style="background-color: rgb(255, 255, 255);"]]), if you have made them available.31 +The previously downloaded updates need to be shared. This allows the ACMP Agents to receive the pending updates and cache them locally before installing them on the ACMP Server. During this distribution, the ACMP Agents obtain the ACMP Updates independently from the distributed file repositories (see [[distributed File Repositories>>doc:ACMP.66.ACMP-Solutions.System.Verteilte File Repositories.WebHome||style="background-color: rgb(255, 255, 255);"]]), if you have made them available. 32 32 33 33 **3. Installing Updates** 34 34 35 -The ACMP Updates can only be installed after the previous phases have been completed. You can conveniently initiate the installation of the Update via the ACMP Console, which initiates it on the ACMP Server. As soon as an ACMP Agent tries to log on to the ACMP Server after the Update, it will detect that it needs to update itself. It will use the locally cached or parked Update. If this is not available or is out of date, the update is downloaded from the ACMP Server (see [[Agent Tasks>>doc:ACMP.6 9.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]]).35 +The ACMP Updates can only be installed after the previous phases have been completed. You can conveniently initiate the installation of the Update via the ACMP Console, which initiates it on the ACMP Server. As soon as an ACMP Agent tries to log on to the ACMP Server after the Update, it will detect that it needs to update itself. It will use the locally cached or parked Update. If this is not available or is out of date, the update is downloaded from the ACMP Server (see [[Agent Tasks>>doc:ACMP.66.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]]). 36 36 37 37 The update process goes through several stages (//Downloaded//, //In Distribution// and //Installed//). The following status will be displayed: 38 38 ... ... @@ -45,10 +45,6 @@ 45 45 Once a user is working in the ACMP Updates plugin, it is automatically locked for other users. The lock is to prevent another download or update from being added at the same time, which could cause problems. 46 46 {{/aagon.infobox}} 47 47 48 -{{box}} 49 -**Tip**: If you find several minor releases among the Updates, you can go directly to the highest version (e.g. to go directly from version 6.9 to 6.9.2 without selecting 6.9.1 individually) that has been released for you. These will then be downloaded individually one after the other. 50 -{{/box}} 51 - 52 52 = Configure ACMP Updates = 53 53 54 54 To perform an ACMP Update, navigate to //System// > //ACMP// //Update//. When you open the menu for the first time, you will be guided through a wizard that will help you with the configuration. You can call up the wizard at a later time via the //System// > //Help// > //Display// //ACMP// //Updates// //First// //Steps// ribbon bar. ... ... @@ -64,10 +64,10 @@ 64 64 {{/figure}} 65 65 66 66 67 -On the first page, specify which proxy settings are to be used when downloading Updates. To do this, enable the //Use proxy// checkbox, otherwise the first option //Use system proxy settings// will be automatically applied. The settings refer to the information you entered under //System// > //Settings// > //ACMP// //Server// > //[[Server proxy configuration>>doc:ACMP.6 9.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HServer-Proxy-Konfiguration"]].// Enter a proxy address and the HTTP port. If the proxy uses authentication, also enable this checkbox and enter a username and password. Then test the connection and check that your entries are correct.63 +On the first page, specify which proxy settings are to be used when downloading Updates. To do this, enable the //Use proxy// checkbox, otherwise the first option //Use system proxy settings// will be automatically applied. The settings refer to the information you entered under //System// > //Settings// > //ACMP// //Server// > //[[Server proxy configuration>>doc:ACMP.66.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HServer-Proxy-Konfiguration"]].// Enter a proxy address and the HTTP port. If the proxy uses authentication, also enable this checkbox and enter a username and password. Then test the connection and check that your entries are correct. 68 68 69 69 {{aagon.infobox}} 70 -You can configure the ACMP Console so that it connects to the ACMP update service via a proxy server. Change the settings directly within the [[Server proxy configuration>>doc:ACMP.6 9.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HServer-Proxy-Konfiguration"]].66 +You can configure the ACMP Console so that it connects to the ACMP update service via a proxy server. Change the settings directly within the [[Server proxy configuration>>doc:ACMP.66.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HServer-Proxy-Konfiguration"]]. 71 71 {{/aagon.infobox}} 72 72 73 73 Click on //Next >// to continue with the Update settings. ... ... @@ -100,7 +100,7 @@ 100 100 The //Download Updates// tab lists all available Updates, their version and size, and the release notes for that version on the right. To download a new update, click the //Download// button in the ribbon bar. A new window will open showing the progress of the download. Once the Update has been downloaded, it will disappear from the list of available updates and will be listed under //Manage Updates//. 101 101 102 102 {{figure}} 103 -[[image:6 9_ACMP Update_Updates herunterladen_1441.png||alt="66_Update Mechanismus_Tab Updates herunterladen_2078.png"data-xwiki-image-style-alignment="center"]]99 +[[image:66_Update Mechanismus_Tab Updates herunterladen_2078.png||data-xwiki-image-style-alignment="center"]] 104 104 105 105 {{figureCaption}} 106 106 Download Updates ... ... @@ -116,7 +116,7 @@ 116 116 {{/aagon.warnungsbox}} 117 117 118 118 {{figure}} 119 -[[image:6 9_ACMP Update_Updates verwalten_1441.png||alt="66_Update Mechanismus_Übersicht Updates verwalten_1280.png"data-xwiki-image-style-alignment="center"]]115 +[[image:66_Update Mechanismus_Übersicht Updates verwalten_1280.png||data-xwiki-image-style-alignment="center"]] 120 120 121 121 {{figureCaption}} 122 122 Overview of managed Updates ... ... @@ -136,7 +136,7 @@ 136 136 Continue by clicking on //Integrate//. 137 137 138 138 {{figure}} 139 -[[image:6 9_Update Mechanismus_Offline Update Integration_727.png||alt="66_Update Mechanismus_Offline Update Integration_727.png" data-xwiki-image-style-alignment="center"]]135 +[[image:66_Update Mechanismus_Offline Update Integration_727.png||data-xwiki-image-style-alignment="center"]] 140 140 141 141 {{figureCaption}} 142 142 Select Offline Updates ... ... @@ -150,7 +150,7 @@ 150 150 ACMP Updates starts to integrate the Updates, going through the same steps for each ZIP file uploaded: The update signature is checked, then the ACMP Update file is transferred to the server and then the ACMP Updates are integrated on the ACMP Server. This is to ensure that only functional Updates are integrated. The integration of the Updates is only completed when all files have been successfully integrated. Exit the wizard and click //Finish//. 151 151 152 152 {{figure}} 153 -[[image:6 9_Update Mechanismus_Offline Update Integration Wizard_727.png||alt="66_Update Mechanismus_Offline Update Integration Wizard_727.png" data-xwiki-image-style-alignment="center"]]149 +[[image:66_Update Mechanismus_Offline Update Integration Wizard_727.png||data-xwiki-image-style-alignment="center"]] 154 154 155 155 {{figureCaption}} 156 156 Offline Update Integration of the files on the ACMP Server ... ... @@ -174,7 +174,7 @@ 174 174 Use the //Show information// button in the ribbon bar to display the Release Notes for the relevant version. 175 175 176 176 {{figure}} 177 -[[image:6 9_ACMP Update_Verteile Update Version_1441.png||alt="66_Update Mechanismus_Updates freigeben_1163.png"data-xwiki-image-style-alignment="center"]]173 +[[image:66_Update Mechanismus_Updates freigeben_1163.png||data-xwiki-image-style-alignment="center"]] 178 178 179 179 {{figureCaption}} 180 180 Distribution Update version ... ... @@ -187,7 +187,7 @@ 187 187 Select the version of the Update that you have previously released for distribution and click //Install//. A wizard will open to guide you through the installation. Read the installation instructions on the first page and tick the "I have read the installation instructions" box to click //Next >//. 188 188 189 189 {{figure}} 190 -[[image:6 9_ACMP Update_Installationshinweise_956.png||alt="66_Update Mechanismus_Installationshinweise_956.png"data-xwiki-image-style-alignment="center"]]186 +[[image:66_Update Mechanismus_Installationshinweise_956.png||data-xwiki-image-style-alignment="center"]] 191 191 192 192 {{figureCaption}} 193 193 Installation instructions for the Update version ... ... @@ -203,7 +203,7 @@ 203 203 Click //Next >// again. 204 204 205 205 {{figure}} 206 -[[image:6 9_Update Mechanismus_Installationsvoraussetzungen_956.png||alt="66_Update Mechanismus_Installationsvoraussetzungen_956.png" data-xwiki-image-style-alignment="center"]]202 +[[image:66_Update Mechanismus_Installationsvoraussetzungen_956.png||data-xwiki-image-style-alignment="center"]] 207 207 208 208 {{figureCaption}} 209 209 Installation requirements for the Update ... ... @@ -256,16 +256,14 @@ 256 256 Below you will find some special features that need to be considered in connection with the ACMP Updates: 257 257 258 258 |**Speciality**|**Erklärung** 259 -|Setting up deployed file repositories|Optimise the distribution of Updates in your ACMP environment by setting up distributed file repositories (see [[Distributed file repositories>>doc:ACMP.6 9.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]). This procedure is particularly recommended for companies that have several locations.255 +|Setting up deployed file repositories|Optimise the distribution of Updates in your ACMP environment by setting up distributed file repositories (see [[Distributed file repositories>>doc:ACMP.66.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]). This procedure is particularly recommended for companies that have several locations. 260 260 |Degree of distribution of Updates|The distribution level of Updates is calculated based on managed Clients. Manual Clients and Clients that have been inventoried via the OneScanClient are not taken into account. 261 261 |Updates of other components in connection with ACMP (e.g. Web Interfaces of the Helpdesk or AESB)|((( 262 262 After installing an Update of a component that is used in connection with ACMP (e.g. the Web Interface of the Helpdesk, AESB, ACMP Gateway or Notifier etc.), it may be necessary to reinstall the respective component. In such a case, you will be informed via an information dialogue. 263 263 264 -You can read more info on the installations and Updates of the additional components [[here>>doc:ACMP.6 9.ACMP installieren.ACMP Zusatzkomponenten installieren.WebHome]].260 +You can read more info on the installations and Updates of the additional components [[here>>doc:ACMP.66.ACMP installieren.ACMP Zusatzkomponenten installieren.WebHome]]. 265 265 ))) 266 -|Version sequence of patches|((( 267 -The //Manage Updates //tab displays the updates in the order in which they were released by Aagon. If several versions are available, you can install the latest one directly, provided that the updates have been integrated by then. The ACMP Agent can update directly to the target version and ACMP automatically performs the updates incrementally. 268 -))) 262 +|Version sequence of patches|The //Manage Updates// tab displays the Updates in the order in which they were released by Aagon. You must also adhere to this order during network share and installation so that they can be installed correctly. When an Update is deployed, all older Updates that have not yet been deployed are also released. The procedure for installing Updates is the same. 269 269 270 270 = Notes on the Update = 271 271 ... ... @@ -314,7 +314,7 @@ 314 314 315 315 **Note for installation outside the internal corporate network on agents that are to report via the ACMP Gateway:** 316 316 317 -The share directory can be copied to a USB stick. Launcher.exe can be executed in the usual way. If there are ZIP files in the Launcher.exe directory with the machine name and the Gateway certificates as content, the certificate for the machine will be installed. For example, a client with the machine name can first be inventoried using the Offline Scanner and then a certificate can be created for it using the Gateway plugin (//ACMP Gateway// > [[Manual Deployment>>doc:ACMP.6 9.ACMP-Solutions.System.Gateway.Clients.WebHome||anchor="HClient-ZertifikatfFCrdiemanuelleVerteilungerstellen"]]) and stored on the USB stick.311 +The share directory can be copied to a USB stick. Launcher.exe can be executed in the usual way. If there are ZIP files in the Launcher.exe directory with the machine name and the Gateway certificates as content, the certificate for the machine will be installed. For example, a client with the machine name can first be inventoried using the Offline Scanner and then a certificate can be created for it using the Gateway plugin (//ACMP Gateway// > [[Manual Deployment>>doc:ACMP.66.ACMP-Solutions.System.Gateway.Clients.WebHome||anchor="HClient-ZertifikatfFCrdiemanuelleVerteilungerstellen"]]) and stored on the USB stick. 318 318 319 319 {{aagon.warnungsbox}} 320 320 This procedure does not work via the network share!

