Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

Troubleshoot PowerShell issues in SAM

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

Microsoft links cited here belong to Microsoft Corp., © 2018, available at, as obtained on June 29, 2018.

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

The SolarWinds Platform server requires at least Windows PowerShell 2.0 or later to run PowerShell commands on remote machines. SolarWinds recommends using PowerShell 5.1. If the SolarWinds Platform 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. Upgrade to the latest version of PowerShell.

Connection- or authentication-related errors for the Windows PowerShell Monitor

If you encounter connection- or authentication-related messages when using the Windows PowerShell Monitor, verify that you are using an administrator-level account with valid credentials.

Make sure the RPC server is available and that the Windows PowerShell execution policy is not set to Restricted, the default setting. To check the execution policy, type the following command at the PowerShell command prompt: Get-ExecutionPolicy

See also:

If PowerShell was installed on Windows Server 2012 with Exchange 2013 and then uninstalled, a known Microsoft issue may remove a registry key required by remote PowerShell. 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.