Skip to Content

Changes for page acmp Update

Last modified by Sabrina V. on 2026/10/06 11:18
From version 12.1
edited by Sabrina V.
on 2026/10/06 11:18
Change comment: There is no comment for this version
To version 9.1
edited by Sabrina V.
on 2026/06/09 10:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -acmp Update
1 +ACMP Update
Content
... ... @@ -6,43 +6,43 @@
6 6  
7 7  = General =
8 8  
9 -acmp Update is used to distribute, manage and install acmp Updates. You can use the plugin to view all available updates, download them directly and distribute them.
9 +ACMP Update is used to distribute, manage and install ACMP Updates. You can use the plugin to view all available updates, download them directly and distribute them.
10 10  
11 11  {{aagon.infobox}}
12 -acmp Updates can only be used with valid licences. You also need a valid contract for Updates and support.
12 +ACMP Updates can only be used with valid licences. You also need a valid contract for Updates and support.
13 13  {{/aagon.infobox}}
14 14  
15 15  The Update process consists of three steps:
16 16  
17 17  {{figure}}
18 -[[image:hmfile_hash_3f81bd45.png||alt="Update process" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
18 +[[image:hmfile_hash_3f81bd45.png||alt="Update process" data-xwiki-image-style-alignment="center"]]
19 19  
20 20  {{figureCaption}}
21 -Update process of acmp Update
21 +Update process of ACMP Update
22 22  {{/figureCaption}}
23 23  {{/figure}}
24 24  
25 25  **~1. Download Updates**
26 26  
27 -Updates are first downloaded from the Aagon web server using the acmp console and stored on the acmp server. The acmp console needs internet access for this.
27 +Updates are first downloaded from the Aagon web server using the ACMP console and stored on the ACMP server. The ACMP console needs internet access for this.
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.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]), 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.610.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.610.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.610.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  
39 39  |(% style="width:155px" %)**Status**|(% style="width:1209px" %)**Meaning**
40 -|(% style="width:155px" %)Downloaded|(% style="width:1209px" %)The Update has been downloaded from the Aagon update server and saved on the acmp Server.
41 -|(% style="width:155px" %)In Distribution|(% style="width:1209px" %)The Update is released for distribution and can be deployed to the acmp Clients.
42 -|(% style="width:155px" %)Installed|(% style="width:1209px" %)The Update has been installed on the acmp Server. The installation on the acmp Clients is started as soon as the Client has all update files and logs on to the acmp Server.
40 +|(% style="width:155px" %)Downloaded|(% style="width:1209px" %)The Update has been downloaded from the Aagon update server and saved on the ACMP Server.
41 +|(% style="width:155px" %)In Distribution|(% style="width:1209px" %)The Update is released for distribution and can be deployed to the ACMP Clients.
42 +|(% style="width:155px" %)Installed|(% style="width:1209px" %)The Update has been installed on the ACMP Server. The installation on the ACMP Clients is started as soon as the Client has all update files and logs on to the ACMP Server.
43 43  
44 44  {{aagon.infobox}}
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.
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 48  {{box}}
... ... @@ -49,51 +49,51 @@
49 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 50  {{/box}}
51 51  
52 -= Configure acmp Updates =
52 += Configure ACMP Updates =
53 53  
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.
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.
55 55  
56 -The following diagram illustrates the steps you need to take before an Update can be deployed to your Agent or one of your Clients. Click on //Configure acmp Updates// to open the First Steps Wizard.
56 +The following diagram illustrates the steps you need to take before an Update can be deployed to your Agent or one of your Clients. Click on //Configure ACMP Updates// to open the First Steps Wizard.
57 57  
58 58  {{figure}}
59 -[[image:66_ACMP Update Konfiguration_879.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
59 +[[image:66_ACMP Update Konfiguration_879.png||data-xwiki-image-style-alignment="center"]]
60 60  
61 61  {{figureCaption}}
62 -acmp Update Configuration
62 +ACMP Update Configuration
63 63  {{/figureCaption}}
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.610.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HServerproxyconfiguration"]].// 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.
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.610.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.610.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HScheduledServerTasks"]].
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.610.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.
74 74  
75 75  {{figure}}
76 -[[image:66_Update Mechanismus_First Steps Wizard 1_843.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
76 +[[image:66_Update Mechanismus_First Steps Wizard 1_843.png||data-xwiki-image-style-alignment="center"]]
77 77  
78 78  {{figureCaption}}
79 -Proxy settings of the acmp Update First Steps Wizard
79 +Proxy settings of the ACMP Update First Steps Wizard
80 80  {{/figureCaption}}
81 81  {{/figure}}
82 82  
83 -Specify the intervals at which the acmp Console should automatically find new Updates. Enter your interval in days; the default value here is to find new Updates every five days. Tick the box //Show info dialog in case of new Updates// if you also want to be informed. A dialogue will inform you about new Updates when you start the acmp Console. Otherwise, if Updates are available, a warning triangle is always displayed in the navigation next to acmp Updates. Click on //Finish// to close the wizard.
83 +Specify the intervals at which the ACMP Console should automatically find new Updates. Enter your interval in days; the default value here is to find new Updates every five days. Tick the box //Show info dialog in case of new Updates// if you also want to be informed. A dialogue will inform you about new Updates when you start the ACMP Console. Otherwise, if Updates are available, a warning triangle is always displayed in the navigation next to ACMP Updates. Click on //Finish// to close the wizard.
84 84  
85 85  {{figure}}
86 -[[image:66_Update Mechanismus_First Steps Wizard 2_843.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
86 +[[image:66_Update Mechanismus_First Steps Wizard 2_843.png||data-xwiki-image-style-alignment="center"]]
87 87  
88 88  {{figureCaption}}
89 -Update settings in the acmp Updates First Steps Wizard
89 +Update settings in the ACMP Updates First Steps Wizard
90 90  {{/figureCaption}}
91 91  {{/figure}}
92 92  
93 -You have finished the initial configuration for the acmp Updates.
93 +You have finished the initial configuration for the ACMP Updates.
94 94  
95 95  
96 -After successful setup, the acmp Updates is divided into three tabs~:// //[[Download Updates>>doc:||anchor="HDownloadUpdates"]], //[[Manage Updates>>doc:||anchor="HManageUpdates"]] //und [[Configuration>>doc:||anchor="HConfiguration"]].
96 +After successful setup, the ACMP Updates is divided into three tabs~:// //[[Download Updates>>doc:||anchor="HUpdatesherunterladen"]], //[[Manage Updates>>doc:||anchor="HUpdatesverwalten"]] //und [[Configuration>>doc:||anchor="HKonfiguration"]].
97 97  
98 98  == Download Updates ==
99 99  
... ... @@ -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:69_ACMP Update_Updates herunterladen_1441.png||alt="66_Update Mechanismus_Tab Updates herunterladen_2078.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
103 +[[image:69_ACMP Update_Updates herunterladen_1441.png||alt="66_Update Mechanismus_Tab Updates herunterladen_2078.png" data-xwiki-image-style-alignment="center"]]
104 104  
105 105  {{figureCaption}}
106 106  Download Updates
... ... @@ -109,7 +109,7 @@
109 109  
110 110  == Manage Updates ==
111 111  
112 -The //Manage Updates// tab provides various information about the updates: In addition to the version number, the status (//Downloaded//, //Installed// and //In Distribution//) is displayed, as well as the Distribution Level and Distribution Information. The Distribution degree shows the progress of the Distribution using a progress bar and a percentage. The Distribution Information shows how many Clients have already cached or parked the Update (this information can also be accessed via the „Parked acmp Updates“ display field). The Distribution start and Installation dates give you a time component of when which Update was put into circulation. These historical dates allow you to track certain workflows at a much later date. If you have a large number of updates installed, you can use the search field and filter by specific version numbers. The ribbon bar can be used to distribute and install Updates, or to view information about selected versions (Release Notes). You can use the button provided to integrate Updates offline.
112 +The //Manage Updates// tab provides various information about the updates: In addition to the version number, the status (//Downloaded//, //Installed// and //In Distribution//) is displayed, as well as the Distribution Level and Distribution Information. The Distribution degree shows the progress of the Distribution using a progress bar and a percentage. The Distribution Information shows how many Clients have already cached or parked the Update (this information can also be accessed via the „Parked ACMP Updates“ display field). The Distribution start and Installation dates give you a time component of when which Update was put into circulation. These historical dates allow you to track certain workflows at a much later date. If you have a large number of updates installed, you can use the search field and filter by specific version numbers. The ribbon bar can be used to distribute and install Updates, or to view information about selected versions (Release Notes). You can use the button provided to integrate Updates offline.
113 113  
114 114  {{aagon.warnungsbox}}
115 115  Please note that Offline Update integration should only be used in exceptional cases and that you should always opt for downloading online Updates.
... ... @@ -116,7 +116,7 @@
116 116  {{/aagon.warnungsbox}}
117 117  
118 118  {{figure}}
119 -[[image:69_ACMP Update_Updates verwalten_1441.png||alt="66_Update Mechanismus_Übersicht Updates verwalten_1280.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
119 +[[image:69_ACMP Update_Updates verwalten_1441.png||alt="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
... ... @@ -125,9 +125,9 @@
125 125  
126 126  === Integrate Offline Updates ===
127 127  
128 -Click on //Integrate Offline Updates// in the ribbon bar. A wizard will open where you can insert the ZIP files so that acmp can read them as offline Updates. To do this, click on the plus icon ([[image:Update-Datei der Liste hinzufügen Icon.png||data-cmp-info="10" height="23" width="23"]]) and select all the ZIP files in your Updates directory that you want to insert into the system.
128 +Click on //Integrate Offline Updates// in the ribbon bar. A wizard will open where you can insert the ZIP files so that ACMP can read them as offline Updates. To do this, click on the plus icon ([[image:Update-Datei der Liste hinzufügen Icon.png||height="23" width="23"]]) and select all the ZIP files in your Updates directory that you want to insert into the system.
129 129  
130 -Click on //Open// to close the window and return to the wizard where the selected files are located. To remove any of the files, select an entry and click ([[image:Ausgewählte Update-Dateien aus der Liste entfernen Icon.png||data-cmp-info="10" height="23" width="23"]]) or press //Delete//.
130 +Click on //Open// to close the window and return to the wizard where the selected files are located. To remove any of the files, select an entry and click ([[image:Ausgewählte Update-Dateien aus der Liste entfernen Icon.png||height="23" width="23"]]) or press //Delete//.
131 131  
132 132  {{aagon.infobox}}
133 133  Please note that the .cat files must be located next to the ZIP files for correct integration. The name of the two files must be identical, only the extension may be different. Also avoid renaming the files.
... ... @@ -136,7 +136,7 @@
136 136  Continue by clicking on //Integrate//.
137 137  
138 138  {{figure}}
139 -[[image:69_Update Mechanismus_Offline Update Integration_727.png||alt="66_Update Mechanismus_Offline Update Integration_727.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
139 +[[image:69_Update Mechanismus_Offline Update Integration_727.png||alt="66_Update Mechanismus_Offline Update Integration_727.png" data-xwiki-image-style-alignment="center"]]
140 140  
141 141  {{figureCaption}}
142 142  Select Offline Updates
... ... @@ -147,13 +147,13 @@
147 147  To ensure successful integration of Updates, all required previous versions must always be pre-installed. A security dialogue will inform you if a version is missing. The installation will start if the window continues, otherwise the integration of the Updates will fail.
148 148  {{/aagon.infobox}}
149 149  
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//.
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:69_Update Mechanismus_Offline Update Integration Wizard_727.png||alt="66_Update Mechanismus_Offline Update Integration Wizard_727.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
153 +[[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"]]
154 154  
155 155  {{figureCaption}}
156 -Offline Update Integration of the files on the acmp Server
156 +Offline Update Integration of the files on the ACMP Server
157 157  {{/figureCaption}}
158 158  {{/figure}}
159 159  
... ... @@ -162,19 +162,19 @@
162 162  === Distributing Updates ===
163 163  
164 164  {{aagon.infobox}}
165 -Before you start distributing Updates, you should make backups. Read here (Verlinkung) how to perform an acmp backup.
165 +Before you start distributing Updates, you should make backups. Read here (Verlinkung) how to perform an ACMP backup.
166 166  {{/aagon.infobox}}
167 167  
168 168  Before you can distribute an Update, you must first download the appropriate version. Start by selecting the required version from the downloaded entries and click on it. Click on //Distribute// in the ribbon bar. A dialogue box opens, which you must confirm in order to start deploying an update. The Distribution will start and the status will change (//Downloaded// > //In Distribution//) and you can see from the Distribution Information how many Clients the Update has already been parked on.
169 169  
170 170  {{aagon.infobox}}
171 -You can use the “Parked acmp Updates“ display field in Query Management to see which acmp Agents already have the Update locally and which do not.
171 +You can use the “Parked ACMP Updates“ display field in Query Management to see which ACMP Agents already have the Update locally and which do not.
172 172  {{/aagon.infobox}}
173 173  
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:69_ACMP Update_Verteile Update Version_1441.png||alt="66_Update Mechanismus_Updates freigeben_1163.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
177 +[[image:69_ACMP Update_Verteile Update Version_1441.png||alt="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:69_ACMP Update_Installationshinweise_956.png||alt="66_Update Mechanismus_Installationshinweise_956.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
190 +[[image:69_ACMP Update_Installationshinweise_956.png||alt="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
... ... @@ -194,7 +194,7 @@
194 194  {{/figureCaption}}
195 195  {{/figure}}
196 196  
197 -acmp checks the necessary requirements for a successful installation in the background. The wizard can only continue if all criteria are met. The installation requirements include the presence of all update files, acmp support for SQL Server, acmp compatibility with SQL Server and acmp access to the database.
197 +ACMP checks the necessary requirements for a successful installation in the background. The wizard can only continue if all criteria are met. The installation requirements include the presence of all update files, ACMP support for SQL Server, ACMP compatibility with SQL Server and ACMP access to the database.
198 198  
199 199  {{aagon.infobox}}
200 200  If the prerequisites are not met, you must take the necessary measures and precautions. If necessary, update the SQL Server or check your antivirus software for missing files and restore the files.
... ... @@ -203,7 +203,7 @@
203 203  Click //Next >// again.
204 204  
205 205  {{figure}}
206 -[[image:69_Update Mechanismus_Installationsvoraussetzungen_956.png||alt="66_Update Mechanismus_Installationsvoraussetzungen_956.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
206 +[[image:69_Update Mechanismus_Installationsvoraussetzungen_956.png||alt="66_Update Mechanismus_Installationsvoraussetzungen_956.png" data-xwiki-image-style-alignment="center"]]
207 207  
208 208  {{figureCaption}}
209 209  Installation requirements for the Update
... ... @@ -210,10 +210,10 @@
210 210  {{/figureCaption}}
211 211  {{/figure}}
212 212  
213 -You must check the checkboxes for verification before you can start the installation. The three checkboxes assume that you have done all the necessary preparations for installing an acmp Update. This includes that you have saved a new and functional [[backup of the acmp database>>doc:.Use Cases für Updates.Ein vollständiges ACMP Backup durchführen.WebHome]] and the [[acmp Server directory>>doc:.Use Cases für Updates.Ein vollständiges ACMP Backup durchführen.WebHome||anchor="HBackupoftheACMPserverdirectory"]] and that you are satisfied with the agent distribution level.
213 +You must check the checkboxes for verification before you can start the installation. The three checkboxes assume that you have done all the necessary preparations for installing an ACMP Update. This includes that you have saved a new and functional [[backup of the ACMP database>>doc:.Use Cases für Updates.Ein vollständiges ACMP Backup durchführen.WebHome]] and the [[ACMP Server directory>>doc:.Use Cases für Updates.Ein vollständiges ACMP Backup durchführen.WebHome||anchor="HSicherungdesACMPSerververzeichnissesvornehmen"]] and that you are satisfied with the agent distribution level.
214 214  
215 215  {{figure}}
216 -[[image:66_Update Mechanismus_Verifizierung_956.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
216 +[[image:66_Update Mechanismus_Verifizierung_956.png||data-xwiki-image-style-alignment="center"]]
217 217  
218 218  {{figureCaption}}
219 219  Verification of the installation preparations
... ... @@ -222,10 +222,10 @@
222 222  
223 223  Finally, click on //Install//.
224 224  
225 -The Updates will now be installed on the acmp Server. As soon as the Update is finished, close the information window and the acmp Console will restart automatically.
225 +The Updates will now be installed on the ACMP Server. As soon as the Update is finished, close the information window and the ACMP Console will restart automatically.
226 226  
227 227  {{figure}}
228 -[[image:66_Update Mechanismus_Installation des Updates_534.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
228 +[[image:66_Update Mechanismus_Installation des Updates_534.png||data-xwiki-image-style-alignment="center"]]
229 229  
230 230  {{figureCaption}}
231 231  Information window after a successfully installed Update
... ... @@ -232,7 +232,7 @@
232 232  {{/figureCaption}}
233 233  {{/figure}}
234 234  
235 -Log in to the acmp Console again to download the Updates and install the new version on your Client.
235 +Log in to the ACMP Console again to download the Updates and install the new version on your Client.
236 236  
237 237  
238 238  == Configuration ==
... ... @@ -240,11 +240,11 @@
240 240  The configurations allow you to store proxy and update settings that will be taken into account during the update process. You will have already configured all of the following settings when you run the wizard for the first time. This tab is used to make subsequent changes, such as the time interval for finding new updates or different ports and proxy settings.
241 241  
242 242  |(% style="width:161px" %)**Section**|(% style="width:1203px" %)**Description**
243 -|(% style="width:161px" %)Proxy settings|You can use the connection properties to configure a proxy Server through which the acmp Console connects to the Aagon Update Server. To do this, check the //Use proxy// box and select one of the available options (//Use system proxy settings// or //Manual proxy configuration//). In the case of manual proxy configuration, enter the proxy address and proxy HTTP port. If the proxy uses authentication, also select this check box and enter a user name and password. Then test the connection and check that your entries are correct.
244 -|(% style="width:161px" %)Update settings|Configure an interval after which the acmp Console should automatically find new Updates (specified in days). Check the box //Show info dialog in case of new Updates// if you also want to be informed.
243 +|(% style="width:161px" %)Proxy settings|You can use the connection properties to configure a proxy Server through which the ACMP Console connects to the Aagon Update Server. To do this, check the //Use proxy// box and select one of the available options (//Use system proxy settings// or //Manual proxy configuration//). In the case of manual proxy configuration, enter the proxy address and proxy HTTP port. If the proxy uses authentication, also select this check box and enter a user name and password. Then test the connection and check that your entries are correct.
244 +|(% style="width:161px" %)Update settings|Configure an interval after which the ACMP Console should automatically find new Updates (specified in days). Check the box //Show info dialog in case of new Updates// if you also want to be informed.
245 245  
246 246  {{figure}}
247 -[[image:66_ACMP Update Konfiguration_Einstellung.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
247 +[[image:66_ACMP Update Konfiguration_Einstellung.png||data-xwiki-image-style-alignment="center"]]
248 248  
249 249  {{figureCaption}}
250 250  Update configuration
... ... @@ -251,41 +251,41 @@
251 251  {{/figureCaption}}
252 252  {{/figure}}
253 253  
254 -= Special features of the acmp Updates =
254 += Special features of the ACMP Updates =
255 255  
256 -Below you will find some special features that need to be considered in connection with the acmp Updates:
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.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]). This procedure is particularly recommended for companies that have several locations.
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.610.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 -|Updates of other components in connection with acmp (e.g. Web Interfaces of the Helpdesk or aesb)|(((
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.
261 +|Updates of other components in connection with ACMP (e.g. Web Interfaces of the Helpdesk or AESB)|(((
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 264  You can read more info on the installations and Updates of the additional components [[here>>doc:ACMP.610.ACMP installieren.ACMP Zusatzkomponenten installieren.WebHome]].
265 265  )))
266 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.
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 268  )))
269 269  
270 270  = Notes on the Update =
271 271  
272 -In preparation for an Update, you should first disable any additional acmp components that may be present. This includes the following examples:
272 +In preparation for an Update, you should first disable any additional ACMP components that may be present. This includes the following examples:
273 273  
274 -* acmp AD Agent
275 -* acmp AD Connector
276 -* acmp Data Gateway
277 -* acmp Data Proxy
278 -* acmp Notifier
279 -* acmp WMI Scanner
280 -* acmp XML Importer
274 +* ACMP AD Agent
275 +* ACMP AD Connector
276 +* ACMP Data Gateway
277 +* ACMP Data Proxy
278 +* ACMP Notifier
279 +* ACMP WMI Scanner
280 +* ACMP XML Importer
281 281  * Contact Adapter
282 282  * Container Adapter
283 283  * Network Boot Service
284 284  
285 -Next, create a backup of the acmp database. Detailed instructions on how to create a backup can be found [[here>>doc:.Use Cases für Updates.WebHome]]. Also backup the acmp Server directory ~(%PROGRAMFILES%\ACMP), the acmp settings from the registry (HKEY_LOCAL_MACHINE\SOFTWARE\AAGON or HKEY_LOCAL_MACHINE\Wow6432Node\AAGON) and any remote file repositories.
285 +Next, create a backup of the ACMP database. Detailed instructions on how to create a backup can be found [[here>>doc:.Use Cases für Updates.WebHome]]. Also backup the ACMP Server directory ~(%PROGRAMFILES%\ACMP), the ACMP settings from the registry (HKEY_LOCAL_MACHINE\SOFTWARE\AAGON or HKEY_LOCAL_MACHINE\Wow6432Node\AAGON) and any remote file repositories.
286 286  
287 287  (% style="text-align:center" %)
288 -[[image:sqlserver_db_backup.png||alt="SQLServer_DB_Backup" data-cmp-info="10" height="377" width="539"]]
288 +[[image:sqlserver_db_backup.png||alt="SQLServer_DB_Backup" height="377" width="539"]]
289 289  Backing up the database using SQL Server Management Studio
290 290  
291 291  
... ... @@ -292,14 +292,14 @@
292 292  Also check the following:
293 293  
294 294  * Is there enough disk space available for the Update?
295 -* Are all users logged out of the acmp console, or have they closed the Console?
295 +* Are all users logged out of the ACMP console, or have they closed the Console?
296 296  * Is the virus scanner temporarily disabled for the Update to ensure a smooth process?
297 297  
298 298  {{aagon.infobox}}
299 -If the Update includes a client component, you should ensure that your update locations are set up correctly prior to the update, and that you have a sufficiently high distribution level for the Update. This will prevent a large increase in network load during the Update. The settings for this can be found in the acmp Console under //System// > //acmp Updates// > //Configuration// and under //System// > //Distributed File Repositories//.
299 +If the Update includes a client component, you should ensure that your update locations are set up correctly prior to the update, and that you have a sufficiently high distribution level for the Update. This will prevent a large increase in network load during the Update. The settings for this can be found in the ACMP Console under //System// > //ACMP Updates// > //Configuration// and under //System// > //Distributed File Repositories//.
300 300  {{/aagon.infobox}}
301 301  
302 -Also make sure that you do not run the update at times of high load when the acmp Server is running other tasks in addition to the acmp service.
302 +Also make sure that you do not run the update at times of high load when the ACMP Server is running other tasks in addition to the ACMP service.
303 303  
304 304  
305 305  = Manual Agent installation using the Launcher.exe =
... ... @@ -310,11 +310,11 @@
310 310  
311 311  **Note for missing administrator rights:**
312 312  
313 -If you do not have administrator rights to run the agent installation, the Launcher.exe will contact the Server and initiate a server-side push process if [[configured>>doc:||anchor="HManageUpdates"]].
313 +If you do not have administrator rights to run the agent installation, the Launcher.exe will contact the Server and initiate a server-side push process if [[configured>>doc:||anchor="HUpdatesverwalten"]].
314 314  
315 -**Note for installation outside the internal corporate network on agents that are to report via the acmp Gateway:**
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.610.ACMP-Solutions.System.Gateway.Clients.WebHome||anchor="HCreateaClientCertificateforManualDeployment"]]) and stored on the USB stick.
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.610.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!
... ... @@ -321,12 +321,12 @@
321 321  {{/aagon.warnungsbox}}
322 322  
323 323  
324 -= acmp Console Update Service in the Windows system service =
324 += ACMP Console Update Service in the Windows system service =
325 325  
326 -With acmp version 6.6.0 there is a new service that you can use to manage the acmp Console Updates service. Open the command prompt on the PC by pressing the [Windows] and [R] keys simultaneously. The „Run“ command opens. Type services.msc and confirm with OK. Locate the above service in the list. In general, the service ensures that consoles can be updated even without the appropriate rights. The update service runs in the background while the update is being downloaded. If you have administrator rights, you can //exit//, //stop// or //restart// the service from the left hand pages, otherwise the service will only be visible to all other users.
326 +With ACMP version 6.6.0 there is a new service that you can use to manage the ACMP Console Updates service. Open the command prompt on the PC by pressing the [Windows] and [R] keys simultaneously. The „Run“ command opens. Type services.msc and confirm with OK. Locate the above service in the list. In general, the service ensures that consoles can be updated even without the appropriate rights. The update service runs in the background while the update is being downloaded. If you have administrator rights, you can //exit//, //stop// or //restart// the service from the left hand pages, otherwise the service will only be visible to all other users.
327 327  
328 328  {{figure}}
329 -[[image:66_Dienste_ACMP Console Update Service_951.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
329 +[[image:66_Dienste_ACMP Console Update Service_951.png||data-xwiki-image-style-alignment="center"]]
330 330  
331 331  {{figureCaption}}
332 332  Windows services for the ACMP Console Update Service
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community