Applications Systems

Configure a Windows Script Monitor

This article aims to explain what is needed to interpret different script languages (vbScript, Perl, Python, JScript) and how to configure the Windows Script Monitor to use these.

First published date

10/16/2018 7:06 PM

Last published date

11/23/2020 12:35 PM

Overview

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

Product section

Server Application Monitor

Resolution

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

vbScript

None. Included with Windows.

JScript

None. Included with Windows.

Perl:

ActivePerl from http ://www.activestate.com/activeperl/downloads (© 2018 ActiveState Software Inc., available at https://www.activestate.com/, obtained on October 16, 2018)

Python:

ActivePython from http ://www.activestate.com/activepython/downloads (© 2018 ActiveState Software Inc., available at https://www.activestate.com/, obtained on October 16, 2018)
Python Extensions for Windows (pywin32-217.win-amd64-py3.2.exe) from http://sourceforge.net/projects/pywin32/ (© 2018 Slashdot Media, available at https://sourceforge.net/projects/pywin32/, obtained on October 16, 2018)

To test:

On the system hosting the Orion Poller, open a CMD prompt.

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

If the command fails, the interpreter is not installed correctly. Consult the manufacturer of the interpreter.
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.

Disclaimer: Please note, any content posted here is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.