Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > AppInsight for Exchange: PowerShell is not working

AppInsight for Exchange: PowerShell is not working

Table of contents
No headers


If PowerShell 2.0 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. You can create the required registry key by following these instructions. 

SolarWinds strongly recommends that you back up your registry before making any edits to your system registry. You should only edit the registry if you are experienced and confident in doing so. Using a registry editor incorrectly can cause serious issues with your operating system, which could require you to reinstall your operating system to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

To recreate the registry key:

  1. Open Notepad.
  2. Copy and paste the following text into Notepad:

          Windows Registry Editor Version 5.00
     "PSCompatibleVersion"="1.0, 2.0"
     "ConsoleHostAssemblyName"="Microsoft.PowerShell.ConsoleHost, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=msil"

  1. Save the file as PowerShellv1.reg and then double-click it to add it to the registry. (A reboot may be required.)

If you prefer to not run PowerShell 2.0 on the Exchange Server, the simplest method for enabling AppInsight for Exchange is to complete the steps outlined below. Provided the registry key shown above is configured properly, there is no requirement to leave PowerShell 2.0 enabled.

  1. Enable PowerShell 2.0.
  2. Navigate to the Node Details view by clicking any Windows node.
  3. From the Management resource, click List Resources.
  4. Check the Microsoft for Exchange Server box to enable AppInsight Application data collection, and then click Submit.
  5. Navigate to the All Applications resource to verify the addition by clicking the Applications tab in the web console.
  6. Select the new AppInsight for Exchange application in this view and enter Exchange credentials when prompted. 
  7. Click Configure Server.
  8. Disable PowerShell 2.0. 


Last modified