Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.6.1 Administrator Guide > AppInsight for Exchange > Set PowerShell permissions for Exchange

Set PowerShell permissions for Exchange

Updated: 3-9-2017

After verifying an install, or installing PowerShell 2.0 or higher, you need to set the permissions. These permissions are required for AppInsight for Exchange and the Exchange server.

  1. On the remote computer, open the PowerShell console.
  2. Execute this command:Set-PSSessionConfiguration Microsoft.Powershell -ShowSecurityDescriptorUI -Force The permissions dialog should appear.
  3. Enable Full Control under the Permissions for Everyone group, and select Allow.
  4. Ensure that the group containing the polling user has access to Microsoft PowerShell, and click OK.
  5. Verify all permissions are set and saved.

Resolving errors after a reinstall

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. Security patches or updates may also cause this issue. You can create the required registry key by following these instructions:

  1. Open Notepad and copy and paste the following text .
    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.
Last modified