Applications Systems

PowerShell scripts in SCM are on hold

This KB article explains how to change the set number of PowerShell scripts that can be executed simultaneously in Server Configuration Monitor from the default of five.

First published date

2/21/2019 9:02 PM

Last published date

2/21/2019 9:02 PM

Overview

This KB article explains how to change the default number of PowerShell scripts that can be executed simultaneously in Server Configuration Monitor.

Product section

Server Configuration Monitor

Resolution

When the maximum number of concurrently running scripts is exceeded in Server Configuration Monitor (SCM), other scripts are put on hold in a queue. When a running script completes, the next script starts. Scripts are executed in the order in which they were put on hold.

SCM does not execute more than 'X' PowerShell scripts at the same time on the monitored node. You can configure 'X' in Centralized Settings as "max # of simultaneously running scripts allowed." The default configuration is set at five.

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.