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) > AppInsight for Exchange: Generate the Zero Config script and manually run it on the target system

AppInsight for Exchange: Generate the Zero Config script and manually run it on the target system

Table of contents
Created by Chris Foley, last modified by MindTouch on Jun 23, 2016

Views: 1,164 Votes: 2 Revisions: 4


This article describes how to manually generate the the Zero Config script, copy it to the target system and then run it. This usually happens when the AppInsight for Exchange Application's Configure Server button fails to copy the script to the target system.


  • SAM v6.1 and later
  • All Microsoft Windows versions


  1. Open a command prompt on the system hosting SAM.
  2. Go to the SAM installation directory.  By default, the location is C:\Program Files (x86)\SolarWinds\Orion\APM\.
  3. Run the following command:
    SolarWinds.APM.RemoteWinRmConfiguratorFull.exe AQEBAQ== AQEBAQ== AQEBAQ== AQEBAQ== AQEBAQ==
  4. Go to C:\ProgramData\SolarWinds\APM\RunWinRMConfigurator\ and open the WinRMandWindowsAuthenitcationEnabler.ps1 using a text file editor such as Notepad.
  5. Initialize the following variables with values:
    • $userToFind: Set the value for this to the username of the account to be used for monitoring.
    • $userDomain: Set the value for this to the domain of the account specified for $userToFind.
    • $targetIP: This value is the IP address being used by the Node the ApInsight for Exchange Application is assigned to.
  6. Copy the script file to the Exchange Server in question and run it in an elevated PowerShell prompt.


Last modified