Changes for page acmp Agent

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

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -acmp Agent
1 +ACMP Agent
Content
... ... @@ -1,18 +1,18 @@
1 1  {{aagon.floatingbox/}}
2 2  
3 -The agent is deployed to the network clients directly from the acmp Console. It is required to send Client Commands directly to a client and to maintain continuous communication between the client and the server.
3 +The agent is deployed to the network clients directly from the ACMP Console. It is required to send Client Commands directly to a client and to maintain continuous communication between the client and the server.
4 4  
5 -= acmp Kiosk =
5 += ACMP Kiosk =
6 6  
7 -On this page, you can configure the acmp Kiosk.
7 +On this page, you can configure the ACMP Kiosk.
8 8  
9 -[[Settings (acmp Kiosk)>>image:ACMP Settings.png||alt="Einstellungen: ACMP Kiosk" data-cmp-info="10"]]
9 +[[Settings (ACMP Kiosk)>>image:ACMP Settings.png||alt="Einstellungen: ACMP Kiosk"]]
10 10  
11 11  In the //General// section, you specify the icon properties. You have the following three options:
12 12  
13 13  |(% style="width:253px" %)**Option**|(% style="width:1111px" %)**Description**
14 -|(% style="width:253px" %)Do not display a tray icon|(% style="width:1111px" %)As a result, your users will not see a tray icon for either the acmp Kiosk or the Command Launcher
15 -|(% style="width:253px" %)Display acmp Kiosk Tray Icon|(% style="width:1111px" %)This causes the acmp Kiosk tray icon to be displayed, replacing the Command Launcher.
14 +|(% style="width:253px" %)Do not display a tray icon|(% style="width:1111px" %)As a result, your users will not see a tray icon for either the ACMP Kiosk or the Command Launcher
15 +|(% style="width:253px" %)Display ACMP Kiosk Tray Icon|(% style="width:1111px" %)This causes the ACMP Kiosk tray icon to be displayed, replacing the Command Launcher.
16 16  
17 17  = Agent Task =
18 18  
... ... @@ -52,12 +52,12 @@
52 52  
53 53  On this page, you first specify the agent installation and network identification account. Here, you can access existing global accounts, create new ones, or specify a specific account. To do so, enter the username and corresponding password in the appropriate fields.
54 54  
55 -[[System settings (Agent)>>image:68_System_ACMP Agent_Allgemein.png||alt="Systemeinstellungen: ACMP Agent" data-cmp-info="10"]]
55 +[[System settings (Agent)>>image:68_System_ACMP Agent_Allgemein.png||alt="Systemeinstellungen: ACMP Agent"]]
56 56  
57 57  You can specify that the system first check whether the specified account has sufficient rights for installation on all computers found on the network. To do this, select the “Check rights on target computers” checkbox.
58 58  
59 59  {{aagon.infobox}}
60 -If the acmp Server is installed on an operating system newer than Windows Server 2003, the specified account is also used for network discovery. This account must therefore have sufficient rights for RPC and for scanning the network.
60 +If the ACMP Server is installed on an operating system newer than Windows Server 2003, the specified account is also used for network discovery. This account must therefore have sufficient rights for RPC and for scanning the network.
61 61  {{/aagon.infobox}}
62 62  
63 63  
... ... @@ -64,11 +64,11 @@
64 64  
65 65  == **Agent Installation Folder** ==
66 66  
67 -Specify the storage location for the acmp Agent files. After installation, this is also where you’ll find CommandLauncher.exe, which you can use to launch the Client Command Launcher and execute Client Commands as an alternative to the tray icon.
67 +Specify the storage location for the ACMP Agent files. After installation, this is also where you’ll find CommandLauncher.exe, which you can use to launch the Client Command Launcher and execute Client Commands as an alternative to the tray icon.
68 68  
69 69  == **Client Settings** ==
70 70  
71 -To uniquely identify computers on the network, acmp offers various options for Windows and Unix clients. Select the value that is unique on your network.
71 +To uniquely identify computers on the network, ACMP offers various options for Windows and Unix clients. Select the value that is unique on your network.
72 72  
73 73  * Windows Clients:
74 74  ** Computer SID
... ... @@ -86,9 +86,9 @@
86 86  
87 87  == **Online Status** ==
88 88  
89 -The online status feature allows you to define a time period for all client-based queries, which is displayed in the Query Management interface. Here, you can specify the number of minutes after which the client’s last contact with the acmp Server is no longer considered online. The default value is 60 minutes. Active Clients that are displayed as online in the Query are marked with a green dot; Offline Clients are displayed with a gray icon. Manual Clients, OSC, etc., are not considered online Clients and are displayed without an icon.
89 +The online status feature allows you to define a time period for all client-based queries, which is displayed in the Query Management interface. Here, you can specify the number of minutes after which the client’s last contact with the ACMP Server is no longer considered online. The default value is 60 minutes. Active Clients that are displayed as online in the Query are marked with a green dot; Offline Clients are displayed with a gray icon. Manual Clients, OSC, etc., are not considered online Clients and are displayed without an icon.
90 90  
91 -If you want to verify the Clients’ online status, you must enable the corresponding checkbox. Only then will the acmp Agent contact the acmp Server at the interval you specified.
91 +If you want to verify the Clients’ online status, you must enable the corresponding checkbox. Only then will the ACMP Agent contact the ACMP Server at the interval you specified.
92 92  
93 93  == Job Execution Mode ==
94 94  
... ... @@ -98,7 +98,7 @@
98 98  |Always|In this mode, the job always runs as soon as the start condition for that job is met. A Job Log is always generated.|A Managed Software job will not make any changes on a client if the same version of the software included in the Managed Software job is already installed. The job log created for this simply indicates that the job ran but that no changes were made.
99 99  |Only when changes are applied|With this option enabled, the job is executed, and a Job Log is created only if the job also performed an update (either for Managed Software or a Windows Update).|With this configuration, there will be no Job Log, since no “actual execution” took place—the software did not need to be updated.
100 100  
101 -[[Job Execution Mode for the Start Conditions>>image:69_Einstellungen ACMP Agent_Job-Ausführungsmodus_749.png||data-cmp-info="10"]]
101 +[[Job Execution Mode for the Start Conditions>>image:69_Einstellungen ACMP Agent_Job-Ausführungsmodus_749.png]]
102 102  
103 103  
104 104  
... ... @@ -112,7 +112,7 @@
112 112  Please note that to view the login history, you need a user who has the appropriate right. You can assign and enable this right via [[User Management>>doc:ACMP.610.ACMP-Solutions.System.Benutzerverwaltung.WebHome]] (//Rights of User// > //Client Management// > Query Management > Client Details > Open Client Details > “View Client Login History”).
113 113  {{/aagon.infobox}}
114 114  
115 -[[Required rights in user management for using the sign-in history>>image:68_Benutzerverwaltung_Rechte des Benutzers Anmeldeverlauf_988.png||data-cmp-info="10"]]
115 +[[Required rights in user management for using the sign-in history>>image:68_Benutzerverwaltung_Rechte des Benutzers Anmeldeverlauf_988.png]]
116 116  
117 117  
118 118  
... ... @@ -129,21 +129,23 @@
129 129  
130 130  You can now select which of the linked contacts should be the client's primary user. To do so, check the checkbox in the //Primary User// column next to the specific contact.
131 131  
132 -[[Manually Setting the Primary User in Client Details>>image:68_System_ACMP Agent_Manueller Hauptbenutzer.png||alt="Manuelle Festlegung des Hauptbenutzers in den Client Details" data-cmp-info="10"]]
132 +[[Manually Setting the Primary User in Client Details>>image:68_System_ACMP Agent_Manueller Hauptbenutzer.png||alt="Manuelle Festlegung des Hauptbenutzers in den Client Details"]]
133 133  
134 134  
135 135  
136 136  == Automatic Primary User Detection ==
137 137  
138 -With automatic primary user detection, it is possible to automatically and dynamically determine a client’s primary user based on logins to that client. To do this, there are two linked functions in the acmp Console’s system settings—“Login History” and “Primary User”—that must be enabled for automatic primary user detection.
138 +With automatic primary user detection, it is possible to automatically and dynamically determine a client’s primary user based on logins to that client. To do this, there are two linked functions in the ACMP Console’s system settings—“Login History” and “Primary User”—that must be enabled for automatic primary user detection.
139 139  
140 140  (% class="box infomessage" %)
141 141  (((
142 -[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt="Hinweis" data-cmp-info="10" height="32" width="32"]] **Hinweis: **
142 +[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt="Hinweis" height="32" width="32"]] **Hinweis: **
143 143  
144 144  Both functions are disabled by default for privacy reasons.
145 145  )))
146 146  
147 +
148 +
147 147  === Enable Login History Tracking ===
148 148  
149 149  By enabling the first function, //Scan Login History//, logins can be tracked and saved. Only “real” logins are counted - that is, Windows logins in which a full session is established. Both RDP sessions and local logins are tracked.
... ... @@ -153,24 +153,19 @@
153 153  **Example**: For example, it is not considered a login when a user logs back into the Client after the screen has been locked.
154 154  )))
155 155  
156 -After activation, you can view the client's login history in the Client Details under the //Software //> //Operating System //folder in the //Login History //entry. Please note that the data for the login history is retrieved via the System Scanner. This means that the login history can only be stored for clients that were detected via the acmp Agent or the OneScanClient.
158 +After activation, you can view the client's login history in the Client Details under the //Software //> //Operating System //folder in the //Login History //entry. Please note that the data for the login history is retrieved via the System Scanner. This means that the login history can only be stored for clients that were detected via the ACMP Agent or the OneScanClient.
157 157  
158 -[[A Client's Login Process>>image:Anmeldeverlauf_Hauptbenutzer.png||alt="Anmeldeverlauf eines Clients" data-cmp-info="10"]]
160 +[[A Client's Login Process>>image:Anmeldeverlauf_Hauptbenutzer.png||alt="Anmeldeverlauf eines Clients"]]
159 159  
160 160  For all clients that were added in other ways, a login history cannot be generated. Accordingly, the primary user must still be set manually, even if the clients are not explicitly on the blacklist. 
161 161  You can also specify in the settings how many days after they are created the recorded login histories should be deleted by a server job.
162 162  
163 163  {{aagon.infobox}}
164 -Information that has already been deleted from the login history cannot be restored or added later.
165 -
166 -Example: If data is deleted after 90 days by default and the settings are temporarily changed to 30 days, the data that has already been deleted as a result will not be restored if the 90-day retention period is subsequently reinstated.
167 -In this case, it will take up to 60 days for the data set to return to the intended retention period.
168 -{{/aagon.infobox}}
169 -
170 -{{aagon.infobox}}
171 171  If you have many clients and your system retains login histories for a long time, large amounts of data may accumulate, which can slow down your system. Therefore, you should not set the number of days before login histories are deleted to be too high.
172 172  {{/aagon.infobox}}
173 173  
169 +
170 +
174 174  === Enable Setting the Primary User ===
175 175  
176 176  The activation of the second function, //Automatically Set Primary User//, automatically designates a user as the primary user after a specified number of consecutive logins. You can set the number of consecutive logins required in the settings.
... ... @@ -185,7 +185,7 @@
185 185  Login history tracking is also activated even if the client is excluded from automatic primary user detection due to blacklisting.
186 186  {{/aagon.infobox}}
187 187  
188 -[[Enable Automatic Primary User Detection>>image:68_System_ACMP Agent_Haupbenutzer automatischen setzen.png||alt="Automatische Hauptbenutzererkennung aktivieren" data-cmp-info="10"]]
185 +[[Enable Automatic Primary User Detection>>image:68_System_ACMP Agent_Haupbenutzer automatischen setzen.png||alt="Automatische Hauptbenutzererkennung aktivieren"]]
189 189  
190 190  Once you have enabled automatic primary user detection, the //Linked Contacts// entry in the Client Details will display a banner at the bottom of the window indicating that the primary user for the selected client is set automatically. The client also detects and remembers the user type. If the user is an Active Directory user, the user’s contact is automatically listed as a linked contact and set as the primary user.
191 191  
... ... @@ -193,16 +193,18 @@
193 193  Automatic contact linking works only for AD users. Other user types are not linked.
194 194  {{/aagon.infobox}}
195 195  
196 -[[Display of the automatically linked primary user in the Client Details>>image:68_System_ACMP Agent_Hauptbenutzer_verknüpft.png||alt="Anzeige des automatisch verknüpften Hauptbenutzers in den Client Details" data-cmp-info="10"]]
193 +[[Display of the automatically linked primary user in the Client Details>>image:68_System_ACMP Agent_Hauptbenutzer_verknüpft.png||alt="Anzeige des automatisch verknüpften Hauptbenutzers in den Client Details"]]
197 197  
198 198  Once automatic primary user detection is enabled, you can no longer reset or manually change the primary user. You can still manually add new Shortcuts and delete manually added Shortcuts, provided that the linked contact is not the primary user.
199 199  
197 +
198 +
200 200  = Remote Desktop Services =
201 201  
202 202  Here you can define how data collected from Remote Desktop connections is handled.
203 203  
204 204  {{figure}}
205 -[[image:68_System_Einstellungen_RemotedesktopDienste_1327.png||alt="Remotedeskotp Dienste.PNG" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
204 +[[image:68_System_Einstellungen_RemotedesktopDienste_1327.png||alt="Remotedeskotp Dienste.PNG" data-xwiki-image-style-alignment="center"]]
206 206  
207 207  {{figureCaption}}
208 208  Remote Desktop Services settings
... ... @@ -213,11 +213,11 @@
213 213  
214 214  == **Cleaning Up Collected Data** ==
215 215  
216 -By default, data collected by the acmp Agent via Remote Desktop connections is deleted after 180 days.
215 +By default, data collected by the ACMP Agent via Remote Desktop connections is deleted after 180 days.
217 217  
218 218  == **Data Collection Methods** ==
219 219  
220 -When the acmp Agent logs in via Remote Desktop, you can choose which method to use for data collection. You can select one of the following three options:
219 +When the ACMP Agent logs in via Remote Desktop, you can choose which method to use for data collection. You can select one of the following three options:
221 221  
222 222  * Never send collected data
223 223  * Send only if the client has Remote Desktop Services installed
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community