Documentation forOrion Platform

Execute an external Visual Basic script in the Orion Platform

This topic applies to all Orion Platform products except for the following products:


In some situations, you may want to execute a Visual Basic (VB) script when a network event occurs to perform a specific action.

SolarWinds recommends that scripts and batch files be placed on the root of c:\ to simplify the path for the batch file.

  1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert Wizard.
  2. Select the Execute an External VB Script option, then click Configure Action.
  3. Under Execute an External VB Script settings:
    1. Select a VB Script Interpreter from the drop down list.
    2. Enter the Network path to the external VB Script in the field provided.
      For example: Use c:\test.vbs, where c:\ is the disk on your main Orion poller and test.vbs is your external VB Script to be executed.
    3. Select the account for running the action. Enter users as domain\user.

      SolarWinds recommends that you create tailored low-privilege accounts on the machine to run specific external programs, scripts, and alert actions. See Secure external programs and script alerting actions for details.

  4. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This schedule only applies to the alert action you are editing.

    This is often used to prevent an action from occurring during specific windows.

  5. Select how frequently this action occurs for each triggered alert in Execution Settings.

  6. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate button. When the trigger or reset conditions of the alert are met, the VB script runs.

How to use scripts with arguments

To use scripts with arguments, your VBScript must be able to read parameters.

Script example

If (Wscript.Arguments.Count < 2) Then


End If

parameter1= Wscript.Arguments(0)

parameter2 = Wscript.Arguments(1)

Then, you can enter script with parameters (such as alert variables) into the path to script.

Path example:
c:\vbscript.vbs "${N=Alerting;M=AlertName}" "${N=Alerting;M=AlertTriggerTime;F=DateTime"}

See the thwack post on how to remanage nodes using a VB script when an alert is triggered.

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.