Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Running a PowerShell batch file does not work when alert is triggered

Running a PowerShell batch file does not work when alert is triggered

Created by Roie.Exconde, last modified by Rodim Suarez_ret on Mar 08, 2017

Views: 328 Votes: 0 Revisions: 5

Updated March 8, 2016

Overview

Running a batch file directly on the server executes a PowerShell script as expected, but when the batch file is executed through the Advanced Alerts, it states that it executed and resulting in a false positive.

Environment

  • All NPM versions 
  • Windows Server 2008 and 2012

Resolution

Run the PowerShell script with elevated privilege and set execution policy to bypass.

 

Last modified

Tags

Classifications

Public