Changes for page ACMP Update

Summary

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

Details

Page properties

Content

...	...	@@ -28,11 +28,11 @@
28	28
29	29	**2. Manage Updates**
30	30
31		-The previously downloaded updates need to be shared. This allows the ACMP Agents to receive the pending updates and cache them locally before installing them on the ACMP Server. During this distribution, the ACMP Agents obtain the ACMP Updates independently from the distributed file repositories (see [[distributed File Repositories>>doc:ACMP.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.67.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.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.67.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
...	...	@@ -60,7 +60,7 @@
60	60	{{/figure}}
61	61
62	62
63		-On the first page, specify which proxy settings are to be used when downloading Updates. To do this, enable the //Use proxy// checkbox, otherwise the first option //Use system proxy settings// will be automatically applied. The settings refer to the information you entered under //System// > //Settings// > //ACMP// //Server// > //[[Server proxy configuration>>doc:ACMP.66.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HServer-Proxy-Konfiguration"]].// Enter a proxy address and the HTTP port. If the proxy uses authentication, also enable this checkbox and enter a username and password. Then test the connection and check that your entries are correct.
	63	+On the first page, specify which proxy settings are to be used when downloading Updates. To do this, enable the //Use proxy// checkbox, otherwise the first option //Use system proxy settings// will be automatically applied. The settings refer to the information you entered under //System// > //Settings// > //ACMP// //Server// > //[[Server proxy configuration>>doc:ACMP.67.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.
64	64
65	65	{{aagon.infobox}}
66	66	You can configure the ACMP Console so that it connects to the ACMP update service via a proxy server. Change the settings directly within the [[Server proxy configuration>>doc:ACMP.66.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HServer-Proxy-Konfiguration"]].
...	...	@@ -252,12 +252,12 @@
252	252	Below you will find some special features that need to be considered in connection with the ACMP Updates:
253	253
254	254	|**Speciality**|**Erklärung**
255		-|Setting up deployed file repositories|Optimise the distribution of Updates in your ACMP environment by setting up distributed file repositories (see [[Distributed file repositories>>doc:ACMP.66.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]). This procedure is particularly recommended for companies that have several locations.
	255	+|Setting up deployed file repositories|Optimise the distribution of Updates in your ACMP environment by setting up distributed file repositories (see [[Distributed file repositories>>doc:ACMP.67.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]). This procedure is particularly recommended for companies that have several locations.
256	256	|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.
257	257	|Updates of other components in connection with ACMP (e.g. Web Interfaces of the Helpdesk or AESB)|(((
258	258	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.
259	259
260		-You can read more info on the installations and Updates of the additional components [[here>>doc:ACMP.66.ACMP installieren.ACMP Zusatzkomponenten installieren.WebHome]].
	260	+You can read more info on the installations and Updates of the additional components [[here>>doc:ACMP.67.ACMP installieren.ACMP Zusatzkomponenten installieren.WebHome]].
261	261	)))
262	262	|Version sequence of patches|The //Manage Updates// tab displays the Updates in the order in which they were released by Aagon. You must also adhere to this order during network share and installation so that they can be installed correctly. When an Update is deployed, all older Updates that have not yet been deployed are also released. The procedure for installing Updates is the same.
263	263
...	...	@@ -308,7 +308,7 @@
308	308
309	309	**Note for installation outside the internal corporate network on agents that are to report via the ACMP Gateway:**
310	310
311		-The share directory can be copied to a USB stick. Launcher.exe can be executed in the usual way. If there are ZIP files in the Launcher.exe directory with the machine name and the Gateway certificates as content, the certificate for the machine will be installed. For example, a client with the machine name can first be inventoried using the Offline Scanner and then a certificate can be created for it using the Gateway plugin (//ACMP Gateway// > [[Manual Deployment>>doc:ACMP.66.ACMP-Solutions.System.Gateway.Clients.WebHome||anchor="HClient-ZertifikatfFCrdiemanuelleVerteilungerstellen"]]) and stored on the USB stick.
	311	+The share directory can be copied to a USB stick. Launcher.exe can be executed in the usual way. If there are ZIP files in the Launcher.exe directory with the machine name and the Gateway certificates as content, the certificate for the machine will be installed. For example, a client with the machine name can first be inventoried using the Offline Scanner and then a certificate can be created for it using the Gateway plugin (//ACMP Gateway// > [[Manual Deployment>>doc:ACMP.67.ACMP-Solutions.System.Gateway.Clients.WebHome||anchor="HClient-ZertifikatfFCrdiemanuelleVerteilungerstellen"]]) and stored on the USB stick.
312	312
313	313	{{aagon.warnungsbox}}
314	314	This procedure does not work via the network share!