Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Server & Application Monitor (SAM) > PowerShell APM monitor error: You should update your PowerShell to PowerShell 2.0

PowerShell APM monitor error: You should update your PowerShell to PowerShell 2.0

Updated January 20, 2017


This article discusses the issue where the PowerShell application monitor returns the following error even when the PowerShell version used is 4.0: 

WARNING: You should update your PowerShell to PowerShell 2.0 


SAM 6 and later


The warning is thrown by Get-VMJob from the endpoint (target Server where the SAM template is assigned) itself and not by Orion.


  1. Verify that the server where the template is assigned is actually running PowerShell 4.0.

  2. Confirm where the problem resides. Refer to PowerShell Veeam backup status report (© 2017 Veeam, available at, obtained on January 19, 2017.)

  3. Take the problematic script, open PowerShell ISE and connect remotely to the node using the same credentials and the check if the ISE console displays the same warning.

  4. Confirm that the warning is thrown by Get-VMJob  using Veeam cmdlets. This means that the problem is on the target node and not in Orion.

  5. Use the -WarningVariable common parameter to address the warning. Refer to Saving Warnings to a variable in PowerShell (© 2017 Stack Exchange, Inc., available at, obtained on January 19, 2017.)


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.


Last modified