Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Configure a Windows Script Monitor

Configure a Windows Script Monitor

Table of contents
Created by Chris Foley, last modified by Rodim Suarez_ret on Jul 12, 2016

Views: 1,450 Votes: 2 Revisions: 2

Updated

Overview

This article aims to explain what is needed to interpret different script languages and how to configure Windows Script Monitor to use these.

Environment

  • All SAM versions
  • Windows systems

Steps

Requirements to be installed on the system hosting the Orion Poller:

vbScript

  • None.  Included with Windows.

JScript

  • None.  Included with Windows.

Perl:

Python:

 

To test:

  1. On the system hosting the Orion Poller, open a CMD prompt.
  2. Type the following command:
    cscript //E:{Interpreter} {Script Path and Filename}

    Examples: 

    cscript TestScript.vbs

    cscript //E:Python TestScript.py

    cscript //E:PerlScript TestScript.pl

  3. If the command fails, the interpreter is not installed correctly. Consult the manufacturer of the interpreter.
  4. If the command succeeds, specify the {Interpreter} value used in the command, as the "Script Engine" value within the Windows Script Monitor.

 

Note: If the 32-bit version of the interpreter is installed, make sure to set the platform within the Application's Settings page to x86.  On the other hand, if the 64-bit version of the interpreter is installed, make sure to set the platform within the Application's Settings page to x64.

 

Last modified

Tags

Classifications

Public