Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > PowerShell 2.0 was not detected on the Exchange server

PowerShell 2.0 was not detected on the Exchange server

Overview

PowerShell 2.0 or later is required for remote execution but it was not detected on the Exchange server. 

Environment

  • All SAM versions
  • Windows 2008 (not 2008 R2)

Resolution

PowerShell 2.0 or later is usually installed with Microsoft Server. Install it, if necessary. See Microsoft's documentation website (© Microsoft Corp, available at https://docs.microsoft.com/en-us/powershell/, obtained on April 30, 2018).

You may also need to set PowerShell permissions for Exchange.Download Powershell 2.0 or later. 

  1. In Windows 2012, open PowerShell session in Administrator context
  2. Type Import-Module ServerManager and hit enter.
  3. Type Get-WindowsFeature | Where-Object {$_.Name -eq "PowerShell-V2"} and hit enter.
  4. If the 'Install State' is not 'Installed', type Add-WindowsFeature -Name "PowerShell-V2" and hit enter.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified

Tags

Classifications

Public