Changes for page Unix Agent installieren

Summary

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

Details

Page properties

Content

...	...	@@ -7,10 +7,6 @@
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.69.Arbeiten mit der ACMP Console.Clients erfassen.Offline Scanner.WebHome||anchor="“HRunUnixOfflineScanner”"]].
8	8	{{/aagon.infobox}}
9	9
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.
12		-{{/aagon.versionierungsbox}}
13		-
14	14	= Installation requirements =
15	15
16	16	There are several requirements for you and your system for installing the Unix Agent.
...	...	@@ -57,12 +57,8 @@
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"]].
	56	+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		-
66	66	=== Execute Client Command ===
67	67
68	68	After you have released the Client Command, you can execute it.
...	...	@@ -91,26 +91,10 @@
91	91
92	92	=== Specify SICS credentials ===
93	93
94		-To perform the installation of the Unix Agent on the target computers, you must enter your SICS session data.
	86	+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.
95	95
96		-**SICS user**
	88	+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.
97	97
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		-
114	114	{{aagon.infobox}}
115	115	If the connection to one of the defined fallback SICS could be established successfully, the connection is maintained until the next restart.
116	116	{{/aagon.infobox}}
...	...	@@ -248,14 +248,6 @@
248	248
249	249	**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.
250	250
251		-= **Updating the Unix Agent** =
252		-
253		-Updating the Unix Agent is done in the same way as its [[installation via a Client Command.>>||anchor="HInstallationwiththeClientCommand"]]
254		-
255		-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.
256		-
257		-The agent then starts automatically and takes over the existing communication with the ACMP Server.
258		-
259	259	= Administration of Linux and MacOS Clients =
260	260
261	261	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.68.ACMP-Solutions.Desktop Automation.Unix Scripts.WebHome]].