Changes for page ACMP Update

Last modified by Sabrina V. on 2026/02/25 13:58

From 3.1 to 4.1 From 7.1 to 8.1

From version 4.1

edited by Sabrina V.
on 2025/05/05 09:59

Change comment: There is no comment for this version

To version 7.1

edited by Sabrina V.
on 2026/02/16 12:41

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -28,11 +28,11 @@
  **2. Manage Updates**
--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.68.ACMP-Solutions.System.Verteilte File Repositories.WebHome||style="background-color: rgb(255, 255, 255);"]]), if you have made them available.
++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.69.ACMP-Solutions.System.Verteilte File Repositories.WebHome||style="background-color: rgb(255, 255, 255);"]]), if you have made them available.
  **3. Installing Updates**
--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.68.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]]).
++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.69.ACMP-Solutions.Client-Management.Agentenplaner.WebHome]]).
  The update process goes through several stages (//Downloaded//, //In Distribution// and //Installed//). The following status will be displayed:
@@ -45,6 +45,10 @@
  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.
  {{/aagon.infobox}}
++{{box}}
++**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.
++{{/box}}
++
  = Configure ACMP Updates =
  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.
@@ -60,10 +60,10 @@
  {{/figure}}
--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.68.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.
++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.69.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.
  {{aagon.infobox}}
--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.68.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HServer-Proxy-Konfiguration"]].
++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.69.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HServer-Proxy-Konfiguration"]].
  {{/aagon.infobox}}
  Click on //Next >// to continue with the Update settings.
@@ -96,7 +96,7 @@
  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//.
  {{figure}}
--[[image:66_Update Mechanismus_Tab Updates herunterladen_2078.png||data-xwiki-image-style-alignment="center"]]
++[[image:69_ACMP Update_Updates herunterladen_1441.png||alt="66_Update Mechanismus_Tab Updates herunterladen_2078.png" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Download Updates
@@ -112,7 +112,7 @@
  {{/aagon.warnungsbox}}
  {{figure}}
--[[image:66_Update Mechanismus_Übersicht Updates verwalten_1280.png||data-xwiki-image-style-alignment="center"]]
++[[image:69_ACMP Update_Updates verwalten_1441.png||alt="66_Update Mechanismus_Übersicht Updates verwalten_1280.png" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Overview of managed Updates
@@ -132,7 +132,7 @@
  Continue by clicking on //Integrate//.
  {{figure}}
--[[image:66_Update Mechanismus_Offline Update Integration_727.png||data-xwiki-image-style-alignment="center"]]
++[[image:69_Update Mechanismus_Offline Update Integration_727.png||alt="66_Update Mechanismus_Offline Update Integration_727.png" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Select Offline Updates
@@ -146,7 +146,7 @@
  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//.
  {{figure}}
--[[image:66_Update Mechanismus_Offline Update Integration Wizard_727.png||data-xwiki-image-style-alignment="center"]]
++[[image:69_Update Mechanismus_Offline Update Integration Wizard_727.png||alt="66_Update Mechanismus_Offline Update Integration Wizard_727.png" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Offline Update Integration of the files on the ACMP Server
@@ -170,7 +170,7 @@
  Use the //Show information// button in the ribbon bar to display the Release Notes for the relevant version.
  {{figure}}
--[[image:66_Update Mechanismus_Updates freigeben_1163.png||data-xwiki-image-style-alignment="center"]]
++[[image:69_ACMP Update_Verteile Update Version_1441.png||alt="66_Update Mechanismus_Updates freigeben_1163.png" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Distribution Update version
@@ -183,7 +183,7 @@
  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 >//.
  {{figure}}
--[[image:66_Update Mechanismus_Installationshinweise_956.png||data-xwiki-image-style-alignment="center"]]
++[[image:69_ACMP Update_Installationshinweise_956.png||alt="66_Update Mechanismus_Installationshinweise_956.png" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Installation instructions for the Update version
@@ -199,7 +199,7 @@
  Click //Next >// again.
  {{figure}}
--[[image:66_Update Mechanismus_Installationsvoraussetzungen_956.png||data-xwiki-image-style-alignment="center"]]
++[[image:69_Update Mechanismus_Installationsvoraussetzungen_956.png||alt="66_Update Mechanismus_Installationsvoraussetzungen_956.png" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Installation requirements for the Update
@@ -252,14 +252,16 @@
  Below you will find some special features that need to be considered in connection with the ACMP Updates:
  |**Speciality**|**Erklärung**
--|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.68.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]). This procedure is particularly recommended for companies that have several locations.
++|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.69.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]). This procedure is particularly recommended for companies that have several locations.
  |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.
  |Updates of other components in connection with ACMP (e.g. Web Interfaces of the Helpdesk or AESB)|(((
  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.
--You can read more info on the installations and Updates of the additional components [[here>>doc:ACMP.68.ACMP installieren.ACMP Zusatzkomponenten installieren.WebHome]].
++You can read more info on the installations and Updates of the additional components [[here>>doc:ACMP.69.ACMP installieren.ACMP Zusatzkomponenten installieren.WebHome]].
  )))
--|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.
++|Version sequence of patches|(((
++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.
++)))
  = Notes on the Update =
@@ -308,7 +308,7 @@
  **Note for installation outside the internal corporate network on agents that are to report via the ACMP Gateway:**
--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.68.ACMP-Solutions.System.Gateway.Clients.WebHome||anchor="HClient-ZertifikatfFCrdiemanuelleVerteilungerstellen"]]) and stored on the USB stick.
++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.69.ACMP-Solutions.System.Gateway.Clients.WebHome||anchor="HClient-ZertifikatfFCrdiemanuelleVerteilungerstellen"]]) and stored on the USB stick.
  {{aagon.warnungsbox}}
  This procedure does not work via the network share!