Troubleshoot PowerShell issues

This section provides various troubleshooting tips for issues you may encounter when using SAM with PowerShell. You can find additional information in the following resources:

All Microsoft links cited here belong to Microsoft Corp., © 2018, are available at https://docs.microsoft.com, and were obtained on June 29, 2018.

Your organization should internally review and assess to what extent PowerShell is incorporated into your environment. This is especially important when importing scripts from third parties, including content posted by other customers in the SolarWinds online IT community, THWACK. To learn more, see PowerShell security considerations.

"PowerShell 2.0 was not detected on the Exchange server" message

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.

In SAM, 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.

If you receive PowerShell errors when running AppInsight for Exchange on Windows Server 2016 with SAM 6.5 or earlier, upgrade to the latest version of SAM.

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.

To learn more, see PowerShell 2.0 was not detected on the Exchange server in the Success Center.

Troubleshoot the Windows PowerShell Monitor

If you encounter connection- or authentication-related error messages when using the Windows PowerShell Monitor, verify that you are entering the user name and password of an administrator-level account. If you think you have entered an incorrect credential, correct the mistake and then retest.

Make sure that the RPC server is available and that the Windows PowerShell execution policy is not set to Restricted (the default setting). You can check the execution policy by entering the following command at the PowerShell command prompt: Get-ExecutionPolicy

To learn more, visit the SolarWinds Success Center and see Problems using the Windows PowerShell Monitor in SAM

If PowerShell was installed on Windows Server 2012 with Exchange 2013 and subsequently uninstalled, a Microsoft error removes the required registry key for remote PowerShell to work properly. Security patches or updates may also remove registry keys. If you encounter this issue, see steps for recreating the required registry key in Set PowerShell permissions for Exchange.