Custom Command Line Script

How To Configure

Post-processing scripts can be configured via the "Run custom command line script" option. Variables from the table below can be used in post-processing scripts.

For example, the following command line will copy the file that was analyzed by Kiosk to "E:\MD_POST_ACTION_BY_PAC" folder and delete after the copy.

Copy

After entering your scripts, click Apply .

Be sure to test the script before configuring with Kiosk as the script is not validated.

Paths or parameters containing blanks should be surrounded in "quotes".

Using Pre-defined Variables in Command Line Scripts

VariableDescriptionNotes
%%%file_path%%%The absolute path of the file scanned
%%%threat_name%%%The name of the threat found by the enginesThis variable only applies to infected scan results (“1”)
%%%scan_finished%%%The time when the scan was finishedLocal time of the kiosk system
%%%ticket_id%%%A random number assigned to each Kiosk session
%%%scan_results%%%Integer representation of the scan result
%%%process_result%%%

The process outcome

  • Allowed

  • Blocked

Running a Powershell script

To execute a Powershell script as a post action, the corresponding group policy needs to be set. See About Execution Policies under USE GROUP POLICY TO MANAGE EXECUTION POLICY. Enable "Turn on Script Execution" -> select "Allow all scripts"

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard