Skip to Content

Changes for page acmp Update

Last modified by Sabrina V. on 2026/10/06 11:18
From version 1.1
edited by jklein
on 2024/08/13 08:28
Change comment: Imported from XAR
To version 12.1
edited by Sabrina V.
on 2026/10/06 11:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -ACMP Update
1 +acmp Update
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.jklein
1 +XWiki.SV
Content
... ... @@ -6,94 +6,94 @@
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 -(% style="text-align:center" %)
19 -[[image:https://manual.aagon.com/acmp/de/61/hmfile_hash_3f81bd45.png]]
18 +[[image:hmfile_hash_3f81bd45.png||alt="Update process" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
20 20  
21 21  {{figureCaption}}
22 -Update process of ACMP Update
21 +Update process of acmp Update
23 23  {{/figureCaption}}
24 24  {{/figure}}
25 25  
26 26  **~1. Download Updates**
27 27  
28 -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.
29 29  
30 30  **2. Manage Updates**
31 31  
32 -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.
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.
33 33  
34 34  **3. Installing Updates**
35 35  
36 -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]]).
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]]).
37 37  
38 38  The update process goes through several stages (//Downloaded//, //In Distribution// and //Installed//). The following status will be displayed:
39 39  
40 40  |(% style="width:155px" %)**Status**|(% style="width:1209px" %)**Meaning**
41 -|(% style="width:155px" %)Downloaded|(% style="width:1209px" %)The Update has been downloaded from the Aagon update server and saved on the ACMP Server.
42 -|(% style="width:155px" %)In Distribution|(% style="width:1209px" %)The Update is released for distribution and can be deployed to the ACMP Clients.
43 -|(% 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.
44 44  
45 45  {{aagon.infobox}}
46 -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.
47 47  {{/aagon.infobox}}
48 48  
49 -= Configure ACMP Updates =
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}}
50 50  
51 -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.
52 += Configure acmp Updates =
52 52  
53 -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.
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 54  
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 +
55 55  {{figure}}
56 -(% style="text-align:center" %)
57 -[[image:66_ACMP Update Konfiguration_879.png]]
59 +[[image:66_ACMP Update Konfiguration_879.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
58 58  
59 59  {{figureCaption}}
60 -ACMP Update Configuration
62 +acmp Update Configuration
61 61  {{/figureCaption}}
62 62  {{/figure}}
63 63  
64 64  
65 -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.
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.
66 66  
67 67  {{aagon.infobox}}
68 -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"]].
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"]].
69 69  {{/aagon.infobox}}
70 70  
71 71  Click on //Next >// to continue with the Update settings.
72 72  
73 73  {{figure}}
74 -(% style="text-align:center" %)
75 -[[image:66_Update Mechanismus_First Steps Wizard 1_843.png]]
76 +[[image:66_Update Mechanismus_First Steps Wizard 1_843.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
76 76  
77 77  {{figureCaption}}
78 -Proxy settings of the ACMP Update First Steps Wizard
79 +Proxy settings of the acmp Update First Steps Wizard
79 79  {{/figureCaption}}
80 80  {{/figure}}
81 81  
82 -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.
83 83  
84 84  {{figure}}
85 -(% style="text-align:center" %)
86 -[[image:66_Update Mechanismus_First Steps Wizard 2_843.png]]
86 +[[image:66_Update Mechanismus_First Steps Wizard 2_843.png||data-cmp-info="10" 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="HUpdatesherunterladen"]], //[[Manage Updates>>doc:||anchor="HUpdatesverwalten"]] //und [[Configuration>>doc:||anchor="HKonfiguration"]].
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"]].
97 97  
98 98  == Download Updates ==
99 99  
... ... @@ -100,8 +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 -(% style="text-align:center" %)
104 -[[image:66_Update Mechanismus_Tab Updates herunterladen_2078.png]]
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"]]
105 105  
106 106  {{figureCaption}}
107 107  Download Updates
... ... @@ -110,7 +110,7 @@
110 110  
111 111  == Manage Updates ==
112 112  
113 -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.
114 114  
115 115  {{aagon.warnungsbox}}
116 116  Please note that Offline Update integration should only be used in exceptional cases and that you should always opt for downloading online Updates.
... ... @@ -117,8 +117,7 @@
117 117  {{/aagon.warnungsbox}}
118 118  
119 119  {{figure}}
120 -(% style="text-align:center" %)
121 -[[image:66_Update Mechanismus_Übersicht Updates verwalten_1280.png]]
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"]]
122 122  
123 123  {{figureCaption}}
124 124  Overview of managed Updates
... ... @@ -127,9 +127,9 @@
127 127  
128 128  === Integrate Offline Updates ===
129 129  
130 -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.
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.
131 131  
132 -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//.
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//.
133 133  
134 134  {{aagon.infobox}}
135 135  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.
... ... @@ -138,8 +138,7 @@
138 138  Continue by clicking on //Integrate//.
139 139  
140 140  {{figure}}
141 -(% style="text-align:center" %)
142 -[[image:66_Update Mechanismus_Offline Update Integration_727.png]]
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"]]
143 143  
144 144  {{figureCaption}}
145 145  Select Offline Updates
... ... @@ -150,14 +150,13 @@
150 150  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.
151 151  {{/aagon.infobox}}
152 152  
153 -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//.
154 154  
155 155  {{figure}}
156 -(% style="text-align:center" %)
157 -[[image:66_Update Mechanismus_Offline Update Integration Wizard_727.png]]
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"]]
158 158  
159 159  {{figureCaption}}
160 -Offline Update Integration of the files on the ACMP Server
156 +Offline Update Integration of the files on the acmp Server
161 161  {{/figureCaption}}
162 162  {{/figure}}
163 163  
... ... @@ -166,20 +166,19 @@
166 166  === Distributing Updates ===
167 167  
168 168  {{aagon.infobox}}
169 -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.
170 170  {{/aagon.infobox}}
171 171  
172 172  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.
173 173  
174 174  {{aagon.infobox}}
175 -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.
176 176  {{/aagon.infobox}}
177 177  
178 178  Use the //Show information// button in the ribbon bar to display the Release Notes for the relevant version.
179 179  
180 180  {{figure}}
181 -(% style="text-align:center" %)
182 -[[image:66_Update Mechanismus_Updates freigeben_1163.png]]
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"]]
183 183  
184 184  {{figureCaption}}
185 185  Distribution Update version
... ... @@ -192,8 +192,7 @@
192 192  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 >//.
193 193  
194 194  {{figure}}
195 -(% style="text-align:center" %)
196 -[[image:66_Update Mechanismus_Installationshinweise_956.png]]
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"]]
197 197  
198 198  {{figureCaption}}
199 199  Installation instructions for the Update version
... ... @@ -200,7 +200,7 @@
200 200  {{/figureCaption}}
201 201  {{/figure}}
202 202  
203 -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.
204 204  
205 205  {{aagon.infobox}}
206 206  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.
... ... @@ -209,8 +209,7 @@
209 209  Click //Next >// again.
210 210  
211 211  {{figure}}
212 -(% style="text-align:center" %)
213 -[[image:66_Update Mechanismus_Installationsvoraussetzungen_956.png]]
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"]]
214 214  
215 215  {{figureCaption}}
216 216  Installation requirements for the Update
... ... @@ -217,11 +217,10 @@
217 217  {{/figureCaption}}
218 218  {{/figure}}
219 219  
220 -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.
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.
221 221  
222 222  {{figure}}
223 -(% style="text-align:center" %)
224 -[[image:66_Update Mechanismus_Verifizierung_956.png]]
216 +[[image:66_Update Mechanismus_Verifizierung_956.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
225 225  
226 226  {{figureCaption}}
227 227  Verification of the installation preparations
... ... @@ -230,11 +230,10 @@
230 230  
231 231  Finally, click on //Install//.
232 232  
233 -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.
234 234  
235 235  {{figure}}
236 -(% style="text-align:center" %)
237 -[[image:66_Update Mechanismus_Installation des Updates_534.png]]
228 +[[image:66_Update Mechanismus_Installation des Updates_534.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
238 238  
239 239  {{figureCaption}}
240 240  Information window after a successfully installed Update
... ... @@ -241,7 +241,7 @@
241 241  {{/figureCaption}}
242 242  {{/figure}}
243 243  
244 -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.
245 245  
246 246  
247 247  == Configuration ==
... ... @@ -249,12 +249,11 @@
249 249  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.
250 250  
251 251  |(% style="width:161px" %)**Section**|(% style="width:1203px" %)**Description**
252 -|(% 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.
253 -|(% 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.
254 254  
255 255  {{figure}}
256 -(% style="text-align:center" %)
257 -[[image:66_ACMP Update Konfiguration_Einstellung.png]]
247 +[[image:66_ACMP Update Konfiguration_Einstellung.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
258 258  
259 259  {{figureCaption}}
260 260  Update configuration
... ... @@ -261,39 +261,41 @@
261 261  {{/figureCaption}}
262 262  {{/figure}}
263 263  
264 -= Special features of the ACMP Updates =
254 += Special features of the acmp Updates =
265 265  
266 -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:
267 267  
268 268  |**Speciality**|**Erklärung**
269 -|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.
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.
270 270  |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.
271 -|Updates of other components in connection with ACMP (e.g. Web Interfaces of the Helpdesk or AESB)|(((
272 -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.
273 273  
274 -You can read more info on the installations and Updates of the additional components [[here>>doc:ACMP.66.ACMP installieren.ACMP Zusatzkomponenten installieren.WebHome]].
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]].
275 275  )))
276 -|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.
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 +)))
277 277  
278 278  = Notes on the Update =
279 279  
280 -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:
281 281  
282 -* ACMP AD Agent
283 -* ACMP AD Connector
284 -* ACMP Data Gateway
285 -* ACMP Data Proxy
286 -* ACMP Notifier
287 -* ACMP WMI Scanner
288 -* 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
289 289  * Contact Adapter
290 290  * Container Adapter
291 291  * Network Boot Service
292 292  
293 -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.
294 294  
295 295  (% style="text-align:center" %)
296 -[[image:https://manual.aagon.com/acmp/de/61/sqlserver_db_backup.png||alt="SQLServer_DB_Backup" height="377" width="539"]]
288 +[[image:sqlserver_db_backup.png||alt="SQLServer_DB_Backup" data-cmp-info="10" height="377" width="539"]]
297 297  Backing up the database using SQL Server Management Studio
298 298  
299 299  
... ... @@ -300,14 +300,14 @@
300 300  Also check the following:
301 301  
302 302  * Is there enough disk space available for the Update?
303 -* 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?
304 304  * Is the virus scanner temporarily disabled for the Update to ensure a smooth process?
305 305  
306 306  {{aagon.infobox}}
307 -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//.
308 308  {{/aagon.infobox}}
309 309  
310 -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.
311 311  
312 312  
313 313  = Manual Agent installation using the Launcher.exe =
... ... @@ -318,11 +318,11 @@
318 318  
319 319  **Note for missing administrator rights:**
320 320  
321 -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"]].
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"]].
322 322  
323 -**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:**
324 324  
325 -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.
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.
326 326  
327 327  {{aagon.warnungsbox}}
328 328  This procedure does not work via the network share!
... ... @@ -329,13 +329,12 @@
329 329  {{/aagon.warnungsbox}}
330 330  
331 331  
332 -= ACMP Console Update Service in the Windows system service =
324 += acmp Console Update Service in the Windows system service =
333 333  
334 -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.
335 335  
336 336  {{figure}}
337 -(% style="text-align:center" %)
338 -[[image:66_Dienste_ACMP Console Update Service_951.png]]
329 +[[image:66_Dienste_ACMP Console Update Service_951.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
339 339  
340 340  {{figureCaption}}
341 341  Windows services for the ACMP Console Update Service
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community