Setup Instructions

Getting Ready

This guide will walk you through setting up the Cloudamize Agentless Data Collector. Once the collector is setup, you will be able to discover and assess up to 500 Windows and Linux physical and virtual machines on the subnet.

The table below lists the relevant ports for machine discovery and communication to the Cloudamize servers. Please note the following rules for each class of machine:

  • 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
  • Each Windows endpoint
    • TCP ports 135 and the range 1025-65535 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-65535 RPC dynamic port range
TCP 443 SSL to communicate with the Cloudamize servers

Ports relevant to the Cloudamize Agentless Data Collector



Minimum Requirements

The Cloudamize Agentless Data Collector will need to be installed on a physical or virtual Windows machine meeting the following minimum requirements (based on monitoring 500 machines):

  • 64-bit Windows Server 2003 SP2 or higher
  • .NET framework version 4.0
  • 4 CPU cores
  • 5 GB RAM
  • 2 GB persistent storage



Setup Instructions

The latest version of the Cloudamize Agentless Data Collector can be downloaded here:


The Cloudamize Agentless Data Collector can easily be installed using a Graphical User Interface. Upon launching the installer, you will see the following window:



Click Next to continue to the End User License Agreement.




Review and accept the terms in the License Agreement and click Next to continue. 




You will then be required to enter your customer key. If you choose to route the data through your own proxy, you can enter the address, port, username, and password on this screen. Click next once you are ready to continue.




Click Install to begin the Cloudamize Agentless Data Collector installation. 




Once the installation completes, click Finish to close the installer. You are now ready to begin adding and configuring hosts for data collection. If you have any questions about the above process, please contact [email protected]



Add and Configure Hosts

Continue on to our guide for next steps on how to Add and Configure Hosts with the Cloudamize Agentless Data Collector. 




Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • 0

    This page does not include the download URL to the agentless connector :( Can you add it? I am trying to download it.



  • -1

    Hi Afeez, 


    You must open a request service asking for the setup for the agentless data collector, they send you an email with a link.


  • 0

    Hi. There's one important omission in this guide. Adding guests will fail with errors that indicates networking issues if you are missing proper DNS forwarding / reverse lookups. DNS Forwarding alone may not be adequate since translation from IP -> Name must happen as part of authorization. If IP cannot be resolved to a hostname the logon will fail, and by the look of the error it may look like a "port / networking issue".

    ==> Checking the WMI connection to host  Failure.
    Here is the reason.
    SocketException = No such host is known
    -> Checking the ping connection to host  Success.
    -> Checking the TCP connection to port 135 on host  Success.
    Done with checking all hosts.


    I would suggest you add a requirement aka:

    - WINS IP to Name resolution or DNS Forward and Reverse lookup records for each entry that will be scanned by the agent.

    I'm not sure whether I would suggest WINS at all, but I leave that up to you.

    The LINK you send us to for troubleshooting WMI does not mention this requirement since the MS article there assumes we are using names.

    Ref troubleshooting link:


Please sign in to leave a comment.