Windows Installation Prerequisites for Agentless Data Collector
...
Machine with Cloudamize Agentless Data Collector installed
TCP port 445 open inbound
TCP ports 443 and a proxy server port if a proxy is being used (e.g.,8080, 80) open outbound to our servers at am.cloudamize.com (for US infrastructure), am-de.cloudamize.com (for EU infrastructure), or am-ae.cloudamize.com (for UAE infrastructure).
If your system locally caches DNS resolution, you may need to resolve am.cloudamize.com to 35.171.170.26 or am-de.cloudamize.com to 18.194.12.63 to allow egress traffic. This feature is not currently available for our UAE region.
Each Windows endpoint
TCP ports 135 and the dynamic RPC port ranges open inbound, appropriate for your OS versions:
Windows Server 2008 and later: TCP ports 49152 to 65535 open inbound
Windows Server 2003 and earlier: TCP ports 1025 to 5000 open inbound
TCP port 445 open outbound to the machine with the Agentless Data Collector installed
Each Linux endpoint
TCP port 22 open inbound
Protocol | Port | Usage |
TCP | 22 | SSH to access Linux servers |
TCP | 135 | Windows RPC |
TCP | 445 | Microsoft-DS Active Directory and SMB, Windows shares |
TCP | 1025-5000 | RPC dynamic port range for Windows Server 2003 and earlier |
TCP | 49152-65535 | RPC dynamic port range for Windows Server 2008 and later |
TCP | 443 | SSL to communicate with the Cloudamize servers |
Fig. 2 Ports relevant to the Cloudamize Agentless Data Collector
...
Dedicated 64-bit Windows Server 2012 R2 or higher
.NET Framework version 4.0
8 CPU cores
16 GB RAM
2 5 GB persistent storage
Requirement for Agentless Data Collector to Collect SQL Data from a remote machine(If SQL data is required)
PowerShell 2.0 is required to collect basic SQL Server data on the remote machine.
PowerShell 5.1 is required to collect additional SQL Server data on the remote machine.
.NET Framework 3.5 is the minimum requirement on the remote machine.
For additional data collection, the account used to add the nodes to the ADC UI should have permission to access MS SQL instances on the remote host. If not, add the account to Security/Logins in SQL Server Management Studio on the remote host.
...