Child pages
  • Collector / Server
Skip to end of metadata
Go to start of metadata


Open-AudIT introduces the feature of Collector / Server with the 2.0.6 release.

Collector / Server is designed so that you can have a 'collector' Open-AudIT running on a subnet and discovering devices that is controlled by the 'server'.

Collector / Server is an Enterprise only feature. Enterprise customers receive one Collector license for free. Additional Collector license can be purchased as required.


Once installed and setup, control of the collector is performed on the server.

The only required network ports between the collector and server are 80 or 443. The Open-AudIT database is not shared between these installs.

By default the collector will request from the server any discovery tasks every 15 minutes.

Any discovery tasks for the collector should be scheduled for 0, 15, 30 or 45 minutes.


In the example below our server will be running on and our collector will be running on


Install Open-AudIT Enterprise on your designated Server.

Log in to Open-AudIT on the server.

Add a license for Open-AudIT Enterprise. (The Enterprise Server License has one built in Collector License.)

Add an additional license for Open-AudIT Collector (if you have one).

Note - Enterprise users receive one Collector license for free as part of their Enterprise License.

Make a user account in Open-AudIT for your collector. (menu -> Manage -> Users -> Create User). Ensure the type is 'collector'. Ensure you click the Default Organisation. Ensure the role is 'collector'. These details will be required below.

Users Create


Install Open-AudIT on your designated Collector.

The collector license is built into the server license.  As such a collector instance does not require a license to be installed.

Log in to Open-AudIT Enterprise on the collector.

In the menu click Collector -> Make this install a Collector.

Provide a name for this collector.

Provide the address of the Server ( in the host field.

Provide the username and password that were used above when creating the collector user.

Provide the network address of the Collector ( This is used to populate discoveries on the server. This is the usual network address used in discovery and should be where the target device submit their audits to (the Collector).

Click Submit.

You should now have configured your collector to ask the server for any Discovery tasks, every 15 minutes.

After Login.

Collector Create

Collector Dashboard


Checking the registration of the collector has succeeded

You should now be able to see on the server, the collector you have just registered. Go to menu -> Admin -> Collectors -> List Collectors.









You should now be able to see on the collector, the task that will run every 15 minutes that will ask the server for any discoveries to execute. Go to menu -> Admin -> Tasks -> List Tasks.




Creating a discovery for the collector

On the server.

Add credentials as required.





On the server.

Create a Discovery. NOTE - Choose the network address of the collector server.






On the server.

Create a task. NOTE - use the Collector you just created. Choose the Discovery you just created. Set your minute for 0 and/or 15 and/or 30 and/or 45. Choose the required hour(s), day(s), etc.


Credentials Create

Discoveries Create

Tasks Create


Once you have configured credentials, discoveries and tasks the next time the collector checks-in with the server, if a discovery is due to run, it should run. The collector should forward the details of any discovered devices to the server.

More Information

Collectors and Orgs.

Credentials and Orgs.