Changes for page Unix Agent installieren

Last modified by Sabrina V. on 2026/06/02 12:29

From version 16.1

edited by Sabrina V.
on 2026/06/02 12:29

Change comment: There is no comment for this version

To version 1.1

edited by jklein
on 2025/07/25 08:54

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,0 @@
1		-Unix Agent

Author

@@ -1,1 +1,1 @@
--XWiki.SV
++XWiki.jklein

Content

@@ -3,14 +3,6 @@
  (% class="wikigeneratedid" %)
  The Unix Agent is the completely renewed and technically revised further development of the Linux and Mac agents. The agent can be deployed and installed without Python using a supplied Client Command. The inventory data is transmitted to the ACMP Server in full and updated.
--{{aagon.infobox}}
--If you use Unix clients that are not connected to the network, you can inventory them using the [[Unix Offline Scanner>>doc:ACMP.610.Arbeiten mit der ACMP Console.Clients erfassen.Offline Scanner.WebHome||anchor="“HRunUnixOfflineScanner”"]].
--{{/aagon.infobox}}
--
--{{aagon.versionierungsbox}}
--Please note that the assignment of a maintenance window profile to containers with Unix agents is only supported in its full form starting with AESB version 1.12. Additionally, creating a maintenance window profile is possible starting with ACMP version 6.9.
--{{/aagon.versionierungsbox}}
--
  = Installation requirements =
  There are several requirements for you and your system for installing the Unix Agent.
@@ -39,36 +39,21 @@
  * Linux and MacOS Clients must be able to reach SICS via Rest (any firewalls must allow port 3950).
  * Firewall settings for SICS must be customizable if necessary.
--{{box}}
--**Note**: Please note that the Unix Agent has been advanced with additional scanners in ACMP version 6.10. The System Scanner requires certain packages for this purpose, which must be installed or downloaded on Linux environments.
--You will need the following packages:
--**TPM**:
++{{aagon.warnungsbox}}
++If you want to install the Unix agent on MacOS devices with an M1 or M2 chip, you must first install the //Rosetta 2 //framework on your MacOS devices. For more information, see [[Apple Support.>>https://support.apple.com/de-de/102527]]
++{{/aagon.warnungsbox}}
--*  „tpm-tools“ for TPM 1.2 Chips
--* -„tpm2-tools“ for TPM 2.0 Chips
--
--**Login History**:
--
--* „util-linux“
--
--Execute these packages in the terminal.
--__Example__: For Ubuntu 24.04, the installation commands would be as follows:
--„sudo apt install tpm-tools“
--„sudo apt install tpm2-tools“
--„sudo apt install util-linux“
--{{/box}}
--
  = Installation with the Client Command =
--An existing SICS connection to the ACMP server is required to install the Unix Agent. If you have not yet configured a SICS connection, you must do so first. Instructions for configuring the SICS connection can be found in the section [[Configuring the SICS connection>>doc:AESB.111.AESB installieren, konfigurieren und aktualisieren.SICS-Verbindung konfigurieren.WebHome]].
++An existing SICS connection to the ACMP server is required to install the Unix Agent. If you have not yet configured a SICS connection, you must do so first. Instructions for configuring the SICS connection can be found in the section [[Configuring the SICS connection>>doc:AESB.19.AESB installieren, konfigurieren und aktualisieren.SICS-Verbindung konfigurieren.WebHome]].
  The Unix Agent is installed using a Client Command in ACMP. To do this, the Client Command must first be imported and released.
--{{aagon.warnungsbox}}
++{{aagon.warning box}}
  Installing the Unix Agent stops and removes the Linux Agent.
  The ClientID used by the Linux Agent is retained and reused by the Unix Agent.
--{{/aagon.warnungsbox}}
++{{/aagon.warning box}}
  === Import and release Client Command ===
@@ -76,12 +76,8 @@
  {{{ACMP Unix Agent verteilen & Inventory__{1F5A4238-731B-44B6-84F0-3EFB8F2D3222}.sim}}}
--For information on how to import and release a Client Command in ACMP, refer to the section [[Create Client Commands>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Client Commands.Client Command erstellen.WebHome||anchor="HImport"]].
++For information on how to import and release a Client Command in ACMP, refer to the section [[Create Client Commands>>doc:ACMP.67.ACMP-Solutions.Client Commands.Client Command erstellen.WebHome||anchor="HImport"]] .
--{{aagon.warnungsbox}}
--To ensure that clients are properly detected and can be managed, you must use a version of the Unix Agent that is compatible with your ACMP version. Otherwise, your Linux and macOS clients will not be detected as manageable clients.
--{{/aagon.warnungsbox}}
--
  === Execute Client Command ===
  After you have released the Client Command, you can execute it.
@@ -90,7 +90,7 @@
  In the dialog window that opens, click the //Execute// button. The Client Command interface opens, where you can configure the installation of the Unix Agent.
--[[Configuring the Unix Agent using the Client Command>>image:Unix Agent - Fallback-SICS.png||alt="“Configuring" data-xwiki-image-style-alignment="center" height="600" width="480"]]
++[[Configuring the Unix Agent using the Client Command>>image:Unix Agent - Fallback-SICS.png||alt=“Configuring the Unix Agent using the Client Command” data-xwiki-image-style-alignment=“center” height="600" width="480"]]
  = Configuring the Unix Agent =
@@ -100,7 +100,7 @@
  The Unix Agent is transferred to the target computers via SSH; valid user data must be entered accordingly. Unlike the Linux Agent, the Unix Agent transfers the scan data directly to the ACMP Server.
--{{aagon.warnungsbox}}
++{{aagon.warningsbox}}
  The user whose user data is specified as SSH credentials for the installation must be created on each of the target computers and have “sudo” rights (superuser do) there.
  {{/aagon.warnungsbox}}
@@ -110,29 +110,16 @@
  === Specify SICS credentials ===
--To perform the installation of the Unix Agent on the target computers, you must enter your SICS session data.
++To install the Unix Agent on the target computers, you must specify your SICS session data. The specified endpoint must be in the format //wss:~/~/ipaddress:port//. Please note that all target computers must have access to this endpoint. You assigned the continuing user data to the operator during the AESB installation.
--**SICS user**
++You can also specify multiple fallback SICS connections in the tabs. If the primary SICS connection fails and cannot be used, an attempt is made to establish a connection to another defined SICS and to carry out the transfer via one of the fallback connections. The list of fallback SICS connections is used continuously, starting with fallback SICS #1, until a connection to one of the defined fallback SICS connections can be established or there are no more fallback connections in the list.
--For the SICS user, you can create an AESB user with minimal permissions. This user must be created in the AESB console. For more info, see the section [[managing AESB users>>https://doc.aagon.com/bin/view/AESB/111/Workspaces/Benutzer/#HBenutzerverwalten]].
++(% class="box infomessage" %)
++((
++[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt=“Note” height="32" width="32"]] **Note: **
--**SICS server**
--
--The endpoint must be specified in the format “wss:~/~/server:port”, for example:
--
--* wss:~/~/ipaddress:port
--* wss:~/~/hostname:port
--* wss:~/~/FQHN:port (Fully Qualified Host Name)
--
--Please note that all target computers require access to this endpoint. You assigned the additional user credentials for the operator during the AESB installation.
--
--**SICS Fallbacks**
--
--In the tabs, you can specify multiple fallback SICS connections. If the primary SICS connection fails and cannot be used, the system will attempt to establish a connection to another defined SICS and perform the transfer via one of the fallback connections. The list of fallback SICS connections is used continuously, starting with Fallback SICS #1, until a connection to one of the defined fallback SICS connections has been established or there are no continuing fallback connections remaining in the list.
--
--{{aagon.infobox}}
  If the connection to one of the defined fallback SICS could be established successfully, the connection is maintained until the next restart.
--{{/aagon.infobox}}
++)))
  === Options ===
@@ -150,9 +150,11 @@
  To install the Unix Agent as a permanent resource, you can execute the agent in the //Agent Installation// mode. The Unix Agent is now transferred to the target computer and registered as a service. Following installation, the agent starts automatically and obtains its configuration from ACMP within 10 minutes. The agent is now entered as a client in ACMP and contains the basic client details. The execution file can be found under the path: ##/usr/local/sbin/aagon/ACMPUnixAgent/##
--The agent also uses another directory to store various resources that are relevant to the agent. This directory can be found under the path:## /etc/aagon/ACMPUnixAgent/##
++The agent also uses another directory to store various resources that are relevant to the agent. This directory can be found under the path:## /etc/aagon/ACMPUnixAgent/##
++((
  The Agent Tasks templates are used to execute the scanners. These can be used in exactly the same way as with the ACMP Windows Agent (Container). The following jobs are currently taken into account within the Agent Tasks:
++)))
  * System scanner
  * Software scanner
@@ -166,7 +166,7 @@
  In the //Activated Scanners// area, you can disable individual scanners. This is useful if you do not need certain information or if problems occur with one or more scanners.
--=== Client Command Settings ===
++=== CC Settings ===
  By clicking the checkbox in the CC Settings area, you can specify that no confidential information (e.g., passwords) is stored in the Client Command.
@@ -175,7 +175,7 @@
  After executing the Client Command, a dialog window will appear informing you whether the Client Command was executed successfully. The number of processed Clients is displayed, along with information on whether connection errors (SSH errors) were detected.
  {{figure}}
--[[image:CC_Erfolgsmeldung.png||alt="“Success" data-xwiki-image-style-alignment="“center”"]]
++[[image:CC_Erfolgsmeldung.png||alt=“Success message about installation of the Unix Agent” data-xwiki-image-style-alignment=“center”]]
  {{figureCaption}}
  Success message about installation of the Unix Agent
@@ -184,104 +184,86 @@
  = Logging =
--If connection errors occur during the execution of the Unix Agent, these errors are written to the file ##SSH_Errors.log## and to the log of the Client Command. You can find the file either in the default folder ##C:\Logs## or in the directory you specified for logging the Unix Agent.
++Sollte es bei der Ausführung vom Unix Agent zu Verbindungsfehler kommen, werden diese Fehler in die Datei ##SSH_Errors.log## und in das Log des Client Commands geschrieben. Die Datei finden Sie entweder im Standard-Ordner ##C:\Logs## oder in dem Verzeichnis, das Sie für das Logging des Unix Agents angegeben haben.
  {{aagon.infobox}}
--These connection errors do not cause the Client Command to be terminated. Therefore, these errors are not displayed if you have selected the logging setting //Only on errors //for the console log.
++Diese Verbindungsfehler führen nicht zu einem Abbruch des Client Commands. Daher werden diese Fehler nicht angezeigt, wenn Sie die Logging-Einstellung //Nur bei Fehlern //für das Consolen-Log ausgewählt haben.
  {{/aagon.infobox}}
--If you would like to receive immediate feedback about possible connection errors after executing the Client Command, you should either select the //Always //option for the console log settings or check the file ##SSH_Errors.log##.
++Falls Sie also nach einer Ausführung des Client Commands direkt Feedback über mögliche Verbindungsfehler haben möchte, sollte Sie für die Logging-Einstellung des Consolen-Logs entweder die Option //Immer //wählen oder in der Datei ##SSH_Errors.log## nachschauen.
  = Troubleshooting =
--Below you will find solutions to various problems that may occur during the installation of the Unix Agent.
++Im Folgenden finden Sie Lösungen zu verschiedenen Problemen, die bei der Installation des Unix Agent auftreten können.
  ----
--**Symptom:** The Unix Agent could not be deployed on the Clients and no errors are displayed in the log.
++**Symptom:** Der Unix Agent konnte nicht auf den Clients verteilt werden und im Log werden keine Fehler angezeigt.
--**Cause: **The Unix Agent does not yet exist as a service, so no errors can be written to the log.
++**Ursache: **Der Unix Agent ist noch gar nicht als Service vorhanden, daher können auch keine Fehler in das Log geschrieben werden.
--**Action: **Start troubleshooting in your system's journalctl and find entries for the failed installation of the Unix Agent.
++**Maßnahme: **Beginnen Sie die Fehlersuche im journalctl Ihres Systems und suchen Sie dort nach Einträgen zur fehlgeschlagenen Installation des Unix Agents.
  ----
--**Symptom:** After distributing the Unix Agent using the Client Command, the Unix client does not appear in ACMP.
++**Symptom:** Nach der Verteilung des Unix Agents mittels des Client Commands taucht der Unix-Client nicht in ACMP auf.
--**Cause:** An error occurred during the execution of the Client Command, but was not immediately apparent due to the settings.
++**Ursache:** Es trat ein Fehler bei der Ausführung des Client Commands auf, der aber aufgrund der Einstellungen nicht direkt ersichtlich war.
--**Action:** In the properties of the Client Command in the plugin //Options //in the Combobox //Show console log// enable the option //Only on errors// and confirm the
--dialog with //OK//. After executing the Client Command again, a console log should now be displayed in the event of an error, which may provide information about the cause of the problem.
++**Maßnahme:** Aktivieren Sie in den Eigenschaften des Client Commands im Plugin //Optionen //in der Combobox //Consolen-Log anzeigen// die Option //Nur bei Fehlern// und bestätigen Sie den
++Dialog mit //OK//. Nach einer erneuten Ausführung des Client Commands, sollte nun im Falle eines Fehlers ein Consolen-Log angezeigt werden, das ggf. Aufschluss über die Ursache des Problems liefert.
--If the Unix systems still do not appear in ACMP, there may be many reasons for this. It is therefore recommended to activate logging for the agent and the SICS.  Then go through the chain from start to end.
++Falls die Unix-Systeme immer noch nicht im ACMP auftauchen, kann dies viele Gründe haben. Deswegen empfiehlt es sich, das Logging für den Agent und den SICS zu aktivieren.  Anschließend sollte man die Kette von Anfang bis Ende durchgehen.
  ----
--**Symptom:** After distributing the Unix Agent using the Client Command, the Unix client does not appear in ACMP. The error “Invalid input detected: endpoint” is displayed in the SmartInspect log.
++**Symptom:** Nach der Verteilung des Unix Agents mittels des Client Commands taucht der Unix-Client nicht in ACMP auf. Im SmartInspect Log wird der Fehler „Invalid input detected: endpoint"  angezeigt.
--**Cause:** An error occurred during the connection to SICS because the protocol may not have been prefixed during the connection. You can see this in the SmartInspect log in the row //Application settings//: ##“SicsEndpoint: <AESB-SICS-NAME_IP>:3950”##
++**Ursache:** Es trat ein Fehler bei der Verbindung zum SICS auf, weil das Protokoll ggf. bei der Verbindung nicht vorangestellt wurde. Dies können Sie im SmartInspect Log in der Zeile //Application settings// erkennen: ##„SicsEndpoint: <AESB-SICS-NAME_IP>:3950“##
--**Action:** Make sure that the SICS endpoint is set to ##wss:~/~/<AESB-SICS-NAME_IP>:3950## and not just ##<AESB-SICS-NAME_IP>:3950##
++**Maßnahme:** Stellen Sie sicher, dass als SICS-Endpoint ##wss:~/~/<AESB-SICS-NAME_IP>:3950## verwendet wird und nicht nur ##<AESB-SICS-NAME_IP>:3950##
  ----
--**Symptom:** The Unix Agent is not located on the target system at the following location: ##/usr/local/sbin/aagon/ACMPUnixAgent.##
++**Symptom:** Der Unix Agent liegt nicht auf dem Zielsystem an der Stelle: ##/usr/local/sbin/aagon/ACMPUnixAgent.##
--**Cause:** There may be several causes for this problem:
++**Ursache:** Diesem Problem können mehrere Ursachen zugrunde liegen:
--* The login user is not allowed to obtain root rights via sudo.
--* The user has root rights, but root is not allowed to log in via SSH.
--* The user has root rights and root is not allowed to log in via SSH, but the SSH daemon is not running properly.
++* Der Loginuser darf sich nicht per sudo Root-Rechte verschaffen.
++* Der User besitzt Root-Rechte, aber Root darf sich nicht per SSH einloggen.
++* Der User besitzt Root-Rechte und Root darf sich nicht per SSH einloggen, aber der SSH-Daemon läuft nicht ordnungsgemäß.
--**Action:** Make sure that the SSH user is allowed to log in via SSH and can obtain root rights.
++**Maßnahme:** Stellen Sie sicher, dass der SSH-Benutzer sich per SSH einloggen darf und sich Root-Rechte verschaffen kann.
  ----
--**Symptom:** The Unix agent starts but does not reach the //running// status.
++**Symptom:** Der Unix Agent startet, erreicht aber nicht den Status //running//.
--**Cause:** The agent does not seem to be able to connect to SICS.
++**Ursache:** Der Agent scheint keine Verbindung zum SICS zu bekommen.
--**Action:** Check whether the network connection to SICS is working. If this does not solve the problem, enable logging in the Client Command and perform the action again. Then look for error messages in the output.
++**Maßnahme:** Überprüfen Sie, ob die Netzwerkverbindung zum SICS funktioniert. Falls dies das Problem nicht behebt, aktivieren Sie das Client Command das Logging und führen Sie die Aktion erneut durch. Suchen Sie anschließend in der Ausgabe nach Fehlermeldungen.
  ----
--**Symptom:** The agent is not started at system start.
++**Symptom:** Der Agent wird beim Systemstart nicht mit gestartet.
--**Cause:** Something went wrong when setting up or starting the service.
++**Ursache:** Beim Einrichten oder Starten des Dienstes ist etwas fehlgeschlagen.
--**Action:** Execute the Client Command for installing the Unix Agent again.
++**Maßnahme:** Führen Sie das Client Command zur Installation des Unix-Agent erneut aus.
  ----
--**Symptom:** The Unix Agent is running, but the corresponding Unix client does not appear in an ACMP query.
++**Symptom:** Der Unix Agent läuft, aber der entsprechende Unix-Client taucht nicht in einer ACMP-Abfrage auf.
--**Cause:** The SICS cannot forward the scan data of the Unix Agent to the ACMP Server because the connection is not available.
++**Ursache:** Der SICS kann die Scan-Daten des Unix Agenten nicht an den ACMP Server weiterleiten, weil die Verbindung nicht verfügbar ist.
--**Action:** Check in the ACMP Console settings whether the SICS connection of the ACMP Server is still working (in the ACMP Server / SICS connection plugin) and whether the checkbox for SICS users to access the public API is activated. Further information on this problem can be found in the log of the ACMP Server or the Unix Agent.
++**Maßnahme:** Prüfen Sie in den Einstellungen der ACMP Console, ob die SICS-Verbindung des ACMP Servers noch funktioniert (im Plugin ACMP Server / SICS-Verbindung) und ob die Checkbox für den Zugriff von SICS-Benutzern auf die Public API aktiviert ist. Weitere Informationen zu diesem Problem finden Sie ggf. im Log des ACMP Servers oder des Unix Agents.
  ----
--**Symptom:** The Unix client appears in an ACMP query, but no scan data is available.
++**Symptom:** In einer ACMP-Abfrage taucht der Unix-Client auf, aber es sind keine Scandaten verfügbar.
--**Cause:** During installation, the system waits between 2 and 10 minutes until the scan settings for this Unix client are retrieved by sending a request to the ACMP Server.
++**Ursache:** Bei der Installation wird zwischen 2 und 10 Minuten gewartet, bis mittels einer Anfrage an den ACMP Server die für diesen Unix-Client getätigten Scan-Einstellungen geholt werden.
--**Action: **If necessary, wait a little longer until the scan data has been loaded. If no scan data appears after significantly more than 10 minutes, you should enable logging for all components involved and check the entire chain from start to end for errors.
--
--= **Updating the Unix Agent** =
--
--Updating the Unix Agent is done in the same way as its [[installation via a Client Command.>>||anchor="HInstallationwiththeClientCommand"]]
--
--In this process, the agent is redistributed and installed on the target systems via the ACMP Console. The transfer takes place via SSH using the appropriate permissions. During execution, the existing agent is replaced by the current version and reconfigured as a service.
--
--The agent then starts automatically and takes over the existing communication with the ACMP Server.
--
--= Administration of Linux and MacOS Clients =
--
--Previously, clients running Linux or macOS could only be detected and inventoried with the Unix Agent. They could not, however, be administered, and no shell scripts or jobs could be executed on these clients. Now, newly detected Linux and macOS clients can be managed if inventoried using the Unix Agent. This also enables the automated, time-controlled execution of Unix scripts as jobs. For more info, see the section [[Unix Scripts>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Unix Scripts.WebHome]].
--
--(% class="box infomessage" %)
--(((
--[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt="Hinweis" height="32" width="32"]]  **Note: **
--
-- All Linux and MacOS clients that are registered with Unix Agent version 1.10 or older cannot be managed. To make your Linux or MacOS clients manageable, register them again via the Unix Agent.
--)))
++**Maßnahme: **Warten Sie ggf. noch etwas länger, bis die Scandaten geladen wurden. Falls nach deutlich mehr als 10 Minuten immer noch keine Scandaten auftauchen, sollten Sie das Logging für alle beteiligten Komponenten aktivieren und die gesamte Kette von Anfang bis Ende auf Fehler prüfen.
++{{/aagon.warning}}