AgentX server communicates with the agents installed in the endpoints, manages configurations remotely, and monitors their statuses. It is the communication gateway between AgentX Manager installed in Logpoint and AgentX Client installed in the endpoint.
Release Date: October 21, 2024
Release Version: 1.4.2
Supported On: Logpoint v7.2.0 and later
Download: AgentX_Server_1.4.2.pak
SHA256: 16a4ca441d1fff6d95aa12fe78448506a2afcac8dd262c7de7ba26221e755182
Documentation: AgentX guide
Key Information
- AgentX Cluster can only be configured on a Distributed Logpoint set up using an IP address.
- When using AgentX, keep the IP address as the Logpoint server alias in System Settings. Don’t modify it. If you do, an "AgentX server is down" error is triggered when adding a device in AgentX.
-
If there are multiple network interfaces, AgentX configuration is applied only to the primary interface. To implement the configuration on the secondary interface, your network administrator must configure it within your routing protocol.
- Downgrading AgentX Server from v1.4.2 to v1.2.0 after installing AgentX Manager v1.4.5 may cause log loss and is not recommended. If a downgrade is necessary, contact support.
- If you are using AgentX in distributed mode, then upgrading it from previous versions to v1.4.5 will break the connection between all nodes in the distributed architecture, stopping log transmission across the entire setup. The workaround can be found here.
- AgentX Manager v1.2.1 is not compatible with AgentX Server v1.4.2. Go to version compatibility matrix for more information.
- When upgrading the AgentX Server, please note that the new version may take some time to reflect due to its file size exceeding 500MB
- The installation of Windows Installer v1.4.2 might take more than one minute.
- Find the known issues for AgentX here.
Enhancements
The following enhancements were added:
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| AgentX Server logging architecture is now moved from file to memory-based to enhance log processing and storage. | EDR-1449 | - |
Bug Fixes
The following issues were solved:
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| CPU usage was high when analyzing and decoding logs from the event ID 0840. | EDR-1365 | 76237 |
| Users could not install AgentX Server in Logpoint where Universal Normalizer v5.2.0 and later was installed. | EDR-1500, EDR-1491 | 78531, 78894, 79075, 78390, 79163 |
| Log collection stopped because the rootCA.pem and sslagent.crt certificates expired after one month and one year instead of ten years. | EDR-1579 | 84133 |
| Users could not install AgentX Server in Logpoint where Universal Normalizer v5.2.0 and later was installed. | EDR-1500, EDR-1491 | 78531, 78894, 79075, 78390, 79163 |
| The event channel logs collected from Windows PowerShell were missing the user field, leading to difficulty in identifying specific user actions. | EDR-1626 |
Previous Releases
AgentX Server v1.2.0
Release Date: August 16, 2023
Release Version: 1.2.0
Supported On: Logpoint v7.1.0 and later
Download: AgentX_Server_1.2.0.pak
SHA256:
Documentation: AgentX guide
Key Information
- You need to install AgentX Server in Logpoint. Follow the instructions as mentioned in the AgentX Guide.
- If you upgrade AgentX Server to v1.2.0, you must upgrade AgentX Manager, Debian Installer and Windows Installer to v1.2.0 too.
- AgentX Server 1.2.0 is compatible with AgentX Manager 1.2.1.
AgentX Server v1.1.0
Release Date: March 30, 2023
Release Version: 1.1.0
Supported On: Logpoint v7.1.0 and later
Download: AgentX_Server_1.1.0.pak
SHA256: 8d0b066decb7c76ee3a64e296163127be251c1664a27fa7ed37726137847bdeb
Documentation: AgentX guide
Important
For early adopter customers, if AgentX is already installed in your Logpoint, remove the configuration and uninstall AgentX Server before upgrading to v1.1.0.
Support
If you have any queries or require assistance, create a support ticket here.
Comments
Article is closed for comments.