Changes for page Unix Agent installieren
Last modified by Sabrina V. on 2026/06/02 12:29
From version 10.1
edited by Sabrina V.
on 2026/04/16 05:41
on 2026/04/16 05:41
Change comment:
There is no comment for this version
To version 13.1
edited by Sabrina V.
on 2026/06/01 12:11
on 2026/06/01 12:11
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,7 +4,7 @@ 4 4 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. 5 5 6 6 {{aagon.infobox}} 7 -If you use Unix clients that are not connected to the network, you can inventory them using the [[Unix Offline Scanner>>doc:ACMP.6 9.Arbeiten mit der ACMP Console.Clients erfassen.Offline Scanner.WebHome||anchor="“HRunUnixOfflineScanner”"]].7 +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”"]]. 8 8 {{/aagon.infobox}} 9 9 10 10 {{aagon.versionierungsbox}} ... ... @@ -41,7 +41,7 @@ 41 41 42 42 = Installation with the Client Command = 43 43 44 -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.1 9.AESB installieren, konfigurieren und aktualisieren.SICS-Verbindung konfigurieren.WebHome]].44 +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]]. 45 45 46 46 The Unix Agent is installed using a Client Command in ACMP. To do this, the Client Command must first be imported and released. 47 47 ... ... @@ -57,8 +57,12 @@ 57 57 58 58 {{{ACMP Unix Agent verteilen & Inventory__{1F5A4238-731B-44B6-84F0-3EFB8F2D3222}.sim}}} 59 59 60 -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"]] .60 +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"]]. 61 61 62 +{{aagon.warnungsbox}} 63 +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. 64 +{{/aagon.warnungsbox}} 65 + 62 62 === Execute Client Command === 63 63 64 64 After you have released the Client Command, you can execute it. ... ... @@ -87,10 +87,26 @@ 87 87 88 88 === Specify SICS credentials === 89 89 90 -To install the Unix Agent on the target computers, you must specifyyour 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.94 +To perform the installation of the Unix Agent on the target computers, you must enter your SICS session data. 91 91 92 - You can also specify multiple fallbackSICSconnections in the tabs. If the primary SICS connection fails and cannot beused, an attempt is made to establish a connection to anotherdefined 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.96 +**SICS user** 93 93 98 +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]]. 99 + 100 +**SICS server** 101 + 102 +The endpoint must be specified in the format “wss:~/~/server:port”, for example: 103 + 104 +* wss:~/~/ipaddress:port 105 +* wss:~/~/hostname:port 106 +* wss:~/~/FQHN:port (Fully Qualified Host Name) 107 + 108 +Please note that all target computers require access to this endpoint. You assigned the additional user credentials for the operator during the AESB installation. 109 + 110 +**SICS Fallbacks** 111 + 112 +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. 113 + 94 94 {{aagon.infobox}} 95 95 If the connection to one of the defined fallback SICS could be established successfully, the connection is maintained until the next restart. 96 96 {{/aagon.infobox}}

