Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Server & Application Monitor (SAM) > Switching Job Engine v2 to different account than local system causes Windows script monitor to stop working completely

Switching Job Engine v2 to different account than local system causes Windows script monitor to stop working completely

Overview

The customer has encountered VBScript issues while running scripts from Server and Applicaiton Manager (SAM) with relevant error message from debug logs:

SolarWinds.APM.Probes.Script.WindowsScriptExecuteException: Exception when trying to run script ---> System.ComponentModel.Win32Exception: A required privilege is not held by the client

Environment

SAM version 6.0

Cause

The customer runs Job Engine v2 under a local administrator account and it is unable to poll Windows Management Instrumentation (WMI) nodes. 
Note: Running any script via Windows script monitor will not work at all if Job Engine v2 is switched to administrator account. 
 

Resolution

The issue with the VBScript is likely the context under which it is being executed. Job Engine v2 is running under local System account by default. The system has no ability or permissions to access remote network resources because this is how Windows OS security works.

The following options will allow the customer to resolve the issue:
  1. Perform user impersonation as part of the VBScript. For user impersonation, see the SAM Administrator Guide for detailed information - http://www.solarwinds.com/documentation/apm/docs/SAMAdminGuide.pdf 
  2. Rewrite the script to use PowerShell instead, which support impersonation natively and optional remote execution. 
  3. Use the SAM agent. Install it on the server they want to monitor (10.80.33.155) and change to local pathing (c:\temp\). See Note below for details.

Note: For step 3, find the following link for complete details on using or installing the SAM agent  - http://www.solarwinds.com/documentation/en/flarehelp/sam/content/samagagenttop.htm 

 

Last modified
22:10, 30 Nov 2016

Tags

Classifications

Public