Changes for page Agentless Scanner

Last modified by Sabrina V. on 2026/10/08 10:49

From version 6.1
edited by Sabrina V.
on 2026/10/08 10:49
Change comment: There is no comment for this version
To version 4.1
edited by Sabrina V.
on 2026/07/30 08:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,10 +4,10 @@
4 4  
5 5  = Functionality =
6 6  
7 -The Agentless Scanner consists of three main components: the AD connector, the AD agent and the WMI scanner. The basic data of a client is collected from the AD, compared with the data available in acmp, and finally stored if it does not already exist. Once set up, Clients that are newly connected to the AD are automatically inventoried. This eliminates the need to trigger an inventory manually.
7 +The Agentless Scanner consists of three main components: the AD connector, the AD agent and the WMI scanner. The basic data of a client is collected from the AD, compared with the data available in ACMP, and finally stored if it does not already exist. Once set up, Clients that are newly connected to the AD are automatically inventoried. This eliminates the need to trigger an inventory manually.
8 8  
9 9  {{aagon.infobox}}
10 -Because the agentless scanner cannot read all the data due to the way it works, it provides less data than the acmp agent.
10 +Because the agentless scanner cannot read all the data due to the way it works, it provides less data than the ACMP agent.
11 11  {{/aagon.infobox}}
12 12  
13 13   The following section explains how each component works in detail.
... ... @@ -19,9 +19,9 @@
19 19  In multi-domain environments, the NetBios name may not be resolved correctly when read by the AD Connector. To avoid this error, an additional attempt is made to reach the clients via FQDN.
20 20  {{/aagon.infobox}}
21 21  )))
22 -|=AD Agent |The AD Agent is responsible for comparing the received data with the data already present in acmp. If a new client or an existing client with new data is found in AD, the client's basic data (name, description, domain and address) is stored or modified in the acmp database. This allows the client to be found in the agent installation and its basic data to be processed normally (e.g. in queries or client commands).
22 +|=AD Agent |The AD Agent is responsible for comparing the received data with the data already present in ACMP. If a new client or an existing client with new data is found in AD, the client's basic data (name, description, domain and address) is stored or modified in the ACMP database. This allows the client to be found in the agent installation and its basic data to be processed normally (e.g. in queries or client commands).
23 23  |=WMI Scanner |(((
24 -The WMI scanner is required so that continuing data of the Client can be inventoried which go beyond the basic data. A scan of the WMI of the Client is triggered. This data is then stored in the acmp Database. This means that Clients which are not accessible via NetBIOS (e.g. due to certain network guidelines) and therefore do not appear in the Agent Installation can also be inventoried.
24 +The WMI scanner is required so that continuing data of the Client can be inventoried which go beyond the basic data. A scan of the WMI of the Client is triggered. This data is then stored in the ACMP Database. This means that Clients which are not accessible via NetBIOS (e.g. due to certain network guidelines) and therefore do not appear in the Agent Installation can also be inventoried.
25 25  )))
26 26  
27 27  = Installation requirements =
... ... @@ -28,7 +28,7 @@
28 28  
29 29  Before you can perform the installation, check the following requirements:
30 30  
31 -* The services are installed on the server on which acmp is also installed.
31 +* The services are installed on the server on which ACMP is also installed.
32 32  * At least .Net Framework version 4.7.2 is installed.
33 33  * Message Queuing is installed.
34 34  
... ... @@ -38,7 +38,7 @@
38 38  
39 39  == Run installation ==
40 40  
41 -To use the Agentless Scanner, you must first install its services. To do this, run the acmp Agentless Scanner_Installer.exe installation file located in the acmp Server installation directory in the Installers/AgentlessScan folder. Follow the installation instructions and install all the components.
41 +To use the Agentless Scanner, you must first install its services. To do this, run the ACMP Agentless Scanner_Installer.exe installation file located in the ACMP Server installation directory in the Installers/AgentlessScan folder. Follow the installation instructions and install all the components.
42 42  
43 43  [[Installation of the Agentless Scanner>>image:Agentless Scanner_Installer.png||alt="Installation des Agentless Scanners"]]
44 44  
... ... @@ -56,12 +56,12 @@
56 56  
57 57  == General ==
58 58  
59 -The connection string to the acmp database is entered by default in the General area. If this is not available or if a different connection string is entered, click on Get database connection string from acmp configuration to have the connection string to the acmp database entered automatically.
59 +The connection string to the ACMP database is entered by default in the General area. If this is not available or if a different connection string is entered, click on Get database connection string from ACMP configuration to have the connection string to the ACMP database entered automatically.
60 60  Now click on Test connection string to test the connection. If you receive the message Connection successful, the connection to the database has been established. If you receive the message Failed to connect instead, the connection string must be customized.
61 61  To customize the connection string, click Edit connection string and enter the correct connection string. Then repeat the test process until the connection has been successfully established.
62 62  If you encounter any problems, Aagon Support will be happy to help you. Alternatively, you can find further information on general adjustments to the connection string here.
63 63  
64 -[[Establish connection to acmp database>>image:Agentless Scanner_General.png||alt="Verbindung zur ACMP Datenbank herstellen"]]
64 +[[Establish connection to ACMP database>>image:Agentless Scanner_General.png||alt="Verbindung zur ACMP Datenbank herstellen"]]
65 65  
66 66  == AD Connector ==
67 67  
... ... @@ -91,7 +91,7 @@
91 91  In addition to the two settings mentioned above, you can specify in the “Client Import Destination” entry how the detected clients and the collected data should be handled. You can choose from the following options:
92 92  
93 93  * //Inventory// – The Inventory is populated with the clients, including the collected data
94 -* //AgentDistribution// – The detected clients are added to the acmp Agent Installation
94 +* //AgentDistribution// – The detected clients are added to the ACMP Agent Installation
95 95  * //Inventory and AgentDistribution// – Both processes are executed
96 96  
97 97  [[Configure the Active Directory Agent>>image:Agentless Scanner_AD Agent.png||alt="Active Directory Agent konfigurieren"]]
... ... @@ -107,7 +107,7 @@
107 107  
108 108  [[Configure the WMI Scanner>>image:Agentless Scanner_WMI Scanner.png||alt="WMI Scanner konfigurieren"]]
109 109  
110 -In addition to the two settings mentioned above, you can use the //Database Request Frequency// entry to specify the interval (in hours) at which the acmp Database should be checked. During this check, all Clients that have been detected by the //AD Connector// but for which no data is yet available are identified. These clients are then passed to the WMI Scanner, which initiates a scan of the clients’ WMI to retrieve their advanced data and properties.
110 +In addition to the two settings mentioned above, you can use the //Database Request Frequency// entry to specify the interval (in hours) at which the ACMP Database should be checked. During this check, all Clients that have been detected by the //AD Connector// but for which no data is yet available are identified. These clients are then passed to the WMI Scanner, which initiates a scan of the clients’ WMI to retrieve their advanced data and properties.
111 111  
112 112  Under //Domain Credentials//, you can specify user accounts that have administrator rights on the clients to be scanned. You must enter at least one user here. To do so, follow these steps:
113 113  
... ... @@ -115,7 +115,7 @@
115 115  1. Under //Domain name (FQDN)//, enter the “Fully Qualified Domain Name” of the domain whose Clients are to be scanned.
116 116  1. Under //User Name//, enter the username. This must be formatted as “User@FQDN” (User Principal Name, UPN).
117 117  
118 -1. {{aagon.infobox}}The domain name specified first and the user's FQDN do not have to be identical. The domain name acts as a filter for the client data that is passed. This ensures that only clients that belong to the corresponding domain according to the acmp Database are scanned.{{/aagon.infobox}}
118 +1. {{aagon.infobox}}The domain name specified first and the user's FQDN do not have to be identical. The domain name acts as a filter for the client data that is passed. This ensures that only clients that belong to the corresponding domain according to the ACMP Database are scanned.{{/aagon.infobox}}
119 119  1. In the “Password” field, enter the user password.
120 120  1. Click the OK button to confirm your entries and close the dialog box.
121 121  
... ... @@ -129,7 +129,7 @@
129 129  
130 130  1. Execution of a local Python script on all Linux and macOS clients using the “Linux and macOS Inventory” Client Command.
131 131  1. Automatic generation of XML files (one file per client) on a specific network share by the script, each containing all the collected client information.
132 -1. The generated XML files are read by the XML Importer; the information they contain is captured and finally added to the acmp Database.
132 +1. The generated XML files are read by the XML Importer; the information they contain is captured and finally added to the ACMP Database.
133 133  
134 134  Since only the XML import (step 3) is performed within the Agentless Scanner itself, only the configuration of the XML Importer is described here. For more information on executing the Python script and generating the XML files (Steps 1 and 2), please refer to the section on Linux and macOS Inventory.
135 135  
... ... @@ -216,13 +216,13 @@
216 216  
217 217  = Update the Agentless Scanner =
218 218  
219 -After installing an acmp Update, you may need to update the Agentless Scanner
219 +After installing an ACMP Update, you may need to update the Agentless Scanner
220 220  
221 221  {{aagon.infobox}}
222 -You can check the acmp Release Notes to see if you need to update any additional components, and if so, which ones.
222 +You can check the ACMP Release Notes to see if you need to update any additional components, and if so, which ones.
223 223  {{/aagon.infobox}}
224 224  
225 -If a new version of the Agentless Scanner is available in the acmp update, you can update your existing installation as follows:
225 +If a new version of the Agentless Scanner is available in the ACMP update, you can update your existing installation as follows:
226 226  
227 -1. Navigate to the acmp Server's installation directory and open the Installers/AgentlessScan folder, which contains the installation file acmp Agentless Scanner_Installer.exe.
228 -1. Follow the [[installation instructions>>doc:ACMP.610.ACMP-Solutions.Client-Management.Agenteninstallation.WebHome||anchor="HConfiguringtheAgentlessScanner"]] and install all five components.
227 +1. Navigate to the ACMP Server's installation directory and open the Installers/AgentlessScan folder, which contains the installation file ACMP Agentless Scanner_Installer.exe.
228 +1. Follow the [[installation instructions>>doc:ACMP.610.ACMP-Solutions.Client-Management.Agenteninstallation.WebHome||anchor="HAgentlessScannerkonfigurieren"]] and install all five components.
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community