Run the Add-On with PowerShell
First, provide a path to your add-on followed by script parameters with their values. Each parameter is preceded with a dash; a space separates a parameter name from its value. You can skip some parameters— the script uses a default value unless you explicitly define one. If necessary, modify the parameters as required.
To run the add-on with PowerShell:
Step 1 – On the computer where you want to execute the add-on, start Windows PowerShell.
Step 2 – Enter a path to the add-on, or drag and drop the add-on file into the console window.
Step 3 – Add script parameters. The console looks similar to the following:
Windows PowerShell
Copyright (C) 2014 Microsoft Corporation. All rights reserved.
PS C:\Users\AddOnUser> C:\Add-ons\Netwrix_Auditor_Add-on_for_AlienVault_USM.ps1 - NetwrixAuditorHost 172.28.6.15
NOTE: If the script path contains spaces (e.g., C:\Netwrix Add-ons), embrace it in double quotes and insert the ampersand (&) symbol in front (e.g., & "C:\Netwrix Add-ons").
Step 4 – Hit Enter.
Depending on the number of Activity Records stored in Netwrix Auditor Audit Database execution may take a while. Ensure the script execution completed successfully. Netwrix Auditor creates the Netwrix Auditor Integration event log and fills it with events.
By default, the add-on sets the Netwrix Auditor Integration event log size to 1GB and the retention to "Overwrite events as needed". For more information about event log fields, see the documentation.
NOTE: The add-on trims event records longer than 30,000 characters.
At the end of each run, the script creates the Netwrix_Auditor_Event_Log_Export_Add-on_EventIDs.txt file. It defines mapping between the Activity Records and related Event IDs . You can use this file to track possible duplicates of Event IDs created at each script execution. The script writes duplicates, if any, to the Netwrix_Auditor_Event_Log_Export_Add-on_EventIDsDuplicates.txt file.
Similarly, the add-on also creates the Netwrix_Auditor_Event_Log_Export_Add-on_CategoriesIDs.txt file that defines mapping between the Data Source and related Category ID.
Applying Filters
Every time you run the script, Auditor makes a timestamp. The next time you run the script, it retrieves new Activity Records starting from that timestamp. Consider the following:
-
By default, the add-on doesn't apply any filters when exporting Activity Records. If you're running the add-on for the first time (there is no timestamp yet) with no filters, the add-on exports Activity Records for the last month only. This helps to optimize solution performance during the first run. At the end of the first run, the add-on creates the timestamp, and the next run starts the export from that timestamp.
-
However, if you specify a time period for Activity Records to export, the add-on applies this filter at the first run and all runs that follow.