Knowledge Base Article #:
SolarWinds N-central 9.x
September 17, 2014
The following troubleshooting process is designed to quickly resolve script or Policy errors.
The following should be verified to resolve issues with running scripts and distributing software:
- Is there feedback from the task that was run?
- At the Service Organization level, identify the task that was run in the Job Status view.
- Click the Name of the task.
- Click Status.
- Review the status logs to determine if they indicate why the failure occurred.
- Is PowerShell 2.0 installed on the managed devices (this is required for an Automation Policy or PowerShell script)?
- At the Service Organization or Customer level, navigate to the All Devices view.
- Click Filter.
- In the Filter drop-down menu, select
Devices without PowerShell 2.0.
- Select the affected device (or devices).
- Click Add Scheduled Task.
- Click Run a Script.
- Ensure that the Location is
From SolarWinds N-central's Script Repository.
Install PowerShell 2.0 From Microsoft.
- Run the new script and the targeted devices will have PowerShell 2.0 installed.
- After 24 hours has passed, verify that the script has functioned properly by filtering the All Devices view again using the
Devices without PowerShell 2.0Filter.
- When the script was run or software distributed, was the Use Device Credentials option selected? Ensure that the populated device credentials are being used instead of local credentials (which may not provide sufficient access).
- Are Administrator credentials configured in the Properties tab for all of the target devices? Review the Properties tab of a workstation or server device and verify that Administrator credentials are configured. SolarWinds N-central's scripting uses these credentials when running on host systems.
- If no credentials are configured, navigate to the Customer/Site level.
- Click Administration > Defaults > Appliance Settings.
- Click the Credentials tab.
- Configure the appropriate User Name and Password.
- Select Propagate to distribute the credentials to all of the relevant managed devices.
- Are the required PowerShell command line plugins installed?
- Is Remote Execution enabled for PowerShell?
- Remote Execution must be enabled in order to allow SolarWinds N-central to run PowerShell commands remotely. To resolve this issue, create a .BAT file with the following contents:
PowerShell Set-ExecutionPolicy Remotesigned.
- Run the batch file through SolarWinds N-central (using the Run Script feature) and this issue should be resolved.
- Is the SolarWinds N-central Agent that is installed on the device out of date?
- Navigate to the All Devices view and refer to the Agent Version column to verify the current version of the installed Agents.
- Compare this to the version of SolarWinds N-central by clicking Help > Version Information in the navigation pane.
- Select the check box beside the Name of each of the devices that have outdated Agents and click Update Monitoring Software > Upgrade Agent > Now.
- If a script fails to find a directory or path, from where was the script run?
- By default, SolarWinds N-central will run scripts from a temporary directory. If the script is required to be run from a specific path, you should use a File Transfer Scheduled Task to put the script in the appropriate directory and then run the script with a batch file.
Does PowerShell have Remote Execution rights?
Does the software have its plug-in Windows feature installed? For example, Windows Backup PowerShell Plug-in for Command Line must be added from Windows.
You may be required to install PowerShell 2.0 manually on any devices for which the script did not function properly.
If the managed devices are non-domain based computers, you will need to create an administrator account on each device in order for scripts to function properly. User-level accounts often do not have the access required to run scripts. The appropriate credentials must be configured in the Properties tabs of the relevant devices.
Windows Server Backup requires that you add the Windows Feature for Windows Server backup command line processing. You should verify that this has been done.