Installing ACMP agents
To install the ACMP Agent in your network, you can either start the installation from the console or initiate it via the network.
Installation via console
Open the agent installation in Client Management. All domains and workgroups with the machines they contain are displayed here. The icons are explained in the legend on the right.
| The ACMP Agent can be installed on this machine. |
| It has not yet been checked whether the ACMP Agent can be installed on this machine. |
| The installation of the ACMP Agent is not possible on this machine. |
| Installation is possible, but has not yet been carried out. |
| The ACMP Agent is currently being installed. |
The ACMP Console is currently waiting for data from the machine. | |
| The installation could not be finished successfully. |
Note:
If the ACMP Server is running on a Windows Server 2012, please ensure that the “Computer Browser” service is started. Also, make sure to specify a user under System > Settings > Agent Settings who has the right to browse the network.
This page is divided into three tabs. The Network tab allows you to install the ACMP Agent. This tab is displayed by default. The second tab, Installation Rules, allows you to add individual installation rules. On the third tab, Configuration, you can define individual scan sources.
Installation via network
Another way to install the ACMP Agent is as follows: Access the machine on which ACMP is installed via the network environment. Under the corresponding network share, you will find a subdirectory called Client. This subdirectory contains the file Launcher.exe, which you simply start to install the client. This process can be executed via a login script, for example.
Customize the parameters of Launcher.exe
Below are some parameters that you can customize for Launcher.exe. Unless explicitly stated in the parameter that the installation mechanism is to be started, the program will only execute this one specific command. Please note that the parameters are not sensitive.
Note:
The parameters are checked in the order in which they are shown here. This means that the first parameter found is processed first. The parameter /MAKENEWCLIENTID is an exception to this rule, as checking continues after this parameter because it only sets a flag.
| Parameter | Description |
| /MAKENEWCLIENTID | Sets the flag Force a new ClientID for the installation mechanism.
|
| /RESTART | The logic from /TERMINATE (1) and the normal installation mechanism as in (No parameter) (2) are called. |
| /FORCEREINSTALLATION | The logic from /TERMINATE (1) and “UnInst.exe /SILENT /VERYSILENT” (2) are called. Then the normal installation mechanism is called as in (No parameter) (3).
|
| /MARKFORPOSTDEPLOYMENT | The server request with the changed rollout status “Post Deployment” is sent. |
| /PREPAREPOSTDEPLOYMENT | The logic from /MARKFORPOSTDEPLOYMENT (1) and /RESTART (2) is executed.
This parameter is only available from ACMP version 5.3 onwards. |
| (No Parameter) | The normal installation process starts. |
Transfer Gateway certificates via Launcher.exe
If you want to transfer Gateway certificates via Launcher.exe, the %RECHNERNAME%.zip file must be stored in the folder containing Launcher.exe. This file contains all relevant files required for the ACMP Gateway. Run Launcher.exe as administrator.