Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Server & Application Monitor (SAM) > AppInsight for Exchange: Configuration failing

AppInsight for Exchange: Configuration failing

Overview

This article lists AppInsight for Exchange configuration issues.

Environment

All SAM versions

Issue 1

The configuration script has detected multiple "Organization Management" or "View-Only Organization Management" Exchange Security groups within your Active Directory infrastructure.

Cause

An Administrator within your organization has manually relocated the original Exchange security groups to a different OU (not recommended or supported by Microsoft) other than the one in the root OU. At some point after moving the groups, "setup /PrepareAD" & "setup /PrepareDomain" was run to upgrade your Exchange organization.

Resolution

Rename the groups which were moved out of the root OU and verify the groups in the root OU "Microsoft Exchange Security Groups" have the correct members.

 

Issue 2

The configuration script has detected that a WinRM HTTPS port has been previously configured, but is unable to use it because the WinRM listener is not configured properly.

Cause

The configuration script has detected that a WinRM HTTPS port has been previously configured, but is unable to use it because the WinRM listener is not configured properly.

Resolution

 

  1. Open a Command Prompt in an elevated context.
  2. Type: winrm get winrm/config/listener?Address=*+Transport=HTTPS
    This will return information pertaining to the existing HTTPS listener.
  3. Type: netstat -an | find "5986"
    This will show if your server is currently listening on the WinRM port 5986.
  4. Type: winrm delete winrm/config/listener?Address=*+Transport=HTTPS
    This will delete the broken WinRM HTTS listener.
  5. Re-run the Configure Server button. The configuration script will automatically recreate the WinRM HTTPS listener.

 

Issue 3​

The configuration script has detected an invalid assembly name which it is unable to load, and therefore unable to complete the configuration.

Cause

No definitive cause has been determined. Possibly due to an update or third party program.

Resolution

  1. Open PowerShell in an elevated context.
  2. Type: get-childitem -Path wsman:\localhost\plugin\microsoft.powershell\InitializationParameters
    This retrieves the PowerShell initialization parameters.
  3. The correct output to this command is ParamName = PSVersion and ParamValue = 2.0 or 3.0 depending on the version of PowerShell installed.
  4. If there exists ParamName = assemblyname and ParamName = pssessionconfigurationtypename, these need to be removed.
  5. Type: Remove-Item -Path wsman:\localhost\plugin\microsoft.powershell\InitializationParameters\assemblyname
    This removes the ‘assemblyname’ parameter.
  6. Type: Remove-Item -Path wsman:\localhost\plugin\microsoft.powershell\InitializationParameters\pssessionconfigurationtypename
    This removes the ‘pssessionconfigurationtypename’ parameter.

 

 

Last modified

Tags

Classifications

Public