Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Tips for executing external scripts and batch files with alerts

Tips for executing external scripts and batch files with alerts

Table of contents
Created by Aileen de Lara_ret, last modified by carolyn.mazenko on Jul 10, 2018

Views: 6,814 Votes: 0 Revisions: 4


This article provides tips to prevent errors if you are using either the Execute an external program or the Execute an external VB script actions with an Orion alert.


All Orion Core products


  • Basic alerts and advanced alerts fire alert action scripts differently. Generally, if a batch or VBS script runs correctly from the desktop of your Orion server, it will most likely fire correctly from a basic alert.
  • Run all external batch files and scripts from the C: drive of your Orion server.
  • Remove all spaces in VB script names.
  • In some cases, quotation marks may be required around script names and any variables that are passed to the called script.
  • Microsoft locks down the way scripts run by default for a service, so that applications with graphical user interfaces cannot be launched. It is possible, however, to configure services to interact with the desktop, as shown in the following procedure:

Note: Running a process under the Local Account may be considered a security risk.

a. Click Start > Control Panel > Administrative Tools > Services.

b. Right-click the service you want to configure, and then click Properties.

c. On the Log On tab, select Local System account, and then check Allow service to interact with desktop.

  • If a script does not run as expected from the Advanced Alert Manager, even if it runs correctly from the desktop, confirm that the user under which the Advanced Alert manager is running has permission to run the desired script, as shown in the following procedure:

a. Click Start > Control Panel > Administrative Tools > Services.

b. If the account listed under User Name is not able to restart the service, the service will fail to launch.


The Advanced Alert Manager was discontinued and functionality was rolled into the Orion Platform. For the latest information about alerts, see Alerting resources for Orion Platform products.

  • If the service is launched by a non-Administrator user, complete the following steps to launch the service as an Administrator:

a. Right-click the service, and then click Properties.

b. On the Log On tab, select This account.

c. Provide or Browse to a user with administrative privileges, and then provide and confirm the administrative user password.

d. Click OK.




Last modified