...
The Cloudamize Agentless Data Collector will need to be installed on a physical or virtual Windows machine, meeting the following minimum requirements:
...
Setup a new Windows instance to host the agentless data collector
When using multiple data collectors, ensure that each individual data collector’s scope of IP ranges is unique
Each data collector can, by default, assess up to a maximum of 500 instances (configurable)
Exclude the data collectors collector IP address when adding hosts
Linux remote hosts: Cloudamize ADC cannot collect data when requiretty is true in sudo in remote hosts
...
Machine with Cloudamize Agentless Data Collector installed
TCP port 445 open opens 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 (US), am-de.cloudamize.com (EU), or am-ae.cloudamize.com (UAE).
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.
...
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 opens outbound to the machine with the Agentless Data Collector installed
Each Linux endpoint
TCP port 22 open opens inbound
The table below lists the relevant ports for machine discovery and communication to the Cloudamize servers:
...
After downloading: Run the MSI file by double-clicking it and click clicking "Next"
...
Accept the End-User License Agreement and click “Next”
...
Once the installation completes, click Finish to close the installer
...
Add and Configure Hosts
Continue on to Continue to our guide for next the following steps on how to Add and Configure Hosts with the Cloudamize Agentless Data Collector.
Windows Troubleshooting
Account Credentials
...
This error occurs when a Domain name is not specified. The format for the username is DomainName\Administrator
Cloudamize Agentless Data Collector is flagged by Antivirus
Our An anti-virus may flag our agentless data collector may be flagged by anti-virus as the installation package includes obfuscated code to protect our Intellectual Property. When the Cloudamize agentless data collector is flagged by an antivirus, re-installing on the same host is sometimes not possible due to remnants left behind during the uninstallation process. Cloudamize recommends a fresh installation of the agentless data collector on a different host that meets the prerequisites.
In the event that hosts were added to the agentless data collector, the HostInfo.xml and HostInfoBackup.xml file files should be backed up in a separate folder, such as C:\Temp, before uninstalling the Cloudamize agentless data collector. These files are located in: C:\Program Files\CloudamizeAgentlessDC or C: Program File (x86)\CloudamizeAgentlessDC depending on your architecture. Please note that these files can only be accessed by accounts that belong to the Administrators group.
...
When the HostInfo.xml and HostInfoBackup.xml files are backed up, the Cloudamize agentless data collector can be uninstalled. You can download the latest version of the data collector from the portal.
...
The host [IP Address] is down
The account name and password are incorrect, or the account does not have sufficient privileges.
If the server is domain joined, the domain controller itself may not be running.
The Active Directory administrator group may not include the domain administrator group.
The user account provided may not be in the domain admin group, or it may not be the local administrator account.
A local account on the server is in use, and it is a member of the administrators administrator's group but not the administrator account itself.
...
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersio n\Policies\system\LocalAccountTokenFilterPolicy
Note: If A new registry key will be required if the file path does not exist a new registry key will be required. Please note that this will require administrative privileges.
Open Regedit, right-click on the System folder, and select “New” and “DWORD (32-bit)”
...
Change the name of the new registry entry to : LocalAccountTokenFilterPolicy.
...
Right-click on the registry entry and select “Modify”
...
If you are still experiencing issues, please send log files of the affected node(s) to helpdesk@cloudamize.com. The log files are located in C:/Program Files/Cloudamize for Windows machines, /usr/local/cloudamize/logs/ for Linux.