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) > 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: 

  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"

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

Note: 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 Applications data collection. When done, click Submit.
  5. Navigate to the All Applications resource to verify the addition by clicking the Applications tab in the web console.
  6. Click on the newly added AppInsight for Exchange application in this view and then enter your Exchange credentials when prompted. 
  7. Once your credentials are entered, click Configure Server.
  8. Disable PowerShell 2.0. 


Last modified