Unix Agent

(% 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.

5

6

= Installation requirements =

7

8

There are several requirements for you and your system for installing the Unix Agent.

9

10

=== Requirements for your knowledge of ACMP ===

11

12

* You have a basic understanding of how to configure SICS.

13

* You know how to import Client Commands into ACMP.

14

* You know how to execute Client Commands.

15

16

=== Requirements for your environment ===

17

18

* ACMP is installed.

19

* SICS is installed on a server.

20

* The ACMP Server is connected to SICS.

21

* SICS users are allowed to access the public API.

22

23

=== Requirements for your MacOS and Linux systems ===

24

25

Our [[general system requirements>>https://www.aagon.com/produkte/ueberblick/systemanforderungen-acmp/#c4421]] provide an overview of all tested distributions.

26

27

In addition, certain settings are required on your systems:

28

29

* An installed SSH server that is accessible from outside (important for agent distribution).

30

* Root must be able to log in from outside via ssh or, alternatively, a user who can obtain root rights via sudo (sudo must be installed for the alternative).

31

* Linux and MacOS Clients must be able to reach SICS via Rest (any firewalls must allow port 3950).

32

* Firewall settings for SICS must be customizable if necessary.

33

34

= Installation with the Client Command =

35

36

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]].

37

38

The Unix Agent is installed using a Client Command in ACMP. To do this, the Client Command must first be imported and released.

39

40

41

Installing the Unix Agent stops and removes the Linux Agent.

42

43

The ClientID used by the Linux Agent is retained and reused by the Unix Agent.

44

45

46

=== Import and release Client Command ===

47

48

The file for the required Client Command of the Unix Agent is named as in the following example:

49

50

{{{ACMP Unix Agent verteilen & Inventory__{1F5A4238-731B-44B6-84F0-3EFB8F2D3222}.sim}}}

51

52

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"]] .

53

54

=== Execute Client Command ===

55

56

After you have released the Client Command, you can execute it.

57

58

In the ACMP Console, navigate to Client Commands > Execute. Then double-click to select the Client Command for the Unix Agent.

59

60

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.

61

62

[[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"]]

63

64

= Configuring the Unix Agent =

65

66

For the configuration of the Unix Agent, there are various areas in the Client Command where you can make specific settings.

67

68

=== SSH credentials ===

69

70

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.

71

72

73

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.

74

75

76

=== Select Clients ===

77

78

In the upper right corner of the dialog window, you can use the IPv4 address to specify the clients on which the Unix Agent is to be deployed. To do this, you can either specify an IPv4 range or compile a list of IPv4 addresses.

79

80

=== Specify SICS credentials ===

81

82

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.

83

84

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.

85

86

87

If the connection to one of the defined fallback SICS could be established successfully, the connection is maintained until the next restart.

=== Options ===

In the //Options //area, you can configure settings for logging and specify the mode in which the agent should be executed.

**Enable logging**

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.

**One-time scan**

For a one-time inventory of a client, the agent can be executed in //One-time scan// mode. The Unix agent is now transferred to the target computer and started. After the scanner has been executed successfully, the agent is removed from the system again. To ensure that the new results can be assigned accordingly when the //One-time scan// mode is executed again, the ClientID remains on the client. You can find this under the path: ##/etc/aagon/ACMPUnixAgent/agentId##

101

102

**Agent installation**

103

104

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/##

105

106

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/##

107

108

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

* Update settings

**Uninstall agent**

To uninstall the Unix agent as a service, you can execute the agent in the //Uninstall agent// mode. The registered Unix agent service is now removed from the target computer together with the execution file.

117

118

=== Activated scanners ===

119

120

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.

121

122

=== Client Command Settings ===

123

124

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.

125

126

=== Feedback on execution ===

127

128

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.

129

130

131

[[image:CC_Erfolgsmeldung.png||alt="“Success" data-xwiki-image-style-alignment="“center”"]]

132

133

134

Success message about installation of the Unix Agent

= 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.

141

142

143

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.

144

145

146

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##.

= Troubleshooting =

Below you will find solutions to various problems that may occur during the installation of the Unix Agent.

----

**Symptom:** The Unix Agent could not be deployed on the Clients and no errors are displayed in the log.

155

156

**Cause: **The Unix Agent does not yet exist as a service, so no errors can be written to the log.

157

158

**Action: **Start troubleshooting in your system's journalctl and find entries for the failed installation of the Unix Agent.

----

**Symptom:** After distributing the Unix Agent using the Client Command, the Unix client does not appear in ACMP.

163

164

**Cause:** An error occurred during the execution of the Client Command, but was not immediately apparent due to the settings.

165

166

**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

167

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.

168

169

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.

----

**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.

174

175

**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”##

176

177

**Action:** Make sure that the SICS endpoint is set to ##wss:~/~/<AESB-SICS-NAME_IP>:3950## and not just ##<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.##

182

183

**Cause:** There may be several causes for this problem:

184

185

* The login user is not allowed to obtain root rights via sudo.

186

* The user has root rights, but root is not allowed to log in via SSH.

187

* The user has root rights and root is not allowed to log in via SSH, but the SSH daemon is not running properly.

188

189

**Action:** Make sure that the SSH user is allowed to log in via SSH and can obtain root rights.

----

**Symptom:** The Unix agent starts but does not reach the //running// status.

194

195

**Cause:** The agent does not seem to be able to connect to SICS.

196

197

**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.

----

**Symptom:** The agent is not started at system start.

202

203

**Cause:** Something went wrong when setting up or starting the service.

204

205

**Action:** Execute the Client Command for installing the Unix Agent again.

----

**Symptom:** The Unix Agent is running, but the corresponding Unix client does not appear in an ACMP query.

210

211

**Cause:** The SICS cannot forward the scan data of the Unix Agent to the ACMP Server because the connection is not available.

212

213

**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.

----

**Symptom:** The Unix client appears in an ACMP query, but no scan data is available.

218

219

**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.

220

221

**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.

222

223

= Administration of Linux and MacOS Clients =

224

225

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]].

226

227

(% class="box infomessage" %)

228

(((

229

[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg||alt="Hinweis" height="32" width="32"]] **Note: **

230

231

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.

232

)))

author	version	line-number	content
		1	{{aagon.floatingbox/}}
		2
		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.
		5
		6	= Installation requirements =
		7
		8	There are several requirements for you and your system for installing the Unix Agent.
		9
		10	=== Requirements for your knowledge of ACMP ===
		11
		12	* You have a basic understanding of how to configure SICS.
		13	* You know how to import Client Commands into ACMP.
		14	* You know how to execute Client Commands.
		15
		16	=== Requirements for your environment ===
		17
		18	* ACMP is installed.
		19	* SICS is installed on a server.
		20	* The ACMP Server is connected to SICS.
		21	* SICS users are allowed to access the public API.
		22
		23	=== Requirements for your MacOS and Linux systems ===
		24
		25	Our [[general system requirements>>https://www.aagon.com/produkte/ueberblick/systemanforderungen-acmp/#c4421]] provide an overview of all tested distributions.
		26
		27	In addition, certain settings are required on your systems:
		28
		29	* An installed SSH server that is accessible from outside (important for agent distribution).
		30	* Root must be able to log in from outside via ssh or, alternatively, a user who can obtain root rights via sudo (sudo must be installed for the alternative).
		31	* Linux and MacOS Clients must be able to reach SICS via Rest (any firewalls must allow port 3950).
		32	* Firewall settings for SICS must be customizable if necessary.
		33
		34	= Installation with the Client Command =
		35
		36	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]].
		37
		38	The Unix Agent is installed using a Client Command in ACMP. To do this, the Client Command must first be imported and released.
		39
		40	{{aagon.warnungsbox}}
		41	Installing the Unix Agent stops and removes the Linux Agent.
		42
		43	The ClientID used by the Linux Agent is retained and reused by the Unix Agent.
		44	{{/aagon.warnungsbox}}
		45
		46	=== Import and release Client Command ===
		47
		48	The file for the required Client Command of the Unix Agent is named as in the following example:
		49
		50	{{{ACMP Unix Agent verteilen & Inventory__{1F5A4238-731B-44B6-84F0-3EFB8F2D3222}.sim}}}
		51
		52	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"]] .
		53
		54	=== Execute Client Command ===
		55
		56	After you have released the Client Command, you can execute it.
		57
		58	In the ACMP Console, navigate to Client Commands > Execute. Then double-click to select the Client Command for the Unix Agent.
		59
		60	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.
		61
		62	[[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"]]
		63
		64	= Configuring the Unix Agent =
		65
		66	For the configuration of the Unix Agent, there are various areas in the Client Command where you can make specific settings.
		67
		68	=== SSH credentials ===
		69
		70	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.
		71
		72	{{aagon.warnungsbox}}
		73	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.
		74	{{/aagon.warnungsbox}}
		75
		76	=== Select Clients ===
		77
		78	In the upper right corner of the dialog window, you can use the IPv4 address to specify the clients on which the Unix Agent is to be deployed. To do this, you can either specify an IPv4 range or compile a list of IPv4 addresses.
		79
		80	=== Specify SICS credentials ===
		81
		82	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.
		83
		84	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.
		85
		86	{{aagon.infobox}}
		87	If the connection to one of the defined fallback SICS could be established successfully, the connection is maintained until the next restart.
		88	{{/aagon.infobox}}
		89
		90	=== Options ===
		91
		92	In the //Options //area, you can configure settings for logging and specify the mode in which the agent should be executed.
		93
		94	Enable logging
		95
		96	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.
		97
		98	One-time scan
		99
		100	For a one-time inventory of a client, the agent can be executed in //One-time scan// mode. The Unix agent is now transferred to the target computer and started. After the scanner has been executed successfully, the agent is removed from the system again. To ensure that the new results can be assigned accordingly when the //One-time scan// mode is executed again, the ClientID remains on the client. You can find this under the path: ##/etc/aagon/ACMPUnixAgent/agentId##
		101
		102	Agent installation
		103
		104	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/##
		105
		106	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/##
		107
		108	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:
		109
		110	* System scanner
		111	* Software scanner
		112	* Update settings
		113
		114	Uninstall agent
		115
		116	To uninstall the Unix agent as a service, you can execute the agent in the //Uninstall agent// mode. The registered Unix agent service is now removed from the target computer together with the execution file.
		117
		118	=== Activated scanners ===
		119
		120	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.
		121
		122	=== Client Command Settings ===
		123
		124	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.
		125
		126	=== Feedback on execution ===
		127
		128	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.
		129
		130	{{figure}}
		131	[[image:CC_Erfolgsmeldung.png\|\|alt="“Success" data-xwiki-image-style-alignment="“center”"]]
		132
		133	{{figureCaption}}
		134	Success message about installation of the Unix Agent
		135	{{/figureCaption}}
		136	{{/figure}}
		137
		138	= Logging =
		139
		140	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.
		141
		142	{{aagon.infobox}}
		143	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.
		144	{{/aagon.infobox}}
		145
		146	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##.
		147
		148	= Troubleshooting =
		149
		150	Below you will find solutions to various problems that may occur during the installation of the Unix Agent.
		151
		152	----
		153
		154	Symptom: The Unix Agent could not be deployed on the Clients and no errors are displayed in the log.
		155
		156	Cause: The Unix Agent does not yet exist as a service, so no errors can be written to the log.
		157
		158	Action: Start troubleshooting in your system's journalctl and find entries for the failed installation of the Unix Agent.
		159
		160	----
		161
		162	Symptom: After distributing the Unix Agent using the Client Command, the Unix client does not appear in ACMP.
		163
		164	Cause: An error occurred during the execution of the Client Command, but was not immediately apparent due to the settings.
		165
		166	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
		167	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.
		168
		169	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.
		170
		171	----
		172
		173	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.
		174
		175	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”##
		176
		177	Action: Make sure that the SICS endpoint is set to ##wss:~/~/<AESB-SICS-NAME_IP>:3950## and not just ##<AESB-SICS-NAME_IP>:3950##
		178
		179	----
		180
		181	Symptom: The Unix Agent is not located on the target system at the following location: ##/usr/local/sbin/aagon/ACMPUnixAgent.##
		182
		183	Cause: There may be several causes for this problem:
		184
		185	* The login user is not allowed to obtain root rights via sudo.
		186	* The user has root rights, but root is not allowed to log in via SSH.
		187	* The user has root rights and root is not allowed to log in via SSH, but the SSH daemon is not running properly.
		188
		189	Action: Make sure that the SSH user is allowed to log in via SSH and can obtain root rights.
		190
		191	----
		192
		193	Symptom: The Unix agent starts but does not reach the //running// status.
		194
		195	Cause: The agent does not seem to be able to connect to SICS.
		196
		197	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.
		198
		199	----
		200
		201	Symptom: The agent is not started at system start.
		202
		203	Cause: Something went wrong when setting up or starting the service.
		204
		205	Action: Execute the Client Command for installing the Unix Agent again.
		206
		207	----
		208
		209	Symptom: The Unix Agent is running, but the corresponding Unix client does not appear in an ACMP query.
		210
		211	Cause: The SICS cannot forward the scan data of the Unix Agent to the ACMP Server because the connection is not available.
		212
		213	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.
		214
		215	----
		216
		217	Symptom: The Unix client appears in an ACMP query, but no scan data is available.
		218
		219	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.
		220
		221	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.
		222
		223	= Administration of Linux and MacOS Clients =
		224
		225	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]].
		226
		227	(% class="box infomessage" %)
		228	(((
		229	[[image:https://doc.aagon.com/bin/download/XWiki/Aagon Infobox/WebHome/Information.svg\|\|alt="Hinweis" height="32" width="32"]] Note:
		230
		231	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.
		232	)))

Wiki source code of Unix Agent installieren