Changes for page acmp Agent

Summary

• Page properties (2 modified, 0 added, 0 removed)

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"]]
	9	+[[Settings (acmp Kiosk)>>image:ACMP Settings.png||alt="Einstellungen: ACMP Kiosk" data-cmp-info="10"]]
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
...	...	@@ -22,7 +22,7 @@
22	22
23	23	The software scanner assists you in using [[Licence Management>>doc:ACMP.610.ACMP-Solutions.Lizenzmanagement.WebHome]].
24	24
25		-You can specify whether the software scanner should ignore updates and system components during the scan. This will reduce the number of results accordingly. You can also specify whether to enable the search for user-specific setup and uninstallation paths. This option is disabled by default. Once activated, the uninstall string will be displayed in the [[Client Details>>doc:ACMP.610.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen auswerten.WebHome||anchor="HClientDetailsanzeigenlassen"]].
	25	+You can specify whether the software scanner should ignore updates and system components during the scan. This will reduce the number of results accordingly. You can also specify whether to enable the search for user-specific setup and uninstallation paths. This option is disabled by default. Once activated, the uninstall string will be displayed in the [[Client Details>>doc:ACMP.610.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen auswerten.WebHome||anchor="HOpenandworkwithClientDetails"]].
26	26
27	27	== **File Scanner** ==
28	28
...	...	@@ -48,18 +48,16 @@
48	48
49	49	= General =
50	50
51		-== (% id="cke_bm_1512S" style="display:none" %)** **(%%) ==
52		-
53	53	== **Agent Installation and Network Account** ==
54	54
55	55	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.
56	56
57		-[[System settings (Agent)>>image:68_System_ACMP Agent_Allgemein.png||alt="Systemeinstellungen: ACMP Agent"]]
	55	+[[System settings (Agent)>>image:68_System_ACMP Agent_Allgemein.png||alt="Systemeinstellungen: ACMP Agent" data-cmp-info="10"]]
58	58
59	59	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.
60	60
61	61	{{aagon.infobox}}
62		-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.
63	63	{{/aagon.infobox}}
64	64
65	65
...	...	@@ -66,11 +66,11 @@
66	66
67	67	== **Agent Installation Folder** ==
68	68
69		-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.
70	70
71	71	== **Client Settings** ==
72	72
73		-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.
74	74
75	75	* Windows Clients:
76	76	** Computer SID
...	...	@@ -86,13 +86,11 @@
86	86	If the selected value is ambiguous, scan data from another Client will be overwritten, and your database will become corrupted.
87	87	{{/aagon.warnungsbox}}
88	88
89		-
90		-
91	91	== **Online Status** ==
92	92
93		-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.
94	94
95		-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.
96	96
97	97	== Job Execution Mode ==
98	98
...	...	@@ -102,7 +102,7 @@
102	102	|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.
103	103	|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.
104	104
105		-[[Job Execution Mode for the Start Conditions>>image:69_Einstellungen ACMP Agent_Job-Ausführungsmodus_749.png]]
	101	+[[Job Execution Mode for the Start Conditions>>image:69_Einstellungen ACMP Agent_Job-Ausführungsmodus_749.png||data-cmp-info="10"]]
106	106
107	107
108	108
...	...	@@ -116,13 +116,13 @@
116	116	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”).
117	117	{{/aagon.infobox}}
118	118
119		-[[Required rights in user management for using the sign-in history>>image:68_Benutzerverwaltung_Rechte des Benutzers Anmeldeverlauf_988.png]]
	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"]]
120	120
121	121
122	122
123	123	== Manually Designating a Primary User ==
124	124
125		-You can manually designate a primary user in the Client Details. To do this, you must first open a client using a Query and then [[display the Client Details>>doc:ACMP.610.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen auswerten.WebHome||anchor="HClientDetailsanzeigenlassen"]].
	121	+You can manually designate a primary user in the Client Details. To do this, you must first open a client using a Query and then [[display the Client Details>>doc:ACMP.610.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen auswerten.WebHome||anchor="HOpenandworkwithClientDetails"]].
126	126
127	127	Within the Client Details, navigate to the //Linked Contacts// entry. There, all contacts currently linked to the client are displayed. The following functions are available in the detail view of the linked contacts:
128	128
...	...	@@ -133,91 +133,100 @@
133	133
134	134	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.
135	135
136		-[[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"]]
	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"]]
137	137
138	138
139	139
140	140	== Automatic Primary User Detection ==
141	141
142		-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.
143	143
144	144	(% class="box infomessage" %)
145	145	(((
146		-[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt="Hinweis" height="32" width="32"]] **Hinweis: **
	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: **
147	147
148	148	Both functions are disabled by default for privacy reasons.
149	149	)))
150	150
151		-=== Erfassung des Anmeldeverlaufs aktivieren ===
	147	+=== Enable Login History Tracking ===
152	152
153		-Durch die Aktivierung der ersten Funktion, //Scannen des Anmeldeverlaufs//, können die Anmeldungen erfasst und gespeichert werden. Es werden ausschließlich “echte” Logins gezählt, also Windows-Logins, bei denen ein vollständiger Session-Aufbau stattfindet. Erfasst werden dabei sowohl RDP-Sessions als auch lokale Anmeldungen.
	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.
154	154
155	155	(% class="box" %)
156	156	(((
157		-**Beispiel**: Es gilt beispielsweise nicht als Login, wenn ein Benutzer sich nach Bildschirmsperre wieder am Client anmeldet.
	153	+**Example**: For example, it is not considered a login when a user logs back into the Client after the screen has been locked.
158	158	)))
159	159
160		-(% class="wikigeneratedid" %)
161		-Nach der Aktivierung können Sie den Anmeldeverlauf des Clients in den Client Details unter dem Ordner //Software //> //Betriebssystem //im Eintrag //Anmeldeverlauf //einsehen. Beachten Sie, dass die Daten für den Anmeldeverlauf über den System Scanner abgerufen werden. Das bedeutet, dass die Speicherung des Anmeldeverlaufs nur für Clients möglich ist, die über den ACMP Agent oder den OneScanClient erfasst wurden.
	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.
162	162
163		-[[Anmeldeverlauf eines Clients>>image:Anmeldeverlauf_Hauptbenutzer.png||alt="Anmeldeverlauf eines Clients"]]
	158	+[[A Client's Login Process>>image:Anmeldeverlauf_Hauptbenutzer.png||alt="Anmeldeverlauf eines Clients" data-cmp-info="10"]]
164	164
165		-Für alle Clients, die auf andere Weise erfasst wurden, kann kein Anmeldeverlauf erzeugt werden. Entsprechend muss der Hauptbenutzer weiterhin manuell gesetzt werden, auch wenn die Clients nicht explizit auf der Blacklist stehen.
	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	+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.
166	166
167		-Ebenfalls können Sie in den Einstellungen festlegen, nach wie vielen Tagen die erfassten Anmeldeverläufe durch einen Server-Job gelöscht werden sollen.
	163	+{{aagon.infobox}}
	164	+Information that has already been deleted from the login history cannot be restored or added later.
168	168
	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	+
169	169	{{aagon.infobox}}
170		-Bei vielen Clients in Verbindung mit einer langen Speicherdauer der Anmeldeverläufe ist es möglich, dass große Datenmengen entstehen, die Ihr System verlangsamen. Daher sollten Sie die Anzahl der Tage bis zur Löschung der Anmeldeverläufe nicht zu groß wählen.
	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.
171	171	{{/aagon.infobox}}
172	172
173		-=== Setzen des Hauptbenutzers aktivieren ===
	174	+=== Enable Setting the Primary User ===
174	174
175		-Durch die Aktivierung der zweiten Funktion, //Hauptbenutzer automatisch setzen//, wird ein Benutzer nach einer bestimmten Anzahl an aufeinanderfolgenden Logins automatisch als Hauptbenutzer gesetzt. Die Anzahl der benötigten aufeinanderfolgenden Anmeldungen können Sie in den Einstellungen festlegen.
	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.
176	176
177	177	{{aagon.warnungsbox}}
178		-Die Berechnung des Hauptbenutzers wird nicht direkt durch eine Benutzeranmeldung angestoßen, sondern findet erst 10 Minuten nach der ersten Anmeldung statt. Daher kommt es ggf. zu einer Verzögerung zwischen den Anmeldungen und dem Setzen des Hauptbenutzers.
	179	+The calculation of the primary user is not triggered directly by a user login, but takes place 10 minutes after the first login. Therefore, there may be a delay between logins and the designation of the primary user.
179	179	{{/aagon.warnungsbox}}
180	180
181		-Durch statisches oder dynamisches Blacklisting ist es möglich, spezifische Clients von diesem Automatismus auszuschließen. Dazu können Sie ausgewählte Clients in den Einstellungen entweder statisch zur Liste der Clients ohne Hauptbenutzer hinzufügen oder [[Filteroptionen anwenden>>doc:ACMP.68.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen erstellen.Filteroptionen anwenden.WebHome]], um Clients ohne Hauptbenutzer dynamisch zu verwalten.
	182	+Static or dynamic blacklisting allows you to exclude specific clients from this automatic process. To do this, you can either statically add selected clients to the list of clients without a primary user in the settings, or [[apply filter options>>doc:ACMP.68.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen erstellen.Filteroptionen anwenden.WebHome]] to dynamically manage clients without a primary user.
182	182
183	183	{{aagon.infobox}}
184		-Die Erfassung des Anmeldeverlaufs ist auch aktiviert, wenn der Client durch Blacklisting von der automatischen Hauptbenutzererkennung ausgeschlossen ist.
	185	+Login history tracking is also activated even if the client is excluded from automatic primary user detection due to blacklisting.
185	185	{{/aagon.infobox}}
186	186
187		-[[Automatische Hauptbenutzererkennung aktivieren>>image:68_System_ACMP Agent_Haupbenutzer automatischen setzen.png||alt="Automatische Hauptbenutzererkennung aktivieren"]]
	188	+[[Enable Automatic Primary User Detection>>image:68_System_ACMP Agent_Haupbenutzer automatischen setzen.png||alt="Automatische Hauptbenutzererkennung aktivieren" data-cmp-info="10"]]
188	188
189		-Sobald Sie die automatische Hauptbenutzererkennung aktiviert haben, wird Ihnen in den Client Details im Eintrag// Verknüpfte Kontakte// mit einem Banner am unteren Ende des Fensters angezeigt, dass der Hauptbenutzer für den ausgewählten Client automatisch gesetzt wird. Dabei erkennt und merkt sich der Client ebenfalls den Benutzer-Typ. Sofern es sich bei dem Benutzer um einen Active Directory-Benutzer handelt, wird der Kontakt des Benutzers automatisch als verknüpfter Kontakt gelistet und als Hauptbenutzer gesetzt.
	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.
190	190
191	191	{{aagon.infobox}}
192		-Die automatische Kontakt-Verknüpfung funktioniert ausschließlich bei AD-Benutzern. Andere Benutzer-Typen werden nicht verknüpft.
	193	+Automatic contact linking works only for AD users. Other user types are not linked.
193	193	{{/aagon.infobox}}
194	194
195		-[[Anzeige des automatisch verknüpften Hauptbenutzers in den Client Details>>image:68_System_ACMP Agent_Hauptbenutzer_verknüpft.png||alt="Anzeige des automatisch verknüpften Hauptbenutzers in den Client Details"]]
	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"]]
196	196
197		-Sobald die automatische Hauptbenutzererkennung aktiviert ist, ist es nicht mehr möglich den Hauptbenutzer zurückzusetzen oder manuell zu ändern. Sie können weiterhin neue Verknüpfungen manuell hinzufügen und manuell hinzugefügte Verknüpfungen löschen, sofern der verknüpfte Kontakt nicht der Hauptbenutzer ist.
	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.
198	198
199		-= Remotedesktop Dienste =
	200	+= Remote Desktop Services =
200	200
201		-Hier können Sie das Verhalten von erhobenen Daten der Remotedesktop-Verbindungen definieren.
	202	+Here you can define how data collected from Remote Desktop connections is handled.
202	202
203	203	{{figure}}
204		-[[image:68_System_Einstellungen_RemotedesktopDienste_1327.png||alt="Remotedeskotp Dienste.PNG" data-xwiki-image-style-alignment="center"]]
	205	+[[image:68_System_Einstellungen_RemotedesktopDienste_1327.png||alt="Remotedeskotp Dienste.PNG" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
205	205
206	206	{{figureCaption}}
207		-Einstellungen der Remotedesktop Dienste
	208	+Remote Desktop Services settings
208	208	{{/figureCaption}}
209	209	{{/figure}}
210	210
211		-== **Aufräumen erhobener Daten** ==
212	212
213		-Standardmäßig werden die gesammelten Daten vom ACMP Agenten über Remotedesktop-Verbindungen standardmäßig nach 180 Tagen gelöscht.
214	214
215		-== **Datenerhebungsverfahren** ==
	214	+== **Cleaning Up Collected Data** ==
216	216
217		-Sie können bei der Remotedesktop-Anmeldung des ACMP Agenten entscheiden, über welches Verfahren die Daten erhoben werden. Aus folgenden drei Möglichkeiten können Sie entscheiden:
	216	+By default, data collected by the acmp Agent via Remote Desktop connections is deleted after 180 days.
218	218
219		-* Erhobene Daten niemals senden
220		-* Nur senden, wenn der Client Remotedesktop Dienste installiert hat
221		-* Erhobene Daten immer senden
	218	+== **Data Collection Methods** ==
222	222
223		-Standardmäßig ist die Option "Nur senden, wenn der Client Remotedesktop Dienste installiert hat" ausgewählt.
	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:
	221	+
	222	+* Never send collected data
	223	+* Send only if the client has Remote Desktop Services installed
	224	+* Always send collected data
	225	+
	226	+By default, the “Send only if the client has Remote Desktop Services installed” option is selected.
	227	+
	228	+