Submit a ticketCall us
Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > PowerShell 2.0 was not detected on the Exchange server

PowerShell 2.0 was not detected on the Exchange server

January 14, 2019


The Orion server uses Windows PowerShell 2.0 or later to run PowerShell commands on remote machines. If the Orion server cannot execute PowerShell commands on a Microsoft Exchange server, you may receive error messages indicating that a request could not be processed, the content type is absent/invalid, or remote configuration failed.  


  • SolarWinds SAM 6.2.x or later
  • Windows Server 2008 R2 SP1 or later (SAM 6.2.x — SAM 6.4)
  • Windows Server 2012 or later (SAM 6.5 or later)
  • Microsoft Exchange


AppInsight for Exchange uses PowerShell 3.0 or later, depending on the SAM version. PowerShell 3.0 may not be able to run PowerShell cmdlets for Exchange due to a broken registry key, depending on the operating system and Microsoft Exchange versions. This is a known Microsoft issue; see Installing the Windows PowerShell 2.0 Engine.

All Microsoft links cited here belong to Microsoft Corp., © 2018, are available at, and were obtained on June 29, 2018.  


Microsoft Server installations usually include PowerShell version 3.0 and later with backward compatibility support. However, some scripts and programs may be incompatible with a particular PowerShell version and return error messages mentioned above in the Overview.

If Exchange indicates that PowerShell 2.0 is required, you can either:

Per Microsoft guidelines, the PowerShell 2.0 Engine is intended for use only if an existing script or host program cannot run because it is incompatible with Windows PowerShell 3.0 or 4.0, or Microsoft .NET Framework 4. 


You may also need to set PowerShell permissions for Exchange, as described in the following example for Windows Server 2012. 

  1. In Windows Server 2012, open a PowerShell session as an administrator.
  2. Type Import-Module ServerManager and press Enter
  3. Type Get-WindowsFeature | Where-Object {$_.Name -eq "PowerShell-V2"} and press Enter.
  4. If the 'Install State' is not 'Installed', type Add-WindowsFeature -Name "PowerShell-V2" and press Enter.


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.


If you receive a PowerShell version error when running AppInsight for Exchange on a Windows Server 2016 server, upgrade to SAM 6.6 or later.

See also Use PowerShell in SAM in online help.


Last modified