Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You will be redirected to the Logging page. You can refresh this page and see the progress of the Discovery run. Note that the first log may take a short while if the script has to determine if a number of target devices are active on a large subnet range. 

Once the initial list of target devices has been obtained you should see details of each target as it is scanned and input into Open-AudIT.

Logging

NOTE - The logging is quite verbose so there is now a feature to purge the log file at Menu -> Admin -> Logs -> Purge Log.

You should see logging similar to the below. In the below instance, a Discovery run was performed on 192.168.0.1-5 and the device at 192.168.0.1 was found and SNMP scanned.

 

on the open-audit.com domain and the two computers win2k8dc and winxp-pro were audited.

Image Added

 

How Does it Work

When running a Discovery against an Active Directory domain, the process is different depending on if your Open-AudIT server is installed on a Windows or Linux machine.

Windows Discovery of AD

The discover_domain.vbs script is run locally with the values provided as per the form. The Open-AudIT server will then talk to the domain controller, obtain a list of computers and audit them.

Linux Discovery of AD

The discover_domain.vbs and audit_windows.vbs are copied to the nominated server and the discover_domain.vbs script is started on that Active Directory server. The server will obtain a list of computers, audit them and then submit the result to the Open-AudIT server. The linux programs smbclient and winexe are used to enable Linux to copy the scripts and start them on the Windows server.