A complete ACMP system consists of a server with the matching SQL database, one or more clients and at least one console.
The ACMP server is installed on a central computer and controls all connected compontents from there. It contains the basic modules, the database connection and a console. Here, all other solutions are installed. These include functions for the server and the clients. With the standardized interfaces, any number of solutions can be installed on the server. When new solutions are added, they are automatically distributed to the clients from this server. This means that solutions only have to be installed on the server.
Clients
Clients can communicate in three ways with the server:
| 1. | The ACMP Agent, which scans the client and transfers the data to the server, is installed on the clients. The server then enters these data in the database. The ACMP Agent itself is a Windows service. The settings to activate the ACMP Agent are configured centrally on the server. In addition, management functions can be run on ACMP Agent; for example, a program can be started or stopped on a remote computer. |
| 2. | The second option is the OneScanClient, a passive program, which is located on the server and is started by the client. This can be done, e.g. via the login script. This client determines all the data of the computer in one go, and then transmits them to the server and eventually this passes to the server, and runs off afterwards. |
| 3. | The Agentless Scanner is able to capture clients through an Active Directory. This approach is useful in cases where clients cannot be captured due to network policies, such as multiple network segments without NetBIOS support. Here, the Agentless Scanner is able to read the basic data of clients from an Active Directory and runs a WMI remote scan on the basis of these data. However, the data are not as complete as in the case of the other two scanners. |
Command Launcher
The Command Launcher can be installed on the network computers together with the ACMP Agent. Thus, you can mache so-called Client Commands available to the users. Afterwards, these Client Commands can be executed independently by the user. This method is suitable for processes with low priority and/or high client-side load, to allow users to determine the timing themselves. An example is a software installation or software update.
Console
The console is the tool for the system administrator. It allows the system administrator ot operate all ACMP solutions. The console serves to launch database queries on the server and to display the results, to enter the settings for capturing data on the clients, to generate and present reports and to administer the clients as well as the entire system. This includes user management, which makes it possible to assign certain rights to each user of the system, which determine the rights of the user in regard to the console. Moreover, it is possible from this point to keep the entire system up to date via the Internet by means of the "Active Update" tool.
In the database, all the information of the clients is stored. These data can be accessed and modified via the console. In addition, information can be archived via the console, with which the console itself or the clients can work. The database may but need not be located on the same server as the ACMP.
The central focal point for communication between the components is the ACMP server. From there, all solutions are made available and adaptations can be actively redistributed if necessary. Here the data are collected, stored in the database or made available to the console. Any number of consoles can access the server. The number of registered clients is limited only by the capacity of the actual SQL database used, the network bandwidth and the amount of ACMP licenses.
Last change on 10.03.2014