Changes for page Unix Agent installieren

Summary

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

Details

Page properties

Content

...	...	@@ -1,7 +1,7 @@
1	1	{{aagon.floatingbox/}}
2	2
3	3	(% class="wikigeneratedid" %)
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.
	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	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,7 +8,7 @@
8	8	{{/aagon.infobox}}
9	9
10	10	{{aagon.versionierungsbox}}
11		-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.
	11	+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.
12	12	{{/aagon.versionierungsbox}}
13	13
14	14	= Installation requirements =
...	...	@@ -15,17 +15,17 @@
15	15
16	16	There are several requirements for you and your system for installing the Unix Agent.
17	17
18		-=== Requirements for your knowledge of ACMP ===
	18	+=== Requirements for your knowledge of acmp ===
19	19
20	20	* You have a basic understanding of how to configure SICS.
21		-* You know how to import Client Commands into ACMP.
	21	+* You know how to import Client Commands into acmp.
22	22	* You know how to execute Client Commands.
23	23
24	24	=== Requirements for your environment ===
25	25
26		-* ACMP is installed.
	26	+* acmp is installed.
27	27	* SICS is installed on a server.
28		-* The ACMP Server is connected to SICS.
	28	+* The acmp Server is connected to SICS.
29	29	* SICS users are allowed to access the public API.
30	30
31	31	=== Requirements for your MacOS and Linux systems ===
...	...	@@ -39,17 +39,20 @@
39	39	* Linux and MacOS Clients must be able to reach SICS via Rest (any firewalls must allow port 3950).
40	40	* Firewall settings for SICS must be customizable if necessary.
41	41
42		-{{box}}
43		-**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.
	42	+{{aagon.infobox}}
	43	+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.
	44	+
	45	+The Unix Agent reads the TPM information from the physical devices and then populates certain fields (e.g., “TPM enabled,” “TPM on,” or “TPM manufacturer”) with the corresponding values.
	46	+
44	44	You will need the following packages:
45		-**TPM**:
	48	+**TPM:**
46	46
47		-* „tpm-tools“ for TPM 1.2 Chips
48		-* -„tpm2-tools“ for TPM 2.0 Chips
	50	+ „tpm-tools“ for TPM 1.2 Chips
	51	+ -„tpm2-tools“ for TPM 2.0 Chips
49	49
50		-**Login History**:
	53	+**Login History:**
51	51
52		-* „util-linux“
	55	+ „util-linux“
53	53
54	54	Execute these packages in the terminal.
55	55	__Example__: For Ubuntu 24.04, the installation commands would be as follows:
...	...	@@ -56,13 +56,13 @@
56	56	„sudo apt install tpm-tools“
57	57	„sudo apt install tpm2-tools“
58	58	„sudo apt install util-linux“
59		-{{/box}}
	62	+{{/aagon.infobox}}
60	60
61	61	= Installation with the Client Command =
62	62
63		-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]].
	66	+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]].
64	64
65		-The Unix Agent is installed using a Client Command in ACMP. To do this, the Client Command must first be imported and released.
	68	+The Unix Agent is installed using a Client Command in acmp. To do this, the Client Command must first be imported and released.
66	66
67	67	{{aagon.warnungsbox}}
68	68	Installing the Unix Agent stops and removes the Linux Agent.
...	...	@@ -74,12 +74,12 @@
74	74
75	75	The file for the required Client Command of the Unix Agent is named as in the following example:
76	76
77		-{{{ACMP Unix Agent verteilen & Inventory__{1F5A4238-731B-44B6-84F0-3EFB8F2D3222}.sim}}}
	80	+{{{acmp Unix Agent verteilen & Inventory__{1F5A4238-731B-44B6-84F0-3EFB8F2D3222}.sim}}}
78	78
79		-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"]].
	82	+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"]].
80	80
81	81	{{aagon.warnungsbox}}
82		-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.
	85	+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.
83	83	{{/aagon.warnungsbox}}
84	84
85	85	=== Execute Client Command ===
...	...	@@ -86,7 +86,7 @@
86	86
87	87	After you have released the Client Command, you can execute it.
88	88
89		-In the ACMP Console, navigate to Client Commands > Execute. Then double-click to select the Client Command for the Unix Agent.
	92	+In the acmp Console, navigate to Client Commands > Execute. Then double-click to select the Client Command for the Unix Agent.
90	90
91	91	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.
92	92
...	...	@@ -98,7 +98,7 @@
98	98
99	99	=== SSH credentials ===
100	100
101		-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.
	104	+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.
102	102
103	103	{{aagon.warnungsbox}}
104	104	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.
...	...	@@ -114,7 +114,7 @@
114	114
115	115	**SICS user**
116	116
117		-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]].
	120	+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]].
118	118
119	119	**SICS server**
120	120
...	...	@@ -124,7 +124,7 @@
124	124	* wss:~/~/hostname:port
125	125	* wss:~/~/FQHN:port (Fully Qualified Host Name)
126	126
127		-Please note that all target computers require access to this endpoint. You assigned the additional user credentials for the operator during the AESB installation.
	130	+Please note that all target computers require access to this endpoint. You assigned the additional user credentials for the operator during the aesb installation.
128	128
129	129	**SICS Fallbacks**
130	130
...	...	@@ -140,7 +140,7 @@
140	140
141	141	**Enable logging**
142	142
143		-By selecting the //Enable logging// option, you can load the logs to your machine (or the machine with the ACMP Console) after installation or execution. Enabling logging is already available at this point in the Client Command and can be useful, as errors may occur during installation or execution as Inventory One-Time-Scan.
	146	+By selecting the //Enable logging// option, you can load the logs to your machine (or the machine with the acmp Console) after installation or execution. Enabling logging is already available at this point in the Client Command and can be useful, as errors may occur during installation or execution as Inventory One-Time-Scan.
144	144
145	145	**One-time scan**
146	146
...	...	@@ -148,11 +148,11 @@
148	148
149	149	**Agent installation**
150	150
151		-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/##
	154	+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/##
152	152
153	153	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/##
154	154
155		-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:
	158	+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:
156	156
157	157	* System scanner
158	158	* Software scanner
...	...	@@ -206,7 +206,7 @@
206	206
207	207	----
208	208
209		-**Symptom:** After distributing the Unix Agent using the Client Command, the Unix client does not appear in ACMP.
	212	+**Symptom:** After distributing the Unix Agent using the Client Command, the Unix client does not appear in acmp.
210	210
211	211	**Cause:** An error occurred during the execution of the Client Command, but was not immediately apparent due to the settings.
212	212
...	...	@@ -213,11 +213,11 @@
213	213	**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
214	214	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.
215	215
216		-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.
	219	+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.
217	217
218	218	----
219	219
220		-**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.
	223	+**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.
221	221
222	222	**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”##
223	223
...	...	@@ -253,17 +253,17 @@
253	253
254	254	----
255	255
256		-**Symptom:** The Unix Agent is running, but the corresponding Unix client does not appear in an ACMP query.
	259	+**Symptom:** The Unix Agent is running, but the corresponding Unix client does not appear in an acmp query.
257	257
258		-**Cause:** The SICS cannot forward the scan data of the Unix Agent to the ACMP Server because the connection is not available.
	261	+**Cause:** The SICS cannot forward the scan data of the Unix Agent to the acmp Server because the connection is not available.
259	259
260		-**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.
	263	+**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.
261	261
262	262	----
263	263
264		-**Symptom:** The Unix client appears in an ACMP query, but no scan data is available.
	267	+**Symptom:** The Unix client appears in an acmp query, but no scan data is available.
265	265
266		-**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.
	269	+**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.
267	267
268	268	**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.
269	269
...	...	@@ -271,9 +271,9 @@
271	271
272	272	Updating the Unix Agent is done in the same way as its [[installation via a Client Command.>>||anchor="HInstallationwiththeClientCommand"]]
273	273
274		-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.
	277	+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.
275	275
276		-The agent then starts automatically and takes over the existing communication with the ACMP Server.
	279	+The agent then starts automatically and takes over the existing communication with the acmp Server.
277	277
278	278	= Administration of Linux and MacOS Clients =
279	279