Wiki source code of ACMP Update

Last modified by Sabrina V. on 2024/10/08 11:35

version	line-number	content
1.1	1	{{aagon.priorisierung}}
	2	1
	3	{{/aagon.priorisierung}}
	4
	5	{{aagon.floatingbox/}}
	6
20.1	7	= General =
1.1	8
20.1	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.
1.1	10
	11	{{aagon.infobox}}
20.1	12	ACMP Updates can only be used with valid licences. You also need a valid contract for Updates and support.
1.1	13	{{/aagon.infobox}}
	14
20.1	15	The Update process consists of three steps:
1.1	16
	17	{{figure}}
20.1	18	(% style="text-align:center" %)
	19	[[image:https://manual.aagon.com/acmp/de/61/hmfile_hash_3f81bd45.png]]
1.1	20
	21	{{figureCaption}}
20.1	22	Update process of ACMP Update
1.1	23	{{/figureCaption}}
	24	{{/figure}}
	25
20.1	26	~1. Download Updates
1.1	27
20.1	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.
1.1	29
20.1	30	2. Manage Updates
1.1	31
20.1	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.
1.1	33
20.1	34	3. Installing Updates
1.1	35
20.1	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]]).
1.1	37
20.1	38	The update process goes through several stages (//Downloaded//, //In Distribution// and //Installed//). The following status will be displayed:
1.1	39
20.1	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.
1.1	44
	45	{{aagon.infobox}}
20.1	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.
1.1	47	{{/aagon.infobox}}
	48
20.1	49	= Configure ACMP Updates =
1.1	50
20.1	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.
1.1	52
20.1	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.
1.1	54
	55	{{figure}}
20.1	56	(% style="text-align:center" %)
	57	[[image:66_ACMP Update Konfiguration_879.png]]
1.1	58
	59	{{figureCaption}}
20.1	60	ACMP Update Configuration
1.1	61	{{/figureCaption}}
	62	{{/figure}}
	63
	64
20.1	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.
1.1	66
	67	{{aagon.infobox}}
20.1	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"]].
1.1	69	{{/aagon.infobox}}
	70
20.1	71	Click on //Next >// to continue with the Update settings.
1.1	72
	73	{{figure}}
20.1	74	(% style="text-align:center" %)
	75	[[image:66_Update Mechanismus_First Steps Wizard 1_843.png]]
1.1	76
	77	{{figureCaption}}
20.1	78	Proxy settings of the ACMP Update First Steps Wizard
1.1	79	{{/figureCaption}}
	80	{{/figure}}
	81
20.1	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.
1.1	83
	84	{{figure}}
20.1	85	(% style="text-align:center" %)
	86	[[image:66_Update Mechanismus_First Steps Wizard 2_843.png]]
1.1	87
	88	{{figureCaption}}
20.1	89	Update settings in the ACMP Updates First Steps Wizard
1.1	90	{{/figureCaption}}
	91	{{/figure}}
	92
20.1	93	You have finished the initial configuration for the ACMP Updates.
1.1	94
	95
20.1	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"]].
1.1	97
20.1	98	== Download Updates ==
1.1	99
20.1	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//.
1.1	101
	102	{{figure}}
20.1	103	(% style="text-align:center" %)
	104	[[image:66_Update Mechanismus_Tab Updates herunterladen_2078.png]]
1.1	105
	106	{{figureCaption}}
20.1	107	Download Updates
1.1	108	{{/figureCaption}}
	109	{{/figure}}
	110
20.1	111	== Manage Updates ==
1.1	112
20.1	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.
1.1	114
	115	{{aagon.warnungsbox}}
20.1	116	Please note that Offline Update integration should only be used in exceptional cases and that you should always opt for downloading online Updates.
1.1	117	{{/aagon.warnungsbox}}
	118
	119	{{figure}}
20.1	120	(% style="text-align:center" %)
	121	[[image:66_Update Mechanismus_Übersicht Updates verwalten_1280.png]]
1.1	122
	123	{{figureCaption}}
20.1	124	Overview of managed Updates
1.1	125	{{/figureCaption}}
	126	{{/figure}}
	127
20.1	128	=== Integrate Offline Updates ===
1.1	129
20.1	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.
1.1	131
20.1	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//.
1.1	133
	134	{{aagon.infobox}}
20.1	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.
1.1	136	{{/aagon.infobox}}
	137
20.1	138	Continue by clicking on //Integrate//.
1.1	139
	140	{{figure}}
20.1	141	(% style="text-align:center" %)
	142	[[image:66_Update Mechanismus_Offline Update Integration_727.png]]
1.1	143
	144	{{figureCaption}}
20.1	145	Select Offline Updates
1.1	146	{{/figureCaption}}
	147	{{/figure}}
	148
	149	{{aagon.infobox}}
20.1	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.
1.1	151	{{/aagon.infobox}}
	152
20.1	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//.
1.1	154
	155	{{figure}}
20.1	156	(% style="text-align:center" %)
	157	[[image:66_Update Mechanismus_Offline Update Integration Wizard_727.png]]
1.1	158
	159	{{figureCaption}}
20.1	160	Offline Update Integration of the files on the ACMP Server
1.1	161	{{/figureCaption}}
	162	{{/figure}}
	163
20.1	164	The main view of the plugin will now list the newly added Updates, which you can now share and install.
1.1	165
20.1	166	=== Distributing Updates ===
1.1	167
	168	{{aagon.infobox}}
20.1	169	Before you start distributing Updates, you should make backups. Read here (Verlinkung) how to perform an ACMP backup.
1.1	170	{{/aagon.infobox}}
	171
20.1	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.
1.1	173
	174	{{aagon.infobox}}
20.1	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.
1.1	176	{{/aagon.infobox}}
	177
20.1	178	Use the //Show information// button in the ribbon bar to display the Release Notes for the relevant version.
1.1	179
	180	{{figure}}
20.1	181	(% style="text-align:center" %)
	182	[[image:66_Update Mechanismus_Updates freigeben_1163.png]]
1.1	183
	184	{{figureCaption}}
20.1	185	Distribution Update version
1.1	186	{{/figureCaption}}
	187	{{/figure}}
	188
	189
20.1	190	=== Installing Updates ===
1.1	191
20.1	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 >//.
1.1	193
	194	{{figure}}
20.1	195	(% style="text-align:center" %)
	196	[[image:66_Update Mechanismus_Installationshinweise_956.png]]
1.1	197
	198	{{figureCaption}}
20.1	199	Installation instructions for the Update version
1.1	200	{{/figureCaption}}
	201	{{/figure}}
	202
20.1	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.
1.1	204
	205	{{aagon.infobox}}
20.1	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.
1.1	207	{{/aagon.infobox}}
	208
20.1	209	Click //Next >// again.
1.1	210
	211	{{figure}}
20.1	212	(% style="text-align:center" %)
	213	[[image:66_Update Mechanismus_Installationsvoraussetzungen_956.png]]
1.1	214
	215	{{figureCaption}}
20.1	216	Installation requirements for the Update
1.1	217	{{/figureCaption}}
	218	{{/figure}}
	219
20.1	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.
1.1	221
	222	{{figure}}
20.1	223	(% style="text-align:center" %)
	224	[[image:66_Update Mechanismus_Verifizierung_956.png]]
1.1	225
	226	{{figureCaption}}
20.1	227	Verification of the installation preparations
1.1	228	{{/figureCaption}}
	229	{{/figure}}
	230
20.1	231	Finally, click on //Install//.
1.1	232
20.1	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.
1.1	234
	235	{{figure}}
20.1	236	(% style="text-align:center" %)
	237	[[image:66_Update Mechanismus_Installation des Updates_534.png]]
1.1	238
	239	{{figureCaption}}
20.1	240	Information window after a successfully installed Update
1.1	241	{{/figureCaption}}
	242	{{/figure}}
	243
20.1	244	Log in to the ACMP Console again to download the Updates and install the new version on your Client.
1.1	245
	246
20.1	247	== Configuration ==
1.1	248
20.1	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.
1.1	250
20.1	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.
1.1	254
	255	{{figure}}
20.1	256	(% style="text-align:center" %)
	257	[[image:66_ACMP Update Konfiguration_Einstellung.png]]
1.1	258
	259	{{figureCaption}}
20.1	260	Update configuration
1.1	261	{{/figureCaption}}
	262	{{/figure}}
	263
20.1	264	= Special features of the ACMP Updates =
1.1	265
20.1	266	Below you will find some special features that need to be considered in connection with the ACMP Updates:
1.1	267
20.1	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.
	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.
1.1	273
20.1	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]].
1.1	275	)))
20.1	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.
1.1	277
20.1	278	= Notes on the Update =
1.1	279
20.1	280	In preparation for an Update, you should first disable any additional ACMP components that may be present. This includes the following examples:
1.1	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
	289	* Contact Adapter
	290	* Container Adapter
	291	* Network Boot Service
	292
20.1	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.
1.1	294
	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"]]
20.1	297	Backing up the database using SQL Server Management Studio
1.1	298
	299
20.1	300	Also check the following:
1.1	301
20.1	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?
	304	* Is the virus scanner temporarily disabled for the Update to ensure a smooth process?
1.1	305
	306	{{aagon.infobox}}
20.1	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//.
1.1	308	{{/aagon.infobox}}
	309
20.1	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.
1.1	311
	312
20.1	313	= Manual Agent installation using the Launcher.exe =
1.1	314
20.1	315	You can run the Launcher.exe file in the C:\Program Files (x86)\Aagon\ACMP Server\Clients\Client directory or its network share to start an installation.
1.1	316
20.1	317	No further information is required as all settings are automatically taken from Settings.ini (C:\Program Files (x86)\Aagon\ACMP Server\Clients\).
	318
	319	Note for missing administrator rights:
	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"]].
	322
	323	Note for installation outside the internal corporate network on agents that are to report via the ACMP Gateway:
	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.
	326
	327	{{aagon.warnungsbox}}
	328	This procedure does not work via the network share!
	329	{{/aagon.warnungsbox}}
	330
	331
	332	= ACMP Console Update Service in the Windows system service =
	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.
	335
1.1	336	{{figure}}
20.1	337	(% style="text-align:center" %)
	338	[[image:66_Dienste_ACMP Console Update Service_951.png]]
1.1	339
	340	{{figureCaption}}
20.1	341	Windows services for the ACMP Console Update Service
1.1	342	{{/figureCaption}}
	343	{{/figure}}