Prerequisites – Overview
Collector Agent – Desktop Agent and Server Agent
Microsoft Windows
Almaden Desktop Agent (ADA) – Windows 7 or higher.
Almaden Server Agent (ASA) – Windows Server 2012 R2 or higher.
Linux
Almaden Desktop Agent (ADA)
Kernel 2.2, 2.4 e 2.6.
RedHat 6.2 ou superior / RPM-based derivatives.
Debian 6 ou superior /DPKG-based derivatives.
Almaden Server Agent (ASA)
Kernel 2.2, 2.4 e 2.6.
RedHat 6.2 ou superior / RPM-based derivatives.
Debian 6 ou superior / DPKG-based derivatives.
MacOS
Almaden Desktop Agent (ADA)
MacOS Big Sur 11.x or higher.
Minimum sizing Desktop/Server Agent (Without plugins)
The minimum settings required for the relay to work are:
CPU: 2 Core 2.8 GHz+
Available disk space: 120 GB
Memory: 4 GB
Operacional Systems
Servers: Windows Server 2012 or higher, CentOs, Fedora, Ubuntu, Debia, RedHat, Solaris.
Desktop: Windows 7 or higher, CentOs, Fedora, Ubuntu, RedHat, Debian, MacOS (For MacOS, please consult our support.).
Minimum sizing for Agent + Plugins (Netscan, Distribution and Relay servers)
The minimum settings required for the relay to work are:
CPU: 2 Core 2.8 GHz+
Available disk space: 120 GB
Memory: 4 GB
Operacional system: Windows Server 2012 or higher
Plugins Agent
Netscan
Operating System: Windows 10 or Later (Does not work on Windows Server).
CPU: 2 Core 2.8 GHz+
Disk Space: 120 GB
Memory: 4 GB
ADW ( Distribuition Wizard)
Operating System: Windows Server 2012 or later (Does not work on Windows 10,11).
CPU: 2 Core 2.8 GHz+
Disk Space: 120 GB
Memory: 4 GB
Network Requirements
Protocol: SMB
Port: 5900
SNMP
Operating System: Windows Server 2012 or later (Does not work on Windows 10,11).
CPU: 2 Core 2.8 GHz+
Disk Space: 120 GB
Memory: 4 GB
Support Remote Access (SRA)
Supported Operating Systems
Microsoft Windows
| Client Version | Server Version | Version |
|---|---|---|
| Microsoft Windows 11 | Microsoft Windows Server 2022 | Latest version available |
| Microsoft Windows Server 2019 | Latest version available | |
| Microsoft Windows 10 (32-bit and 64-bit) | Microsoft Windows Server 2016 | Latest version available |
| Microsoft Windows 8.1 (32-bit and 64-bit) | Microsoft Windows Server 2012 R2 | Latest version available |
| Microsoft Windows 8 (32-bit and 64-bit) | Microsoft Windows Server 2012 | Latest version available |
| Microsoft Windows 7 (32-bit and 64-bit) | Microsoft Windows Server 2008 R2 | Latest version available |
Mac OS
| Client Version | Version |
|---|---|
| macOS 14.X Sonoma | Latest version available |
| macOS 13.X Ventura | Latest version available |
| macOS 12.X Monterey | Latest version available |
| macOS 11.X Big Sur | Latest version available |
| macOS 10.15 Catalina | Latest version available |
| macOS 10.14 Mojave | Latest version available |
Linux
- Linux kernel 2.4 and higher (64 bit)
- glibc 2.12 or newer
- systemd
- X Window System
Tested on:
- Ubuntu 16.04, 18.04, 20.04
- Debian 10, 9
- CentOS 8
Not supported:
- Wayland
- Linux 32-bit
- arm64 architecture
Relay – Agent data transmission methods
Our agents have three methods of transmitting data to the cloud:
Method 1 – Sending to centralized relays
The agent transmits the information collected through outgoing relays using port 1999 to connect to the relay, with that all information output will be centralized in the relays.
Method 2 – Sending directly to the cloud
The agent transmits the collected information directly to the Almaden cloud, requiring the release of all equipment to the internet.
Method 3 – Sending in a hybrid form
In this method, the agent will look for the relay in the network and if not found, it will use the local relay to transmit the information. An important alert is that in this method the relay installed locally on the equipment will always test the outgoing connection, if it is not released or correctly blocked, this can generate excessive denial logs in the firewall.
